I had a USB drive fail.  Unfortunately, it wasn't backed up.  The USB is not completely bad, (I can still see many files on it).  I've built a new USB.  What files would I need to move to the new USB from the old one (i.e. config, etc) in order for it to work properly...if that can be done.  

 

If it can't be done, how would I recover the ability to mount the drives?

Edited June 21, 20179 yr by jeffreywhunter

https://wiki.lime-technology.com/Files_on_v6_boot_drive

So if I read this correctly, really the ONLY directory that matters (other than being at the version?) is the \config directory - and in particular the super.dat file.  So essentially, if I copy over the config directory, I should be good to go?

12 minutes ago, jeffreywhunter said:

So if I read this correctly, really the ONLY directory that matters (other than being at the version?) is the \config directory - and in particular the super.dat file.  So essentially, if I copy over the config directory, I should be good to go?

You will have to get a new key for the new drive.

 

Are you sure the original is really bad and not just corrupt? If you can still read from it you might just copy the config folder, then prepare it again as a new install starting with reformatting to FAT32, etc. then copy config back.

Yes, I was prepared to get a new key, but have not yet.  Here's what I've done...

 

1. Bought new USB

2. Formated and installed 6.3.5 on it.

3. Booted, access webgui (it wanted a key).

4. Copied config from old USB to new USB

5. When I boot

- Console shows it Boots and has an IP

- I can ping from Windows

- When I try to access WebGUI, I get connection refused

http://my.jetscreenshot.com/12412/20170615-t9wq-41kb.jpg

 

Suggestions?

3 minutes ago, jeffreywhunter said:

Yes, I was prepared to get a new key, but have not yet.  Here's what I've done...

 

1. Bought new USB

2. Formated and installed 6.3.5 on it.

3. Booted, access webgui (it wanted a key).

4. Copied config from old USB to new USB

5. When I boot

- Console shows it Boots and has an IP

- I can ping from Windows

- When I try to access WebGUI, I get connection refused

http://my.jetscreenshot.com/12412/20170615-t9wq-41kb.jpg

 

Suggestions?

Did your config copy include the go file?

yes

 

18 minutes ago, jeffreywhunter said:

yes

 

Type diagnostics at the command line. This will save the diagnostics zip to your flash. Post it.

Attached...

hunternasndh-diagnostics-20170615-1131.zip

@trurlI looked through the diagnostics, didn't see any significant errors.  What would prevent the WebGui from responding?

Have you tried booting in SAFE mode?

@trurlTried Safe, no plugins, no GUI - same error...  This site can't be reached 192.168.29.110 refused to connect.  I'm able to ping.  Telnet gets "session stopped".  But I'm able to login to console and execute commands (ergo the diagnostics command executed previously)...

 

So I also started unraid in GUI mode.  The webgui loaded and displayed the message about getting the GUID for the USB not being correct (and could see the other typical tabs in the WebGui).

 

Thoughts?

Try deleting the contents of the SSH / SSL folder (within config on the flash drive) and then reboot.

4 hours ago, Squid said:

Try deleting the contents of the SSH / SSL folder (within config on the flash drive) and then reboot.

 

Ugh, still getting 

This site can’t be reached

192.168.29.110 refused to connect.

Try:

• Checking the connection
• Checking the proxy and the firewall

ERR_CONNECTION_REFUSED

 

I can see the server in windows file manager, when I try to access it, I'm asked to login, but it states the credentials are not good.

Edited June 16, 20179 yr by jeffreywhunter

@trurl any further thoughts?  Is there a way to get the layout of the drives from the flash?  Its annoying to have to install everything again, but if I can just rebuild, I'm happy to do that.  And this time AppBackup will be installed! 

1 hour ago, jeffreywhunter said:

Is there a way to get the layout of the drives from the flash?

from your previously posted diagnostics  (disk 0 is your parity drive)

