4.2.20 [T32] Hang after about 72 hours

[btaroli]

Well, this is interesting deja vu. Similar to my T31 experience (viewtopic.php?f=51&t=60858), about 72 hours after installation of T32, my Pro 6 hung. I've restarted it, forcefully, and apparently escaped needing a scrub (this time).

Seems like the issue isn't resolved after all...

[btaroli]

Submitted logs, attn to chewbacca

[mdgm]

If not happy with 4.2.19 or 4.2.20 beta you can downgrade to 4.2.16 or 4.2.17 if you'd prefer to run one of those.

See http://www.readynas.com/RAIDiator_x86_4_2_16_Notes and http://www.readynas.com/RAIDiator_x86_4_2_17_Notes

Of course you'd lose any bug fixes and enhancements since then.

4.2.20 is a beta, not everything is necessarily going to work with it.

[btaroli]

I reported that drivel as off-topic. Too bad it wasn't just removed.

[beisser]

i could have removed it yes.. but it wasnt bad enough for that.

maybe it has more educational value this way

[btaroli]

i could have removed it yes.. but it wasnt bad enough for that.

maybe it has more educational value this way

Just needless distraction, IMO. We've all got more important things to do.

[btaroli]

Well, getting back on topic... my NAS crashed again tonight. Just after 5PM. It's back up now, but I'm hoping to hear there is some hope at the end of the tunnel. Is there anything we guinea pigs should be doing to gather more useful info? Or is the solution at hand coming in a build?

[btaroli]

[redacted]

[beisser]

ok i deleted all the junk.. and if he doesnt stop it i can also ban him or worse..

criticism is allright but keep it civil.

[Chewbacca]

btaroli; Can you try T34.

[btaroli]

btaroli; Can you try T34.

I was just about to try downloading it, but the download page says T32 still. Was T34 pulled? I'll try dummying the URL, but want to verify the status before installing (should I be able to retrieve it).

[btaroli]

Have applied T34. Will update as time goes.

[TeknoJnky]

my pro business has hung up twice now on t32. Both times I had to hard power off, could not ping or otherwise connect to nas, normal front button power down sequence did not work, had to hold until power off, then I switched of the hard button in the back for a few then powered up.

the first time, it said I had a failed disk, but tested and reinserted and resynced fine.

the second time, this morning, all disks show fine but still going through a resync process.

While I may or may not have a flakey disk, I would not expect it to bring down the whole nas.

[btaroli]

Yes, I think there is an acknowledged issue in T32. There are newer builds that still seem to be exhibiting problems, but this is why software goes through beta. AFAIK, T32 is still the latest publicly posted beta. I wonder which will be the next... but I am aware that they're still working on the issue.

[TeknoJnky]

ok. I had originally upgrade from 4.2.17 to .20t32 (.17 had run for months and months and I didn't want to bring it down), the ultra 4 has been running all of the .20 beta with no issues, and has even been running t32 since it's release with no downtime or problems.

assuming its not a disk issue, perhaps its something to do with the probus hardware/drivers, dual redund, and/or lacp bonding.