Currently running 6.3.5, and it has been very unstable on my rig since day one.
Before the upgrade, I ran 6.1.9. Rock stable on the exact same hardware.

 

After the upgrade I noticed a folder named "previous" on my Unraid USB-key. Guessing this is the complete copy of my old 6.1.9.

 

My plan is:

1. Stop the parity check which is currently running

2. copy all content from my Unraid USB-key onto another computer for backup

3. Stop the array

4. Copy the files from the previous folder and overwrite the files on /boot, leaving the rest of the files on /boot as they are

5. reboot Unraid and pray

6. Do a new parity check

7. boot my VM and play:)

 

Questions:

Am I going about this the right way?

Is it even possible reverting all the way from 6.3.5 to 6.1.9?

Are there any problems I should be aware of prior to doing so?

(Mind you, my hardware is the same now as it was back on 6.1.9, except for the GPU.)

 

Edited December 21, 20178 yr by blodfjert
solved

I would copy the previous folder from your USB key and try the 6.4 beta. Make sure you can go back from 6.4 because you may not be able to and if that is the case, then you have the right idea to downgrade to 6.1.9. It's just going back doesn't resolve your issues, but it will at least give you a stable system until 6.4 is in final release.

8 minutes ago, blodfjert said:

Is it even possible reverting all the way from 6.3.5 to 6.1.9?

It's possible and there won't be any issues with the array data, there can be with dockers and/or VMs.

@ashman70In my other thread I got in touch with @trinikojak, who are experiencing what seems to be the same instability issues as I am. We're both running Gigabyte motherboards. He has apparently already upgraded to 6.4, but the system hangs are still occuring.

 

I'd like to go the other way, back to good old 6.1.9.

 

@johnnie.black So I can continue according to my plan?:) Nothing to fear, etc?

 

 

Edited December 21, 20178 yr by blodfjert

4 minutes ago, blodfjert said:

Nothing to fear, etc?

You might need to recreate your docker image, though that's easy, not sure about VMs, but they should remain working, worst case you can recreate the VM and use the existing vdisk.

@johnnie.black Recreating the VM is no problem. My biggest worry is having the array mixed up.
But am I correct in assuming that the files on /boot which are not being overwritten should lay there as is? Or should all files be removed from /boot, and then only the files from "previous" be copied onto /boot?

Only files you need to overwrite are the bz* files.

Awesome! I have work to do=)

@johnnie.black Slight hickup. Upon booting 6.1.9, it seems my network is unreachable. My towers static ip has always been 192.168.1.2. When I experienced this earlier, I just had another reboot to fix it. Now that isn't working either. Strange...

You may need to reconfig you network, delete:

 

/boot/config/network.cfg

/boot/config/network-rules.cfg (if it exists)

 

reboot, you'll get an dhcp assigned IP which you can then change.

@johnnie.black You, sir, are a god amongst men!

 

I´m up and running. You were right about the VM and docker messing up, but I should be able to recreate everything.

I have now changed the card and having issues. 

VT-d is disabled

LSI card installed.