Hello all together,
I've already asked this question in the German forum, but I think I'll reach more people if I post this again in English.
A few days ago I wanted to connect to my Proxmox server as usual and found that a connection could no longer be established. After I connected the "fallback monitor" I saw the error "Failed to start sysdemd-fsck@dev-disk-by\hierlaufendeNumber /dev/disk/by-uuid" and
"Dependency failed for mnt-storage2.mount - mnt/storage2." and "Dependency failed for local-fs.target - Local File Systems.".
I then ran a repair scan with "fsck /dev/sda" on which the mnt/storage2 file system is located. After almost 2 hours the scan was finished and I restarted the server, which then ran again. I'm a bit worried though because I have no idea how this could have happened. If there had been a hard drive crash, my Raid drive would in theory show me this, it has its own check for this. Does anyone have an idea what else I could check? Unfortunately, the server has also been extremely slow since the action and responds very slowly, at least via SSH, but not on the virtual servers, but it does that only when I access the Proxmox CLI.
I attaching the log. This is the journal error log that was generated using "journalctl -p 3 -x". In the log is something about the smart values of the SSD, which are unremarkable apart from the wearout. There are no bad sectors or anything else. Unfortunately I can't see any smart values from the disks in the Raid Controller, like you can see in the attached SMART report.
About the server: the Proxmox VE runs on an Intel Nuc7i5BNK from 2018. An external WD Elements drive is connected to this as a backup solution. Data is backed up on a Fantec Qb-35us3r case with Raid 5 and 4 Seagate Barracuda 2tb disks. I am extremely grateful for any help.
I've already asked this question in the German forum, but I think I'll reach more people if I post this again in English.
A few days ago I wanted to connect to my Proxmox server as usual and found that a connection could no longer be established. After I connected the "fallback monitor" I saw the error "Failed to start sysdemd-fsck@dev-disk-by\hierlaufendeNumber /dev/disk/by-uuid" and
"Dependency failed for mnt-storage2.mount - mnt/storage2." and "Dependency failed for local-fs.target - Local File Systems.".
I then ran a repair scan with "fsck /dev/sda" on which the mnt/storage2 file system is located. After almost 2 hours the scan was finished and I restarted the server, which then ran again. I'm a bit worried though because I have no idea how this could have happened. If there had been a hard drive crash, my Raid drive would in theory show me this, it has its own check for this. Does anyone have an idea what else I could check? Unfortunately, the server has also been extremely slow since the action and responds very slowly, at least via SSH, but not on the virtual servers, but it does that only when I access the Proxmox CLI.
I attaching the log. This is the journal error log that was generated using "journalctl -p 3 -x". In the log is something about the smart values of the SSD, which are unremarkable apart from the wearout. There are no bad sectors or anything else. Unfortunately I can't see any smart values from the disks in the Raid Controller, like you can see in the attached SMART report.
About the server: the Proxmox VE runs on an Intel Nuc7i5BNK from 2018. An external WD Elements drive is connected to this as a backup solution. Data is backed up on a Fantec Qb-35us3r case with Raid 5 and 4 Seagate Barracuda 2tb disks. I am extremely grateful for any help.
Last edited: