Hi, I know this should be easy, but ... upon downloading and installing 6.3.5 I am getting a "flash write error 0".  The flash drive is old and replacing it makes sense, but I don't think replacing it is as simple as copying the contents of the existing flash drive to a new one (do I not have to obtain a new guid?)?  Sorry, I looked and couldn't find an answer... thanks for any help.

 

 

BTW, here is the full output: 

 

plugin: updating: unRAIDServer.plg
plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.3.5-x86_64.zip ... done
plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.3.5-x86_64.md5 ... done
Archive: /tmp/unRAIDServer.zip
inflating: /tmp/unRAIDServer/bzimage 
inflating: /tmp/unRAIDServer/bzroot 
inflating: /tmp/unRAIDServer/bzroot-gui 
inflating: /tmp/unRAIDServer/changes.txt 
creating: /tmp/unRAIDServer/config/
inflating: /tmp/unRAIDServer/config/ident.cfg 
inflating: /tmp/unRAIDServer/config/network.cfg 
extracting: /tmp/unRAIDServer/config/go 
creating: /tmp/unRAIDServer/config/plugins/
creating: /tmp/unRAIDServer/config/plugins/dockerMan/
extracting: /tmp/unRAIDServer/config/plugins/dockerMan/template-repos 
extracting: /tmp/unRAIDServer/config/docker.cfg 
extracting: /tmp/unRAIDServer/config/domain.cfg 
inflating: /tmp/unRAIDServer/license.txt 
inflating: /tmp/unRAIDServer/make_bootable.bat 
inflating: /tmp/unRAIDServer/make_bootable_linux 
inflating: /tmp/unRAIDServer/make_bootable_mac 
inflating: /tmp/unRAIDServer/memtest 
creating: /tmp/unRAIDServer/syslinux/
inflating: /tmp/unRAIDServer/syslinux/ldlinux.c32 
inflating: /tmp/unRAIDServer/syslinux/libcom32.c32 
inflating: /tmp/unRAIDServer/syslinux/libutil.c32 
inflating: /tmp/unRAIDServer/syslinux/make_bootable_mac.sh 
inflating: /tmp/unRAIDServer/syslinux/mboot.c32 
inflating: /tmp/unRAIDServer/syslinux/mbr.bin 
inflating: /tmp/unRAIDServer/syslinux/menu.c32 
inflating: /tmp/unRAIDServer/syslinux/syslinux 
inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg- 
inflating: /tmp/unRAIDServer/syslinux/syslinux.exe 
inflating: /tmp/unRAIDServer/syslinux/make_bootable_linux.sh 
inflating: /tmp/unRAIDServer/syslinux/syslinux_linux 
inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg 
flash write error 0, maybe corrupted?
plugin: run failed: /bin/bash retval: 1

First, see if you can get a diagnostics file.    'Tools'   >>>   "Diagnostics'

 

