May 18, 20179 yr Hi all, Been stable with no issues for quite a while, previous upgrades OK, saw 6.3.4, downloaded OK, rebooted when prompted, seeing USB read errors in startup. Had this happen once before, USB checked out OK then and (different) USB checks out OK now. Everything plugged into a UPS, no apparent issues during the upgrade. How can I go about recovering this? Thanks, JT Edited July 7, 20188 yr by pcss Need urgent help recovering
May 18, 20179 yr Are you using USB2 (recommended)? You can also try downloading the update and manually installing to flash.
May 18, 20179 yr Author Login prompt reporting 6.3.4, believe the config has been trashed. Using a Sandisk Ultra Fit USB 3.0 on the motherboard header in a HP N40L. I couldn't find a small enough USB 2.0 drive. It's been fine for well over a year. Will try the upgrade files manually.
July 7, 20188 yr Author Sorry to bump this very old topic, but for various reasons I've been unable to attend to this since and *urgently* need any available help in resurrecting my unRAID install. I'm not certain whether using the installer tool on my existing USB will result in loss of licence and/or data. Help greatly appreciated, thank you!
July 7, 20188 yr Author I managed to get to 6.5.3 using the install tool and transferring my .key file from a backup. I thought transferring disk.cfg would assign disks - this hasn't been the case. I have the files from the existing USB backed up, what should I be doing for the old disks config to be picked up? Thanks!
July 7, 20188 yr Author Failing that, what can I look at from the backup of the old USB to determine what the disk allocations were please?
July 7, 20188 yr Failing that, what can I look at from the backup of the old USB to determine what the disk allocations were please?If you made the backup via the appdata backup/restore plugin, then there's a text file called disk_assignmentsSent via Tapatalk because I'm either at work or enjoying the summer
July 7, 20188 yr Config/super.dat is the file you need.Not following the thread, but worst case is IF you were only running a single parity drive, you can set up a new install, assign all the disks as data disks.If only one comes up as unmountable, then issue a new config and assign that disk as the parity driveSent via Tapatalk because I'm either at work or enjoying the summer
Archived
This topic is now archived and is closed to further replies.