NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS Duo v1 HDD replacement problems
Computer: Ubuntu 14.04 LTS laptop
Device: Netgear ReadyNAS Duo v1
HDD1: Seagate Barracuda 72000.12 ST31000528AS 1TB (Firmware: CC38)
HDD2: Seagate Barracuda ST2000DM001 2TB (Firmware: CC29)
HDD3: Seagate Barracuda ST2000DM001 2TB (Firmware: CC29)
I use my ReadyNAS for home use. It does not get a lot of use since I mainly use it for backup and general storage. It came with HDD1. Since at the time I purchased it I was short on funds, I did not have a second disk for redundancy. However, I recently started getting SMART self-assessment test errors like the one below. Fortunately, I still have access to the disk and all my data seems to be intact. I tried downloading the system logs, but whenever I do, the unit becomes indefinitely unresponsive and I have to cut power and even do a OS re-install from the boot menu.
System log message(s):
After referencing the HDD HCL for my model, I purchased HDD2 from Amazon since it was listed with a very good rating by several reviews and at a great price. I hot-swapped it into the unit and the following messages were reported in the system log:
System log message(s):
As you can see, the unit detected the new disk and successfully performed a disk initialization and RAID sync. I kept HDD1 (with the SMART errors) in the unit with the new HDD2 as the RAID volume. However, within 24 hours, there was a disk fail event on HDD2 as reported in the system log (shown below).
System log message(s):
At this point, the disk was completely unreadable. I searched the forum and even called Seagate support to help determine if perhaps I got a lame disk or if something else was going on, but to no avail. The only bad thing I could find on the forum about that particular Seagate model was that there seemed to be a problem with those with firmware version CC26 (however, the version of the one I purchased was CC29). So, thinking perhaps it was just a lame disk (since it had a very good rating and was reviewed by so many), I ordered a replacement of the same from Amazon. Coincidently or not, the same exact thing happened with the replacement (HDD3).
After this happened, I ordered a USB to SATA/IDE adapter in order to try to figure out what was going on. In viewing HDD2 and HDD3 in Gparted (in Ubuntu), they was displayed as 'unallocated' with a read exclamation point icon next to it. With nothing to lose, I tried creating a partition table and the icon went away. So, I tried hot-swapping it into the unit to see if it would go through the initialization and RAID sync processes again, which it did. This time, however, I removed HDD1 from the unit in order to see if the errors on this disk was causing the failed disk event on HDD2. Of course, when I did this, RAIDar/FrontView showed a flashing yellow LED (as well as the disk make and model) and a flashing green LED for disk 1 on the device. I could access the unit through RAIDar/FrontView and a file browser. I left the unit (with just HDD2 in slot 2 and no disk in slot 1) that way for 3 days and no errors occurred. Since for both HDD2 and HDD3, they had both reported disk fail events within 24 hours of completing the initialization/syncing process, I figured that having lasted 3 days with no errors was a good indication that HDD1 was cause of the disk fail events. So, with HDD2 still in slot 2 of the unit, I hot-swapped HDD3 (after creating a partition table on this drive as I had on HDD2) into slot 1 figuring that it would go through the initialization/syncing process and I would be off and running. However, after doing so, the unit did not detect HDD3. I tried rebooting, both with HDD3 plugged in at bootup and hot-swapping after bootup, but no dice. The power button on the unit would blink and all four LEDs were also blinking in a repetitive pattern (2 successive slow blinks followed by 3 successive fast blinks). The unit was not detected by either RAIDar or FrontView. At this point, I removed both HDD2 and HDD3 and put HDD1 back in hopes of at least being able to detect the unit. But, even with the original disk back in, I could no longer detect it. I tried viewing HDD1 in Gparted to help determine what its status was and I've attached a screenshot. In viewing HDD2 and HDD3 in Gparted, they are both back at the 'unallocated' state with the exclamation point icon next to them. When I first put HDD1 in the USB to SATA/IDE adapter prior to viewing it in GParted, I got the popup message shown below. I've also attached a portion of the syslog.
(Don't know how to attach or insert images so Gparted screen looks like below.)
Popup message when I connected HDD1 to laptop via USB-to-SATA adapter
Unable to mount 2.1 GB Volume:
Error mounting /dev/sdb1 at /media/john/ce8e851f-0c2a-4b1f-82da-b402eafa2896: Command-line `mount -t "ext3" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb1" "/media/john/ce8e851f-0c2a-4b1f-82da-b402eafa2896"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
syslog after connecting HDD1 and HDD2 to laptop
sdb = HDD1
sdc = HDD2
At this point I've spent tens of hours on this problem and at at my wits end as how to resolve it. Although I've search high and low on the Internet through documentation, blogs, forums, and wikis, I am not able to find any answers. If money were no object, I'd buy a newer model unit with support for newer model HDDs. However, that is not an option for me right now.
After all I've done, here are some outstanding questions that I have:
As far as my knowledge and experience, I have spent 15 years as a software engineer in the aerospace and defense industry. I am much more knowledgeable with the Windows OS and am somewhere between a beginner and intermediate when it comes to Linux-based systems. With all that said, I am open to any and all help. Thanks in advance for your anticipated help!
John
Some other notes...
I realize that the new disks I bought are twice the capacity as the one that originally came with the unit. After going through the HDD HCL to find a replacement disk, I found that many of the models are no longer available. Taking into consideration that the original disk was at 45% capacity of its 1TB, I decided to go to a 2 TB capacity since I didn't know how long the remaining models on the HCL were going to be available for my unit model. The Seagate model I chose was by far the best choice taking into consideration capacity, RPMs, transfer rate, cache size, price and user rating. Its only caveat was only having a 1 year warranty. If there is some other HDD model that someone else would recommend for my model of ReadyNAS that has an affordable price (preferable under $100), I'm open to suggestions. I also took into consideration, selling my current unit and going with a newer model if it was reasonably affordable compared to further investing in the one I currently have. However, that didn't pan out to be an option. I also considered staying with a 1TB capacity in order to keep costs down. After going through the HCL, that same Seagate model (but at the 1TB capacity) came out to be the best option using the same parameters mentioned above. However, my concern was that I would encounter the same problems that I have encountered with the 2TB capacity.
Device: Netgear ReadyNAS Duo v1
HDD1: Seagate Barracuda 72000.12 ST31000528AS 1TB (Firmware: CC38)
HDD2: Seagate Barracuda ST2000DM001 2TB (Firmware: CC29)
HDD3: Seagate Barracuda ST2000DM001 2TB (Firmware: CC29)
I use my ReadyNAS for home use. It does not get a lot of use since I mainly use it for backup and general storage. It came with HDD1. Since at the time I purchased it I was short on funds, I did not have a second disk for redundancy. However, I recently started getting SMART self-assessment test errors like the one below. Fortunately, I still have access to the disk and all my data seems to be intact. I tried downloading the system logs, but whenever I do, the unit becomes indefinitely unresponsive and I have to cut power and even do a OS re-install from the boot menu.
System log message(s):
Disk 1 did not pass SMART self-assessment test. Please replace this disk as soon as possible. Growing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk.
After referencing the HDD HCL for my model, I purchased HDD2 from Amazon since it was listed with a very good rating by several reviews and at a great price. I hot-swapped it into the unit and the following messages were reported in the system log:
System log message(s):
Fri Aug 29 01:29:59 CDT 2014 RAID sync finished on volume C. The volume is now fully redundant.
Thu Aug 28 21:22:33 CDT 2014 RAID sync started on volume C.
Thu Aug 28 21:22:27 CDT 2014 Disk initialization successfully finished.
Thu Aug 28 17:48:08 CDT 2014 Disk initialization started. The estimated time of completion is 17 hour(s) and 39 minute(s), at which time you will be notified via email. You can also check the progress in Frontview in the Volumes -> RAID Settings tab. Please do not shutdown the system while the initialization is in progress.
Thu Aug 28 17:47:52 CDT 2014 Disk add event occurred on SATA channel 2.
Thu Aug 28 16:12:15 CDT 2014 System is up.
As you can see, the unit detected the new disk and successfully performed a disk initialization and RAID sync. I kept HDD1 (with the SMART errors) in the unit with the new HDD2 as the RAID volume. However, within 24 hours, there was a disk fail event on HDD2 as reported in the system log (shown below).
System log message(s):
Sat Aug 30 19:50:54 CDT 2014 A SATA reset has been performed on one or more of your disks that may have affected the RAID parity integrity. It is recommended that you perform a RAID volume resync from the RAID Settings tab ( accessible in the Volumes page => Volume tab in FrontView ). The resync process will run in the background, and you can continue to use the ReadyNAS in the meantime.
Sat Aug 30 19:50:37 CDT 2014 Disk fail event occurred on SATA channel 2. If the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead.
At this point, the disk was completely unreadable. I searched the forum and even called Seagate support to help determine if perhaps I got a lame disk or if something else was going on, but to no avail. The only bad thing I could find on the forum about that particular Seagate model was that there seemed to be a problem with those with firmware version CC26 (however, the version of the one I purchased was CC29). So, thinking perhaps it was just a lame disk (since it had a very good rating and was reviewed by so many), I ordered a replacement of the same from Amazon. Coincidently or not, the same exact thing happened with the replacement (HDD3).
After this happened, I ordered a USB to SATA/IDE adapter in order to try to figure out what was going on. In viewing HDD2 and HDD3 in Gparted (in Ubuntu), they was displayed as 'unallocated' with a read exclamation point icon next to it. With nothing to lose, I tried creating a partition table and the icon went away. So, I tried hot-swapping it into the unit to see if it would go through the initialization and RAID sync processes again, which it did. This time, however, I removed HDD1 from the unit in order to see if the errors on this disk was causing the failed disk event on HDD2. Of course, when I did this, RAIDar/FrontView showed a flashing yellow LED (as well as the disk make and model) and a flashing green LED for disk 1 on the device. I could access the unit through RAIDar/FrontView and a file browser. I left the unit (with just HDD2 in slot 2 and no disk in slot 1) that way for 3 days and no errors occurred. Since for both HDD2 and HDD3, they had both reported disk fail events within 24 hours of completing the initialization/syncing process, I figured that having lasted 3 days with no errors was a good indication that HDD1 was cause of the disk fail events. So, with HDD2 still in slot 2 of the unit, I hot-swapped HDD3 (after creating a partition table on this drive as I had on HDD2) into slot 1 figuring that it would go through the initialization/syncing process and I would be off and running. However, after doing so, the unit did not detect HDD3. I tried rebooting, both with HDD3 plugged in at bootup and hot-swapping after bootup, but no dice. The power button on the unit would blink and all four LEDs were also blinking in a repetitive pattern (2 successive slow blinks followed by 3 successive fast blinks). The unit was not detected by either RAIDar or FrontView. At this point, I removed both HDD2 and HDD3 and put HDD1 back in hopes of at least being able to detect the unit. But, even with the original disk back in, I could no longer detect it. I tried viewing HDD1 in Gparted to help determine what its status was and I've attached a screenshot. In viewing HDD2 and HDD3 in Gparted, they are both back at the 'unallocated' state with the exclamation point icon next to them. When I first put HDD1 in the USB to SATA/IDE adapter prior to viewing it in GParted, I got the popup message shown below. I've also attached a portion of the syslog.
(Don't know how to attach or insert images so Gparted screen looks like below.)
Partition File System Size Used Unused Flags
/dev/sdb1 ext3 1.95 GiB 1.95 GiB 6.44 MiB
/dev/sdb2 :!: unknown 250.00 MiB -- --
/dev/sdb3 extended 929.11 GiB -- --
/dev/sdb5 :!: lvm2 pv 929.11 GiB -- -- lvm
unallocated unallocated 211.39 MiB -- --
Popup message when I connected HDD1 to laptop via USB-to-SATA adapter
Unable to mount 2.1 GB Volume:
Error mounting /dev/sdb1 at /media/john/ce8e851f-0c2a-4b1f-82da-b402eafa2896: Command-line `mount -t "ext3" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb1" "/media/john/ce8e851f-0c2a-4b1f-82da-b402eafa2896"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
syslog after connecting HDD1 and HDD2 to laptop
sdb = HDD1
sdc = HDD2
[ 506.130228] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[ 506.130236] EXT4-fs (sdb1): bad block size 16384
[ 894.326698] usb 1-1.1: USB disconnect, device number 4
[ 909.743316] usb 1-1.1: new high-speed USB device number 5 using ehci-pci
[ 909.837368] usb 1-1.1: New USB device found, idVendor=152d, idProduct=0551
[ 909.837374] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 909.837379] usb 1-1.1: Product: USB to ATA/ATAPI Bridge
[ 909.837382] usb 1-1.1: Manufacturer: JMicron
[ 909.837386] usb 1-1.1: SerialNumber: 34106FFFFFFF
[ 909.838140] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[ 909.838274] scsi6 : usb-storage 1-1.1:1.0
[ 911.437580] scsi 6:0:0:0: Direct-Access ORIC0 8628US3-C PQ: 0 ANSI: 2 CCS
[ 911.438100] scsi 6:0:0:1: Direct-Access ORIC0 8628US3-C PQ: 0 ANSI: 2 CCS
[ 911.439203] sd 6:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 911.440198] sd 6:0:0:0: [sdb] Write Protect is off
[ 911.440202] sd 6:0:0:0: [sdb] Mode Sense: 28 00 00 00
[ 911.440702] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 911.441944] sd 6:0:0:1: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 911.442100] sd 6:0:0:1: Attached scsi generic sg3 type 0
[ 911.442108] sd 6:0:0:0: [sdb] No Caching mode page found
[ 911.442113] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 911.443950] sd 6:0:0:1: [sdc] Write Protect is off
[ 911.443956] sd 6:0:0:1: [sdc] Mode Sense: 28 00 00 00
[ 911.446064] sd 6:0:0:1: [sdc] No Caching mode page found
[ 911.446072] sd 6:0:0:1: [sdc] Assuming drive cache: write through
[ 911.450837] sd 6:0:0:0: [sdb] No Caching mode page found
[ 911.450844] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 911.451839] sd 6:0:0:1: [sdc] No Caching mode page found
[ 911.451843] sd 6:0:0:1: [sdc] Assuming drive cache: write through
[ 911.497304] sdb: sdb1 sdb2 sdb3 < sdb5 >
[ 911.497673] sdc: unknown partition table
[ 911.501276] sd 6:0:0:1: [sdc] No Caching mode page found
[ 911.501279] sd 6:0:0:1: [sdc] Assuming drive cache: write through
[ 911.501282] sd 6:0:0:1: [sdc] Attached SCSI disk
[ 911.503541] sd 6:0:0:0: [sdb] No Caching mode page found
[ 911.503544] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 911.503547] sd 6:0:0:0: [sdb] Attached SCSI disk
[ 912.082281] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[ 912.082289] EXT4-fs (sdb1): bad block size 16384
At this point I've spent tens of hours on this problem and at at my wits end as how to resolve it. Although I've search high and low on the Internet through documentation, blogs, forums, and wikis, I am not able to find any answers. If money were no object, I'd buy a newer model unit with support for newer model HDDs. However, that is not an option for me right now.
After all I've done, here are some outstanding questions that I have:
- After finally getting HDD2 to seemly work with my synced data on it (and plugged into slot 2 of the unit), what is the correct procedure for putting in HDD3 in order to have a properly redundant system?
- When HDD1 started reporting SMART self-assessment tests errors, is there a way to rescue the disk to a point where it still may be used to some degree?
- Why does my unit indefinitely hang when I tried to download all logs from within FrontView? Is there an alternative way to access the logs so that I can send them to support when need be?
As far as my knowledge and experience, I have spent 15 years as a software engineer in the aerospace and defense industry. I am much more knowledgeable with the Windows OS and am somewhere between a beginner and intermediate when it comes to Linux-based systems. With all that said, I am open to any and all help. Thanks in advance for your anticipated help!
John
Some other notes...
I realize that the new disks I bought are twice the capacity as the one that originally came with the unit. After going through the HDD HCL to find a replacement disk, I found that many of the models are no longer available. Taking into consideration that the original disk was at 45% capacity of its 1TB, I decided to go to a 2 TB capacity since I didn't know how long the remaining models on the HCL were going to be available for my unit model. The Seagate model I chose was by far the best choice taking into consideration capacity, RPMs, transfer rate, cache size, price and user rating. Its only caveat was only having a 1 year warranty. If there is some other HDD model that someone else would recommend for my model of ReadyNAS that has an affordable price (preferable under $100), I'm open to suggestions. I also took into consideration, selling my current unit and going with a newer model if it was reasonably affordable compared to further investing in the one I currently have. However, that didn't pan out to be an option. I also considered staying with a 1TB capacity in order to keep costs down. After going through the HCL, that same Seagate model (but at the 1TB capacity) came out to be the best option using the same parameters mentioned above. However, my concern was that I would encounter the same problems that I have encountered with the 2TB capacity.
16 Replies
- I wouldn't have recommended those disks. The WD RED or the SeaGate NAS drives could be worth considering.
Do you recall what version of RAIDiator is running on your NAS unit?
Are you able to try backing up your data, do a factory reset (wipes all data, settings, everything) and restore your data from backup?
As for recovering your data using an ordinary x86 Linux machine see e.g. http://home.bott.ca/webserver/?p=306
Using X-RAID disk 2 is typically the dedicated parity disk. That's why it didn't have any partitions on it.
Newer models have distributed parity with partition tables on all disks. - Thanks for your prompt reply!
I wouldn't have recommended those disks. The WD RED or the SeaGate NAS drives could be worth considering.
As I mentioned in my post, I searched for a replacement disk based on the make and models listed in the HCL. The Seagate Barracuda 2TB ST2000DM001 had good specs, had a 4 out of 5 star rating by over 3 thousand user reviews, and was only about $85. If the disk really isn't compatible for the Duo, it shouldn't be on the list. If you need to use a different type of drive based on if it's the primary drive or the secondary (RAID) drive, it shold say so in the documentation. And, speaking of the Netgear documentation, I find it very lacking. Especially since this model is geared towards home use, I don't think it's written very well for the lay person. The average Joe most likely won't be spending hours searching through forums posts. Even with my technical background, I find it cumbersome in finding even basic information. Sorry, I digress!Do you recall what version of RAIDiator is running on your NAS unit?
Sorry, I forgot to include the version of RAIDiator my unit is running. It is running RAIDiator version 4.1.13.Are you able to try backing up your data, do a factory reset (wipes all data, settings, everything) and restore your data from backup?
As I mentioned before, I bought the unit with just one 1TB hard disk (HDD1). Although I would have like to added a second disk after I purchased it, I've been out of work since 2008 due to health issues. Therefore, there hasn't been the funds for the purchase. It wasn't until I recently started getting the SMART self-assessment test errors that I looked at getting a second disk for the unit. Right or wrong, that's the situation I'm in.As for recovering your data using an ordinary x86 Linux machine see e.g. http://home.bott.ca/webserver/?p=306
I went to the website and followed the instructions, however, I got the following messages:
root@john-HP-Pavilion-dm4:/home/john# sudo su
root@john-HP-Pavilion-dm4:/home/john# mkdir /mnt/lvm
root@john-HP-Pavilion-dm4:/home/john# fuseext2 -o ro -o sync_read /dev/sdc1 /mnt/lvm/
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/sdc1 [main (fuse-ext2.c:358)]
fuse-umfuse-ext2: opts.mnt_point: /mnt/lvm/ [main (fuse-ext2.c:359)]
fuse-umfuse-ext2: opts.volname: [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/sdc1 [main (fuse-ext2.c:362)]
fuse-umfuse-ext2: mounting read-only [main (fuse-ext2.c:378)]
root@john-HP-Pavilion-dm4:/home/john#Using X-RAID disk 2 is typically the dedicated parity disk. That's why it didn't have any partitions on it.
I never viewed the disk in Gparted to see what it looked like. However, I observed two things. The first thing I observed was with the original disk in slot 1 and after the secondary disk had successfully initialized and synced, the secondary disk failed within 24 hours, as I mentioned earlier. After this occurred, I did view the secondary disk in Gparted and it only showed an 'unallocated' entry with a red exclamation point icon next to it. This same thing happened again with a different new secondary disk. The second thing I observed was on my third attempt. After the secondary disk had successfully initialized and synced, I removed the original disk in slot 1 to see if my data on the NAS was still accessible through a file browser with just the secondary disk in the unit, and if it would still generate a disk fail event as it had the previous two times. I guess my assumption was that the secondary drive had a full copy of the primary drive, and therefore, it really didn't matter what disk was in what slot – one was always the mirror of the other. That's why, after not seeing another disk fail event after 3 days after removing the original disk in slot 1, I thought if I hot-swapped my other new disk in slot 1, it would properly initialize and sync as did the other disk did in slot 2.Newer models have distributed parity with partition tables on all disks.
As I said, money is tight so I'm trying to make the most of what I already have with the least amount of additional costs. In the end, I want my system to fully redundant and have the know-how to properly replace a disk the next time I have a problem with one of the disks (God forbid!), whether it's in slot 1 or slot 2.
By the way, there are some other questions I have that I forgot to add to my original post.- Is the procedure different for replacing a disk depending on if it's in slot 1 or slot 2?
- Are there utilities that enable you to possibly fix disk errors?
Thanks!
John - Oh, just to reinterate, the original disk was a 1TB capacity disk. Not only do I want to have a redundant unit, I want to expand the storage capacity to 2TB. Since my unit is now considered a legacy model and the number of HD choices are seemly dwindling, I figure in order to extend its longevity, I better expand its capacity now before I have no other choice but to buy a newer model. So, please keep this in mind with any instructions that are given.
(1) add redundancy
(2) expand capacity from 1TB to 2TB
Thanks! soaring-eagle wrote:
Sorry, I forgot to include the version of RAIDiator my unit is running. It is running RAIDiator version 4.1.13.
That is the latest for your unit.soaring-eagle wrote:
root@john-HP-Pavilion-dm4:/home/john# sudo su
root@john-HP-Pavilion-dm4:/home/john# mkdir /mnt/lvm
root@john-HP-Pavilion-dm4:/home/john# fuseext2 -o ro -o sync_read /dev/sdc1 /mnt/lvm/
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/sdc1 [main (fuse-ext2.c:358)]
fuse-umfuse-ext2: opts.mnt_point: /mnt/lvm/ [main (fuse-ext2.c:359)]
fuse-umfuse-ext2: opts.volname: [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/sdc1 [main (fuse-ext2.c:362)]
fuse-umfuse-ext2: mounting read-only [main (fuse-ext2.c:378)]
root@john-HP-Pavilion-dm4:/home/john#
The instructions on the link were not for mounting the 2GB OS partition, but rather for mounting the data volume.soaring-eagle wrote:
I did view the secondary disk in Gparted and it only showed an 'unallocated' entry
The parity disk appears to be blank to your PC, but it isn't.soaring-eagle wrote:
Is the procedure different for replacing a disk depending on if it's in slot 1 or slot 2?
Best to remove and replace the failed disk while the NAS is on.soaring-eagle wrote:
Are there utilities that enable you to possibly fix disk errors?
Disks when they e.g. reallocate sectors will no longer uses the bad sectors. If a disk is having lots of errors then it is failing.- I bought a WD20EFRX NAS HDD and that has been working without problems.
I was wondering if the 2 drive bay slots function differently. I thought that the Duo could be configured in one of two ways: (1) the first with the total capacity being (size of HDD1) + (size of HDD2) and no redundancy and (2) the other being (the smaller size of HDD1 or HDD2) times 2 with redundancy. However, I don't see anyway of changing the configuration to no redundancy.
With that said, since it seems to always be configured with XRAID redundancy, does drive bay slot 1 always function as a "desktop" HDD and drive bay slot 2 always function as a "NAS" HDD (formatted with the XRAID redundancy)? Whether this is the case or not, I'm not sure how to restore the system if either HDD1 fails or if HDD2 fails. I haven't come across any procedures that explain the process of recovering from either one of those types of failures.
Also, if the two drive bays slots do indeed function differently (slot 1 as "desktop" HDD and slot 2 as "NAS" HDD), then would the Seagate ST2000DM001 HDD that I was trying to use in slot 2 work properly in slot 1 (since it is listed in the Hardware Compatibility List)?
My Duo originally came configured with one 1TB HDD. My first task was to add a second HDD for redundancy. In doing so I wanted to also upgrade the storage capacity to 2TB, so the second HDD I bought was 2TB. From reading the documentation, I understand that in a redundant system, the total capacity is going to be limited by the smaller of the two HDDs (in this case the original 1TB HDD). After the second redundant HDD fully installed (initialized and sync'd) and when the original disk is replaced with a 2TB HDD, it is my understanding from the documentation that the system will detect that both HDDs are 2TB and will report the total capacity as 2TB. Am I correct in my understanding?
In summary (and to be clear what I'm asking),- Do the two drive bay slots in the ReadyNAS Duo v1 function differently, more specifically does slot 1 always function as "desktop" HDD (containing OS + data) and slot 2 always function as "NAS" HDD (containing XRAID redundancy of "desktop" HDD)?
- If the answer to the above question is "yes", then would the Seagate S2000DM001 HDD I first tried in slot 2 working properly if used in slot 1 instead and using my new Western Digital WD20EFRX NAS HDD slot 2?
- What are the procedures for restoring the system when either of the HDDs in slot 1 or slot 2 fail?
- In going from a system configured with (HDD1 = 1TB) and (HDD2 = 2TB) to a system configured with (HDD1 = 1TB) and (HDD2 = 2TB), will the system detect and report that the total storage capacity to be 2TB?
Thanks in advance!
John - The second disk installed regardless of slot (or disk 2 if factory done with two disks installed) is the dedicated parity disk. Both disks have the OS & data on them.
If the SeaGate wasn't working before I'm not sure I would want to try using it again. I don't see the point in moving disks around to different slots.
The NAS should be able to handle either disk failing. You can replace the dead disk with a new disk to rebuild the RAID.
You will need both disks to be 2TB for the volume to expand. - I now have 2 WD Red 2TB HDDs in my unit, however, the total volume allocation space is still shown to be ~1TB. How do you get the unit to recognize the full ~2TB size?
- is your volume status redundant? Have you tried rebooting your NAS?
- Sorry it's taken so long to respond to your reply! I had other higher-priority things to attend to and my frustration level with this was too high.
Yes, the system status was shown to be redundant. I tried rebooting from the admin console, but it wouldn't reboot. When I finally did a manual reboot, the unit did reboot, but then other problems started. Below is the sequence of events (via email) with a few comments to help clarify...
Seagate 1TB HDD is original disk. (Channel 1)
WD 2TB HDD #1 is redundant disk added a few months back. (Channel 2)
WD 2TB HDD #2 is recently purchased disk to replace Seagate HDD.
RAIDiator 4.1.13 was running. Previous attempts at updating failed. Not sure why, but figured I'd wait until after getting both disks in unit with good status before addressing it.
[Wed Feb 11 15:12:04 CST 2015] New ReadyNAS firmware available
Name: RAIDiator
Version: 4.1.14
Date: Thu Oct 2 13:08:21 2014
Size: 57583104
[Wed Feb 11 15:12:04 CST 2015] New SMART disk errors detected!
This was the ongoing failure with Seagate HDD.
[Wed Feb 11 15:12:04 CST 2015] Disk failure detected
Disk fail event occurred on SATA channel 1.
If the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead.
removed Seagate 1TB HDD from Channel 1
[Wed Feb 11 15:12:04 CST 2015] Hotplug disk event detected
Disk remove event occurred on SATA channel 1.
added WD 2TB HDD #2 to Channel 1
[Wed Feb 11 15:35:08 CST 2015] Hotplug disk event detected
Disk add event occurred on SATA channel 1.
[Wed Feb 11 15:35:16 CST 2015] RAID event detected
Disk initialization started.
[Wed Feb 11 20:11:27 CST 2015] RAID event detected
RAID sync started on volume C.
[Wed Feb 11 20:11:28 CST 2015] RAID event detected
Disk initialization successfully finished.
[Thu Feb 12 00:20:49 CST 2015] RAID event detected
RAID sync finished on volume C. The volume is now fully redundant.
[Thu Feb 12 07:30:52 CST 2015] RAID event detected
RAID sync started on volume C.
[Thu Feb 12 07:31:21 CST 2015] Disk usage warning
Volume is approaching capacity: 100% used, 832k available.
[Thu Feb 12 07:31:?? CST 2015] Volume expansion requires reboot
The first stage of the in-place volume expansion is done. Please reboot the device to complete the volume expansion.
[Thu Feb 12 07:31:?? CST 2015] System Update Status
Your ReadyNAS device has been updated with a new firmware image. (RAIDiator 4.1.14)
[Thu Feb 12 11:58:?? CST 2015] Disk capacity expansion error. pvcreate /dev/hdc5 /dev/hdc6
At this point, the unit would not properly boot and could not be detected by RAIDar. Therefore, I did an OS reinstall from the Boot Menu. Now, RAIDar detects the unit, shows both HDD present (green LEDs) and shows RAIDiator v4.1.13. However, I cannot view FrontView in a web browser nor access any shares despite the fact that they appear in a file explorer. I also received an email alert that missing shares are detected. I can also ping the unit.
I'm at a complete loss at this point as to what to do to either resolve the problems all together or even further diagnose the problems. Since I can't afford to lose any more hair, any and all help is greatly appreciated! ;-)
John - I am wondering if you have a full OS partition.
Whether that is the cause or not, I suggest
-backing up the data
-doing a factory reset
-rebuilding the NAS and restoring the data.
Tedious, but probably preserves the most hair :-)
If you can't see all the data from Windows, you can try using Linux Reader (http://www.diskinternals.com/linux-reader/) which can read the data disk (but not the mirrored parity disk).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
