Hot answers tagged

2

/sbin/fsck /dev/md0 failed because you don’t have /sbin on your PATH, so fsck couldn’t find fsck.ext4. Running /sbin/fsck.ext4 directly works, as would adding sbin to the PATH: PATH="${PATH}:/sbin" /sbin/fsck /dev/md0


2

You should read the system logs: typically /var/log/messages and/or the output of the journalctl -xe command. If the drive failed recently, the kernel message buffer (viewable with the dmesg command) may also have messages about it. Normally, the dmesg messages will also get stored into the logs, but the logging subsystem may have been configured to ignore ...


1

I run LVM on LUKS on mdadm (RAID 6). When you increase the effective disk space at the physical layer you just need to update the available space in order, layer by layer Physical RAID LUKS PV for VG/LVM If you get the order of operations wrong nothing bad will happen - you'll just get no change.


1

Your MD device ends up being a PV like any other from the point of view of LVM, nothing changes on the LV side so all your LVs are resizable as usual. The MD device itself is resizable too, you can grow your RAID device if you change your drives (or add more) and then resize the PV. I don’t use RAID 5 so I don’t know what LVM’s support for that is like ...


Only top voted, non community-wiki answers of a minimum length are eligible