Mystery mdadm raid1 mounting
I've been tearing my hair out on this for several days so hope some one can help. It's a desktop machine, my partitioning may be a bit unusual but has it's reasons. I use a raid1 array as /home. This is the disk layout.
Code:
john@dhcppc1:~> lsblk One of the drives is down. It needs replacing and also enlarging. For a number of reasons my general idea is to map home to a partition on the spare disc and use rsync to copy the files across. Remove the raid, install new drives, convert to raid, map to home and copy the files across again. To do that I need to remove the current home mapping. The guides about on doing this via mdadm make various suggestions and many are rather old. The above looks to be a simpler way of doing it. I'm basically a desktop person and only go below if I must. I usually manage when I do but fully understanding all of what mdadm can do is a fair old task. I'm also now determined to find out just how /home is mapped even if I fix it some another way. The failure might be down to a power failure or actually the first time I installed opensuse leap 42.2. The install didn't indicate that it would format home but all of the old files from 12.3 went - as they needed to. During install I imported the partitioning and all apart from that aspect looked ok. John - |
From the above it looks like home is not a separate mount, it is under '/' on sda2. You seem to have half a raid1. Post the output of 'cat /proc/mdstat' to see.
|
The quick way to find out what filesystem holds a directory is to use the df command, in your case:
Code:
df /home/ |
Thanks both. Arrggggggggggggggg. I imported my existing partitioning when I installed. It's totally disregarded what I had spec'd a /home. I've been fiddling around for over 4 days trying to sort this.
Code:
john@dhcppc1:~> df /home/ Code:
john@dhcppc1:~> cat /proc/mdstat A scan with mdadm shows one disk active and the other as clean. Checksums ok on both but the one disk shows read errors at about the time I installed / had a power failure but I think that was well before the install. That just leaves how do I remove the current raid completely? It does seem to be mounted but not mapped anywhere. John - |
Just a note.
I used yast2 to delete the raid. One problem. For some reason KDE reboot just hung up and wouldn't. Something about the greater not being happy and couldn't report the bug because it was unhappy. A reboot from the console did work and following that kde's was ok too. Wonder what KDE was doing that needed an unused raid to be there. John - |
All times are GMT -5. The time now is 04:15 PM. |