to make life little easier on housemates i'm having go @ dual-booting raspbian lite , openelec on same card can switch retropie , openelec.
followed instructions @ https://github.com/retropie/retropie-se ... oobs-image , installed both oss. note created custom image of raspbian lite , not full raspbian or retropie. there's long audio related story behind this
upon booting raspbian pushed in "emergency mode" after noticing startup failures @ boot. running 'journalctl -xb' provides lot of output usual relevant lines appear be: first error , things tend go downhill there. , worse still along many others.
error of course me unsure how determine cause. instructions note partition sizes , files sizes of partitions once you've installed , backed up. it's worth noting performed on mac ext2-fuse installed.
, these sizes translated partitions.json following i'm not sure i've gone wrong here pointers gratefully received.
followed instructions @ https://github.com/retropie/retropie-se ... oobs-image , installed both oss. note created custom image of raspbian lite , not full raspbian or retropie. there's long audio related story behind this
upon booting raspbian pushed in "emergency mode" after noticing startup failures @ boot. running 'journalctl -xb' provides lot of output usual relevant lines appear be:
code: select all
dev-mqueue.mount mount process exited, code=exited, status=1 failed mount posix message queue file system unit dev-mqueue.mount entered failed state
code: select all
sys-kernel-debug.mount mount process exited, code=exited, status=1
code: select all
/bin/mount proc execite exit status 1 systemd-remount-fs.service: main process exited, code=exited, status=1/failure failed start remount root , kernel file system
error of course me unsure how determine cause. instructions note partition sizes , files sizes of partitions once you've installed , backed up. it's worth noting performed on mac ext2-fuse installed.
code: select all
/dev/disk2 (internal, physical): #: type name size identifier 0: fdisk_partition_scheme *31.9 gb disk2 1: windows_fat_32 boot 62.9 mb disk2s1 2: linux 1.3 gb disk2s2 $ ls -l *.tar -rw-r--r-- 1 root 499 20414976 may 8 18:58 boot.tar -rw-r--r-- 1 root 499 705877504 may 8 18:57 jessie-lite.tar
code: select all
{ "partitions": [ { "label": "boot", "filesystem_type": "fat", "partition_size_nominal": 63, "want_maximised": false, "uncompressed_tarball_size": 20 }, { "label": "jessielite", "filesystem_type": "ext4", "partition_size_nominal": 1300, "want_maximised": true, "mkfs_options": "-o ^huge_file", "uncompressed_tarball_size": 705 } ] }
what type of card using? i'm asking because i'm investigating problem appears fake card - correct capacity potentially dodgy controller/flash combo.
raspberrypi
Comments
Post a Comment