something like this? https://unix.stackexchange.com/questions/300122/mount-a-single-hard-disk-that-was-part-of-raid-1/381923
On Mon, 22 Jul 2019 at 17:12, bob via luv-main <[email protected]> wrote: > Thanks for the help Glenn. > > On 20/7/19 1:40 pm, Glenn McIntosh via luv-main wrote: > > > On 19/7/19 10:10 am, bob via luv-main wrote: > >> I can access the damaged disk by attaching it to my Kubuntu workstation, > >> reading it with testdisk and all the partitions and data appears to be > >> still there, but I can't see the files because of the RAID filing > >> system ... the raid filesystem > >> refuses to mount and I still can't see the files. > > Just asking for some clarification: > > > > * Are you saying that the files in the image are not visible with a file > > carving tool such as photorec? I'd only suggest file carving as a last > > resort as it is time consuming, but I've had success with it > > particularly for static photo collections which tend to be small files > > and relatively unfragmented, and you can use the jpg exif data to > > reconstruct a semi-useful filename. > I haven't tried this yet as i haven't used photorec before but it is on > my list if necessary. > > * When the good disk was 'wiped', was it just formatted or completely > > erased? If you do have to do low level file recovery, it might be better > > to work with that image instead (assuming you have more spare terabytes > > of storage lying around to copy it onto!) > It appears that all the data was wiped - the partitions are all still > there. Not sure how to do a 'low level file recovery'. > > > > * When you say raid 'filesystem', are you saying it isn't a standard > > file system on top of the raid? Or that there is a backup format on top > > of the filesystem, maybe compressed? > > It appears to be Ext4: > > Disk /dev/sda: 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: dos > Disk identifier: 0xf58d74d3 > > Device Boot Start End Sectors Size Id Type > /dev/sda1 256 4980735 4980480 2.4G fd Linux RAID > autodetect > /dev/sda2 4980736 9175039 4194304 2G fd Linux RAID > autodetect > /dev/sda3 9437184 3907015007 3897577824 1.8T f W95 Ext'd (LBA) > /dev/sda5 9453280 3907015007 3897561728 1.8T fd Linux RAID > autodetect > > I am unable to mount either the either the drive or the partition (sda5) > where I think the data is stored. > > bob@Comp1:~$ sudo mount -o ro /dev/sda /media/ntfs > mount: /media/ntfs: /dev/sda already mounted or mount point busy. > bob@Comp1:~$ sudo mount -o ro /dev/sda5 /media/ntfs > mount: /media/ntfs: unknown filesystem type 'linux_raid_member'. > bob@Comp1:~$ > > The original disk causes the computer to baulk at startup and displays > an American Megatrends screen and the message "SMART Status bad Backup > and replace". I can then continue on through the BIOS and kubuntu starts > OK. I can then see the disk with fdisk but not mount it as above. > > The detail above is using a clone of the original disk. > > _______________________________________________ > luv-main mailing list > [email protected] > https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main > -- Dr Paul van den Bergen
_______________________________________________ luv-main mailing list [email protected] https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
