New answers tagged

0

I'm just updating some of the information given earlier. I had a 3-disk raid5 array working ok when my motherboard died. The array held /dev/md2 as the /home partition 1.2TB and /dev/md3 as the /var partition 300GB. I had two backups of "important" stuff and a bunch of random things I had grabbed from various parts of the internet that I really should ...


0

One way would be to build a container for rsnapshot or similar tool that mounts your data store as a volume. Rsnapshot cannot push backups to another host but you could sync to a directory that's on a remote file system. A restore from an rsnapshot backup is a simple rsync and should be simple to trigger from cloud-init. Another option is to roll a ...


3

If you have a pool built from two disks as a raid-0, your data was striped over both disks. You cannot recover any data from a raid-0 when one disk is missing. Yout only option is a professional data rescue service that can repair the faulted disk.


2

This is a "classical" problem on RAID5 arrays: when one disk die, you discover the others have developped bad sectors. Under this circumstance, many hardware RAID controllers simply drop the entire array (or refuse to start it). If your RAID controller has a "forced" mode to bring the array online (albeit with some unavoidable data corruption), use it. If ...


2

if you cant cat raw device it looks like whole thing is not responding... but if you somehow manage to make it work: first and most important, dump whole usb stick to file, using ddrescue if neccesary, in case shit hits the fan Then use either testdisk or gpart to recover partition table, those programs guesses start of partiton based on filesystem headers ...



Top 50 recent answers are included