Jump to content
scatterbrain

Unraid forgets setup at each reboot

10 posts in this topic Last Reply

Recommended Posts

Posted (edited)

Hi Folks,

 

Hope you can help. I recently had to change my power supply on my 10 disk Unraid server. So I thought why not get rid of my empty 5 disk hotswap cage as well. There were no disks in it at all and I figured an extra fan would be better.

 

In any case new power supply in and turn it on and it boots fine, but no shares show up. I then go into the web admin and can see none of my disks have been assigned, all forgotten. Fortunately I assign disks in physical order = device order and boot it up.

 

Again nothing shows, so checking further I see that my shares all show up on the "Dashboard", but no shares show up on "Shares" also it seems it has forgotten my network name of "Videoraid" and replaced it with "Tower". Although I still cannot see any information in "Shares" and when I hit "Add Shares" it brings up a blank page it seems to be working. That is, now my network name is correct my computers can see my shares.

 

I know something is wrong still so I reboot thinking it may pick up some config files that were missed with the loss of drive assignment (I'm clutching at straws) but on reboot I see it has reverted back to before, that is all the drives are unassigned!

 

Again, hope you folks can help. Diagnostic files attached.

 

Also screenshot of Dashboard showing shares but screenshot below of Shares showing blank!

image.thumb.png.72fa2ae76ff8099f0255cb05a59c601e.png

 

image.thumb.png.01755f32d9d5a4e4675a0566d25a4968.png

 

videoraid-diagnostics-20190722-1433.zip

Edited by scatterbrain
add screenshots

Share this post


Link to post

I have not looked at your diagnostics, but typically something like this is caused by being unable to write the current configuration to your USB Flash drive. You may need to post up new Diagnostics after you make changes in the UI but BEFORE you reboot the server, that is to see if there are any errors of being unable to write to the USB Flash.

Share this post


Link to post

Now having looked at your Diagnostics, your USB Flash drive has issues.

 

Jul 22 14:16:54 Tower kernel: scsi 0:0:0:0: Direct-Access     USB 2.0  SD/MMC Reader         PQ: 0 ANSI: 0 CCS
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] 1984000 512-byte logical blocks: (1.02 GB/969 MiB)
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] No Caching mode page found
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jul 22 14:16:54 Tower kernel: sda: sda1
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk

 

...

 

Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 03 68 c7 00 00 01 00
Jul 22 14:16:54 Tower kernel: blk_update_request: critical medium error, dev sda, sector 223431
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 03 68 c7 00 00 01 00
Jul 22 14:16:54 Tower kernel: blk_update_request: critical medium error, dev sda, sector 223431
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 01 b0 c7 00 00 01 00
Jul 22 14:16:54 Tower kernel: blk_update_request: critical medium error, dev sda, sector 110791
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 01 b0 c7 00 00 01 00
Jul 22 14:16:54 Tower kernel: blk_update_request: critical medium error, dev sda, sector 110791
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 03 68 07 00 00 a8 00
Jul 22 14:16:54 Tower kernel: blk_update_request: critical medium error, dev sda, sector 223239
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 03 68 07 00 00 08 00
Jul 22 14:16:54 Tower kernel: blk_update_request: critical medium error, dev sda, sector 223239
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Jul 22 14:16:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 03 68 07 00 00 08 00
Jul 22 14:16:54 Tower kernel: blk_update_request: critical medium error, dev sda, sector 223239

 

...

 

Jul 22 14:17:02 Tower emhttp: import flash device: sda

 

...

 

Jul 22 14:21:53 Tower kernel: blk_update_request: I/O error, dev sda, sector 110855
Jul 22 14:21:55 Tower kernel: blk_update_request: I/O error, dev sda, sector 111095
Jul 22 14:21:58 Tower kernel: blk_update_request: critical medium error, dev sda, sector 110791
Jul 22 14:30:25 Tower kernel: blk_update_request: I/O error, dev sda, sector 111303
Jul 22 14:30:27 Tower kernel: blk_update_request: I/O error, dev sda, sector 111495
Jul 22 14:30:34 Tower kernel: blk_update_request: critical medium error, dev sda, sector 110791

Share this post


Link to post

Get a print out of the Main screen and  the disk drive assignments with their serial number.

 

Next, shut the server down.  Make a copy of the flash drive to a folder/directory on your PC.  If the copy operation has a problem, try to get a much off as possible.  The config directory is the one that is the most important.  However, in your case, it sounds like it has already been clobbered.  But anything recovered will save you a bit of work... 

 

 Then do a chkdsk (Windows--MAC has a similar command) on it. 

 

If it finds and fixes problems- Great.    If it finds problems and can't fix it, ask for more advice.

 

When plugging the flash drive back in, use a USB2 port  (usually, a USB2 port has a black plastic insert). 

Share this post


Link to post

Thanks everyone, honestly awesome to see community support in action!

 

I was unable to copy over everything for subsequently obvious reasons! I did a chkdsk d: /r and it camb back with bad clusters in 5 config files and bzroot-gui. See screenshot:

