× ReadyCLOUD server will have a maintenance deployment starting 11pm PST on Jan 17th, 2021, expected service downtime of 30~45 minutes. During that period, ReadyCLOUD mobile app or web portal might not allow logins and remote file access.
Reply
Aspirant

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#

 

Message 1 of 17

Accepted Solutions
Aspirant

Re: NV+ V2 stuck at booting

Ok so to follow up and hopefully finish this off...

 

I was able to hot swap the first drive and that kicked off the resync process which took about 20 hours to complete.  Now everything is looking normal via frontview and the LCD screen etc.  There is still the smartctl.org in the logs but the drives are reporting fine and everything looks normal.

 

So to just recap what happened and fixed it...

 

Upon a reboot the unit hung at "Booting..." on the LCD screen and subsequent reboots would not change that

What finally worked was removing a disk from the unit, powering it on, getting stuck at the same booting message and powering it off.

 

Then reinserted the disk and the unit would boot properly after that but with an unprotected volume

 

Hot swapping the drive started the resync process and now things appear normal.

 

 

Hopefully things stay this way  Smiley Happy

Thanks to all who posted and helped me out.

Craig.

View solution in original post

Message 17 of 17

All Replies
NETGEAR Employee Retired

Re: NV+ V2 stuck at booting

Hello Craigatitus2,

 

Welcome to the community!

 

Please try Skip Volume check from the boot menu and see if that will boot the NAS to normal. 

 

Regards,

JennC
NETGEAR Community Team
Message 2 of 17
Aspirant

Re: NV+ V2 stuck at booting

Thank you for responding.  I will try that after i complete the backup of all the data and report back.

 

Thanks

Craig.

Message 3 of 17
Aspirant

Re: NV+ V2 stuck at booting

Hi JennC

 

I tried the Skip Volume Check from the boot menu but the same thing happens.  It gets stuck on saying Booting... with network drives actually being available and Transmission being up but not Sabnzb.  The frontview software just says Device is Offline.

 

Are there any other options to try to get this back up and running?   

 

Thanks

Craig.

Message 4 of 17
NETGEAR Employee Retired

Re: NV+ V2 stuck at booting

Hello Craigatitus2,

 

Usually Skipping Volume check will let you in so you can get to be able to access the shares and back up the files and the dashboard/admin page to download all the logs to see if all disks are fine.

 

I guess you need to contact support center for this case, they will require a per incident support service contract.

 

Regards,

JennC
NETGEAR Community Team
Message 5 of 17
Aspirant

Re: NV+ V2 stuck at booting

Hi JennC

 

Thanks again for responding.  I can currently access all the shares and can access the logs via the SSH connection.  I just need some directon on what logs are important and then i can provide them.

 

If i do a memory test, disk test, or an OS reinstall from the boot menu, will this delete any data or remove the current volume on the disks?   

 

Since Sabnzb won't start, it makes me think its something to do with that.  Is there a way to uninstall this from the SSH connection and have it removed from startup?  Or will doing an OS reinstall accomplish this?

 

Thanks

Craig.

Message 6 of 17
NETGEAR Employee Retired

Re: NV+ V2 stuck at booting

 

Hello Craigatatis2,

 

Factory reset and swapping disks will delete the data, the OS reinstall, memory test and disk test are safe. 

 

• OS reinstall. Reinstalls the firmware from the internal flash to the disks. Use the OS reinstall boot mode when the system crashes and corrupts some configuration files. OS reinstall boot mode also resets some settings on your unit, such as Internet protocol settings and the administrator password, to defaults.

 

• Memory test. Performs a memory test. The pass or fail result is reported using the unit’s LEDs. Contact a NETGEAR technical support representative to interpret memory test results. • Disk test. Performs an offline full disk test. This can take 4 hours or more, depending on the size of your disks.Any problems are reported in the RAIDar discovery tool.

 

• Disk test. Performs an offline full disk test. This can take 4 hours or more, depending on the size of your disks.Any problems are reported in the RAIDar discovery tool.

 

As for the logs, you need to look for disk_smart.log, this will list all currently inserted disks with their status.

 

Regards,

 

 

