current sdcard installs try to mount nonexistatnt sdcard
by justwantin from LinuxQuestions.org on (#5DV74)
I usually update a spare bananpro to current. Sometimes install is on an sdcard sometimes to an sdd drive. I have not been able to install current onto an sdcard and be able to correctly reboot since current around 07/12/20 and before that current around 20/09/20.
Attempts at an sdcard install with current post 07/01/21 will install OK but on reboot the kernel tries to mount mmcblk1p3 instead of mmcblk0p3.Code:<snipped>
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead.
You can try to fix it. Type 'exit' when things are done.
/bin/sh: can't access tty; job control turned off
/ # [ 32.754759] vcc3v0: disabling
[ 32.757795] vcc5v0: disabling
/ # fdisk -l
Disk /dev/sda: 7381 MB, 7739768832 bytes, 15116736 sectors
19380 cylinders, 39 heads, 20 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sda1 0,33,3 1020,38,20 2048 15116735 15114688 7380M 83 Linux
Disk /dev/mmcblk1: 14 GB, 15523119104 bytes, 30318592 sectors
473728 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk1p1 * 0,33,3 27,24,30 2048 411647 409600 200M 83 Linux
/dev/mmcblk1p2 27,24,31 96,31,62 411648 1460223 1048576 512M 82 Linux
swap
/dev/mmcblk1p3 96,32,1 1023,244,62 1460224 30318591 28858368 13.7G 83 Linux
/ #I installed current 04/02/21 today onto an sdd drive with no problem but later using the same source usb stick installed onto a sdcard and ended up with the kernel trying to boot from mmcblk1 instead of mmcblk0 (see above). I'm at a loss to figure this out. Can anyone give me a heads up?
Attempts at an sdcard install with current post 07/01/21 will install OK but on reboot the kernel tries to mount mmcblk1p3 instead of mmcblk0p3.Code:<snipped>
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead.
You can try to fix it. Type 'exit' when things are done.
/bin/sh: can't access tty; job control turned off
/ # [ 32.754759] vcc3v0: disabling
[ 32.757795] vcc5v0: disabling
/ # fdisk -l
Disk /dev/sda: 7381 MB, 7739768832 bytes, 15116736 sectors
19380 cylinders, 39 heads, 20 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sda1 0,33,3 1020,38,20 2048 15116735 15114688 7380M 83 Linux
Disk /dev/mmcblk1: 14 GB, 15523119104 bytes, 30318592 sectors
473728 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk1p1 * 0,33,3 27,24,30 2048 411647 409600 200M 83 Linux
/dev/mmcblk1p2 27,24,31 96,31,62 411648 1460223 1048576 512M 82 Linux
swap
/dev/mmcblk1p3 96,32,1 1023,244,62 1460224 30318591 28858368 13.7G 83 Linux
/ #I installed current 04/02/21 today onto an sdd drive with no problem but later using the same source usb stick installed onto a sdcard and ended up with the kernel trying to boot from mmcblk1 instead of mmcblk0 (see above). I'm at a loss to figure this out. Can anyone give me a heads up?