NV+ ver. 2 - No access to vol after disk failure #24051202
Hi,
I seem to have a few disks that are about to die, so I would just like to check that the approach that I am contemplating is the "right" one.
Here goes: My NV+ ver. 2 had a broken disk after a reboot. I hot-swapped the broken disk with a new one and the system started to resync. At some point it went into life support mode, but after finishing resync it is now back online with full capacity, stating in Frontview that the volume is redundant and reporting that status of all four disks are OK. However on the Readynas itself the light for drive no. 2 is constantly flashing. When checking the detailed status of drive no. 2 I do see that the ATA error count is 6 and that there is a pretty high number at the command timeout value. Despite the fact that the log does not offer up any errors on this drive, I guess I need to swap that drive asap as well. Correct?
I also have increased command timeout on another disk, but this disk still report zero under ATA error count. Therefore I do believe that I should replace this drive as well, but that I should prioritize replacing the drive that actually report ATA errors. Correct?
And yes, critical data that cannot be restored elsewhere from has been backed up, but I would prefer to avoid having to restore large amounts of data from various locations.
Re: NV+ ver. 2 - Disk no flash but no error in Frontview
Yes you should replace that drive too. What disk make and model are they and are they still under warranty. After you replace, run vendor tools on the bad disk and return it to the manufacturer if there are errors and it's under warranty. The other disk with command timeouts and no ATA errors - I'd replace it and run tests on it as with the other drive.
Re: NV+ ver. 2 - Disk no flash but no error in Frontview
None of the disks are under warranty, so that is not an issue. My main concern was that the actions and order of doing things that I was contemplating was the right one. Thanks for the input!
Re: NV+ ver. 2 - No access to data vol after disk failure
Ok, I have replaced the two first disks and beyond what I describe above, the resync completed without any errors. But now I have started to get errors on my Mac saying that there was errors in the CNID DB. Decided to try a reboot and a volume rescan to check that the issues during replacement of the disks had not caused problems in the basic volume. Apparently that was a mistake as I have now lost all access to the data volume.
On reboot I got the following error message: fsck from util-linux-ng 2.17.2 e2fsck 1.41.14 (22-Dec-2010) fsck.ext4: No such file or directory while trying to open /dev/c/c Possibly non-existent device?
Are there any chance that I will be able to recover from this with less than total loss of the data or do I need to do a factory reset and restore data from elsewhere?
Re: NV+ ver. 2 - No access to data vol after disk failure
I do have backup of essential data, but part of the data is music ripped from a large cd collection where the only "backup" is the CDs themselves, therefor I would like to give it a shot to see if I can salvage the data volume rather than having to restore the data from scratch.
But the only way is to contact support and pay for them to try to perform diagnostics? To be honest in my last contact with support they were all but helpful just referring me to the forum as my NAS is out of warranty...
Re: NV+ ver. 2 - No access to data vol after disk failure
Sorry to hear that, your OP suggested you were happy with the backup you had, or I would have suggested making one? Clearly you didn't have an adequate backp. There are other posts about that Cnid db error, did you find them? I think mdgm's advice is sensible if you really want the best chance of getting the data back. If you try anything else you may make data recovery more difficult.
Re: NV+ ver. 2 - No access to data vol after disk failure
vandermerwe wrote:
Sorry to hear that, your OP suggested you were happy with the backup you had, or I would have suggested making one? Clearly you didn't have an adequate backp.
I have as much backup as I need. All important data that I cannot recreate is back up to ReadyNAS Vault, so I can easily re-create that. Rest of the data is basically media (movies, music etc.). I do not have room anywhere to create a full backup of all that data and seeing as it can be re-created - although with a bit more work - I do not feel that I can justify spending the money buying so much additional storage space, and have therefore chosen to rely on the redundancy of the NAS knowing full well that this is not a substitute for a backup. (Although this situation do cause me to reconsider if I could re-purpose my old ReadyNAS Duo by buying a couple of 3TB disks to do a weekly clone of the NV+ by rsync)
vandermerwe wrote:
There are other posts about that Cnid db error, did you find them?
Yes, but I did not find anything that really seemed like a solution. Best bet was to restart and do a volume scan, which for some seems to have fixed the issue. Perhaps I have not been looking hard enough.
vandermerwe wrote:
I think mdgm's advice is sensible if you really want the best chance of getting the data back. If you try anything else you may make data recovery more difficult.
I guess this will be my next step then. Do I just open a case with support or do I need to go somewhere specific to purchase the data recovery service?
Re: NV+ ver. 2 - No access to data vol after disk failure
mdgm wrote:
The Duo you have registered is a Duo (v1) which does not support 3TB disks. The max you can use is 2x2TB disks.
Actually thought that the last update upgraded the Duo v1 to support 3TB drives, but if not then I guess I will have to consider another route if I want to do additional back up.
I will try to contact support and see what they can do.
Re: NV+ ver. 2 - No access to vol after disk failure #240512
Got a reply from Netgear support who offered a data recovery service for 190 EUR. Without any sort of security that recovery would be a success and with data that can be restored through a little more work, I think that is to expensive. So I decided to try my luck and inserted the two failed disk back in to the system. Now I for some reason have access to the file system again - however I get the following error:
***** File system check performed at Sat Oct 18 12:08:23 PDT 2014 ***** fsck from util-linux-ng 2.17.2 /dev/mapper/c-c: Superblock has an invalid journal (inode 8). CLEARED. *** ext3 journal has been deleted - filesystem is now ext2 only ***
/dev/mapper/c-c: Superblock has_journal flag is clear, but a journal inode is present. CLEARED. /dev/mapper/c-c contains a file system with errors, check forced. /dev/mapper/c-c: Journal inode is not in use, but contains data. CLEARED. /dev/mapper/c-c: Inode 2424849 has an invalid extent node (blk 186916865, lblk 0)
/dev/mapper/c-c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) ##############
Further disk one remain dead and I get the following error report on disk 2 (the second disk that I originally replaced): ATA error count has increased in the last day.
Disk 2: Previous count: 0 Current count: 6 ##################
Trying to run fsck manually as suggested in the error message warns me that /dec/mapper/c-c is mounted and running fsck will cause damage to the volume, however trying to un-mount /dev/mapper/c-c reports that it is not mounted...
Trying to connect to the drive in finder (at least using CIFS) gives me access to all files and I believe that I should be able recover all files to an external drive which I intend to attempt. However do you believe that there is any chance of repairing the error reported above and get the two disks replaced while still retaining access to the data?
