Upgrade to 4.1.8 on NV+ stuck on "Booting" case 16910762

[wwalkersd]

On Saturday morning I started the upgrade of my NV+ from 4.1.5 to 4.1.7. The download was successful, I was prompted to reboot the ReadyNAS, and I did so. I checked back on it a couple of hours later and RAIDar showed the status as "Booting". The next chance I got to check it was Sunday morning, over 24 hours later. RAIDar still showed its status as "Booting". So, I powered down the NAS with the power button and rebooted it. It's been over an hour, and it still shows "Booting" in RAIDar and on the front panel.

Was there some reason I needed to upgrade to 4.1.6 first? What should I do now? There's no access to the NAS via Frontview.

OK, I just had a brainwave and tried connecting via ssh using the IP address, since I had previously had ssh access enabled. This was successful. The prompt I get is "Linux 2.4.18 Padre".

Sadly, I don't enough at this point to figure out what's going on. Wait, maybe I know a little.

/var/log/raidiator_version indicates that I'm still on 4.1.5 (RAIDiator!!version=4.1.5,time=1239467045). I'm not finding anything in any of the other log files (examined using tail) that would seem to indicate a problem.

ps -e shows these processes running:

Code: Select all

WalkerNAS:/var/log# ps -e
  PID TTY          TIME CMD
    1 ?        00:00:05 init
    2 ?        00:00:00 ksoftirqd/0
    3 ?        00:00:00 events/0
    4 ?        00:00:00 khelper
    5 ?        00:00:00 kthread
   10 ?        00:00:00 kblockd/0
   13 ?        00:00:00 khubd
   41 ?        00:00:00 pdflush
   42 ?        00:00:00 pdflush
   43 ?        00:00:00 kswapd0
   44 ?        00:00:00 aio/0
   45 ?        00:00:00 cifsoplockd
   46 ?        00:00:00 cifsdnotifyd
   92 ?        00:00:00 kvblade
   93 ?        00:00:00 mtdblockd
  106 ?        00:00:00 hotplug-sata
  131 ?        00:00:00 djsyncd
  132 ?        00:00:00 djcheckd
  135 ?        00:00:00 hotplug-gmac
  394 ?        00:00:04 raidard
  553 ?        00:00:00 sshd
  562 ttyS1    00:00:00 getty
  563 ?        00:00:00 sshd
  565 pts/0    00:00:00 bash
  597 pts/0    00:00:00 ps


I think I'm out of ideas at this point. The force is weak with me, O Great Jedi Masters.

[chirpa]

You can do direct updates from 4.1.5 to 4.1.7, it should have worked.

Can you give me access to SSH on it (port forward setup) ?

[wwalkersd]

Um, sure. However, I just found a file /.update_fail which contains "SYSTEM_UPDATE_FAIL_EXTRACT"

Does that mean what I think it means, that the downloaded update was not properly extracted from an archive? Odd that the system didn't tell me about it.

I think I have to reboot my router to get the port forwarding to work, so I'll get back to you when it's set. Thanks, Chirpa, that was fast!

[WhoCares?]

While you're on it, can you do a

Code: Select all

df -kh

Sounds like your root file system hasn't got enough space left to successfully extract the firmware image.

-Stefan

[wwalkersd]

Chirpa, port forward for SSH (port 22, TCP, UDP) in place. IP in PM Let me know when you're done.

[wwalkersd]

Stefan:

Code: Select all

WalkerNAS:/# df -kh
Filesystem            Size  Used Avail Use% Mounted on
/dev/hdc1             1.9G  438M  1.4G  23% /
tmpfs                  16k     0   16k   0% /USB


That looks kinda small. See sig for drives.

[markwoll]

edit your message to chirpa and take out the ip address.
I would just PM it to him.

[mdgm]

OS partition is 2GB on Sparc devices (e.g. NV+). That's normal. Plenty of free space. Your data volume isn't mounted (so either you haven't reached that far in the boot process or it can't mount your volume for some reason).

[kiwi1]

Sounds like a simular issue to mine

[sphardy]

Sounds very similar to these reported issues:

viewtopic.php?f=7&t=43468#p245129
viewtopic.php?f=17&t=45333&p=258275
viewtopic.php?f=17&t=47442

Workaround in each of these cases is to pull out one of the drives and reboot, then reinsert the drive and await the resync.

Sounds like a simular issue to mine

Actually, completely different judging by your other posts

[kiwi1]

Funny all my posts/issues have been caused by having the second drive in place. Front view took ages to load I mean 20 minutes+ per instruction. I tried everything then found this post and decided to pull drive 2 out just to see as I'd tried everything else i.e firmware upgraded, tested & swapped drives, new router I even isolated my network all to no avail. Took drive 2 out and bang front view works a charm and have just uploaded full release of 4.7 and now re-booting etc before I add the second drive back, hopefully then it will re-sync correctly.(God I hope so as the box has nearly been thrown out the window a few times now)

I know I've used a WD drive in a netgear product but what a load of balls this process is, there should be a warning on buying third party drives or something. Maybe there is and I missed it but the time wasted and frustration caused I feel like a bloody NV+ guru now and all I wanted to do was stream movies from a back up.... rant over

[mdgm]

4.1.7 should fix most compatibility issues with WD disks. If it's a WD20EARS, I'd suggest you backup your data, verify backup is good, do a System > Config backup, then factory default with both disks in place. A factory default on 4.1.7 is needed for 4k sector alignment.

There is warnings in the manuals to only choose drives from the compatibility list.

[sphardy]

Funny all my posts/issues have been caused by having the second drive in place.

That maybe correct, however this post (it seems) and the 3 I referred to report symptoms where the NAS fails to boot at all with all drives installed - not just go slow. That and the fact WD drives you have are well known to have issues, including affect performance, that 4.1.7 specifically addresses strongly suggests yours is a very different issue.

Good luck with the resync

[wwalkersd]

Well, this has wandered a bit from my original request. Anyway, I opened a tech support ticket, number 13710255.

[kiwi1]

Box is now failing to boot with 2 drives with new firmware! So I'll boot with 1 but can some one please explain why I need
'A factory default on 4.1.7 is needed for 4k sector alignment.'
And how I'm supposed to do that if it hangs on booting!
Thx