NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 - ...
Try powering down, removing the disks (labeling by slot). Then power up, and confirm that RAIDar can see the NAS (no disks status).
If you have access to a windows machine, try testing the disks with vendor tools (Lifeguard for Western Digital, Seatools for Seagate)
FWIW, the guidance in the readynas led language document says:
ReadyNAS OS is booting, this stage should not last for more than 3 minutes. Otherwise, one of disk may be bad or incompatible. SATA backplane is the next to be questioned, and then NAND or SODIMM.
So maybe try running the memory test while the disks are being tested.
Hi Stephen
Thanks for the quick reply.
With drives removed OSX Raidar does indeed see it in "No disks detected" status
Memory test is as far as "checking pat 2" without complaining yet
Guess I need to find a windows machine to borrow to test the drives. Everything here is OSX or Ubuntu.
Mark
If you can't find a windows machine, you should still be able to run a SMART diag with smartctl.
Hi Again
Managed to get a USB<->SATA cable to connect the drives to a Ubuntu machine, and pulled off the following;
All drives pass the SMARTCTL health request.
Drives 1(Left), 2 and 3 show partitions. Drive 4 (right) doesn't.
Now customer doesn't actually know how these were configured. They thought it was standard x-raid across all drives but may have been raid on 3 drives + hot spare. If that'd explain the drive that looks empty.
Is there any way to tell how these were configured?
Thanks
Mark
————————————————————————————————————
Drive 1 Left
[Fri Jun 30 15:31:30 2017] scsi 2:0:0:0: Direct-Access ST2000VN W1H1ND0N PQ: 0 ANSI: 2 CCS
[Fri Jun 30 15:31:30 2017] sd 2:0:0:0: Attached scsi generic sg2 type 0
[Fri Jun 30 15:31:30 2017] sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[Fri Jun 30 15:31:30 2017] sd 2:0:0:0: [sdb] Write Protect is off
[Fri Jun 30 15:31:30 2017] sd 2:0:0:0: [sdb] Mode Sense: 00 38 00 00
[Fri Jun 30 15:31:30 2017] sd 2:0:0:0: [sdb] Asking for cache data failed
[Fri Jun 30 15:31:30 2017] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[Fri Jun 30 15:31:30 2017] sdb: sdb1 sdb2 sdb3 < sdb5 >
[Fri Jun 30 15:31:30 2017] sd 2:0:0:0: [sdb] Attached SCSI disk# fdisk -l /dev/sdb
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 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
# smartctl -H /dev/sdb
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.8.0-45-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————————————————————————————————————
Drive 2 Middle-Left
[Fri Jun 30 15:33:57 2017] scsi 2:0:0:0: Direct-Access ST2000VN W1H1NWYC PQ: 0 ANSI: 2 CCS
[Fri Jun 30 15:33:57 2017] sd 2:0:0:0: Attached scsi generic sg2 type 0
[Fri Jun 30 15:33:57 2017] sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[Fri Jun 30 15:33:57 2017] sd 2:0:0:0: [sdb] Write Protect is off
[Fri Jun 30 15:33:57 2017] sd 2:0:0:0: [sdb] Mode Sense: 00 38 00 00
[Fri Jun 30 15:33:57 2017] sd 2:0:0:0: [sdb] Asking for cache data failed
[Fri Jun 30 15:33:57 2017] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[Fri Jun 30 15:33:57 2017] sdb: sdb1 sdb2 sdb3 < sdb5 >
[Fri Jun 30 15:33:57 2017] sd 2:0:0:0: [sdb] Attached SCSI disk
# fdisk -l /dev/sdb
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 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# smartctl -H /dev/sdb
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.8.0-45-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————————————————————————————————————
Drive 3 Middle Right
[Fri Jun 30 15:36:02 2017] scsi 2:0:0:0: Direct-Access ST2000VN W1H1P1KZ PQ: 0 ANSI: 2 CCS
[Fri Jun 30 15:36:02 2017] sd 2:0:0:0: Attached scsi generic sg2 type 0
[Fri Jun 30 15:36:02 2017] sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[Fri Jun 30 15:36:02 2017] sd 2:0:0:0: [sdb] Write Protect is off
[Fri Jun 30 15:36:02 2017] sd 2:0:0:0: [sdb] Mode Sense: 00 38 00 00
[Fri Jun 30 15:36:02 2017] sd 2:0:0:0: [sdb] Asking for cache data failed
[Fri Jun 30 15:36:02 2017] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[Fri Jun 30 15:36:02 2017] sdb: sdb1 sdb2 sdb3 < sdb5 >
[Fri Jun 30 15:36:02 2017] sd 2:0:0:0: [sdb] Attached SCSI disk# fdisk -l /dev/sdb
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 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# fdisk -l /dev/sdb
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 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
root@bluestripe:~# smartctl -H /dev/sdb
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.8.0-45-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————————————————————————————————————
Drive 4 Right
[Fri Jun 30 15:37:36 2017] scsi 2:0:0:0: Direct-Access ST2000VN W1H1N9Q3 PQ: 0 ANSI: 2 CCS
[Fri Jun 30 15:37:36 2017] sd 2:0:0:0: Attached scsi generic sg2 type 0
[Fri Jun 30 15:37:36 2017] sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[Fri Jun 30 15:37:37 2017] sd 2:0:0:0: [sdb] Write Protect is off
[Fri Jun 30 15:37:37 2017] sd 2:0:0:0: [sdb] Mode Sense: 00 38 00 00
[Fri Jun 30 15:37:37 2017] sd 2:0:0:0: [sdb] Asking for cache data failed
[Fri Jun 30 15:37:37 2017] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[Fri Jun 30 15:37:37 2017] sd 2:0:0:0: [sdb] Attached SCSI disk
# fdisk -l /dev/sdb
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes# smartctl -H /dev/sdb
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.8.0-45-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: PASSEDThe 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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
