Thanks again for the help. I am struggling a bit with the intricacies of
this but am progressing a little I think.
I have not yet tried Russell's suggestion of purchasing two new 4TB
drives because of the expense but will go in that direction as a last
resort. I have copied the data onto 2TB drives which are the same size
and type as the originals. Not sure if that will achieve all that is
I have been trying with mdadm to mount the drive but so far with no
My mdadm.conf shows the drive:
# definitions of existing MD arrays
ARRAY /dev/md/2 metadata=1.2
but when I try to mount the partition sda5 I get:
bob@Comp1:~$ sudo mount /dev/md2 /media/ntfs
mount: /media/ntfs: can't read superblock on /dev/md2.
bob@Comp1:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
md2 : inactive sda5(S)
1948779840 blocks super 1.2
unused devices: <none>
Any further instructions or suggestions appreciated
I need some advise with regard to rescuing data from a raid disk.
I gave a friend a Synology two bay NAS set up as a raid array to store
their data safely and suggested that it was backed up regularly to
another disk as well for safely. All their family photos for the last
10 years or so are stored there - the only copies.
Husband (Windows User) familiarized himself with the Synology and things
seemed to be OK. However he decided that I was being overcautious and
that extra backup wasn't needed. :-(
Unfortunately one of the disks failed and husband in his wisdom decided
to 'fix' it and instead wiped all the data from the good disk - disaster.
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. I have tried ddrescue which I have been able to use to copy
data from the main partition on the damaged disk onto an old ntfs disk I
had lying around but it is still unreadable as the raid filesystem
refuses to mount and I still can't see the files.
I have the good disk still (no data as it was wiped, but partitions
still there) and another spare identical 2 Tb disk as well.
All I want is to rescue the photo files from the disk - I can then
replace the disks in the Synology NAS and reinstall as well as having
the photos safely saved elsewhere.
How am i best to proceed?
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'.
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.
Both Google Chrome and Firefox refuse to connect to this link, claiming
that it's insecure.
Life is too short to waste time trying to find ways to prolong it.
This isn't a well defined question at this point, but I'm asking here as
there may be insight on offer.
I'm currently using a Linksys WRT AC1900 as my router at home (the
original version, not v2). It has OpenWRT installed, and I keep it up to
date. It's fine for the moment.
When 802.11ax hardware becomes more readily available, I plan to upgrade
to something else. In particular, I would prefer to run an operating
system that can be upgraded package by package instead of having to
install an entire image, and which is more like a typical Linux
distribution than OpenWRT is. Of course, it needs to offer all of the
desired networking functionality.
So, on the hardware and software side, what are the interesting projects
to consider in this area? For the hardware, wireless and at least 4
Ethernet ports would be ideal, as well as high reliability and more
RAM/CPU performance than consumer devices provide. As noted, I plan to
wait for 802.11ax (unless the current hardware runs into problems
meanwhile, of course).
-----BEGIN PGP SIGNED MESSAGE-----
For those of us whom use OpenPGP/GPG keys with GNUPG implementation
(perhaps everyone whom interacts with SKS servers)... there has been a
very long standing technical problem that is currently causing issues.
The problem, in a nutshell causes keys to significantly increase in
size due to bad data being easily uploaded to the SKS servers without
proper validation and consequently severely effecting performance of
anything using the public keyring database. If you experience the
problem, it will be due to a significant increase of the size of your
public keyring file. When processing the public keyring data, the CPU
gets pinned at 100% for at least one thread.
What I have done is a full export of keys to ASCII armoured files and
look at the larger files -- in my case the two largest were for Micah
Lee and the Tor Project keys. Delete problematic keys and import
fresh sane data for them.
Having older backups of the Tor Project's key, I've replaced the key
with one that doesn't have the extra bad payload. The former key
/may/ not be easily found as the Tor website directs you to an SKS
server to collect the data and it doesn't appear to be easily
available directly from Tor project's own website.
For Micah Lee's key, I got it from keybase.io (micahflee).
There are different solutions, keybase.io is but one. In any case the
SKS servers are in big trouble as they stand today.
A reason for the problem popping up might be related to a simple key
refresh; so that is a major problem. It's been said that even just
using the keys can cause problems when you don't have any keys with
bad data, but I'm not so sure about that.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----