boot error

[johndoe297]

so one day my server just stopped working, and i'm not sure what happened, i only had remote access at the time. now i am back with physical access, and when i boot up this error is all i get. i don't know what happened or what is going on.

[ 34.172239] ata3.00: Read log 0x00 page 0x00 failed, Emask 0x4
[ 34.172253] ata3.00: failed to set xfermode (err_mask=0x40)
[ 49.788239] ata3.00: Read log 0x00 page 0x00 failed, Emask 0x4
[ 49.788251] ata3.00: failed to set xfermode (err_mask=0x40)
[ 67.196241] ata3.00: Read log 0x00 page 0x00 failed, Emask 0x4
[ 67.196257] ata3.00: failed to set xfermode (err_mask=0x40)
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mapper/pve-root does not exist. Dropping to a shell!

BusyBox v1.35.0 (Debian 1:1.35.0-4+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) _

 

[Folke]

Hi,
have you done anything special before this error occurred, like updating your system?
If not, this looks like a prime candidate for hardware failure.
To verify this, you could try booting from an usb stick and check the S.M.A.R.T. values of the disk[0] and try to mount it.

[0] https://www.fosslinux.com/111631/us...-to-check-the-health-of-your-hdds-or-ssds.htm

 

[johndoe297]

i didn't do anything. i was wondering if there was some kind of update that screwed the system. i am attempting to boot from an ubuntu usb now.

 

[Folke]

Proxmox only updates if prompted, unless something like unattended-updates would be explicitly installed and configured.
If I understand you correctly, the system became unresponsive on its own and wasn't rebooted manually, which nudges me more into the direction of hardware failure, since an issue that prevents the system from even mounting the root partition had to be in the kernel/initrd which only gets loaded on boot, not after an update. This is also the reason why some OS'ses insist on rebooting after an update, to load an updated version of these components

Unfortunately I'm gone for today, but I'll check in again tomorrow

 

[johndoe297]

so it does seem to be that the boot drive failed. i suppose my question now is what is the easiest way to recover the system? fortunately nothing on that particular drive was critical, it was just the proxmox boot, and the VM/cont drive. all my critical data, family photos etc were stored on a secondary drive that seems to still be functioning, that was essentially a nfs share i created in a truenas VM on the main drive. i know that may be a bit outside of proxmox forums but if anyone can offer advice, i'd appreciate it. i guess my plan is to buy a new boot drive, rebuild the proxmox server, and see if i can access the secondary drive in a new truenas VM.