image.png.4d0a3a353b32d92b8aa8ff4a8f341d6f.png

 

But checking those files and they were filled with binary garbage. So with some trepidation I stuck the drive back in my machine (at least my license file was sound!) and of course the drive assignment was lost again, as was the server name. I then entered those back in and rebooted to see if it was saving the data and it was! Unfortunately I still couldn't configure the shares but thought that might have something to do with the corrupted bzroot-gui file. So I figured I may as well take advantage of the upgrade facility and hopefully that would replace that file.....

 

image.png.df9252567318d35f52db69a1bf9c7761.png

 

Nope, it doesnt fix everythign like now server name is also resetting. But at least I can now save my drive assignments!

 

Unfortunately when I try to modify shares etc I get served blank pages, any ideas?tower-diagnostics-20190722-1726.zip

 

It never ends does it? :)

 

Share this post


Link to post

Ok, that is one old flash Drive.  It is only 1GB in  size and you have been using it since 2010.  But far more important, it has over 600,000 bytes in bad sectors!  I would personally be replacing it as soon as possible.  Transferring your existing license to a new flash drive is an automatic process since you have your key file. 

 

Basically you are looking for a USB2 flash drive of less 32GB from a brand name manufacturer of flash drives.  (You want to know who made the drive, not who put their name on it!)  Here are the general instructions of transferring your license as well as instruction on installing the OS to new flash drive:

 

https://wiki.unraid.net/UnRAID_6/Changing_The_Flash_Device

 

And here is the link to the Download page for LimeTech:

 

https://unraid.net/download

 

I do think you would be best served by doing a new install of a much later version of Unraid.  It also appears that a lot of the files in your config folder are suspect.  So it would probably take longer to figure out that files are usable than to reconfigure the base system.  If you had a lot of Dockers installed, that issue can be address after the base system is up and running again. 

 

1--  Click on Tools, then New Config, then Retain current configuration: (from version 6.6 onwards it's Preserve current assignments), then select All, then check Yes I want to do this, click Apply then Done.

      Important Warning! Doing a New Config will reset the file system type for all disks to Auto! While usually this is not a problem, especially with

     the latest unRAID, in some circumstances this can lead to unmountable disk(s). If that happens, then you need to select the correct file system for

      those disk(s). If in doubt, ask for help!  

It appears that all of your data disks are formatted with the reiserfs file system with the exception of your cache drive which is set to auto and the parity drive which is never  formatted.  Change 'file system type'  for each of data drives and make sure it is reiserfs.  You get to this setting by clicking on Disk X under  'DEVICE' on the Main page. 

 

2-- Go back to the Main page and check that all of your disk are assigned as you want them 

 

3-- You should see all array disks with blue icons, and a warning (All data on the parity drive will be erased when array is started), and a check box for Parity is already valid. VERY IMPORTANT! Click the check box! Make sure that it's checked to indicate that Parity is already valid or your Parity disk will be rebuilt! Then click the Start button under  Array Operation.

 

You notice that I recommended that you assume that parity is valid.  At this point there is not reason to assume that it is not.  But I would run an non-correcting check to validate this assumption as soon as possible! 

 

If you encounter anything that confuses you, stop and ask before proceeding. 

Share this post


Link to post

Thank you all for your help and sorry I didn't get back earlier.

 

A power outage forced me to address the issues of the flash card and I did the update as directed to Version: 6.7.2. I also copied over the config files which seemed to work and, with the exception of some of the configs that were lost in the original issue, all the other stuff like shares were maintained without further input - yeah!

 

Great job, great community!

Share this post


Link to post

If anyone does a replacement key as suggested in this post then one word of caution. It turns out you are only allowed 1 replacement per year. I replaced my faulty flash-drive with a spare Micro SD card and assumed it was temporary until I got my new high speed flash drive in. Well I tried to install to the flash drive but then fell afoul of the 1 replacement per year issue!

 

I've sent a note to support to see if they can allow another replacement.....let's find out!

Share this post


Link to post
3 minutes ago, scatterbrain said:

If anyone does a replacement key as suggested in this post then one word of caution. It turns out you are only allowed 1 replacement per year. I replaced my faulty flash-drive with a spare Micro SD card and assumed it was temporary until I got my new high speed flash drive in. Well I tried to install to the flash drive but then fell afoul of the 1 replacement per year issue!

 

I've sent a note to support to see if they can allow another replacement.....let's find out!

You are correct that 1 automated transfer per year is allowed.   Any additional transfers have to be handled by an email to Limetech explaining why but they are normally accommodating to such requests - it just adds a little delay to the process.

Share this post


Link to post

Just and update. Support came back with a request for the Flash GUID, I sent it to them and within 10 minutes of the second email I had  my server operational with my new Flash drive. They answered the first email within 3 hours (I didnt see it for an hour) and the second one in 10 minutes.

 

Yet again a great experience with the Unraid team! It really is a 5* service and exceptionally good value.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.