Second, Pull the Flash Drive and run chkdsk on it in a Windows computer.  (Apple OS's have a similar utility.)  While you have it out, backup all of that Flash Disk.

16 hours ago, Frank1940 said:

First, see if you can get a diagnostics file.    'Tools'   >>>   "Diagnostics'

 

Second, Pull the Flash Drive and run chkdsk on it in a Windows computer.  (Apple OS's have a similar utility.)  While you have it out, backup all of that Flash Disk.

Thanks Frank1940.  I ran Diagnostics overnight and it was still "Downloading" .  Refreshing the page changed this to "Download"; clicking on the "Done" button produced no file download or link.  So, I'm not sure if a zipped file was produced; it appears not.  At any rate, I will copy over the syslog and send that along next.  Thanks.

It downloads to whatever directory/folder you have set for your browser to download into.

20 hours ago, Frank1940 said:

First, see if you can get a diagnostics file.    'Tools'   >>>   "Diagnostics'

 

Second, Pull the Flash Drive and run chkdsk on it in a Windows computer.  (Apple OS's have a similar utility.)  While you have it out, backup all of that Flash Disk.

zip file attached.  I had to run Diagnostics on Firefox; Chrome would not create file.  

tower-diagnostics-20170713-1253.zip

update: running diskutil from Terminal on flash drive exited with error code 0, presumably indicating no issues.  I have copied contents of flash drive to my mac; then, formatted (as FAT) a new flash drive, named in UNRAID, and copied all contents over.  Put this back on unRAID box and I come up with a blinking cursor.  I think this is where I have to modify guid but I await your instructions.  Thanks again.

Not quite right!  You get the new key file after unRAID has booted.  The procedure is here:

 

      https://lime-technology.com/replace-key/

 

One of two things may have happened. 

 

First one---  You did not run the script on your Mac to make the disk bootable. Try this first possibility  first.  (The instructions for doing this are in the link in the second possibility.)

 

Second possibility--- It could be you have some files that were clobbered on the original flash drive.   (The upgrade write to the drive could have been with corrupted data.)  And that will have to fixed first. 

 

I would reformat that drive and download the software from LimeTech for the version you want.  Then see this section of the upgrade manual for the files that you need to move over to preserve the basic settings:

       https://wiki.lime-technology.com/Upgrading_to_UnRAID_v6#Install_the_unRAID_upgrade

 

(You can copy over the go file.)  At this point, you should get your new key file using the link above.  I am not sure what you have to do get all of your Dockers and VM's up-and-running but I would tend to do that in stages unless someone else (more knowledgeable than me) jumps in to provide you will detailed instructions

21 hours ago, Frank1940 said:

First, see if you can get a diagnostics file.    'Tools'   >>>   "Diagnostics'

 

Second, Pull the Flash Drive and run chkdsk on it in a Windows computer.  (Apple OS's have a similar utility.)  While you have it out, backup all of that Flash Disk.

Here is what I have done (I am still getting to BIOS screen, then to "Initializing", a brief (too quick to view) list of devices, then the blank screen with cursor):

 

erase new flash drive to FAT format.  copy over all files from the freshly downloaded version of unRAID (6.3.5). run make bootable for mac. copy over .key file to config folder.  also copy over shares folder, ident.cfg, share.cfg, network.cfg to config folder (note that the last three I copied over on a second attempt; on my initial attempt I did not).  I HAVE confirmed BIOS: the initial item in the boot order is the USB drive.  I have confirmed that the USB port is ok (at least, i can enter items from keyboard attached to it).  I have tried with copying over the go file and without doing that. I have even tried all of the above on yet another new flash drive.  Pretty confused right now.. and thanks again for your prompt responses.

11 minutes ago, smellthebean said:

I HAVE confirmed BIOS: the initial item in the boot order is the USB drive.

It's usually not good enough to have the first boot priority to be USB Removable.  Usually you have to set it to hard disk and then from hard disk priorities (BBS Priorities) select the Flash Drive.  Also should be noted that when selecting the flash drive, if there are 2 entries (UEFI-xxxxx and a non-UEFI) you should select the NON UEFI one on 6.3.5

 

Also, have you tried actually pressing F9 (or your m/b's equivalent) during the POST to allow you to manually select the Boot Device?

 

23 hours ago, Frank1940 said:

First, see if you can get a diagnostics file.    'Tools'   >>>   "Diagnostics'

 

Second, Pull the Flash Drive and run chkdsk on it in a Windows computer.  (Apple OS's have a similar utility.)  While you have it out, backup all of that Flash Disk.

Squid, you are wise.  Yes, I did have to go to a separate screen and make Drive 1 the USB drive.  At this moment I am rebuilding parity (I did have to reassign each drive, probably because I didn't copy over a .cfg file(?), but that isn't much of a problem).  

 

Thank you again, Squid and Frank1940, for your prompt and generous help!

34 minutes ago, smellthebean said:

probably because I didn't copy over a .cfg file(?),

config/super.dat contains your disk assignments.

On 7/12/2017 at 4:37 PM, Frank1940 said:

First, see if you can get a diagnostics file.    'Tools'   >>>   "Diagnostics'

 

Second, Pull the Flash Drive and run chkdsk on it in a Windows computer.  (Apple OS's have a similar utility.)  While you have it out, backup all of that Flash Disk.

Everything seems good now, again thanks, but I am attempting to recover my Plex docker container.  It was available via dropdown and I initiated the process, but it does appear that I am starting over.  Is there a way to do this without having to re-scan my rather large media libraries?  

IF you don't get a response here in a couple of hours, you might want to ask that question in the support thread for the plex package that you are using.

4 hours ago, smellthebean said:

Is there a way to do this without having to re-scan my rather large media libraries?

Basically you just need to configure it like it was configured before and it should pick up where it was since the appdata is not on flash.

On 7/12/2017 at 4:37 PM, Frank1940 said:

40 minutes ago, trurl said:

Basically you just need to configure it like it was configured before and it should pick up where it was since the appdata is not on flash.

Thanks, but right now I can't even get the Docker to come up:  going to settings and turning it off and back on doesn't help.  FYI, I did take Frank's advice and posted this on a more appropriate support thread.