Monkeyair

I followed the instructions and got the disk formatted: I then did a new config and used the valid parity, started the array and stopped the parity check. I then stopped the array and unassigned the disk to show missing. When I restarted the array I see the following and no emulated drive in windows explorer: If I then add the device back to the array I get the option to rebuild. Should I do this?

The compromised data disk is listed as unmountable, which is why I thought that the format option would fix the file system ready for a rebuild. Obviously, I know that is not the case now. By the time I noticed what the format was doing the system had written 4000000 writes to a 6TB parity. The total data on the compromised disk was roughly 5TB. How much damage can I expect 4000000 writes to have done? Will the unmountable disk show in explorer? Can I get it to mount without compromising any more data on the disk?

I'm using the zoneminder docker to run my ip cams and save the 24/7 data on a HDD mounted outside of the array. I'm very pleased with the results.

Hopefully. Thanks again for all of your help.

27 mins gone and 1931810 errors........

Thanks for that. If I run a parity check with the part formatted data disk as an array device but not mounted in the array, am I going to make things worse by running a parity check? Am I better off waiting for a new disk to replace the data drive and do a rebuild? If there is anything left to rebuild as most of my data was on disk 1 (Formatted disk) I'm trying not to touch the said data disk any more in case it has to go of to a data recovery company.

I now see that format was a BIG mistake! :'(

Fortunately I have managed to mount the faulty drive for now. It must be an intermittent fault. So I only have 1 failed drive for the moment. My parity now shows as valid, but when the array starts no rebuild option is available as the data disk that I used the wrong recovery program on is unmountable. The option is given to me to create a file system and format the disk. I want the disk to mount and rebuild the parity. I initially selected format but bottled it and restarted the system. What is the correct thing to do? Have I compromised the data on my parity drive by letting the data disk format for a while?

Ok. Thanks anyway

So, I did the XFS repair and I got this: This is the Disk info: And after running a new config, I see that this disk info in the unassignded devices shows a reiserfs file system: So have I screwed this disk up by running a program designed to recover an RFS (reiserfs) formatted disk to recover an XFS formatted disk? Any way back do you think?

Ah I see, that's great thanks.

Dual parity? Sounds like a good idea to me. No probs, go ahead and point all you like. Anything that helps someone else that takes their eye off the ball. I won't be the last I'm sure

Every day is a school day! 1 is a data drive, the other is the parity drive that is having nothing repaired From the Wiki: Very important!!! Do NOT run these tools on the parity drive. It does NOT have a file system, and running ANY file system repair tool on your parity drive can corrupt it!

Nothing to be sorry for! it's my own silly fault. I can't believe that I did this.... The disks are now both running the XFS repair, so hopefully all will not be lost. Thanks for replying.

Thanks a lot

Bjp that was your guidance

The disks were XFS formatted. This is the gdisk output: This is the guidance that I followed: So back to the first disk that had been in the parity slot for a short time. Luckily Tom was on-line and helped me figure out what to do. I ran “reiserfsck /dev/md1” (UPDATE 8/8/11: If you ever run on on an OS level device rather than an unRAID device, make sure to use the first partition - ie., “reiserfsck /dev/sdc1", and not the disk level device.) (and it questioned whether this was really a reiserfs formatted drive. It told me to run with the “--rebuild-sb option” if I was sure. If ever you have to run with this option, it asks you a bunch of questions. Here are the correct responses (many thanks to Tom for helping me through these): 1. The version of reiserfs is 3.6.x. This is for unRAID 4.2.1. (This is NOT the default, so be careful) 2. Block size is 4096 (default) 3. “No journal device was specified. (If journal is not available, re-run with --no-journal-available option specified)” Is journal default?” (Answer Y) 4. “Do you use resizer?” (Answer N) 5. It tells you that a new uuid has been generated. 6. “rebuild-sb: You either have a corrupted journal or have just changed the start of the partition with some partition table editor. If you are sure that the start of the partition is ok, rebuild the journal header. Do you want to rebuild the journal header?” Answer Y 7. The following info is displayed: Reiserfs super block in block 16 on 0x901 of format 3.6 with standard journal Count of blocks on the device: 73264320 Number of bitmaps: 2236 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 0 Root block: 0 Filesystem is NOT clean Tree height: 0 Hash function used to sort names: not set Objectid map size 0, max 972 Journal parameters: Device [0x0] Magic [0x0] Size 8193 blocks (including 1 for journal header) (first block 18) Max transaction length 1024 blocks Max batch size 900 blocks Max commit age 30 Blocks reserved by journal: 0 Fs state field: 0x1: some corruptions exist. sb_version: 2 inode generation number: 0 UUID: <my UUID removed> LABEL: Set flags in SB: Is this ok ? (y/n)[n]: 8. Answer “Y”. 9. With amazing speed the program does its thing and ends

I've done something very silly today..... I had an old disk in my array that had failed, so I removed it and ran a new config to reduce the array by one drive. I then added the drives, but put mixed up drive 1 and the parity. Once the system started I stopped the parity synch within seconds, but my data cannot be reached. I've tried following guidance for reiserfsck, but have had no joy. Can anybody help recover my data? My Crashplan backup was part way through, so I only have some of my docs backed up.

I don't have any cameras set up right now so I can't test, but could one be symlinking to the other location? This is the file format on the HDD: When I open the individual files the structure and contents are identical.

Thanks for the ZoneMinder docker, it's working a treat. If I could just run something by you clever fellas.... I have my IP cam recording 24/7 to a HDD outside of the array. ZM is saving the files as JPEG and creating what seems to be duplicate folders, one named the cameras name and the other named "1", which I believe is zone 1. I'm just trying to make sure that I'm using the space on my HDD efficiently and not saving duplicate files when I don't need to. Any advice on the config?

Check this out for ideas: https://www.modmypi.com/shop I have a Raspi2 running Kodi and it has great performance and is not sluggish at all. I use a HTPC for the main system, the Pi's are for other TV's around the house. blimey , i didn't realise how cheap they are now. might pick one up just for messing about on. , it's still a derivative of debian 7 , right ? Do you mean Openelec? It's not based on Debian. They built it from scratch they say on their webpage. I run Openelec on mine.

Check this out for ideas: https://www.modmypi.com/shop I have a Raspi2 running Kodi and it has great performance and is not sluggish at all. I use a HTPC for the main system, the Pi's are for other TV's around the house.

This is from TVheadend log, I think that it's related to permissions: Unable to create dir "/recordings/This Is BBC Four": Permission denied Who is the owner of the recordings folder on the HDD? As far as I know this plugin only mounts the disk, so it has to be wrong permissions set on the folder created on the HDD. Hi Saarg This sorted it: newperms /path/to/mounted/drive/ Thanks

This is from TVheadend log, I think that it's related to permissions: Unable to create dir "/recordings/This Is BBC Four": Permission denied

I'm using your plugin to mount a HDD outside of the array to use as storage for TV recordings and Timeshift from TVHeadend. All has gone well so far, with the disk showing under unassigned devices and I am able to access it through explorer. I have set the default script. I am trying to resolve an issue with its use now. For some reason my recordings are not making it to the HDD. I'm not sure if this is TVHeadend related or Plugin related. Could you please give me a steer as to the correct script that I should be using, or any settings that I may have missed to enable the HDD's use outside of my array? Thanks