Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
ReadyNAS 2100 4.2.27 errors & data loss #24860050
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-03-16
09:15 PM
2015-03-16
09:15 PM
ReadyNAS 2100 4.2.27 errors & data loss #24860050
Hi,
First time poster, long time lurker......
Had a major issue with my 2100. The regular Rsync backups were notifying me of errors, so I starting looking to see what the problem was..
The first error email I received from the NAS was as follows....
Volume scan found errors that it could not easily correct. Please ensure that you have current backups of all valuable data before performing a full volume scan by rebooting the NAS through Frontview with the volume scan option enabled. (ReadyNAS_2100)
***** File system check performed at Tue Mar 3 20:35:26 EST 2015 ***** fsck 1.42.12 (29-Aug-2014)
/dev/c/c: Superblock has an invalid journal (inode 8 ).
CLEARED.
*** ext3 journal has been deleted - filesystem is now ext2 only ***
/dev/c/c: Superblock has_journal flag is clear, but a journal is present.
CLEARED.
/dev/c/c: One or more block group descriptor checksums are invalid. FIXED.
/dev/c/c: Group descriptor 1984 checksum is 0x2689, should be 0x1039.
/dev/c/c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
The subsequent email was much longer and appears to be results of trying to correct bad data??
So now I'm thinking, no problems.....I have a backup!!
Only problem was that while the 2100 could still see the shares (albeit nearly empty), Rsync then removed all my backup data from the NV+.....
Now, after a number of restarts of the 2100 I can't access any of the shares on the 2100. Volume info still shows 630Gb of data used.
Given that I am an absolute ReadyNAS novice, I'm hoping someone may be able to provide some guidance to retrieve at least some of my data from the 2100....
Cheers
Jeff
First time poster, long time lurker......
Had a major issue with my 2100. The regular Rsync backups were notifying me of errors, so I starting looking to see what the problem was..
The first error email I received from the NAS was as follows....
Volume scan found errors that it could not easily correct. Please ensure that you have current backups of all valuable data before performing a full volume scan by rebooting the NAS through Frontview with the volume scan option enabled. (ReadyNAS_2100)
***** File system check performed at Tue Mar 3 20:35:26 EST 2015 ***** fsck 1.42.12 (29-Aug-2014)
/dev/c/c: Superblock has an invalid journal (inode 8 ).
CLEARED.
*** ext3 journal has been deleted - filesystem is now ext2 only ***
/dev/c/c: Superblock has_journal flag is clear, but a journal is present.
CLEARED.
/dev/c/c: One or more block group descriptor checksums are invalid. FIXED.
/dev/c/c: Group descriptor 1984 checksum is 0x2689, should be 0x1039.
/dev/c/c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
The subsequent email was much longer and appears to be results of trying to correct bad data??
So now I'm thinking, no problems.....I have a backup!!
Only problem was that while the 2100 could still see the shares (albeit nearly empty), Rsync then removed all my backup data from the NV+.....
Now, after a number of restarts of the 2100 I can't access any of the shares on the 2100. Volume info still shows 630Gb of data used.
Given that I am an absolute ReadyNAS novice, I'm hoping someone may be able to provide some guidance to retrieve at least some of my data from the 2100....
Cheers
Jeff
Message 1 of 2
Labels:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-03-16
09:24 PM
2015-03-16
09:24 PM
Re: ReadyNAS 2100 4.2.27 errors & data loss #24860050
Doesn't look good.
Can you send me your logs (see the link in my sig)?
Can you send me your logs (see the link in my sig)?
Message 2 of 2