trurl Posted January 10, 2019 Share Posted January 10, 2019 6 minutes ago, rymalco said: not running dockers You have a docker image mounted as shown in the next-to-last line of those "cat /proc/mounts" results. Might as well disable docker, delete the image and reclaim its storage. Quote Link to comment
rymalco Posted January 11, 2019 Share Posted January 11, 2019 11 hours ago, trurl said: You have a docker image mounted as shown in the next-to-last line of those "cat /proc/mounts" results. Might as well disable docker, delete the image and reclaim its storage. Thanks for tip! Quote Link to comment
itimpi Posted January 11, 2019 Share Posted January 11, 2019 It looks as if VMs might also be enabled since libvirt is being mounted. If so disabling that might also be a good idea. Quote Link to comment
Squid Posted January 20, 2019 Share Posted January 20, 2019 (edited) On 1/9/2019 at 11:27 PM, limetech said: If the issue gets reported more often we'll have to dive into kernel source to see what's going on. Here's another one (Also added @johnnie.black's solution to the FAQ) Edited January 20, 2019 by Squid Quote Link to comment
scott47 Posted February 14, 2019 Share Posted February 14, 2019 On 1/9/2019 at 4:28 PM, johnnie.black said: Try this, it worked for me for an identical error, on the flash drive edit syslinux/syslinux.cfg and add root=sda to the boot option you're using after initrd=/bzroot, e.g.: label Unraid OS menu default kernel /bzimage append initrd=/bzroot root=sda Johnnie, thank you for posting this! My situation is a bit different as I'm running Unraid under ESXi, which isn't supported, but has done exactly what I need it to do for years. In my case, everything works perfectly using ESXi 6.0 and ESXi 6.5 but as soon as I tried upgrading to ESXi 6.7 I kept getting the "VFS: cannot open root devise "(null)" or unknown-block(0,0): error -6" message. I tried everything I could think of and had basically decided that ESXi 6.5 was the highest I could use while keeping Unraid. I added the " root=sda" on each of the append initrd lines, rebooted the VM, and it booted up perfectly. Honestly, I have no idea what this does or why it would make any difference at all, but it fixed booting an Unraid 6.6.6 VM in ESXi 6.7 Thanks! Quote Link to comment
prostuff1 Posted July 13, 2019 Share Posted July 13, 2019 I just ran into this issue as well. I have a very old system built for a customer from nearly 10 years ago now. It is only ever used as a file server so there was no real reason to touch it. Well, parts finally started to fail (not the motherboard or processor but the drive cages). The customer was not interested in upgrading anything except for the unRAID OS version. I went to update it and of course nothing booted after 6.2.4. As soon as I put 6.3.5 on the USB drive and attempt to boot I would get the above mentioned error. I updated the BIOS on the board but that solved nothing. So some google-fu later I find this thread and the suggestion to add "root=sda" to the syslinux.cfg. That seems to have worked on the OLD Biostar A760G M2+ board with a Phenom II X4 in it. Not sure what in the kernel between 6.2.4 and 6.3.5 made it stop booting but the "root=sda" trick works fine on this old build. Quote Link to comment
rustmouth Posted April 9, 2020 Share Posted April 9, 2020 I'm also getting this error on every upgrade and sometimes just on reboots after 6.6 I'm going to try this and hoping it will do the trick. Original post requesting help. Quote Link to comment
timstephens24 Posted August 22, 2021 Share Posted August 22, 2021 This just happened to me after a reboot on 6.10.0-rc1. Easy to add root=sda in the syslinux.cfg, but saw there was a post on it so just wanted to bring it up as something that's still occurring (though it seems rare). Quote Link to comment
trurl Posted August 22, 2021 Share Posted August 22, 2021 6 hours ago, timstephens24 said: This just happened to me after a reboot on 6.10.0-rc1. Why post about it in this old thread for a very old version? Quote Link to comment
timstephens24 Posted August 25, 2021 Share Posted August 25, 2021 Because it’s related? Quote Link to comment
rhetorical Posted June 14, 2022 Share Posted June 14, 2022 On 8/22/2021 at 9:59 AM, timstephens24 said: This just happened to me after a reboot on 6.10.0-rc1. Easy to add root=sda in the syslinux.cfg, but saw there was a post on it so just wanted to bring it up as something that's still occurring (though it seems rare). This also happened to me updating to 6.10.2 (I reset back to 6.9) and then again when coming to 6.10.3. Quote Link to comment
trurl Posted June 14, 2022 Share Posted June 14, 2022 On 8/22/2021 at 5:02 PM, trurl said: Why post about it in this old thread for a very old version? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.