Forum Discussion

Initiate

Jun 01, 2019

Ultra 6 on OS6 hangs every few days, now refuses to boot

I have an Ultra 6 Plus upgraded to 4gb of RAM and a Core2Duo E7500. It's been running for years on OS4, zero hiccups in stability. I recently and upgraded it to OS6.9 and stability has gone way d...

secundo

Initiate

Jun 03, 2019

Retired_Member Thanks for your reply! I tried your trick but it didn't get me anywhere. I was able to update the NAS to 6.10.1 and then do an OS Reinstall, but it's still booting in safe mode. The web UI now shows 6.10.1, so at least that part worked!

StephenB Thanks for your reply! Here's what I see in the Boot Menu

Normal
Factory Default
OS Reinstall
Tech Support
Skip Vol Check
Memory Test
Test Disks

If I'm using XRAID2 with double parity with 6 disks, would plugging in only one disk give me any results?

StephenB

Guru - Experienced User

Jun 03, 2019

secundo wrote:

Here's what I see in the Boot Menu

Normal

Factory Default

OS Reinstall

Tech Support

Skip Vol Check

Memory Test

Test Disks

Interesting. I'd always assumed that the conversion process would replace "skip volume check" with "volume read only". Still it might be worth trying that option.

secundo wrote:
If I'm using XRAID2 with double parity with 6 disks, would plugging in only one disk give me any results?

I somehow got mixed up on your RAID mode. You'd need to connect at least 4 disks to the PC to recover data there.

FWIW, XRAID branding has shifted a bit over time. XRAID2 was the OS 4.2.x version (and the "2" didn't mean double parity - it meant "version 2 of XRAID"). OS 6 just called it XRAID again. By default it has single parity, though you can set it up as RAID-6 (switching to flexraid, destroying the data volume, creating a new data volume as RAID-6, and then switching back to XRAID).

mdgm
Virtuoso
Jun 03, 2019
StephenB wrote:

Interesting. I'd always assumed that the conversion process would replace "skip volume check" with "volume read only". Still it might be worth trying that option.
No, though I had thought so for a while.

You can modify /etc/fstab on the root volume, or do certain modifications to syslinux.cfg on the internal flash but that’s more risky.

In any case the error message in safe mode would suggest a problem with the 4GB root volume more so than the data volume. Volume read-only wouldn’t help if the problem is on the 4GB root volume.