My Vero 4k has (a few times now) been unresponsive to the point where I have to pull the plug. I’m not able to log in via SSH (it gets to the User prompt, sometimes, but usually times out before a successful login). Since I pull the plug it seems to corrupt the HDD. It boots into “Recovery” mode and I have to edit FSTAB, comment out the HDD line, then reboot. (This allows me to SSH into the box again). Then I have to run a disk check to fix journal entries before I can redo my fstab file.
A few questions:
- Any idea what is happening that is causing my v4k to become unresponsive?
- Is there a better solution to the hard reboot that would help eliminate the corrupted journal entries?
- Is there a way that I can fix the startup script so that it boots to at least a network prompt, even if the FSTAB fails?