Well, after some happy Knoppix dd_rescue Jedi affairs, the NAS1100 got 3 HDD working, and Netgear rescalate the case; I'm under the impression that more Linux commands are requested in the Tech Support Mode in order to give a final assault to do something for the data...wish I could find some page where to look at for learn that and give it a try by myself.Is someone dealing with that commands with a case like mine? May be just happens that I'm unlucky at the time to search this great forum.After all I'm using Netgear storage since Infrant...I should have some Jedi fellow to ask for this kind assistence.Let's see if my case could stand as the 3 HDD damaged but no data loosed!!!!Cheers!

Just a quick update, I just PUTTY the NAS for be sure that a L3 engineer should not encounter any problem connecting from the Internet to the NAS. All ready to have that elusive connection...For my curiosity, I place a sfdisk on the unit, I got:# sfdisk -lDisk /dev/hdc: 243200 cylinders, 255 heads, 63 sectors/trackWarning: extended partition does not start at a cylinder boundary.DOS and Linux will interpret the contents differently.Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System/dev/hdc1 0+ 254- 255- 2048000 83 Linux/dev/hdc2 254+ 286- 32- 256000 82 Linux swap / Solaris/dev/hdc3 286+ 121599- 121314- 974447286+ 5 Extended/dev/hdc4 0 - 0 0 0 Empty/dev/hdc5 286+ 89403- 89117- 715827881+ 8e Linux LVM/dev/hdc6 89403+ 121598- 32196- 258611211 8e Linux LVMDisk /dev/hde: 243200 cylinders, 255 heads, 63 sectors/trackWarning: extended partition does not start at a cylinder boundary.DOS and Linux will interpret the contents differently.Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System/dev/hde1 0+ 254- 255- 2048000 83 Linux/dev/hde2 254+ 286- 32- 256000 82 Linux swap / Solaris/dev/hde3 286+ 121599- 121314- 974447286+ 5 Extended/dev/hde4 0 - 0 0 0 Empty/dev/hde5 286+ 89403- 89117- 715827881+ 8e Linux LVM/dev/hde6 89403+ 121598- 32196- 258611211 8e Linux LVMDisk /dev/hdg: 121575 cylinders, 255 heads, 63 sectors/trackWarning: extended partition does not start at a cylinder boundary.DOS and Linux will interpret the contents differently.Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System/dev/hdg1 0+ 254- 255- 2048000 83 Linux/dev/hdg2 254+ 286- 32- 256000 82 Linux swap / Solaris/dev/hdg3 286+ 121599- 121314- 974447286+ 5 Extended/dev/hdg4 0 - 0 0 0 Empty/dev/hdg5 286+ 89403- 89117- 715827881+ 8e Linux LVM/dev/hdg6 89403+ 121598- 32196- 258611211 8e Linux LVMDisk /dev/hdi: 243200 cylinders, 255 heads, 63 sectors/tracksfdisk: ERROR: sector 0 does not have an msdos signature /dev/hdi: unrecognized partition table typeNo partitions foundWhere you can see /hdc and /hde are the HDD recovered from the dark side of the force, the /hdg is the survivor original HDD and the /hdi is the brand new HDD not partitioned drive.I understand that partitions over /hdc /hde /hdg are identical, that is for some reason giving me hope to recover data, but, no matter that I put the NAS to boot without check filesystem (as instructed by tech support) the RESYNC option is just not available over Frontview.I wonder, Is it mandatory to have a partitioned HDD to get a RESYNC available over Frontview? I don't think so, but, I like to ask, as I feel we are close to got an answer, positive or negative.Let's see what happens, I realy would love to know how to RESYNC over commands, but that seems to be out of my range, as a more experienced Jedi master is requested.Cheers!

Council:Some curious happened today: the blue led, which usualy blinks as indicating that some is not going fine, turned off; but the USB led turned ON, fixed green.I call tech support to update the case and let them know about, and they confirmed that the NAS is still available over the telnet boot mode, I also confirmed that through PUTTY, and they another time said that a Level 3 engineer connection is required...two months now for get that connection...I can't remember have seen that USB led ON, as I never connect a USB drive to the NAS. Anyway, let's mark the Master Kenobi words: "Patience, you must learn to have patience"

