On 9/21/19 2:19 AM, Liviu Petcu wrote: >>> Yes. Only one of the 2 disks reported by mdadm as failed, is broken. I >>> almost finished making images of all the discs, and for the second "failed" >>> disc ddrescue reported error-free copying. I intend to use the images to >>> recreate the array. I haven't done this before, but I hope I can handle >>> it... >>If by recreate you mean run mdadm --create, you really shouldn't start with that - it's easy to get wrong. >>You can almost certainly use mdadm --assemble --force per >https://raid.wiki.kernel.org/index.php/RAID_Recovery >Yes, I'll do that and all other attempts, with disk images as read only attached loop devices. >Liviu Sorry. I can not handle it. Here's what I did: #losetup --find --show -r /mnt/usb/discX.img # losetup --list NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO /dev/loop1 0 0 0 1 /mnt/usb/disc3.img 0 /dev/loop253 0 0 0 0 /m.sqfs (deleted) 0 /dev/loop4 0 0 0 1 /mnt/usb/disc6.img 0 /dev/loop2 0 0 0 1 /mnt/usb/disc4.img 0 /dev/loop254 0 0 0 0 /run/PMAGIC_2016_10_18.SQFS 0 /dev/loop0 0 0 0 1 /mnt/usb/disc2.img 0 /dev/loop252 0 0 0 0 /fu.sqfs (deleted) 0 /dev/loop3 0 0 0 1 /mnt/usb/disc5.img 0 So /dev/loop[01234] are now read only drives #fdisk -l Disk /dev/loop0: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: A95A32BD-3198-4C9B-8445-BAC177AA5B31 Device Start End Sectors Size Type /dev/loop0p1 2048 8388641 8386594 4G Linux RAID /dev/loop0p2 8390656 3907029134 3898638479 1.8T Linux RAID Disk /dev/loop1: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: A95A32BD-3198-4C9B-8445-BAC177AA5B31 Device Start End Sectors Size Type /dev/loop1p1 2048 8388641 8386594 4G Linux RAID /dev/loop1p2 8390656 3907029134 3898638479 1.8T Linux RAID Disk /dev/loop2: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: A95A32BD-3198-4C9B-8445-BAC177AA5B31 Device Start End Sectors Size Type /dev/loop2p1 2048 8388641 8386594 4G Linux RAID /dev/loop2p2 8390656 3907029134 3898638479 1.8T Linux RAID Disk /dev/loop3: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: A95A32BD-3198-4C9B-8445-BAC177AA5B31 Device Start End Sectors Size Type /dev/loop3p1 2048 8388641 8386594 4G Linux RAID /dev/loop3p2 8390656 3907029134 3898638479 1.8T Linux RAID Disk /dev/loop4: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: A95A32BD-3198-4C9B-8445-BAC177AA5B31 Device Start End Sectors Size Type /dev/loop4p1 2048 8388641 8386594 4G Linux RAID /dev/loop4p2 8390656 3907029134 3898638479 1.8T Linux RAID # mdadm --assemble --force /dev/md1 /dev/loop0p2 /dev/loop1p2 /dev/loop2p2 /dev/loop3p2 /dev/loop4p2 /dev/loop5p2 mdadm: cannot open device /dev/loop0p2: No such file or directory mdadm: /dev/loop0p2 has no superblock - assembly aborted It is wrong? Or something I broke? Thanks. Liviu
