I've been having a series of issues with my legacy setup.

 

The system seeming locks up when I start a parity check after a reboot. It initially came back with 2 disks missing. I rebooted from the GUI and the disks reappeared. I then got the diagnostics and syslog files and started the server. Within a few minutes I lost all connectivity from the GUI and the PC display is also blank.

 

I also cannot update to 6.5.3 - throws a cannot find download server error.

 

Thanks.

tower-syslog-20240820-0929.zip tower-diagnostics-20240820-0929.zip

Syslog after a reboot won't be much help, enable the syslog server and post that after a crash.

 

3 minutes ago, foraye said:

I also cannot update to 6.5.3

From such an old release you may need to do a manual update.

5 minutes ago, JorgeB said:

Syslog after a reboot won't be much help, enable the syslog server and post that after a crash.

 

From such an old release you may need to do a manual update.

I dont see a syslog server option in my network settings...6.3.5

 

Should I attempt a manual update at this point? Where do I get the update files?

https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade

Thanks Man!

 

I have those files already. I thought I had to do incremental upgrades before going to the current release. Please confirm.

7 minutes ago, foraye said:

I have those files already. I thought I had to do incremental upgrades before going to the current release. Please confirm.

You can go directly to the current release.   

Thank you!

I moved and copied BZ* files as instructed. Upon reboot I only got as far as the attached image. Any advice is welcome.

Try booting with a different flash drive using a stock install, no key needed, just to see if it boots.

Thanks, I didn't try a different USB Stick.

 

I rebooted and selected GUI option, it booted into the local splash screen..a big plus from 6.3.5.

 

I had to switch network ports for some reason and also supply a static IP address. Initial boot didn't have network working

 

I'm up to date now!

 

I just checked and my initial install was back in 2008! LOL

 

 

Guys,

 

I was able to upgrade to the latest version, but I still have the same issues of crashing when I spin up the drives and parity check begins. I enabled the syslog server and have it writing to the flash drive I also have the latest diagnostics from yesterday and this morning.

 

Today I found the server frozen and had to do a hard reboot. After that reboot, I had no ethernet connectivity and while going through the GUI Menus, the PC restarted itself and stopped at the previously posted command line. After another restart I ran the Fix Common Problems and this jumped out at me...

 

Your flash drive has possible corruption on /boot/config/network-rules-old.cfg. Post your diagnostics in the forum for more assistance

 

I'm posting all the relevant logs that I captured.

 

please review and comment

syslog syslog-previous tower-syslog-20240822-0137.zip tower-syslog-20240822-1404.zip tower-diagnostics-20240822-1011.zip

There's nothing relevant logged, do you know the time it crashed? Was it at the end of syslog-previous?

It has been crashing for the past few days. I just found the GUI unresponsive. I shut it down and pulled the flash. Logs are attached.

 

It seem to boot fine then just lock up. I hadn't even started the array. I have the syslog server enabled but I dont thing it had the opportunity to write before the lockup.

syslog syslog-previous

Syslog-previous only ran for 3 minutes, did it crash after that?

On 8/23/2024 at 4:08 AM, JorgeB said:

Syslog-previous only ran for 3 minutes, did it crash after that?

Yes it did.

 

Trying to figure out if its the flash or PC hardware. This box has been together for about 15 years and may need a refresh. I just dont want to lose any data.

On 8/23/2024 at 4:08 AM, JorgeB said:

Syslog-previous only ran for 3 minutes, did it crash after that?

5 minutes ago, foraye said:

Yes it did.

In that case, IMHO it's almost certainly a hardware issue.