JennC
NETGEAR Community Team
Message 7 of 17
Aspirant

Re: NV+ V2 stuck at booting

Hi Again

 

I found the logs in the /var/log/frontview folder and the disk_smart.logs show all disks pass each time it runs.  The other logs in here for the partitions, raid config and others "look" normal with nothing glaring out to me and all raids saying clean.  There is also nothing in the smart_errors log files for each of the disks.

 

In the syslog in the main /var/log directory...i think i narrowed it down to around when the issue started and what i see in the logs is as follows:

 

At the weekly run of the smart check on Nov 22nd this message appears

Nov 22 06:47:06 READYNAS kernel: program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 22 06:47:12 READYNAS last message repeated 15 times

 

Then it appears again a few seconds later
Nov 22 06:47:17 READYNAS kernel: program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO
Nov 22 06:47:22 READYNAS last message repeated 15 times

The disk_smart log from this day show nothing out of the ordinary with each disk passing with no errors.

 

Then something happens a few hours later that looks bad with a reboot and then a long period of time before it actually comes back up...

Nov 22 08:28:12 READYNAS kernel: EXT4-fs error (device dm-0): ext4_xattr_block_get: inode 112429004: bad block 1798836317
Nov 22 08:28:12 READYNAS kernel: EXT4-fs error (device dm-0): ext4_xattr_block_list: inode 112429004: bad block 1798836317
Nov 22 08:28:24 READYNAS kernel: EXT4-fs error (device dm-0): ext4_xattr_block_get: inode 112429004: bad block 1798836317
Nov 22 08:28:24 READYNAS kernel: EXT4-fs error (device dm-0): ext4_xattr_block_list: inode 112429004: bad block 1798836317
Nov 22 08:41:06 READYNAS shutdown[22621]: shutting down for system reboot
Nov 22 08:41:07 READYNAS init: Switching to runlevel: 6
Nov 22 08:41:23 READYNAS exiting on signal 15

Nov 22 09:26:27 READYNAS syslogd 1.5.0#6: restart.
Nov 22 09:26:27 READYNAS kernel: klogd 1.5.0#6, log source = /proc/kmsg started.
Nov 22 09:26:27 READYNAS kernel: Linux version 2.6.31.8.nv+v2 (root@NSBU-NJ) (gcc version 4.3.2 (sdk3.2rc1-ct-ng-1.4.1) ) #1 Thu Apr 18 17:40:54 HKT 2013
Nov 22 09:26:27 READYNAS kernel: ....Reboot messages continue.......

 

One part of the reboot messages that stands out to me is the messages about capacity change and unknow partition table but i don't know if this is normal or not.

Nov 22 09:26:27 READYNAS kernel: md2: detected capacity change from 0 to 8987273330688
Nov 22 09:26:27 READYNAS kernel: md2: unknown partition table

 

Then this message comes up throughout the logs a few more times throughout the next few days... Most recently this morning at 6:47 when it think it does its smart disk check cron job.
Nov 22 09:26:55 READYNAS kernel: program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO


Any ideas about this smartctl.org deprecated SCSI message?  Is it perhaps the disk controller starting to go on the NAS?  If it was simply one of the disks i would think it would show smart errors and not pass all the time.  

 

Its also strange that i see transmission starting up in the logs but i see nothing at all about SabNZB...but again maybe this is normal.  The syslog doesn't go back far enough for a "normal" successful boot for me to compare to.

 

I haven't done the boot menu disk check or the boot menu memory test yet...I guess those are next on the list if there isn't anything specific available on this smartctl message.

 

Thanks again.

Craig. 

 

Message 8 of 17
Aspirant

Re: NV+ V2 stuck at booting

Well to update, a Boot Menu Memory test indicated Passed.  A Boot Menu disk test i think was successful as it didn't indicate any errors and i can't find any logs about it.  The unit was just back at the "Booting..." stage when i left it to run overnight.

 

The next step is to do the Boot Menu OS Reinstall i guess.  

 

My question is, will i lose SSH login with an OS Reinstall?

 

Thanks

Craig.

Message 9 of 17
Guru

Re: NV+ V2 stuck at booting


@Craigatitus2 wrote:

 

 

