cmacsound Posted November 24, 2020 Share Posted November 24, 2020 Hello! I'm stuck on a panic at boot. Server was 100+ days running great! Then I powered it down via web interface, an older v6 (can't remember exactly). Day later, upon boot I'm getting the following panic: VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 ... Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ... I attempted to remedy by re-creating usb with latest OS and restored original config folder, got the idea from here, but same panic persists. What else can I try? Thank you! c ps) connected PS2 keyboard is also not responding, should I be concerned this is a mobo issue?? Quote Link to comment
JorgeB Posted November 24, 2020 Share Posted November 24, 2020 See if a different flash drive boots. 1 Quote Link to comment
cmacsound Posted November 24, 2020 Author Share Posted November 24, 2020 Thank you JorgeB! I can confirm that a reformatted USB with the default config boots up just fine, happy to report. Access to the GUI via the web interface works too. How can I best troubleshoot or debug my config folder so that I can restore my settings and shares? Many thanks again Quote Link to comment
JorgeB Posted November 24, 2020 Share Posted November 24, 2020 Might not be a config issue, copy your config to the new flash drive, array won't start because of the key but you can still see if it boots. 1 Quote Link to comment
cmacsound Posted November 24, 2020 Author Share Posted November 24, 2020 Wow that did it! I'm quite surprised because I thought I had tried that already, and yet the kernel panic persisted... Any idea what could have prompted that? The array booted up just fine since I already had a Pro key. I now have an updated Unraid OS and all my shares and settings are back! Very glad to have a backup config in a safe place. Thank you for the help!! Quote Link to comment
JorgeB Posted November 24, 2020 Share Posted November 24, 2020 3 minutes ago, cmacsound said: Any idea what could have prompted that? That issue is usually caused by the flash drive, but not always clear why it happens, wiping the flash drive can sometimes fix it but not always, kind of an elusive problem, a different flash drive can also help, glad it's solved. 1 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.