NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
mike1234i
Sep 12, 2012Aspirant
Unable to mount /dev/c/c #19420777
I have a ReadyNAS Pro Pioneer Edition [X-RAID2] running RAIDiator 4.2.21. My NAS seems to be in bad shape and I was wondering if someone could provide some assistance before I moved on to a rebuild. I was having issues with saving files this morning and it seemed to caused by the filesystem being read only. When I rebooted the ReadyNAS, I got the email:
I tried to do a full scan, but the /dev/c/c still does not mount. The fsck scan gave me a slew of the following errors:
I'd like to recover the volume since there are non-critical items that I do not have a backup of or would take me a while to recreate. However, if needed I am prepared to do a factory reset and move on. My lesson learned will be -- don't play with 3rd party add-ons on your production box.
***** File system check performed at Wed Sep 12 08:31:03 CDT 2012 *****
fsck 1.41.14 (22-Dec-2010)
/dev/c/c: Note: if several inode or block bitmap blocks or part
of the inode table require relocation, you may wish to try
running e2fsck with the '-b 32768' option first. The problem
may lie only with the primary block group descriptors, and
the backup block group descriptors may be OK.
/dev/c/c: Block bitmap for group 1920 is not in group. (block 914014173)
/dev/c/c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
I tried to do a full scan, but the /dev/c/c still does not mount. The fsck scan gave me a slew of the following errors:
Block bitmap for group 1920 is not in group. (block 914014173)
Relocate? yes
Inode bitmap for group 1920 is not in group. (block 914014170)
Relocate? yes
Inode table for group 1920 is not in group. (block 913965056)
WARNING: SEVERE DATA LOSS POSSIBLE.
Relocate? yes
I'd like to recover the volume since there are non-critical items that I do not have a backup of or would take me a while to recreate. However, if needed I am prepared to do a factory reset and move on. My lesson learned will be -- don't play with 3rd party add-ons on your production box.
4 Replies
Replies have been turned off for this discussion
- mdgm-ntgrNETGEAR Employee RetiredOpen a support case at my.NetGear.com and post your case number
- mike1234iAspirantCase number is: 19420777.
- mike1234iAspirantSupport was very responsive about getting back to me, however they were unable to fix the problem. After pulling each disk for testing I realized that the problem is that 3 disks (out of 6) went bad with no warning. My NAS was setup with dual parity, but obviously could not handle 3 failures.
I recently upgraded to 6 3TB Seagate (ST3000DM001) drives. Clearly this was my mistake. Out of the 7 drives (1 spare) originally purchased, 4 have gone bad in less than 4 months. - mdgm-ntgrNETGEAR Employee RetiredDo you have a good backup?
How bad have the 3 disks failed? Are they detected by your PC?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!