My question is, will i lose SSH login with an OS Reinstall?

 

 


No.

 

The IP address configuration is set to DHCP, and the admin password is reset to the default (which I think is "password" for your NAS). Other settings should remain intact.

 

Of course a factory default will destroy everything, so make sure you don't do that.

Message 10 of 17
Aspirant

Re: NV+ V2 stuck at booting

Thanks StephenB.

 

A factory Default may be the next step if the OS Reinstall doesn't work...    I don't know what else to try...

 

Thanks

Craig.

Message 11 of 17
Guru

Re: NV+ V2 stuck at booting


@Craigatitus2 wrote:

 

A factory Default may be the next step if the OS Reinstall doesn't work...    I don't know what else to try...

 

 


If you are the original purchaser, then per-incident paid support from Netgear would be an option.

 

If you don't have a backup then that's worth considering.

Message 12 of 17
Aspirant

Re: NV+ V2 stuck at booting

I am the original purchaser.  Do you know approximately how much the paid support costs?  Money is a little tight right now.

 

Thanks

Craig.

Message 13 of 17
Guru

Re: NV+ V2 stuck at booting


@Craigatitus2 wrote:

I am the original purchaser.  Do you know approximately how much the paid support costs?  Money is a little tight right now.

 

Thanks

Craig.


I don't work for Netgear, and don't have access to their current prices (and they might depend on the region).

 

But $75 US is the amount I recall.  

 

If you needed Data Recovery it would be a lot more (starts at $200, and depends on the time that takes). However, there's no reason to think that data recovery is involved, based on the info we know so far.

Message 14 of 17
Aspirant

Re: NV+ V2 stuck at booting

Ok I think i have some progress but it may still be too early to tell.

 

Since i read that sometimes the disks themselves can cause various Readynas units to get stuck at booting.  I decided to shut the unit down and remove disks and boot it up again one at a time.  So first i removed disk 1 and booted it up and it stopped at the exact same place of stuck at "booting...".   

 

I then shut it down again and inserted disk 1 back in and turned it on.  This time the unit proceeded on past booting and appears to have loaded up somewhat normally (Transmission is failing to start  "transmission-daemon Error loading config file -- exiting. (daemon.c:498)") and i can now get into Frontview.

 

Now the unit indicates that C: is unprotected and Not-Redundant.   All shares are there with what looks like all files in place.  Frontview does not say its running a Resync or anything.  Shouldn't it be automatically trying to resync now or will that attempt on the next boot?  

 

The message "kernel: program smartctl.org is using a deprecated SCSI ioctl, please convert it to SG_IO" is still appearing in the syslogs but at least now i see the other services starting up and looking normal.

 

 

Message 15 of 17
Aspirant

Re: NV+ V2 stuck at booting

Ok a reboot of the unit doesn't seem to kick off the resync either and the volume is still "unprotected".  Can someone recommend the best way to resync the volume?  Should i hot pull the first drive and then put it back in?  Are there linux commands to kick the process off?

 

 

On a side note, the reboot fixed the issue with Transmission and now both Transmission and Sabnzbd are working.

 

Thanks

Craig.

Message 16 of 17
Aspirant

Re: NV+ V2 stuck at booting

Ok so to follow up and hopefully finish this off...

 

I was able to hot swap the first drive and that kicked off the resync process which took about 20 hours to complete.  Now everything is looking normal via frontview and the LCD screen etc.  There is still the smartctl.org in the logs but the drives are reporting fine and everything looks normal.

 

So to just recap what happened and fixed it...

 

Upon a reboot the unit hung at "Booting..." on the LCD screen and subsequent reboots would not change that

What finally worked was removing a disk from the unit, powering it on, getting stuck at the same booting message and powering it off.

 

Then reinserted the disk and the unit would boot properly after that but with an unprotected volume

 

Hot swapping the drive started the resync process and now things appear normal.

 

 

Hopefully things stay this way  Smiley Happy

Thanks to all who posted and helped me out.

Craig.

View solution in original post

Message 17 of 17
Top Contributors
Discussion stats
  • 16 replies
  • 3768 views
  • 0 kudos
  • 3 in conversation
Announcements