RE: restarting raid arrays with uuid

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>-----Original Message-----
>From: linux-raid-owner@xxxxxxxxxxxxxxx [mailto:linux-raid-
>owner@xxxxxxxxxxxxxxx] On Behalf Of Bryan Hepworth
>Sent: 06 June 2016 19:55
>To: linux-raid@xxxxxxxxxxxxxxx
>Subject: restarting raid arrays with uuid
>
>Hi All
>
>I'm not entirely sure this is rescuable. This is an old system that was kept on
>for scratch storage space, unfortunately it was discovered some data hadn't
>moved out of this area. The arrays disappeared after taking them offline and
>rebooting the machine.
>
>I've checked /etc/mdadm.conf
>And mdadm --examine across all of the disks
>I've assembled from uuid
>Ran /proc/mdstat
>
>Any suggestions as to what to try next?
>

After carefully looking at the arrays I have two back as they should be.

I've also discovered that one of the drives with gpt has a partition in it with ext4 data. Gparted has given me the device uuid which I can see in /dev/disk/by-uuid

Unfortunately it says no superblock information when I run mdadm --examine /dev/disk/by-uuid/<uuid number>

gparted  does say ext4 is clean and it does have a --raid tag so my next question is is it safe to mount this drive, or is it best to dd it elsewhere to see what's on it?

Thanks

Bryan
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux