one update, one reboot, one very dead cloud instance

bootkernellinux4 replies · 207 views · started
  1. not gonna lie this is driving me nuts home lab drama. Debian on my cloud instance got a kernel update and now it panics during boot:

    2.481214 VFS: Cannot open root device "sda2" or unknown-block(0,0): error -6

    [    2.481214] VFS: Cannot open root device "sda2" or unknown-block(0,0): error -6
    [    2.481362] Please append a correct "root=" boot option; here are the available partitions:
    [    2.481513] 0b00         1048575 sr0
    [    2.481601]  driver: sr
    [    2.481702] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
    [    2.481843] CPU: 3 PID: 1 Comm: swapper/0 Not tainted
    [    2.481957] Call Trace:
    [    2.482010]  <TASK>
    [    2.482078]  dump_stack_lvl+0x48/0x70
    [    2.482155]  panic+0x118/0x300
    [    2.482231]  mount_block_root+0x1d3/0x1e0
    [    2.482309]  prepare_namespace+0x136/0x165
    [    2.482398] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs ]---
    

    It was running for months without a hiccup. Is this hardware failing at the worst possible time, or the update?

    i haven't touched the hardware in months. no new disks, no new RAM, nothing. it's just the update and a reboot. i'd like to fix this properly instead of reinstalling, cuz there's quite a bit of config on this box. what am i doing wrong??

    1
  2. wait what's teh exact last line of teh panic? Unable to mount root fs, not syncing, a module name?

    6 0 helpful
  3. last line is Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0).

    1 3 helpful
  4. oof VFS: Unable to mount root fs on unknown-block almost always means the initramfs for the new kernel is missing or incomplete (often because /boot was full during teh update). From the old kernel, rebuild it: sudo update-initramfs -u -k all on Debian/Ubuntu or sudo dracut -f --regenerate-all on RHEL/Fedora.

    22 11 helpful
  5. To rule out hardware, check whether teh old kernel is stable over time and run smartctl -a on the disks. A failing disk tends to show I/O errors in dmesg well before a panic.

    2 2 helpful

Reply to this topic

Sign in or create an account to reply.