December 8, 20178 yr Why do you need to do that? If that was your previous release you can copy contents of 'previous' directory on flash to root of flash and then reboot. Alternately can download the zip and copy for the bz* files to your flash: https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.4.0_rc14-x86_64.zip
December 8, 20178 yr Author For testing purposes really.. I didn't know about the "previous" directory, I've been switching between 6.3.5 and rc15.... so I'll have to do the manual way of copying bz* files. 6.3.5 was stable on my i5-2500k. 6.3.5 was not stable on my ryzen 5 1600 cpu/mb upgrade. 6.4 rcu14 was stable with my ryzen 5 cpu/mb + dockers upgraded to 6.4 rcu15 and now I get. Array Starting Starting Services... it's been doing that for 2 hours now... Since it was working fine on rc14... i just want to revert back for testing.
December 8, 20178 yr Author Update.. Did the manual downgrade procedure and now my server is doing a parity check, made it past the starting services issue. Looks to be my normal again. Will update to rc16 when it comes around. i can't do much testing right now.. (need something running at this point) Thanks "limetech" for the downgrade procedure. Joey
December 8, 20178 yr 1 hour ago, Joey Macaraeg said: For testing purposes really.. I didn't know about the "previous" directory, I've been switching between 6.3.5 and rc15.... so I'll have to do the manual way of copying bz* files. 6.3.5 was stable on my i5-2500k. 6.3.5 was not stable on my ryzen 5 1600 cpu/mb upgrade. 6.4 rcu14 was stable with my ryzen 5 cpu/mb + dockers upgraded to 6.4 rcu15 and now I get. Array Starting Starting Services... it's been doing that for 2 hours now... Since it was working fine on rc14... i just want to revert back for testing. Next time something like this happens, please try and capture diagnostics.
Archived
This topic is now archived and is closed to further replies.