Kernel Panic - not syncing VFS

[RodWorks]

Had the first issue about a month ago, when I randomly found Unraid crashed, upon restart I got this error.

 

I recreated my USB drive and it booted up normally and worked fine until yesterday.  Now, I'm getting the crashes and errors more often, but was able to get unraid to boot in Web GUI mode.  I'm also seeing this error on boot sometimes.

 

 

I removed half of my 64 GB of ram to try and isolate a bad ram module.  However, I'm still seeing the errors booting with either half of the ram removed.

 

Also, on the last boot, the system booted up running on only one processor and half the ram.

 

So, any ideas on where to start troubleshooting this issue?

unraid-diagnostics-20201006-2253.zip

Edited October 7, 2020 by RodWorks

[RodWorks]

Update: 

 

System booted and ran perfect with each CPU running solo in socket 0.  After that I put a CPU back in socket 1 (reversed the order now) and the system is running fine again.  I do still have 32 gb (4 x 8gb) pulled from the system.  Hoping one is the problem.

 

Still lost. 

unraid-diagnostics-20201007-1005.zip

[versy]

Happens this all the time? On my system I get these issues once or maximum twice a month.

Where you able to fix it with the memory?

[Source011]

Hi everyone, first post here.

 

I just wanted to give you my 5 cents on this topic and how I partially* solved it (running a Mac Pro 5,1 from 2012).

I upgraded to 6.10 today and after the reboot I was stuck with the same error message
 

VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
Please append a correct "root=" boot option;

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

 

I tried the solutions mentioned in other posts like adding /root/sda, only copy the bz* files and what not, nothing worked. Reformated the USB-stick and ran diskpart to clean it and all that, still no luck. I tried the same with 6.9.2 (what I was running before the update) and still got the same error message. I did all this from Windows and figured I might as well could try the USB creator tool from my MacBook, and lo and behold.. it worked..

 

So what I did was the following:

1. Downloaded and ran the Unraid USB Creator tool
2. Chose "Stable" branch and version "6.9.2"
3. Clicked "Customize" and checked the "Allow UEFI Boot" and entered my IP and all that.
4. Chose my USB-Stick and hit "Write"
5. After the tool was finished I copied the config folder from my backup zip file (the one created in Unraid) to the USB-stick and replaced all files
6. Started the terminal and ran the script "make_bootable_mac" in the root directory of the USB-stick

It booted up just fine and everything worked as it used to..

 

Some final words; Yes, I know, not everyone got a Mac laying around (I don't blame you) but something seems different between the tools on the different platforms.

 

*I only managed to get 6.9.2 running, but I will try the same method tomorrow with 6.10.2 and hope for better results.

Edited June 9, 2022 by Source011
spelling - english isn't my first language :(