Tag Archives: fsck
As seen in my previous post, I’ve been having problems with some harddrives in my workstation. I’ve also had some problems with my TV’s digital box, a Motorola VIP1963.
At first there was some trouble with time-shift not working, but this could be resolved by simply rebooting the device. This wasn’t really worth noting because this device is constantly on and never rebooted, so I guess it was bound to happen sooner or later.
Suddenly the other day, the device rebooted on it’s own, and when it came back up it gave me an error message saying that the harddrive could not be found. This message was in swedish:
Rebuilding a RAID1 mirror with a Truecrypt container on it may require some additional steps. I guess that since no filesystem is visible on the disk, the RAID array is having trouble determining which disk to rebuild from. If your neighbourhood have had a blackout, the filesystem in the container is probably dirty anyway. This is how I take care of the matter on my external ICY Box IB-RD4320 USB chassi.
The manual for ICY Box IB-RD4320 USB chassi have this table regarding the meaning of the LED lamps on the unit:
LVM gives you flexibility at the cost of more complexity. When a system with LVM configured is shutdown uncleanly, there may be some trouble getting back on track again.
Some notes from the top of my head, for occasions when this happens.
- If your LVM system stops booting and complains about the disks, or the disks are suspected being dirty, boot into maintenance/single mode.
- Search for your volume group to see that it’s available:
- Activate your volume group:
- Check filesystem integrity, for each of your logical volumes:
Solving disk problems is a little more complicated when devices are encrypted. You need to keep in mind that a filesystem on an encrypted device can’t be seen unless the device is decrypted. Here is a few problems I’ve come in touch with, together with solutions that have worked for me.
Error unmounting a volume
Error message which may occur when trying to unmount truecrypt volume:
Trying to remove the volume with cryptsetup gives a similar message:
Device /dev/mapper/truecrypt1 is busy.
As the error messages implies, something is keeping the volume open. If lsof doesn’t show anything, it might be an active NFS export keeping it busy.