after reinstall: "VFS: Cannot open root device "LABEL=root"

This forum is for topics dealing with problems with software specifically in the ARMv5 repo.

after reinstall: "VFS: Cannot open root device "LABEL=root"

Postby baafie » Tue Jan 27, 2015 9:33 pm

Hi,

I recently trashed my Arch installation on my GoFlex Net, possibly caused by running a full system update. At any rate, my system stopped sending things to netconsole after the RTC line in dmesg.

So I tried my usual formula for dealing with this situation: I took out my USB stick, removed all files and untarred the ArchLinuxARM-kirkwood-latest.tar.gz tarball from the installation instructions. Now, however, I am greeted with the following on the netconsole:

Code: Select all
[   37.188774] VFS: Cannot open root device "LABEL=rootfs" or unknown-block(0,0): error -6
[   37.196842] Please append a correct "root=" boot option; here are the available partitions:
[   37.205361] 0800       488386584 sda  driver: sd
[   37.210100]   0801       488385560 sda1 000d5dc8-01
[   37.215042] 0810         7816704 sdb  driver: sd
[   37.219769]   0811         7520875 sdb1 000600e9-01
[   37.224712]   0812          294400 sdb2 000600e9-02
[   37.229693] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


Well, at least this is a very informative message. When I attempt to boot again, I notice that there are no messages whatever coming to the kernel netconsole, though the uBoot netconsole still works.

But the question is: what to do about it? I note that the installation instructions no longer mention labeling the root filesystem as 'rootfs', but that is what my GoFlex expects.

Any advice would be appreciated!

Complete netconsole output:
Code: Select all
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.18.1-1-ARCH (nobody@root-armv5-copy) (gcc version 4.9.2 (GCC) ) #1 PREEMPT Tue Dec 23 02:43:32 MST 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Seagate GoFlex Net
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(pogoplug),-(root) root=LABEL=rootfs rootdelay=10 netconsole=@10.10.10.6/eth0,@10.10.10.4/
[   20.944586] cpuidle: using governor menu
[   20.944709] Kirkwood: MV88F6281-A1, TCLK=200000000.
[   20.944729] [Firmware Bug]: Feroceon L2: bootloader left the L2 cache on!
[   20.944736] Feroceon L2: Cache support initialised.
[   20.976289] vgaarb: loaded
[   20.976628] SCSI subsystem initialized
[   37.188774] VFS: Cannot open root device "LABEL=rootfs" or unknown-block(0,0): error -6
[   37.196842] Please append a correct "root=" boot option; here are the available partitions:
[   37.205361] 0800       488386584 sda  driver: sd
[   37.210100]   0801       488385560 sda1 000d5dc8-01
[   37.215042] 0810         7816704 sdb  driver: sd
[   37.219769]   0811         7520875 sdb1 000600e9-01
[   37.224712]   0812          294400 sdb2 000600e9-02
[   37.229693] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   37.238001] CPU: 0 PID: 1 Comm: swapper Not tainted 3.18.1-1-ARCH #1
[   37.244414] [<c000ef88>] (unwind_backtrace) from [<c000c48c>] (show_stack+0x10/0x14)
[   37.252208] [<c000c48c>] (show_stack) from [<c0550dcc>] (panic+0x88/0x1f8)
[   37.259131] [<c0550dcc>] (panic) from [<c07301d0>] (mount_block_root+0x21c/0x2c4)
[   37.266659] [<c07301d0>] (mount_block_root) from [<c073053c>] (prepare_namespace+0x160/0x1c0)
[   37.275230] [<c073053c>] (prepare_namespace) from [<c072fe60>] (kernel_init_freeable+0x1e8/0x230)
[   37.284150] [<c072fe60>] (kernel_init_freeable) from [<c05503c4>] (kernel_init+0x8/0xec)
[   37.292288] [<c05503c4>] (kernel_init) from [<c0009610>] (ret_from_fork+0x14/0x24)
[   37.299898] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   94.728556] random: nonblocking pool is initialized
baafie
 
Posts: 15
Joined: Sun Apr 01, 2012 10:57 am

Re: after reinstall: "VFS: Cannot open root device "LABEL=ro

Postby WarheadsSE » Tue Jan 27, 2015 11:41 pm

You need an initramfs to use a LABEL= for root=
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6792
Joined: Mon Oct 18, 2010 2:12 pm

Re: after reinstall: "VFS: Cannot open root device "LABEL=ro

Postby baafie » Wed Jan 28, 2015 12:30 am

Thanks WarheadsSE.

I have instructions for generating an initramfs/uInitrd, but these seem to be designed for use while actually running ALARM. Can I generate an initramfs from my desktop PC? (If so, how?)
baafie
 
Posts: 15
Joined: Sun Apr 01, 2012 10:57 am

Re: after reinstall: "VFS: Cannot open root device "LABEL=ro

Postby moonman » Wed Jan 28, 2015 2:28 am

You can't
Try this one i created a while back http://goo.gl/GFbtn
If it boots then you can create an updated one.
Pogoplug V4 | GoFlex Home | Raspberry Pi B 512 | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | |[armv5] How to install my.pogoplug.com service | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3111
Joined: Sat Jan 15, 2011 3:36 am
Location: Calgary, Canada

Re: after reinstall: "VFS: Cannot open root device "LABEL=ro

Postby baafie » Wed Jan 28, 2015 10:24 pm

Thanks!

Now I am a step further, kernel log follows:

