Is it a good idea to just execute mdadm -manage /dev/md2 -remove /dev/sda3 I would like to access the data from md2 (the data on the active and not damaged disk, that is /dev/sda3) by mounting it outside of the raid. Md2 seems to be damaged and it is probably the raid with my VMWare images. The following is the output of mda -examine for all 3 disks (I think it should be 3x raid1 disks).
#Disk arbitrator to keep disks mounting how to#
Now I am lost, I have no idea how to recover the disks and get the data back. Mdadm: /dev/sda1 has no superblock - assembly aborted mdadm: cannot open device /dev/sda1: Device or resource busy So I tried to create a virtual device as follows. Mount: /dev/sda1 already mounted or /mnt/rescue/ busy mount -o ro -t ext3 /dev/sda1 /mnt/rescue/ Guessing file system is not going well either. mount: unknown filesystem type 'linux_raid_member' I was trying to mount the disks as follows. Units = cylinders of 8 * 512 = 4096 bytesĭisk /dev/md0 doesn't contain a valid partition tableĢ heads, 4 sectors/track, 526112 cylindersĭisk /dev/md1 doesn't contain a valid partition table dev/sdb01 1458830520 fd Linux raid autodetectĢ heads, 4 sectors/track, 1050224 cylinders I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes
The output for relevant commands is as follows. I just want to mount them all to /mnt/rescue in read only modus to be able to copy VMWare GSX images to another machine and migrate them to ESXi later on. I have a horrible situation where I have to restore data from damaged raid system in a rescue Debian Linux.
0 kommentar(er)
