NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Boot
16 Topics
NV+ V2 stuck at booting
Hello I have been had my NV+ V2 for a few years now without any issue. It has the latest and last firmware (5.3.11 i think) and is populated with 2x WD 4Tb Red and 2x WD 3Tb Red internally and a usb enclosure attached as well. I also have Transmission and Sabnzb addons installed and running as well as SSH access enabled. The issue started today when i noticed that the Transmission website was not accessible from the standard IP. Everything else on the NAS was working fine. In the NAS dashboard software it showed the Transmission service as enabled but not running (no green dot). I wasn't able to enable it from here either after trying. After this i decided a reboot was the next option, I initiated this from the dashboard and let it run its path. 15 minutes later i tried to login to the dashboard and it loads but immediately says Device is Offline. Checking the screen on the unit itself just shows "Booting". I then waited another 15 mintues incase it was doing a long file system check upon boot but it was unchanged. After this i tried a shut down (by removing power as the power button would not restart it) and it went back to the same status. The strange part is that the network shares from the NAS appear to be fully opertaional, as well as Transmission, although now Sabnzb is not working. I'm not an expert by any means of the linux system but looking in SSH i see some bad looking messages about file systems and depreacated SCSI ioctl which i really dont understand. I have attached the contents of 'dmesg' below. I have read some threads about similar booting issues and some say it is a bad drive that prevents this. All the 'smartctl' look normal and don't report any errors. How can i potentially identify which one is bad before pulling each and trying them on my computer. Can someone decipher the issue from the below log or point me in the correct next steps for this? My backup of important data is a little old so i think i was going start with that but i don't think i'll have enough room on other devices to back up everything at the moment. If there are other SSH commands or log files that will be more helpful please let me know. Thanks in advance. hub 3-0:1.0: 2 ports detected usbcore: registered new interface driver usblp Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usbcore: registered new interface driver ums-datafab usbcore: registered new interface driver ums-freecom usbcore: registered new interface driver ums-jumpshot usbcore: registered new interface driver ums-sddr09 usbcore: registered new interface driver ums-sddr55 usbcore: registered new interface driver ums-usbat pwrctl: dev_t_NO. = 0xdd00000, major = 221 USB 3.0 Port Power On, Waiting for 3 seconds HDD_pwrctl_init MPP26 High. MPP28 High. MPP40 High. MPP42 High. Request the irq HDDpwrctrl success. Todo: mknod /dev/buttons c 253 0 mice: PS/2 mouse device common for all mice i2c /dev entries driver md: linear personality registered for level -1 md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 md: raid10 personality registered for level 10 md: raid6 personality registered for level 6 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com cpufreq: Setting CPU Frequency to 1600000 KHz cpufreq: Setting PowerSaveState to off Registered led device: backup Registered led device: sys Registered led device: sys_fail Registered led device: SATA1_act Registered led device: SATA2_act Registered led device: SATA3_act Registered led device: SATA4_act Registered led device: power usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver IPv4 over IPv4 tunneling driver ip_tables: (C) 2000-2006 Netfilter Core Team TCP bic registered NET: Registered protocol family 10 lo: Disabled Privacy Extensions tunl0: Disabled Privacy Extensions NET: Registered protocol family 17 RPC: Registered udp transport module. RPC: Registered tcp transport module. 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> All bugs added by David S. Miller <davem@redhat.com> scsi: waiting for bus probes to complete ... scsi 0:0:0:0: Direct-Access WDC WD40EFRX-68WT0N0 80.0 PQ: 0 ANSI: 5 scsi 0:0:1:0: Direct-Access WDC WD40EFRX-68WT0N0 80.0 PQ: 0 ANSI: 5 scsi 0:0:2:0: Direct-Access WDC WD30EFRX-68AX9N0 80.0 PQ: 0 ANSI: 5 scsi 0:0:3:0: Direct-Access WDC WD30EFRX-68AX9N0 80.0 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512. sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) sd 0:0:0:0: [sda] 0-byte physical blocks sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 23 00 10 00 sd 0:0:1:0: [sdb] Sector size 0 reported, assuming 512. sd 0:0:1:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) sd 0:0:1:0: [sdb] 0-byte physical blocks sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512. sd 0:0:1:0: Attached scsi generic sg1 type 0 sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 23 00 10 00 sd 0:0:2:0: [sdc] Sector size 0 reported, assuming 512. sd 0:0:2:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) sd 0:0:2:0: [sdc] 0-byte physical blocks sda: sd 0:0:2:0: Attached scsi generic sg2 type 0 sd 0:0:3:0: [sdd] Sector size 0 reported, assuming 512. sd 0:0:3:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) sd 0:0:3:0: [sdd] 0-byte physical blocks sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:1:0: [sdb] Sector size 0 reported, assuming 512. sd 0:0:2:0: [sdc] Write Protect is off sd 0:0:2:0: [sdc] Mode Sense: 23 00 10 00 sd 0:0:3:0: Attached scsi generic sg3 type 0 rtc mv_rtc: setting system clock to 2015-11-22 11:42:30 UTC (1448192550) sd 0:0:3:0: [sdd] Write Protect is off sd 0:0:3:0: [sdd] Mode Sense: 23 00 10 00 sd 0:0:2:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:2:0: [sdc] Sector size 0 reported, assuming 512. sdb: sd 0:0:3:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:3:0: [sdd] Sector size 0 reported, assuming 512. sdc: sda1 sda2 sda3 sda4 sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512. sdd: sd 0:0:0:0: [sda] Attached SCSI disk sdb1 sdb2 sdb3 sdb4 sd 0:0:1:0: [sdb] Sector size 0 reported, assuming 512. sd 0:0:1:0: [sdb] Attached SCSI disk sdd1 sdd2 sdd3 sdc1 sdc2 sdc3 sd 0:0:3:0: [sdd] Sector size 0 reported, assuming 512. sd 0:0:2:0: [sdc] Sector size 0 reported, assuming 512. sd 0:0:3:0: [sdd] Attached SCSI disk sd 0:0:2:0: [sdc] Attached SCSI disk Freeing init memory: 128K armvpd: module license 'Proprietary' taints kernel. Disabling lock debugging due to kernel taint ReadyNAS Pro VPD device driver init... Tuxera NTFS driver 3011.10.19 [Flags: R/W MODULE]. eth0: link down eth0: started ADDRCONF(NETDEV_UP): eth0: link is not ready md: bind<sdb1> md: bind<sdc1> md: bind<sdd1> md: bind<sda1> raid1: raid set md0 active with 4 out of 4 mirrors md0: detected capacity change from 0 to 4293906432 md0: unknown partition table md: bind<sdb2> md: bind<sdc2> md: bind<sdd2> md: bind<sda2> raid5: device sda2 operational as raid disk 0 raid5: device sdd2 operational as raid disk 3 raid5: device sdc2 operational as raid disk 2 raid5: device sdb2 operational as raid disk 1 raid5: allocated 4216kB for md1 raid5: raid level 6 set md1 active with 4 out of 4 devices, algorithm 2 RAID5 conf printout: --- rd:4 wd:4 disk 0, o:1, dev:sda2 disk 1, o:1, dev:sdb2 disk 2, o:1, dev:sdc2 disk 3, o:1, dev:sdd2 md1: detected capacity change from 0 to 1073610752 md1: unknown partition table md: bind<sdb3> md: bind<sdc3> md: bind<sdd3> md: bind<sda3> raid5: device sda3 operational as raid disk 0 raid5: device sdd3 operational as raid disk 3 raid5: device sdc3 operational as raid disk 2 raid5: device sdb3 operational as raid disk 1 raid5: allocated 4216kB for md2 raid5: raid level 5 set md2 active with 4 out of 4 devices, algorithm 2 RAID5 conf printout: --- rd:4 wd:4 disk 0, o:1, dev:sda3 disk 1, o:1, dev:sdb3 disk 2, o:1, dev:sdc3 disk 3, o:1, dev:sdd3 md2: detected capacity change from 0 to 8987273330688 md2: unknown partition table md: bind<sdb4> md: bind<sda4> raid5: device sda4 operational as raid disk 0 raid5: device sdb4 operational as raid disk 1 raid5: allocated 2132kB for md3 raid5: raid level 5 set md3 active with 2 out of 2 devices, algorithm 2 RAID5 conf printout: --- rd:2 wd:2 disk 0, o:1, dev:sda4 disk 1, o:1, dev:sdb4 md3: detected capacity change from 0 to 1000192802816 md3: unknown partition table EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. eth0: link up, full duplex, speed 1 Gbps ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready kjournald starting. Commit interval 5 seconds EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on md0, internal journal EXT3-fs: mounted filesystem with ordered data mode. udevd version 125 started Adding 1048440k swap on /dev/md1. Priority:-1 extents:1 across:1048440k EXT4-fs (dm-0): barriers enabled kjournald2 starting: pid 1751, dev dm-0:8, commit interval 5 seconds EXT4-fs (dm-0): internal journal on dm-0:8 EXT4-fs: file extents enabled EXT4-fs: mballoc enabled EXT4-fs (dm-0): mounted filesystem with ordered data mode svc: failed to register lockdv1 RPC service (errno 97). NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace period program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO root@READYNAS:/var#Solved12KViews0likes16Comments
ReadyNAS Pro 6 Corrupt Root - Need Help
I am new to ReadyNAS, I have never owned one and scouting through the Forums I've not found my problem in any detail to assist me start using the ReadyNAS. I have just purchased off eBay a ReadyNAS Pro 6 with no disks or documentation. I have worked out I need RAIDar, I have my 6 Disks (3TB) in the ReadyNAS (there on the HCL). When I turn it on, in RAIDar it says Corrupt Root. It shows the model, IP address and all drives greyed out. Looking through the forum I understand that I need to do something for the ReadyNAS to see the drives. I need to do something to be able to setup the disks in a RAID for RAIDar to see the ReadyNAS completely. Also Admin page button on RAIDar says the page is not accessible. The Browse Button opens my Documents... Could someone tell me how I get the disks to be seen by the ReadyNAS and how to setup the RAID, RAID 6 is the advise I had to setup. There has to a process to make the disks work with teh RaedyNAS Can you keep it simple, I'm not that techno...? Thank youSolved5.9KViews0likes6CommentsReadyNAS Duo v1 stuck on Booting after power outage
There was a power outage at my house which turned my ReadyNAS Duo off. This has happened before so I manually powered it On but could not access FrontView or see it in RAIDar. I then accessed the boot menu to power it On and Skip Volume Check. Now, RAIDar can see it but stuck on Booting. Still can't access FrontView. Responds to pings from cmd prompt.Solved5.9KViews0likes10CommentsReadyNAS Duo V1 cannot access boot menu
Hello, I have a Netgear ReadyNAS Duo (says v2 on the label but is actually a v1) and I cannot access the boot menu to perform an OS reinstall. I inherited it from my Grandad who has passed away and I need to perform the OS reinstall so the administration log-in credentials will be reset to the factory default values. It's very frustrating because I have gone to the password reset webpage and when presented with the security question my Grandad setup I do actually know the answer, but despite trying several variations (acronyms, upper case first letters, nicknames etc.) I keep being told my answers are incorrect... Obviously this is a fairly old ReadyNAS now and therefore Netgear can't provide me with any technical support. To access the boot menu I have done the following procedure: 1) Completely powered off the device. 2) Pressed the reset button on the back with a paperclip (and kept it held down). 3) Powered on the device. 4) Waited for all the lights to flash so I can release the reset button - the lights never flash and therein lies my problem. I would really like to be able to use my ReadyNAS as I'm in the process of creating a backup system for all my photos and videos with the intention of being able to access them all without the computer being switched on. Thanks in advance for any help!SolvedRN10200 Unable to Boot or reset or reinstall OS
My ReadyNAS is invisible to raidAIR and doesn't even show up under my routers connected devices list. I've tried several times to factory reset and it doesn't seem to work. I tried upgrading firmware back sometime in the winter and since then the readyNAS got put away in a box. Recently went to use it again and remembered why it ended up in the box... I've tried an OS reinstall just now with 2 different USB sticks, both times the process goes about it's thing very quickly, but then nothing happens. Is the readyNAS toast or should I just keep trying with other USB drives? Also, the unit is unresponsive to the power button and passed the memory test. I'm kind of stumped.5.1KViews0likes14CommentsReady NAS 102 in accessible (corrupt root)
Netgear Community: I have been using a ReadyNAS DUO V2 device with a single WDC WD20EFRX 2TB HDD without issue. At this time, the device is not accessible, does not register as being on my home network. As of November 24, I found the device inaccessible, and have been looking for answers. With the help of RAIDar 6.2 (for Windows), I see I have a "Status: corrupt root", the "Firmware" is *blank*, the IP address is shown, and the single drive installed in the device shows with a green check mark, and a capacity of about 1863GB. I attempted an "OS reinstall" prior to finding RAIDar and the fact that the LEDs were controlled by the "Backup" button suggest the enclosure itself is operable. I have seen the reference for a "USB recovery" along with the cautions that this ONLY be initiated through Netgear support. My questions are: 1. Is the content of the HDD presumed to be intact (based on the green check mark of RAIDar)? 2. Can >this< HDD be loaded into another, newer (current) Netgear product, and have its content intact and accessible? 3. Can the HDD be accessed *outside* of the ReadyNAS enclosure? 4. If I purchase and install a NEW, unitialized HDD, would that achieve a recovery, such that I could return the current disk to Bay 1, then initiate a RAID operation to the *new* disk in Bay 2? 5. Can the USB recovery process be executed WITHOUT having a HDD installed in the ReadyNAS device? Thanks in advance for your helpful replies.3.9KViews0likes6CommentsReady Nas pro 6 : 3 min cold start, is that normal ?
When my pro 6 hasn't been used for several days after switching on the back button of the power supply and push the front button, it takes 3 minutes before something happen and the disk start to turn. If I make a shutdown and a restart 10 min later there's no waiting time. any idea ? thank's for you help3.4KViews0likes4CommentsReadyNAS Duo RND2000 not booting - no disks detected
My ReadyNAS Duo was working fine yesterday - as far as I know, both disks were OK. I beleive the firmware is up-to-date but has not changed recently. I copied a large number of photos onto it and all seemed well initially but I did not check them as the process too a long time (perhaps longer than usual). Later the device would not shut off as usual so I disconnected and tried to reboot. Various patterns were observed and Raidar was unable to find it. I have seen it with the power light on steady but no other lights. I powered off and removed the disks to try one or two in the two slots. The current sitiuation is that it will not detect disks. Raidar will now find it. Currently the power light is flashing but I can turn it off by holding it down, as usual. It will restart with no disks inserted and can then be discovered using raidar but with useful options greyed out. The power light is flashing and the two LEDs are flashing in a pattern of 2 slow flashes followed by 3 fast ones. Inserting a disk (or two) seems to have little effect. Any ideas? I was thinking about replacement as it's 6 years old and well out of warranty. I'd rather like to be able to access the data!3.3KViews0likes2CommentsRN10223D really dead!
So, my ReadyNas is dead. It does not respond to any commands. I have removed the harddrives and removed all partitions (on a Windows 10). I have used a the USB Recovery Tool to flash new firmware (Version 6.6.0 (arm)). I don't know if the flash went OK but it was running for a while and then shut down by itself as expected. I have tried "Reinstall OS" as well as "Factory default. I can get into the boot menu but as I choose something like disk test, OS reinstall the only thing that happen is that the power LED is flashing for about 4-5 seconds, turns solid blue and then ... nothing. It does not accouire an IP address from my router. Am I missing something? My knowledge about Netgear is somewhat limited so any help would be appreciated. Thank you in advance, LarsSolved3.1KViews0likes10CommentsReadynas Ultra 6 boot problem
Hi Everyone, I have a Readynas Ultra 6. Because of an power outage the Readynas won't boot anymore. - the fan's are working. - the display keeps showing 'readynas' - i found the vga header, but the monitor says 'no cable connected'. - I've replaced the memory. - I've have i disk in the unit and is spinning up. - I tried to restore factory by using a boot usb and the backup button. - i pressed the reset button (on the back) at power on. - I cannot access the bootmenu (display won't change from 'readynas') Can someone please help what else i can do to fix the boot problem. Greetings, Rob3KViews0likes10Comments