problem with NV+ after upgrade to RAIDiator 4.1.19-T9 beta

[ajw]

hello--

I upgraded to RAIDiator 4.1.19-T9 beta over the weekend to gain support back for time machine (for the macs). after having a weird-ish issue with with my appletv, I rebooted specifying check disks on reboot. I could see the unit with RAIDar when the disk check started. Its now been stuck at 49% for a long time (12+ hours) and seems to have hung.

The blue power light flashes three times. The four drive lights are all green.

I can ping the device and get a response. I can't see the unit with RAIDar now.

What is the next step?

I'm hoping this doesn't mean starting over; I have 2TB of data in use (4x 1.5 TB disks).

The logs, before I rebooted, looked ok, nothing seemed to be suggest impending disaster.

any suggestion appreciated

thanks in advance

ajw

[PapaBear]

I am not sure how you could have loaded 4.2.19-T4 Beta on an NV+ as that version is for the X-86 based machines. The latest version for Sparc based units (Duo/NV+) is 4.1.7.

How did you do the upgrade - local or remote?

[mdgm]

The O.P. probably was meaning 4.1.8-T9 beta.

You could try powering down, removing your disks (label order), hooking them up to a SATA port on your PC and checking them using vendor tools

[fredrikw]

I am experiencing a similar problem, but I fail to manage to remove the disks from the NAS while powered down. (And since it doesn't boot completely, they don't come out when powered on either...). How do I remove the disks from a NV+ without power?

[mdgm]

fredrikw, turn the NAS off, then follow the procedure here: http://www.readynas.com/kb/faq/hardware/how_can_i_release_a_stuck_disk_tray

Welcome to the forum!

[ajw]

I am not sure how you could have loaded 4.2.19-T4 Beta on an NV+ as that version is for the X-86 based machines. The latest version for Sparc based units (Duo/NV+) is 4.1.7.

How did you do the upgrade - local or remote?

I suspect someone has kindly edited my post . I can't find any reference to the intel (.2) version in my post any more. But I'm pretty sure I copied that from a page and edited at least one of the mentions of the intel version to make it sparc. so it was likely incorrect for a while.

I performed a local upgrade. I don't think remote updates pick up betas, just the offical gm releases.

as it happens I powered the unit off, resigned to spending days with disk tools or worse. took a punt and I just rebooted the bugger. it came up fine. as soon as it came up it shouted about tons of errors on one disk; thousands. that's fixable.

what I was really looking for were some calming words about not worrying about trashing the raid set if I powered the thing down after it had been stalled for ages. in a roundabout way I got that from another post. so its all good.