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 the message booting on the display and it stayed for hours. I restarted the NV+ and found the system stuck again in booting. I did a OS reinstall and the system booted and performed a FS check. Raidar showed 100%checked and all HDD LEDs in green. I restarted and the system stucked again.
I tried to check if the HDDs are causing this and removed slot 1 booted, no change, reinserted, removed slot 2, and so on. Repeated this for all 4 slots. Booting never finished.
The result now is: System starts, Booting and after some minutes it shows "Booting, done". I can reach it via putty, did a check of the smart info of the HDDs and found nothing obvious ("smartctl"). Since some days,after every boot i receive now a message that shares are not accessible (media, backup, music, etc.).
Any idea how i can access my data again or how to rework this?
I have a second NV+ and a Ultra6 available (ultra6 will not help in this case). The disks in the NV+ are WD20EZRX, the green ones but i switched them all to idle time 300 and load cycle count did not increase significantly during the last years.
Can i transfer the disks to the 2nd NV+ and try if it is running there? If not please give me an information how i can access my data again.
Thank you in advance
Readynas NV+ v1 with 4 WD20EZRX and X-Raid latest firmware 4.14
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
9 Replies
Replies have been turned off for this discussion
You can migrate the disks to the other NAS for testing. Just label the disks by system/slot, and migrate powered down.
But since you do have ssh still working, I suggest first logging in and entering
df . -h
df . -i
I am thinking a full OS partition
Thank you so far,
i will try this as soon as i am at home
Hello,
i tried the df command and got a response, but this says nothing to me:
nas-1:/# df . -h
Filesystem Size Used Avail Use% Mounted on
- 1.9G 1.9G 66M 97% /
nas-1:/# df . -i
Filesystem Inodes IUsed IFree IUse% Mounted on
- 128000 14543 113457 12% /I see that 97% is almost full, but the NAS has by far more diskspace. So i assume this is the room for the OS. Any idea how to correct this.
ClausH42 wrote:
Hello,
i tried the df command and got a response, but this says nothing to me:
nas-1:/# df . -h
Filesystem Size Used Avail Use% Mounted on
- 1.9G 1.9G 66M 97% /
nas-1:/# df . -i
Filesystem Inodes IUsed IFree IUse% Mounted on
- 128000 14543 113457 12% /I see that 97% is almost full, but the NAS has by far more diskspace. So i assume this is the room for the OS. Any idea how to correct this.
The OS partition on the NV+ is only 2 GB. Normally it is around 20-25% full. 97% full certainly creates performance issues.
The next step is to find out where space is going. Look in /var/log and /var/cache first. It they are not the culprit, you'll need to poke around until you find them.
You can truncate run-away logs using "echo > filename"
You should be able to simply delete files in the cache, but don't delete folders. You can delete everything in /var/cache/minidlna/art_cache/c/ (including folders)
If you use DLNA, then there is an add-on to shift its cache to the "c" volume. If you want a link to that, let us know.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
