Situation
Server ran for a long time without issues. Upgraded Unraid OS to 6.10.3. Rebooted but never came back online again.
Booting the server gets stuck at Kernel Panic.
/dev/root: Can't open blockdev VCS: Cannot open root device "(null)" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing VFS: Unable to mount root rs on unknown-block(0,0) CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.15.46-Unraid #1 Hardware name: Apple Inc. Macmini5,3/Mac-ZUYXYZDF8234, BIOS MM51.88Z.0080.B00.1804091930 04/09/2018 Call Trace: <TASK> dump_stack_lvl+0x46/0x5a panic+0xf6/0x2a1 mount_block_root+0x1de/0x1ed ? rest_init+0xbb/0xbb prepare_namespace+0x136/0x165 ? rest_init+0xbb/0xbb kernel_init+0x16/0x11 ret_from_fork+0x22/0x30 </TASK> Kernel Offset: disabled --[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--
What I tried
I tried several things to find a solution, but without success until now. What I've done so far:
- I've created a new Unraid USB stick using a new USB stick. Same issue.
- Created new Unraid USB stick using 6.10.2. Same issue.
- Created new Unraid USB stick using 6.10.0. Same issue.
- Created new Unraid USB stick using 6.9.2. Same issue.
- Created new Unraid USB stick using 6.10.3 and copied /bz* files to the errornous USB stick. Same issue.
- Added "root=" boot option in syslinux.cfg;
-- root=/dev/sda -> Same issue.
-- root=/dev/sda1 -> Same issue.
-- Tried to add root= boot option at the end of the lines in syslinux.cfg and also at the beginning of the lines (according to syslinux docs). Still same issue.
-- Tried another USB port. Same issue.
So:
- USB Stick died? Guess not. New USB stick also won't boot.
- Server hardware/software died? Nothing updated or upgraded. Only Unraid OS on USB. Server runs. It's Unraid that won't boot.
- Wrong Unraid OS version? I've tried to downgrade to 6.9.2 without success. Also 6.10.0-6.20.3 without success.
- Current kernel can't deal with USB stick (location?). I tried adding root= boot options without success.
Well, I guess it's the kernel (config) what bugs here, but I don't know how I'm able to - at least - get my server up and running again.
Someone who can help (with ideas)?
Recommended Comments
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.