Jun 15 10:01:56 HunterNASNDH kernel: mdcmd (1): import 0 sdb 1953514552 0 WDC_WD20EARX-00PASB0_WD-WCAZAE435475
Jun 15 10:01:56 HunterNASNDH kernel: md: import disk0: (sdb) WDC_WD20EARX-00PASB0_WD-WCAZAE435475 size: 1953514552 
Jun 15 10:01:56 HunterNASNDH kernel: mdcmd (2): import 1 sdc 1953514552 0 WDC_WD20EARX-328FB0_WD-WCAZAJ311325
Jun 15 10:01:56 HunterNASNDH kernel: md: import disk1: (sdc) WDC_WD20EARX-328FB0_WD-WCAZAJ311325 size: 1953514552 
Jun 15 10:01:56 HunterNASNDH kernel: mdcmd (3): import 2 sdd 976762552 0 WDC_WD10EARX-00N0YB0_WD-WMC0T0687972
Jun 15 10:01:56 HunterNASNDH kernel: md: import disk2: (sdd) WDC_WD10EARX-00N0YB0_WD-WMC0T0687972 size: 976762552 
Jun 15 10:01:56 HunterNASNDH kernel: mdcmd (4): import 3 sde 976758424 0 WDC_WD10EARS-00Y5B1_WD-WCAV5L941578
Jun 15 10:01:56 HunterNASNDH kernel: md: import disk3: (sde) WDC_WD10EARS-00Y5B1_WD-WCAV5L941578 size: 976758424 
Jun 15 10:01:56 HunterNASNDH kernel: mdcmd (5): import 4 sdf 976762552 0 WDC_WD10EADS-00L5B1_WD-WCAU4A310594
Jun 15 10:01:56 HunterNASNDH kernel: md: import disk4: (sdf) WDC_WD10EADS-00L5B1_WD-WCAU4A310594 size: 976762552 
Jun 15 10:01:56 HunterNASNDH kernel: mdcmd (6): import 5 sdg 976762552 0 ST31000528AS_9VP8Q5FY
Jun 15 10:01:56 HunterNASNDH kernel: md: import disk5: (sdg) ST31000528AS_9VP8Q5FY size: 976762552 
Jun 15 10:01:56 HunterNASNDH kernel: mdcmd (7): import 6 sdi 976762552 0 Hitachi_HDS721010CLA332_JP2940HZ1954HC
Jun 15 10:01:56 HunterNASNDH kernel: md: import disk6: (sdi) Hitachi_HDS721010CLA332_JP2940HZ1954HC size: 976762552 
Jun 15 10:01:56 HunterNASNDH kernel: mdcmd (8): import 7 sdh 976762552 0 Hitachi_HDS721010CLA332_JP9930HZ33T20H
Jun 15 10:01:56 HunterNASNDH kernel: md: import disk7: (sdh) Hitachi_HDS721010CLA332_JP9930HZ33T20H size: 976762552 
Jun 15 10:01:56 HunterNASNDH kernel: mdcmd (9): import 8 sdk 1953514552 0 Hitachi_HDS5C3020ALA632_ML0220F30MT7XD
Jun 15 10:01:56 HunterNASNDH kernel: md: import disk8: (sdk) Hitachi_HDS5C3020ALA632_ML0220F30MT7XD size: 1953514552 

 

THANK YOU!  Did you get this from the syslog or from a file?  I'd like to learn...

1 hour ago, jeffreywhunter said:

syslog

you should be able to find the exact lines easily just by looking at the timestamps

@trurl, perhaps there's another reason for this issue?  I did the following:

 

1. Downloaded latest 6.3.5

2. Purchased fresh USB

3. Expanded zip file to USB installing UR 6.3.5, made bootable

4. Copied Pro.key, Network.cfg and Ident.cfg to /config

5. Rebooted.  Got ERR_CONNECTION_REFUSED

6. Checked server.  Good IP, from server could ping other devices.

7. From windows 10, pinged server successfully.

8. Refreshed browser (chrome latest on Win 10 64bit), suddenly unRaid GUI appears.

9. Go through process to generate new GUID for USB.  Generates works fine.  Get new key.

10. Installed new key.  Got an ERR_CONNECTION_REFUSED (see screenshot).

 

Not sure what to do next...

 

ERR_CONNECTION_REFUSED screenshot during GUID Pro.Key installation.

Turns out the fix for this problem was to get the updated pro.key on the usb BEFORE using it.  Infrequently, it would display the registration page.  When I tried to load the key from the registration page, it failed.  I emailed Tommy and his answer was to copy the pro.key directly to the USB drive.  That solved the problem...