Code: Select all
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.18.1-1-ARCH (nobody@root-armv5-copy) (gcc version 4.9.2 (GCC) ) #1 PREEMPT Tue Dec 23 02:43:32 MST 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Seagate GoFlex Net
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(pogoplug),-(root) root=LABEL=rootfs rootdelay=10 rootfstype=auto netconsole=@10.10.10.6/eth0,@10.10.10.4/
[    7.192698] Kirkwood: MV88F6281-A1, TCLK=200000000.
[    7.192717] [Firmware Bug]: Feroceon L2: bootloader left the L2 cache on!
[    7.192724] Feroceon L2: Cache support initialised.
[    7.224263] vgaarb: loaded
[    7.224603] SCSI subsystem initialized
[   14.724079] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[   14.742717] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   15.330996] NET: Registered protocol family 10
[   15.336847] systemd[1]: Inserted module 'ipv6'
[   15.349424] random: systemd urandom read with 77 bits of entropy available
[   15.374363] systemd[1]: systemd 218 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
[   15.392863] systemd[1]: Detected architecture 'arm'.
[   15.417925] systemd[1]: Set hostname to <alarm>.
[   15.975107] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[   15.998883] systemd[1]: Starting Encrypted Volumes.
[   16.026727] systemd[1]: Reached target Encrypted Volumes.
[   16.032454] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[   16.066700] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[   16.076430] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[   16.084877] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[   16.093096] systemd[1]: Starting Root Slice.
[   16.116699] systemd[1]: Created slice Root Slice.
[   16.121673] systemd[1]: Starting System Slice.
[   16.146701] systemd[1]: Created slice System Slice.
[   16.151852] systemd[1]: Starting system-getty.slice.
[   16.176696] systemd[1]: Created slice system-getty.slice.
[   16.182379] systemd[1]: Starting udev Control Socket.
[   16.206693] systemd[1]: Listening on udev Control Socket.
[   16.212312] systemd[1]: Starting User and Session Slice.
[   16.236698] systemd[1]: Created slice User and Session Slice.
[   16.242665] systemd[1]: Starting Slices.
[   16.266680] systemd[1]: Reached target Slices.
[   16.271330] systemd[1]: Starting LVM2 metadata daemon socket.
[   16.296689] systemd[1]: Listening on LVM2 metadata daemon socket.
[   16.302996] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[   16.326691] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[   16.333890] systemd[1]: Starting Journal Socket (/dev/log).
[   16.356690] systemd[1]: Listening on Journal Socket (/dev/log).
[   16.362843] systemd[1]: Starting Remote File Systems.
[   16.386677] systemd[1]: Reached target Remote File Systems.
[   16.392477] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[   16.400580] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[   16.408417] systemd[1]: Starting Paths.
[   16.426681] systemd[1]: Reached target Paths.
[   16.431269] systemd[1]: Starting udev Kernel Socket.
[   16.456686] systemd[1]: Listening on udev Kernel Socket.
[   16.462223] systemd[1]: Expecting device dev-ttyS0.device...
[   16.486774] systemd[1]: Starting Journal Socket.
[   16.506687] systemd[1]: Listening on Journal Socket.
[   16.511956] systemd[1]: Starting Remount Root and Kernel File Systems...
[   16.540573] systemd[1]: Mounting POSIX Message Queue File System...
[   16.570826] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[   16.619076] systemd[1]: Mounting Temporary Directory...
[   16.653552] systemd[1]: Starting Setup Virtual Console...
[   16.690991] systemd[1]: Mounting Debug File System...
[   16.719583] systemd[1]: Started Set Up Additional Binary Formats.
[   16.735537] systemd[1]: Started Load Kernel Modules.
[   16.745017] systemd[1]: Mounted Configuration File System.
[   16.750890] systemd[1]: Starting Apply Kernel Variables...
[   16.780682] systemd[1]: Mounting FUSE Control File System...
[   16.811052] systemd[1]: Mounted Huge Pages File System.
[   16.825917] systemd[1]: Starting system-serial\x2dgetty.slice.
[   16.852141] systemd[1]: Created slice system-serial\x2dgetty.slice.
[   16.858789] systemd[1]: Starting Swap.
[   16.876695] systemd[1]: Reached target Swap.
[   16.881189] systemd[1]: Starting Delayed Shutdown Socket.
[   16.906690] systemd[1]: Listening on Delayed Shutdown Socket.
[   16.912675] systemd[1]: Starting Device-mapper event daemon FIFOs.
[   16.936684] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[   16.943468] systemd[1]: Starting udev Coldplug all Devices...
[   16.980987] systemd[1]: Listening on Journal Audit Socket.
[   16.987565] systemd[1]: Starting Journal Service...
[   17.056897] systemd[1]: Mounted Debug File System.
[   17.078165] systemd[1]: Mounted FUSE Control File System.
[   17.107810] systemd[1]: Mounted POSIX Message Queue File System.
[   17.136765] systemd[1]: Mounted Temporary Directory.
[   17.176716] systemd[1]: Started Remount Root and Kernel File Systems.
[   17.196757] systemd[1]: Started Create list of required static device nodes for the current kernel.
[   17.236736] systemd[1]: Started Setup Virtual Console.
[   17.256765] systemd[1]: Started Apply Kernel Variables.
[   17.466721] systemd[1]: Started udev Coldplug all Devices.
[   17.546794] systemd[1]: Started Journal Service.
[   17.872196] random: nonblocking pool is initialized
[   18.110160] systemd-journald[132]: Received request to flush runtime journal from PID 1


Sadly after the last message the system seems to have halted. And again, when I power cycle, nothing is sent to the kernel netconsole. :?
baafie
 
Posts: 15
Joined: Sun Apr 01, 2012 10:57 am


Return to ARMv5

Who is online

Users browsing this forum: No registered users and 1 guest