Sign in

IS MY DEBIAN INSTALL TOAST OR CAN I STILL SAVE THIS?

bootkernellinux8 replies 路 131 views 路 started
Reply
  1. Vera V.
    @signalgremlin-1zo

    so annoyed rn home lab drama 馃槶 debian on my old Dell tower 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 teh worst possible time, or the update?

    I havent touched the hardware in months. No new disks, no new RAM, nothing. Its just the update and a reboot. Id like to fix this properly instead of reinstalling, because theres quite a bit of config on this box. what am i doing wrong??

    3
  2. Sami Mendes
    @quietranger

    uhh what's the exact last line of teh panic?? :/ Unable to mount root fs, not syncing, a module name?

    5 4 helpful
  3. Vera V.
    @signalgremlin-1zo
    in reply to @quietranger

    Last line is Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0). hope thats enough info 馃槄

    0 1 helpful
  4. Jonas Adler
    @jonas.adler
    in reply to @signalgremlin-1zo

    ok so first, boot teh previous kernel. In GRUB pick 'Advanced options' (Debian/Ubuntu) or teh older entry in the list (RHEL family). If the old kernel boots, your data is fine and the problem is the new kernel or its initramfs.

    32 2 helpful
  5. Sami Mendes
    @quietranger

    if teh panic mentions a module or driver, third-party modules (DKMS, out-of-tree storage or GPU drivres) may not have been rebuilt for the new kernel. dkms status shows whats built for which krenel.

    0 2 helpful
  8. Lars Wolfe
    @larsw244
    in reply to @aiden_quartz

    lol same thing happened to me to rule out hardware, check whether the old kernel is stbale over time and run smartctl -a on the disks. A failing disk tends to show I/O errors in dmesg well before a panic. worked for me anyway 馃し

    0 10 helpful
  9. Sami Mendes
    @quietranger

    @signalgremlin-1zo thank u this worked!!. @quietranger did u ever fix it??

    33 1 helpful

Reply to this topic

Sign in or create an account to reply.