Server Gone After Reboot

[matthew]

2nd Time this happened. First time I did apt-get update then apt-get upgrade and after reboot server disappeared. Turns out I needed dist-upgrade to upgrade ZFS drivers or something to that nature. That was couple months ago. Now I did apt-get update followed by apt-get dist-update and rebooted. Have not heard from the server since. Its a supermicro server in data center over 100 miles away. Think I will just wait tell I have a chance to go down there because remote hands too look at it were expensive last time.

Any ideas what would have went wrong? This was a fresh install with nothing on it yet. Although I have a license I was using the free repositories since I have had to reinstall it a few times now and did not want to ask for a reissue of key until I had everything configured like I wanted.

 

[matthew]

Error Message:

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

 

[MikeP]

I just did an upgrade from 4.0 to 4.1 on no-subscription (haven't bought one yet, evaluating Proxmox for home/school), and I have no templates.

https://forum.proxmox.com/threads/no-container-templates-on-4-1.26036/

 

[matthew]

This is from screen shot from crash after reboot. Any idea what problem is?

wn-block(0,0)
[ 1.497372] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.2.8-1-pve #1
[ 1.497445] Hardware name: Supermicro X10SLH-F/X10SLM+-F/X10SLH-F/X10SLM+-F,
BIOS 3.0 04/24/2015
[ 1.497520] 0000000000000000 00000000a4f2a0fe ffff8807fbf0fdb8 ffffffff81802
a68
[ 1.497800] 0000000000000000 ffffffff81c8edb0 ffff8807fbf0fe38 ffffffff81800
3bd
[ 1.498080] 6630313000000010 ffff8807fbf0fe48 ffff8807fbf0fde8 00000000a4f2a
0fe
[ 1.498313] Call Trace:
[ 1.498364] [<ffffffff81802a68>] dump_stack+0x45/0x57
[ 1.498421] [<ffffffff818003bd>] panic+0xd0/0x20d
[ 1.498476] [<ffffffff81f6656d>] mount_block_root+0x209/0x2a5
[ 1.498532] [<ffffffff81f667b3>] mount_root+0x68/0x6c
[ 1.498587] [<ffffffff81f66924>] prepare_namespace+0x16d/0x1a6
[ 1.498645] [<ffffffff81f66271>] kernel_init_freeable+0x227/0x250
[ 1.498701] [<ffffffff817f6f50>] ? rest_init+0x80/0x80
[ 1.498754] [<ffffffff817f6f5e>] kernel_init+0xe/0xe0
[ 1.498810] [<ffffffff81809e5f>] ret_from_fork+0x3f/0x70
[ 1.498865] [<ffffffff817f6f50>] ? rest_init+0x80/0x80
[ 1.498957] Kernel Offset: disabled
[ 1.564234] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs
on unknown-block(0,0)

 

[matthew]

Went down and reinstalled. Fresh download of Proxmox ISO off official website today. Selected ZFS Raid1 on (3) 4TB sata drives. After install server booted up fine. Logged in remotely with ssh and https. Bought and installed a license first. Did apt-get update followed by apt-get distupgrade. Took a while to update. Rebooted. No server. Frustrating to say the least. Any ideas? Its a long drive to go back but I bet its same error on screen.

It did exact same thing last time. Its Supermicro motherboard, case, etc.

 

[XueSheng]

I don't know why you have these issues, but if you are using a supermicro server board, you should be able to use IPMI to do further investigation and reinstall without having to drive 100 miles. I'm using the X10SLH-F by the way.

 

[matthew]

I wonder if it has something to do with using 3 drives instead of 2 in a RAID1 array? I have another server sitting next too it running 2 drives in ZFS RAID1 and it has not had this issue.

 

[Raymond Burns]

I have the same issue.
3 x (250GB) drives in ZFS RAID-1.
Using a Supermicro X8DTLF with Xeon 5520

 

[matthew]

The one I did 2 x (4TB) in ZFS-RAID-1 did not do it. 3X seems too.

 

[matthew]

Has this been resolved yet or is it just not safe to do 3 drives in ZFS RAID 1 for some reason?

 

[fabian]

3 disk mirror should work just fine, I suspect some other issue since both of you run super micro boards..