July 29, 20214 yr So a few days ago I was over at a friends house playing some Minecraft off a server hosted on my Unraid server. We started getting disconnected, so I went home figuring the internet equipment just needed to be restarted. Roommate confirmed that it had been acting up. Reboot network equipment, and it still kicks my friend off after about 45 seconds. The network does seem to be stable now though, so I rebooted Unraid from the web UI. It did not come back. After reboot it showed just a terminal interface (should be a VM with GPU passthrough.) Could not connect to Web UI, boot in GUI mode can't connect to localhost.. So I pulled the flashdrive and took a look from my desktop. Chdsk repaired some errors (crap) but things look off. It has renamed itself back to tower and there seem to be a lot of missing files. Just got my new drive in and loaded up a fresh install and oh are there things missing from the old one. So rebuild great just what I want to do. I can't seem to find a backup of the old flash drive, but there may be one somewhere on either the array or the cache drive. Can any of you much more intelligent people than me help find a way to get things booted back without loosing my array? I did find an old diagnostics folder from before so maybe that can help here? Including the diagnostics that I got off just recently and an older one that seems to still have some configuration in it. TLDR: I think my flash drive died and I can't find a backup, but there might be one on the array. tower-diagnostics-20210728-1741.zip ares-diagnostics-20210321-2150.zip
July 29, 20214 yr Community Expert Have you changed any disk assignments since that older diagnostic?
July 29, 20214 yr Community Expert 1 minute ago, trurl said: Have you changed any disk assignments since that older diagnostic? Doesn't look like it. Take a look in the SMART folder in those old diagnostics and you can see your disk assignments. You can create a new install on that flash and use those same disk assignments to get your array started again. Do you have a copy of your license .key file?
July 29, 20214 yr Author 2 minutes ago, trurl said: Doesn't look like it. Take a look in the SMART folder in those old diagnostics and you can see your disk assignments. You can create a new install on that flash and use those same disk assignments to get your array started again. Do you have a copy of your license .key file? Thank you for your help. So I think that older diagnostic is from right after (ish) I upgraded my parity to an 8TB. Found the drive assignments in the folder, there are two there though that aren't numbered. Not supper sure about those. I have a couple of places to look for the license file will check but not high hopes.
July 29, 20214 yr Community Expert 14 minutes ago, xplicitsomebody said: two there though that aren't numbered Here is that same information from syslog. disk0 is parity. sdh (serial ending R2E1) wasn't assigned. Note that the sd identifier can change, only serial number is used to identify disks. I think sr0 is dvd drive. Feb 19 09:53:31 Ares emhttpd: Device inventory: Feb 19 09:53:31 Ares emhttpd: ST8000VN0022-2EL112_ZA1JJJA0 (sdj) 512 15628053168 Feb 19 09:53:31 Ares emhttpd: WDC_WD40EFRX-68N32N0_WD-WCC7K5HTR2E1 (sdh) 512 7814037168 Feb 19 09:53:31 Ares emhttpd: Samsung_SSD_860_EVO_500GB_S3Z1NB0K146251A (sdg) 512 976773168 Feb 19 09:53:31 Ares emhttpd: WDC_WD40EFRX-68N32N0_WD-WCC7K7FRZ775 (sdd) 512 7814037168 Feb 19 09:53:31 Ares emhttpd: ST2000DM006-2DM164_Z4Z7NZA3 (sde) 512 3907029168 Feb 19 09:53:31 Ares emhttpd: WDC_WD40EFRX-68N32N0_WD-WCC7K6RFERDK (sdb) 512 7814037168 Feb 19 09:53:31 Ares emhttpd: WDC_WD40EFRX-68N32N0_WD-WCC7K0PJ5J27 (sdf) 512 7814037168 Feb 19 09:53:31 Ares emhttpd: TOSHIBA_MK5059GSX_1088P15RT (sdc) 512 976773168 Feb 19 09:53:31 Ares emhttpd: WDC_WD40EFRX-68N32N0_WD-WCC7K2YREU4P (sdi) 512 7814037168 Feb 19 09:53:31 Ares emhttpd: Generic_Flash_Disk_F497B9B2-0:0 (sda) 512 30720000 Feb 19 09:53:31 Ares kernel: mdcmd (1): import 0 sdj 64 7814026532 0 ST8000VN0022-2EL112_ZA1JJJA0 Feb 19 09:53:31 Ares kernel: md: import disk0: (sdj) ST8000VN0022-2EL112_ZA1JJJA0 size: 7814026532 Feb 19 09:53:31 Ares kernel: mdcmd (2): import 1 sde 64 1953514552 0 ST2000DM006-2DM164_Z4Z7NZA3 Feb 19 09:53:31 Ares kernel: md: import disk1: (sde) ST2000DM006-2DM164_Z4Z7NZA3 size: 1953514552 Feb 19 09:53:31 Ares kernel: mdcmd (3): import 2 sdb 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K6RFERDK Feb 19 09:53:31 Ares kernel: md: import disk2: (sdb) WDC_WD40EFRX-68N32N0_WD-WCC7K6RFERDK size: 3907018532 Feb 19 09:53:31 Ares kernel: mdcmd (4): import 3 sdc 64 488386552 0 TOSHIBA_MK5059GSX_1088P15RT Feb 19 09:53:31 Ares kernel: md: import disk3: (sdc) TOSHIBA_MK5059GSX_1088P15RT size: 488386552 Feb 19 09:53:31 Ares kernel: mdcmd (5): import 4 sdf 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K0PJ5J27 Feb 19 09:53:31 Ares kernel: md: import disk4: (sdf) WDC_WD40EFRX-68N32N0_WD-WCC7K0PJ5J27 size: 3907018532 Feb 19 09:53:31 Ares kernel: mdcmd (6): import 5 sdd 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K7FRZ775 Feb 19 09:53:31 Ares kernel: md: import disk5: (sdd) WDC_WD40EFRX-68N32N0_WD-WCC7K7FRZ775 size: 3907018532 Feb 19 09:53:31 Ares kernel: mdcmd (7): import 6 sdi 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K2YREU4P Feb 19 09:53:31 Ares kernel: md: import disk6: (sdi) WDC_WD40EFRX-68N32N0_WD-WCC7K2YREU4P size: 3907018532 Feb 19 09:53:31 Ares kernel: mdcmd (8): import 7 Feb 19 09:53:31 Ares kernel: mdcmd (9): import 8 Feb 19 09:53:31 Ares kernel: mdcmd (10): import 9 Feb 19 09:53:31 Ares kernel: mdcmd (11): import 10 Feb 19 09:53:31 Ares kernel: mdcmd (12): import 11 Feb 19 09:53:31 Ares kernel: mdcmd (13): import 12 Feb 19 09:53:31 Ares kernel: mdcmd (14): import 13 Feb 19 09:53:31 Ares kernel: mdcmd (15): import 14 Feb 19 09:53:31 Ares kernel: mdcmd (16): import 15 Feb 19 09:53:31 Ares kernel: mdcmd (17): import 16 Feb 19 09:53:31 Ares kernel: mdcmd (18): import 17 Feb 19 09:53:31 Ares kernel: mdcmd (19): import 18 Feb 19 09:53:31 Ares kernel: mdcmd (20): import 19 Feb 19 09:53:31 Ares kernel: mdcmd (21): import 20 Feb 19 09:53:31 Ares kernel: mdcmd (22): import 21 Feb 19 09:53:31 Ares kernel: mdcmd (23): import 22 Feb 19 09:53:31 Ares kernel: mdcmd (24): import 23 Feb 19 09:53:31 Ares kernel: mdcmd (25): import 24 Feb 19 09:53:31 Ares kernel: mdcmd (26): import 25 Feb 19 09:53:31 Ares kernel: mdcmd (27): import 26 Feb 19 09:53:31 Ares kernel: mdcmd (28): import 27 Feb 19 09:53:31 Ares kernel: mdcmd (29): import 28 Feb 19 09:53:31 Ares kernel: mdcmd (30): import 29 Feb 19 09:53:31 Ares kernel: md: import_slot: 29 empty Feb 19 09:53:31 Ares emhttpd: import 30 cache device: (sdg) Samsung_SSD_860_EVO_500GB_S3Z1NB0K146251A Feb 19 09:53:31 Ares emhttpd: import flash device: sda
July 29, 20214 yr Author Yes! Okay, so I got it spun up and yes the R2E1 was not assigned and i'm pretty sure that sr0 is in fact the DVD drive. Throughs me a bit that it would have an entry in the smart folder though. Found the backup as well now just figuring out how to properly recover with it.
July 29, 20214 yr Author Okay this is resolved, I am back up and running. Thank you so much for your assistance trurl.
July 29, 20214 yr Community Expert You might consider storing flash backup somewhere other than on the server you can't boot because of flash problems. Have you looked into the My Servers plugin?
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.