NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Readynas NV+ stuck at booting - missing shares found
Hello, i have an issue with on of my NV+ v1 which worked for long without an issue (configuration X-Raid). Some days ago when i checked the display after not being able to access the data i found...
I had a look at the etc/fstab using vi and found a large discrepancy between the fstab of my two NV+
the nv+ that does not finish boot:
***** File system check performed at Sun Oct 4 13:28:32 CEST 2015 ***** fsck 1.40.11 (17-June-2008) WARNING: bad format on line 2 of /etc/fstab WARNING: bad format on line 4 of /etc/fstab WARNING: bad format on line 5 of /etc/fstab WARNING: bad format on line 6 of /etc/fstab WARNING: bad format on line 7 of /etc/fstab WARNING: bad format on line 8 of /etc/fstab WARNING: bad format on line 9 of /etc/fstab WARNING: bad format on line 10 of /etc/fstab WARNING: bad format on line 11 of /etc/fstab WARNING: bad format on line 12 of /etc/fstab WARNING: bad format on line 13 of /etc/fstab WARNING: bad format on line 14 of /etc/fstab e2fsck 1.40.11 (17-June-2008) fsck.ext3: No such file or directory while trying to open /dev/c/c^M The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> - fstab 1/33 3% fsck 1.40.11 (17-June-2008) WARNING: bad format on line 2 of /etc/fstab WARNING: bad format on line 4 of /etc/fstab WARNING: bad format on line 5 of /etc/fstab WARNING: bad format on line 6 of /etc/fstab WARNING: bad format on line 7 of /etc/fstab WARNING: bad format on line 8 of /etc/fstab WARNING: bad format on line 9 of /etc/fstab WARNING: bad format on line 10 of /etc/fstab WARNING: bad format on line 11 of /etc/fstab WARNING: bad format on line 12 of /etc/fstab WARNING: bad format on line 13 of /etc/fstab WARNING: bad format on line 14 of /etc/fstab e2fsck 1.40.11 (17-June-2008) fsck.ext3: No such file or directory while trying to open /dev/c/c^M The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ /dev/hdc2 none swap sw 0 0 /dev/hde2 none swap sw 0 0 /dev/hdg2 none swap sw 0 0 proc /proc proc defaults 0 0 /dev/c/c /c ext3 defaults,noatime,user_xattr,acl,user_xattr,user_ /dev/hdc1 / ext3 defaults,noatime 0 1and the nv+ that is up and running:
#----------------------------------------------------------------------------- # <device> <mount> <type> <options> <freq> <pass> #----------------------------------------------------------------------------- /dev/hdc1 / ext2 defaults,noatime 0 proc /proc proc defaults 0 0 /dev/hde2 swap swap defaults 0 0 /dev/hdc2 swap swap defaults 0 0 /dev/hdg2 swap swap defaults 0 0 /dev/c/c /c ext2 defaults,acl,user_xattr,usrqu
the one that is not running shows an ext3 filesystem, whereas the running one shows ext2. As far as i know i never changed this, but what i find more interesting is the long text before the fstab data starts. Even if i do not understand what it tries to tell me
So i rebooted result was the same "Booting done" but only accessible via Putty.
I switched the discs between my 2 NV+ v1. The discs from the nas that still worked are performing a FS check in the new position. The discs from the failed nas are still not accessible. The System says again "booting done" and nothing can be accessed as the raid (X-Raid) is not mounted. I searched the forum but i could not find a howto for mounting the shares from ssh.
Can you please describe what i have to do in putty to mount the shares? I would have enough space to transfer the data to my Ultra6 and then do a factory reset. Did i mention that pulling disc by disc (remaining 3 discs in position) did not lead to a system that booted.
Please tell me howto mount the shares if this is possible. I can restore data from different backups, but i invested a hell of time in sorting and tagging music and pictures.
I had a look at the etc/fstab using vi and found a large discrepancy between the fstab of my two NV+
the nv+ that does not finish boot:
***** File system check performed at Sun Oct 4 13:28:32 CEST 2015 *****
fsck 1.40.11 (17-June-2008)
WARNING: bad format on line 2 of /etc/fstab
WARNING: bad format on line 4 of /etc/fstab
WARNING: bad format on line 5 of /etc/fstab
WARNING: bad format on line 6 of /etc/fstab
WARNING: bad format on line 7 of /etc/fstab
WARNING: bad format on line 8 of /etc/fstab
WARNING: bad format on line 9 of /etc/fstab
WARNING: bad format on line 10 of /etc/fstab
WARNING: bad format on line 11 of /etc/fstab
WARNING: bad format on line 12 of /etc/fstab
WARNING: bad format on line 13 of /etc/fstab
WARNING: bad format on line 14 of /etc/fstab
e2fsck 1.40.11 (17-June-2008)
fsck.ext3: No such file or directory while trying to open /dev/c/c^M
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
- fstab 1/33 3%
fsck 1.40.11 (17-June-2008)
WARNING: bad format on line 2 of /etc/fstab
WARNING: bad format on line 4 of /etc/fstab
WARNING: bad format on line 5 of /etc/fstab
WARNING: bad format on line 6 of /etc/fstab
WARNING: bad format on line 7 of /etc/fstab
WARNING: bad format on line 8 of /etc/fstab
WARNING: bad format on line 9 of /etc/fstab
WARNING: bad format on line 10 of /etc/fstab
WARNING: bad format on line 11 of /etc/fstab
WARNING: bad format on line 12 of /etc/fstab
WARNING: bad format on line 13 of /etc/fstab
WARNING: bad format on line 14 of /etc/fstab
e2fsck 1.40.11 (17-June-2008)
fsck.ext3: No such file or directory while trying to open /dev/c/c^M
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
/dev/hdc2 none swap sw 0 0
/dev/hde2 none swap sw 0 0
/dev/hdg2 none swap sw 0 0
proc /proc proc defaults 0 0
/dev/c/c /c ext3 defaults,noatime,user_xattr,acl,user_xattr,user_
/dev/hdc1 / ext3 defaults,noatime 0 1and the nv+ that is up and running:
#----------------------------------------------------------------------------- # <device> <mount> <type> <options> <freq> <pass> #----------------------------------------------------------------------------- /dev/hdc1 / ext2 defaults,noatime 0 proc /proc proc defaults 0 0 /dev/hde2 swap swap defaults 0 0 /dev/hdc2 swap swap defaults 0 0 /dev/hdg2 swap swap defaults 0 0 /dev/c/c /c ext2 defaults,acl,user_xattr,usrqu
the one that is not running shows an ext3 filesystem, whereas the running one shows ext2. As far as i know i never changed this, but what i find more interesting is the long text before the fstab data starts. Even if i do not understand what it tries to tell me
It seems i am now closer to a solution saving all my data. I rebuild the fstab according to the fstab of my second NV+ and booted it. Raidar recognized it with a dead X-Raid. I did not start the rebuild but i started copying data to my second NV+ and my Readynas Ultra which has enough free space.
After saving all the relevant data i will do a factory reset and rebuild the X-Raid.
:catvery-happy:
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
