Hello,
yesterday I had to power down a PVE server due to network maintenance. When I powered up again after a few hours, PVE booted into Emergency Mode only.
The problem was that a storage mount (LVM ThinPool on an individual SSD) timed out. I commented out the line in fstab and PVE rebooted into normal mode.
When I now mount the volume manually from the console, it mounts fine and afterwards is perfectly accessible in the PVE GUI.
I believe this is the problem in journal:
What can this be? Why could this volume not be mounted yesterday after the service outage, when it could be mounted on restarts before and can be mounted manually today?
Is there some kind of file system check that could have been going on, that had to be completed once before it could be mounted?
Or do I have to write this off as an arbitrary hardware fluke?
Regards
yesterday I had to power down a PVE server due to network maintenance. When I powered up again after a few hours, PVE booted into Emergency Mode only.
The problem was that a storage mount (LVM ThinPool on an individual SSD) timed out. I commented out the line in fstab and PVE rebooted into normal mode.
When I now mount the volume manually from the console, it mounts fine and afterwards is perfectly accessible in the PVE GUI.
I believe this is the problem in journal:
Code:
Timed out waiting for device /dev/ssddata/ssddata_ltp.
dev-ssddata-ssddata_ltp.device: Job dev-ssddata-ssddata_ltp.device/start timed out.
Dependency failed for /mnt/ssddata_ltp.
Dependency failed for Local File Systems.
local-fs.target: Job local-fs.target/start failed with result 'dependency'.
local-fs.target: Triggering OnFailure= dependencies.
mnt-ssddata_ltp.mount: Job mnt-ssddata_ltp.mount/start failed with result 'dependency'.
dev-ssddata-ssddata_ltp.device: Job dev-ssddata-ssddata_ltp.device/start failed with result 'timeout'.What can this be? Why could this volume not be mounted yesterday after the service outage, when it could be mounted on restarts before and can be mounted manually today?
Is there some kind of file system check that could have been going on, that had to be completed once before it could be mounted?
Or do I have to write this off as an arbitrary hardware fluke?
Regards