NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
joepublic1
Apr 22, 2013Aspirant
ReadyNAS Duo v1 Boot Problem
Twice now my ReadyNAS Duo does not complete boot sequence. The blue power on light continues to flash. FrontView is not accessible, the shares are not accessible but the device responds to ping. Nothing happens if I press the power button. The only way to get it out of this state is to pull the power plug out! Then I power on & it takes 8 hours to re-synch the drives.
I have looked at the logs front the time it fails and in the kernel.log I have found it stops near the end of boot just before EHCI. So in the logs I get this:
At this point the system is up.
So what is going wrong?
Is this a hardware issue or software?
There is nothing plugged into the USB ports.
I can't find anything being logged that suggest any error when it fails to complete the boot.
Any suggestions?
I have looked at the logs front the time it fails and in the kernel.log I have found it stops near the end of boot just before EHCI. So in the logs I get this:
Apr 15 16:01:13 MyNAS kernel: kjournald starting. Commit interval 5 seconds
Apr 15 16:01:13 MyNAS kernel: EXT3 FS on hdc1, internal journal
Apr 15 16:01:13 MyNAS kernel: EXT3-fs: mounted filesystem with ordered data mode.
Apr 15 16:01:13 MyNAS kernel: linked, 1000mbps mode
Apr 15 16:01:13 MyNAS kernel: EXT2-fs warning (device hdc1): ext2_fill_super: mounting ext3 filesystem as ext2
Apr 15 16:01:13 MyNAS kernel: Adding 255968k swap on /dev/hdc2. Priority:0 extents:1 across:255968k
Apr 15 16:01:13 MyNAS kernel: enable_irq(11) unbalanced from f804059c
Apr 15 16:01:13 MyNAS kernel: hdc: cache flushes supported
Apr 15 16:01:13 MyNAS kernel: hde: cache flushes supported
Apr 15 16:01:13 MyNAS kernel: hde: unknown partition table
Apr 15 16:01:13 MyNAS kernel: EXT2-fs warning (device dm-0): ext2_fill_super: mounting ext3 filesystem as ext2
When it fails it never gets past the line above, whilst when it is working it carries on with:
Apr 15 16:02:25 MyNAS kernel: ehci_hcd 0000:00:17.2: EHCI Host Controller
Apr 15 16:02:25 MyNAS kernel: ehci_hcd 0000:00:17.2: new USB bus registered, assigned bus number 1
Apr 15 16:02:25 MyNAS kernel: ehci_hcd 0000:00:17.2: irq 27, io mem 0x5c010000
Apr 15 16:02:25 MyNAS kernel: ehci_hcd 0000:00:17.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Apr 15 16:02:25 MyNAS kernel: usb usb1: configuration #1 chosen from 1 choice
Apr 15 16:02:25 MyNAS kernel: hub 1-0:1.0: USB hub found
Apr 15 16:02:25 MyNAS kernel: hub 1-0:1.0: 4 ports detected
Apr 15 16:02:26 MyNAS kernel: USB Universal Host Controller Interface driver v3.0
Apr 15 16:02:26 MyNAS kernel: PCI: VIA IRQ fixup for 0000:00:17.0, from 0 to 11
Apr 15 16:02:26 MyNAS kernel: uhci_hcd 0000:00:17.0: UHCI Host Controller
Apr 15 16:02:26 MyNAS kernel: uhci_hcd 0000:00:17.0: new USB bus registered, assigned bus number 2
Apr 15 16:02:26 MyNAS kernel: uhci_hcd 0000:00:17.0: irq 27, io base 0x5c001000
Apr 15 16:02:26 MyNAS kernel: usb usb2: configuration #1 chosen from 1 choice
Apr 15 16:02:26 MyNAS kernel: hub 2-0:1.0: USB hub found
Apr 15 16:02:26 MyNAS kernel: hub 2-0:1.0: 2 ports detected
Apr 15 16:02:27 MyNAS kernel: PCI: VIA IRQ fixup for 0000:00:17.1, from 0 to 11
Apr 15 16:02:27 MyNAS kernel: uhci_hcd 0000:00:17.1: UHCI Host Controller
Apr 15 16:02:27 MyNAS kernel: uhci_hcd 0000:00:17.1: new USB bus registered, assigned bus number 3
Apr 15 16:02:27 MyNAS kernel: uhci_hcd 0000:00:17.1: irq 27, io base 0x5c001020
Apr 15 16:02:27 MyNAS kernel: usb usb3: configuration #1 chosen from 1 choice
Apr 15 16:02:27 MyNAS kernel: hub 3-0:1.0: USB hub found
Apr 15 16:02:27 MyNAS kernel: hub 3-0:1.0: 2 ports detected
Apr 15 16:02:28 MyNAS kernel: chn=0, statu/LP_S=0x(d0/d050)29, 32
At this point the system is up.
So what is going wrong?
Is this a hardware issue or software?
There is nothing plugged into the USB ports.
I can't find anything being logged that suggest any error when it fails to complete the boot.
Any suggestions?
4 Replies
Replies have been turned off for this discussion
- mdgm-ntgrNETGEAR Employee RetiredOpen a tech support case (see Online Submission link in my sig) and post your case number.
- goptermanAspirantDid you ever get anywhere with this?
It sounds like my Duo is having identical problems although mine never gets to a point where I can see what's going on .....
Power light flashes continually at just under 1 second intervals, Duo is pingable but FrontView is not reachable.
Firmware re-install (quick reset press) did nothing
Factory reset did nothing (http://home.bott.ca/webserver/?p=306 performed afterwards and files are still visible)
All this after a couple of power hits at home.
Is my Duo dead ? I'm seriously considering junking it and buying a newer one - probably from another manufacturer :( - joepublic1AspirantI opened up a support case with Netgear, sent them the logs, but have drawn a blank so far. They seem to be recommending things like you have done plus doing a "Enable the box to Perform volume scan and Check and fix quotas on next boot. " & then reboot. Haven't done that yet, but I think they are clutching straws. Did you check the kernel log to see where the hang occurred? From my logs the system is either just finishing setting up EXT3 or is about to start EHCI USB processing. Would be useful to know where your box hangs.
- goptermanAspirantMany thanks for taking the time to reply joepublic. Sorry about the slow reply in getting back to you.
I have to admit that I don't think my box is getting that far. I have not found any way to talk to it and view the kernel log. Are you using RAIDar? I have it installed on both a Windows box and a Linux box and neither will actually pick up the Duo.
I'm beginning to think that I actually have a hardware fault. The only way I have found to talk to my Duo at all, is to unplug the power lead and then press and hold the power button for 15 seconds (until after the 3rd LED flash) - the so called "Tech Support Mode" boot. I can then telnet to it. The only log file I can find in this state is /var/log/frontview/enclosure.log. It states that my Duo has no disks. I know this is not true - I can see both when I connect them to my PC!!
Having said all that I'm happy to be corrected - that's why I'm asking on here :)
Related Content
NETGEAR Academy

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