Some curious happened today...light show :? After an electrical blackout the NAS is not able to enter Tech Support mode, is not showing itself anymore to the RAIDar and it just blink the blue led of activity while the led from HDD 1 is steady on green.After doing anything else I update my case for let know techsupport.Now, the curious thing: after 30 minutes the HDD 1 led changed OFF, but, the #2 started to blink, then changed to green fix but HDD #3 get green fixed ON.I hope the light show mean some non destructive, I will let the NAS to work prior to shut it down or doing anything else.In short words.-Try to boot (no pressing any button), HDD #1 led green fixed ON.After 30 minutes, HDD #1 led goes OFF, but #2 started blink slowly ON green.After 5 minutes, HDD #2 stays green ON but #3 got ON steady.After 15 minutes #1 got ON fixed green again, now leds #1, #2 and #3 are ON; blue led all the time blinking.HDD #4 is new and it does not have even format.What's going on??????This is getting more interesting...

If you power down the NAS and remove the disks (label order) can you then put it in tech support mode? If so, re-insert the disks again (keeping the same order as before) and let the support agent know what's happened.

Hello again mdgm,I'm almost assure you that the NAS will boot into tech support mode just following your advise.In the meantime the light show goes on, I'm taking notes about the changes, and I detect some logic, and activity is appearing every 10-15 minutes, I have been waiting for 2 months, therefore, I feel no hurries letting the NAS to work, I just hope to be sure when the NAS finished it's errands, I hope that finally the LAN led will go ON and the NAS will show on RAIDar.I might be too optimistic, but, you know: feel, don't think, use your instincts...:-)

3 Disks failed, 2 back, still trying case # 20574298

12 Replies

Replies have been turned off for this discussion

ulic_qel_droma
Aspirant
Jul 17, 2013
We back on the fihgt! Today July the 17th I got my RMA chasis and again at the time to boot I received the same error message, I will continue the case with tech support and let's cross fingers for get a positive answer.

Keep calm...an go on.
ulic_qel_droma
Aspirant
Jul 18, 2013
Yesterday (July 17th) Tech Support is rescalating the case, I just double check that ReadyNAS is reachable from their facilities through a PUTTY check, but, I got curious and issued a sfdisk -l command, and got:

# sfdisk -l

Disk /dev/hdc: 243200 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/hdc1 0+ 254- 255- 2048000 83 Linux
/dev/hdc2 254+ 286- 32- 256000 82 Linux swap / Solaris
/dev/hdc3 286+ 121599- 121314- 974447286+ 5 Extended
/dev/hdc4 0 - 0 0 0 Empty
/dev/hdc5 286+ 89403- 89117- 715827881+ 8e Linux LVM
/dev/hdc6 89403+ 121598- 32196- 258611211 8e Linux LVM

Disk /dev/hde: 243200 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/hde1 0+ 254- 255- 2048000 83 Linux
/dev/hde2 254+ 286- 32- 256000 82 Linux swap / Solaris
/dev/hde3 286+ 121599- 121314- 974447286+ 5 Extended
/dev/hde4 0 - 0 0 0 Empty
/dev/hde5 286+ 89403- 89117- 715827881+ 8e Linux LVM
/dev/hde6 89403+ 121598- 32196- 258611211 8e Linux LVM

Disk /dev/hdg: 121575 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hdg1 0+ 254- 255- 2048000 83 Linux
/dev/hdg2 254+ 286- 32- 256000 82 Linux swap / Solaris
/dev/hdg3 286+ 121599- 121314- 974447286+ 5 Extended
/dev/hdg4 0 - 0 0 0 Empty
/dev/hdg5 286+ 89403- 89117- 715827881+ 8e Linux LVM
/dev/hdg6 89403+ 121598- 32196- 258611211 8e Linux LVM

Disk /dev/hdi: 243200 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/hdi: unrecognized partition table type
No partitions found

As far as I understand, the HDD#4 /dev/hdi reports error as it is just a brand new HDD, and I have not partitioned nor change nothing, I wonder if some Jedi could make a guess about the situation and how bad it looks...

A sfdisk size command shows:

# sfdisk -s
/dev/hdc: 1953504344
/dev/hde: 1953504344
/dev/hdg: 976554308
/dev/hdi: 1953504344
total: 6837067340 blocks
#

And that is correct, as HDDs 1,2 and 4 are 2TB units while #3 is the original X-RAID survaivor of 1 TB.

I'm just waiting for a L3 engineer to connect to the ReadyNAS, something I just not be witness since April...and feel a little bit armless...so close as I recovered 2 of 3 damaged HDD, but no Volume C recovered yet...

Forum Discussion

3 Disks failed, 2 back, still trying case # 20574298

12 Replies

Related Content

Nighthawk app not connecting but Wi-Fi works> Try This...

ReadyNAS 314 trying to install Tautulli from GUI fails (Python fails as well)

SSD disk failed

Firmware update failed

Orbi iOS app Device Manager Error Sorry your device list failed to load. Please try again later.

NETGEAR Academy

ProSupport for Business