NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DOLMark
Jun 28, 2017Aspirant
ReadyNAS NV+ Stuck on Booting
Hi Got a clients NV+ that'd hung completely. It responded to pings but nothing else. Have rebooted it and I get; - All Drives led's green - Can Ping device - No HTTP access - ...
StephenB
Jun 30, 2017Guru - Experienced User
The NV+ uses raid-4 (a parity disk instead of distributed parity blocks). The parity is written to an unpartitioned section of the disk.
So this is consistent with the old XRAID.
The NV+ has a boot menu option to skip the volume check on startup. Did you try that? As a reminder, be sure to shut down the NAS before reinserting the disk drives.
DOLMark
Jun 30, 2017Aspirant
Hi
Yup, tried the skip FS Checks and it just hung at "Booting ...". I gave it about 30 mins before pulling the power.
Mark
- StephenBJun 30, 2017Guru - Experienced User
You can try mounting the array on the ubuntu system - there is a guide here: http://home.bott.ca/webserver/?p=306
- DOLMarkJul 17, 2017Aspirant
Hi
Well after a brief pause to get the right cables etc to arrive so I could get the 4 drives in to another Ubuntu server everything's looking promising... although puzzling :-)
So I now have the existing 4 drive array mounted under standard Ubuntu. No drive errors that I can see.
(command line walk through and details below)
So The drives look ok. Mount ok. I'm still none the wiser about why the redynas wont go past " Checking FS ..."
Dare I ask; "Next suggestion?"
Mark
For the benefit of furture visitors and diagnostics sake;
OS is Ubuntu Workstation v16.10
SDA = Existing Boot drive
SDB to SDE = Drives 1 (left) to 4 (right) from ReadyNAS NV+
From root / sudo user;
# apt-get install fuseext2 lvm2 smart
**** reboot ****
**** check the smart status again, previously was via USB not direct attach ***
# smartctl -H /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.8.0-22-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED# smartctl -H /dev/sdc
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.8.0-22-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED# smartctl -H /dev/sdd
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.8.0-22-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED# smartctl -H /dev/sde
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.8.0-22-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED*** All looks ok there, lets see what the partitions look like ***
# fdisk -l
*** SDA (boot drive) and others removed ***
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00000000Device Boot Start End Sectors Size Id Type
/dev/sdb1 32 4096031 4096000 2G 83 Linux
/dev/sdb2 4096032 4608031 512000 250M 82 Linux swap / Solaris
/dev/sdb3 4608032 3906992335 3902384304 1.8T 5 Extended
/dev/sdb5 4608040 3906992335 3902384296 1.8T 8e Linux LVM
Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00000000Device Boot Start End Sectors Size Id Type
/dev/sdc1 32 4096031 4096000 2G 83 Linux
/dev/sdc2 4096032 4608031 512000 250M 82 Linux swap / Solaris
/dev/sdc3 4608032 3906992335 3902384304 1.8T 5 Extended
/dev/sdc5 4608040 3906992335 3902384296 1.8T 8e Linux LVM
Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00000000Device Boot Start End Sectors Size Id Type
/dev/sdd1 32 4096031 4096000 2G 83 Linux
/dev/sdd2 4096032 4608031 512000 250M 82 Linux swap / Solaris
/dev/sdd3 4608032 3906992335 3902384304 1.8T 5 Extended
/dev/sdd5 4608040 3906992335 3902384296 1.8T 8e Linux LVM
Disk /dev/sde: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/c-c: 5.5 TiB, 5988627251200 bytes, 11696537600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
c c -wi-a----- 5.45t# lvdisplay /dev/c
--- Logical volume ---
LV Path /dev/c/c
LV Name c
VG Name c
LV UUID sIWnvX-Uphi-eWDp-6J0y-qyZ8-h8e2-Xqk0cR
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 0
LV Size 5.45 TiB
Current LE 178475
Segments 3
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:0
*** -o ro to mount read only ***# fuseext2 -o ro -o sync_read /dev/c/c /mnt
fuse-umfuse-ext2: version:'0.4', fuse_version:'29' [main (fuse-ext2.c:331)]
fuse-umfuse-ext2: enter [do_probe (do_probe.c:30)]
fuse-umfuse-ext2: leave [do_probe (do_probe.c:55)]
fuse-umfuse-ext2: opts.device: /dev/c/c [main (fuse-ext2.c:358)]
fuse-umfuse-ext2: opts.mnt_point: /mnt [main (fuse-ext2.c:359)]
fuse-umfuse-ext2: opts.volname: c [main (fuse-ext2.c:360)]
fuse-umfuse-ext2: opts.options: ro,sync_read [main (fuse-ext2.c:361)]
fuse-umfuse-ext2: parsed_options: sync_read,ro,fsname=/dev/c/c [main (fuse-ext2.c:362)]
fuse-umfuse-ext2: mounting read-only [main (fuse-ext2.c:378)]# ls /mnt
aquota.group aquota.user backup home lost+found mediaSo that worked :-)
- Marty_MJul 18, 2017NETGEAR Employee Retired
Hello DOLMark,
It does appear the NAS chassis is ok and the hard drives did passed the test. Can you still set the NAS chassis to telnet/tech support mode? The concern you have described requires assistance from the engineers and/or higher tier who can remote in to the NAS and fix this from the backend.
Unfortunately, It shows on your records that the support warranty of your product is already expired. You may try contacting support center and avail a support contract. That should allow you to extend the support for your product so they can escalate your issue to L3 or patiently wait for anyone in the community who has the knowledge in the SSH commands and fixing some issues from the backend.
Regards,
Marty_M
NETGEAR Community Team
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!