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
Missing shares detected
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2013-04-10
07:21 PM
2013-04-10
07:21 PM
Missing shares detected
Hostname: NAS
Model: ReadyNAS NVX Business Edition [X-RAID2]
Serial: 22M193RN000D6
Firmware: RAIDiator 4.2.22
Memory: 1024 MB [6-6-6-24 DDR2]
IPv4 address: 1+2: 192.168.10.114
Volume C: Offline, X-RAID2, 4 disks, 100% of 4634 GB used
The used space should only be around 25%
During a routine scheduled "Volume consistency check" our ReadyNAS sent these email messages:
1-Volume consistency check failed for Volume C
The on-line filesystem consistency check detected problems with your data volume. Please reboot the system with the volume scan checkbox enabled to do a full filesystem consistency check and repair.
2-Missing shares detected
The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume.
media
backup
3-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.
***** File system check performed at Sun Mar 24 14:01:59 PDT 2013 *****
fsck 1.41.14 (22-Dec-2010)
/dev/c/c: Superblock has an invalid journal (inode 8).
CLEARED.
*** ext3 journal has been deleted - filesystem is now ext2 only ***
/dev/c/c: One or more block group descriptor checksums are invalid. FIXED.
/dev/c/c: Group descriptor 0 checksum is invalid.
/dev/c/c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
4-Missing shares detected
The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume.
media
backup
We are unable to access any share at this point, please advise on what to do next.
Thanks
Model: ReadyNAS NVX Business Edition [X-RAID2]
Serial: 22M193RN000D6
Firmware: RAIDiator 4.2.22
Memory: 1024 MB [6-6-6-24 DDR2]
IPv4 address: 1+2: 192.168.10.114
Volume C: Offline, X-RAID2, 4 disks, 100% of 4634 GB used
The used space should only be around 25%
During a routine scheduled "Volume consistency check" our ReadyNAS sent these email messages:
1-Volume consistency check failed for Volume C
The on-line filesystem consistency check detected problems with your data volume. Please reboot the system with the volume scan checkbox enabled to do a full filesystem consistency check and repair.
2-Missing shares detected
The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume.
media
backup
3-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.
***** File system check performed at Sun Mar 24 14:01:59 PDT 2013 *****
fsck 1.41.14 (22-Dec-2010)
/dev/c/c: Superblock has an invalid journal (inode 8).
CLEARED.
*** ext3 journal has been deleted - filesystem is now ext2 only ***
/dev/c/c: One or more block group descriptor checksums are invalid. FIXED.
/dev/c/c: Group descriptor 0 checksum is invalid.
/dev/c/c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
4-Missing shares detected
The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume.
media
backup
We are unable to access any share at this point, please advise on what to do next.
Thanks
Message 1 of 2
Labels:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2013-04-11
10:49 PM
2013-04-11
10:49 PM
Re: Missing shares detected
Contact NetGear tech support and post your case number. You will need to try to get your case escalated to L3.
Message 2 of 2