Keek Uras Posted April 1, 2023 Share Posted April 1, 2023 (edited) Hello! I upgraded from 6.1.1.5 to 6.1.2 RC2. After the upgrade was complete, I rebooted. Once back into unRAID, the array started fine, but once I clicked on Mount for an NFS share, the server GUI was no longer accessible until reboot. After a few reboots, I figured out it would happen with anything I clicked (Mount, Dockers, Settings, etc). I rolled back to 6.1.1.5 and the issue remains. The last boot, I didn't start the array and was able to go to Tools | Diagnostics (attached). I appreciate any help you can give. Thanks! repository-diagnostics-20230401-1359.zip Edited April 1, 2023 by Keek Uras Quote Link to comment
Keek Uras Posted April 1, 2023 Author Share Posted April 1, 2023 I was able to get back in and recreate the issue after enabling syslog. Please see attached. Thanks. syslog Quote Link to comment
JorgeB Posted April 2, 2023 Share Posted April 2, 2023 If it happens after clicking on settings, and downgrading didn't help, it could be a flash drive config issue, first create a new stock v6.12-rc2 flash drive using a different flash drive, no key needed, just to confirm the GUI works with that one. Quote Link to comment
Keek Uras Posted April 2, 2023 Author Share Posted April 2, 2023 I did run a Windows scan and fix on my current USB stick but it didn't find any issues. I'll give it a try. Thanks! Quote Link to comment
Keek Uras Posted April 2, 2023 Author Share Posted April 2, 2023 4 hours ago, JorgeB said: If it happens after clicking on settings, and downgrading didn't help, it could be a flash drive config issue, first create a new stock v6.12-rc2 flash drive using a different flash drive, no key needed, just to confirm the GUI works with that one. I'm not sure how I can complete this test. None of the drives are assigned when I boot to it and I don't know which one is my parity drive. Quote Link to comment
Keek Uras Posted April 2, 2023 Author Share Posted April 2, 2023 I finally did all the switching back and forth for the parity drive S/N, but this new install says it's going to overwrite my drives and I can't do that. Anything else I can try? Quote Link to comment
JorgeB Posted April 2, 2023 Share Posted April 2, 2023 19 hours ago, Keek Uras said: I figured out it would happen with anything I clicked (Mount, Dockers, Settings, etc). You don't need drives assigned to click on Settings. Quote Link to comment
Keek Uras Posted April 2, 2023 Author Share Posted April 2, 2023 The issue occurs after starting the array. Quote Link to comment
JorgeB Posted April 2, 2023 Share Posted April 2, 2023 Ahh, OK, you can copy super.dat and the pools folder from the old flash drive (config folder), or just re-assign all devices as they were before and check "parity is already valid" before starting the array, no existing data will be deleted, as long as all devices are assigned correctly. Quote Link to comment
Keek Uras Posted April 2, 2023 Author Share Posted April 2, 2023 12 minutes ago, JorgeB said: Ahh, OK, you can copy super.dat and the pools folder from the old flash drive (config folder), or just re-assign all devices as they were before and check "parity is already valid" before starting the array, no existing data will be deleted, as long as all devices are assigned correctly. I did that, now I only get the login command prompt. The web GUI doesn't load at all on the new USB drive. I just get this: This site can’t be reached 172.16.0.166 refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED Quote Link to comment
Keek Uras Posted April 2, 2023 Author Share Posted April 2, 2023 If anyone else has any idea, please let me know. My Windows PC is a VM in unRAID so I'm dead in the water and I work from home. I'm posting from a little Linux NUC I have. Quote Link to comment
JorgeB Posted April 3, 2023 Share Posted April 3, 2023 18 hours ago, Keek Uras said: I did that, now I only get the login command prompt. This was after copying just the files I mentioned above? Quote Link to comment
Keek Uras Posted April 3, 2023 Author Share Posted April 3, 2023 2 hours ago, JorgeB said: This was after copying just the files I mentioned above? Correct. Quote Link to comment
JorgeB Posted April 3, 2023 Share Posted April 3, 2023 That doesn't make sense since those files have nothing to do with the GUI, try starting again, see if you still have access before copying them and them copy them again. Quote Link to comment
Keek Uras Posted April 3, 2023 Author Share Posted April 3, 2023 35 minutes ago, JorgeB said: That doesn't make sense since those files have nothing to do with the GUI, try starting again, see if you still have access before copying them and them copy them again. The GUI worked the first time before copying those files. I'll give it a try but what do I do if the issue remains? I'm using a brand new flash drive and being an IT person, I'm sure I'm copying the right files. I really need to get back up and running today. Quote Link to comment
JorgeB Posted April 3, 2023 Share Posted April 3, 2023 I suspect you have other issues, the symptoms you are describing don't make much sense, starting with the original problem, and the fact that downgrading didn't fix it. Quote Link to comment
Keek Uras Posted April 3, 2023 Author Share Posted April 3, 2023 Everything worked fine until I upgraded. Is there a way to restore unRAID without wiping my drives? Quote Link to comment
Solution JorgeB Posted April 3, 2023 Solution Share Posted April 3, 2023 Yes, you can create a new flash drive then assign all the devices as they were and check "parity is already valid" before array start, all data/pool disks will be imported, if you don't know the assignments then can be seen on the diags posted, disk0 is parity: Apr 1 13:55:46 REPOSITORY kernel: md: import disk0: (sdm) WDC_WD160EMFZ-11AFXA0_2CG607NR size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk1: (sdk) TOSHIBA_MG08ACA16TE_91D0A0SUFWTG size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk2: (sdg) WDC_WD140EDFZ-11A0VA0_9LG79M3G size: 13672382412 Apr 1 13:55:46 REPOSITORY kernel: md: import disk3: (sdi) TOSHIBA_MG08ACA16TE_91L0A23XFWTG size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk4: (sdh) TOSHIBA_MG08ACA16TE_91D0A12BFWTG size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk5: (sdj) TOSHIBA_MG08ACA16TE_91L0A41XFWTG size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk6: (sdf) WDC_WD140EDFZ-11A0VA0_QBJW606T size: 13672382412 Apr 1 13:55:46 REPOSITORY kernel: md: import disk7: (sdl) TOSHIBA_MG08ACA16TE_91L0A30LFWTG size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk8: (sdc) WDC_WD140EDFZ-11A0VA0_9KGVYJ9L size: 13672382412 Apr 1 13:55:46 REPOSITORY kernel: md: import disk9: (sdd) WDC_WD120EMFZ-11A6JA0_XJG0KLNM size: 11718885324 Apr 1 13:55:46 REPOSITORY kernel: md: import disk10: (sdr) WDC_WD120EMFZ-11A6JA0_9JHG38XT size: 11718885324 Apr 1 13:55:46 REPOSITORY kernel: md: import disk11: (sdq) WDC_WD120EMAZ-11BLFA0_8CK40JJE size: 11718885324 Apr 1 13:55:46 REPOSITORY kernel: md: import disk12: (sdn) WDC_WD120EMAZ-11BLFA0_8CJWDE6E size: 11718885324 Apr 1 13:55:46 REPOSITORY kernel: md: import disk13: (sdp) HGST_HUS728T8TALE6L4_VDGMW6LD size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk14: (sdac) HGST_HUS728T8TALE6L4_VDGLS39D size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk15: (sdae) HGST_HUS728T8TALE6L4_VDKZ3DUM size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk16: (sdad) HGST_HUS728T8TALE6L4_VDGMZGJD size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk17: (sdag) HGST_HUS728T8TALE6L4_VDKZS7MM size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk18: (sdaf) HGST_HUS728T8TALE6L4_VDGN090D size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk19: (sdo) WDC_WD60EFRX-68L0BN1_WD-WX11D38E2D7P size: 5860522532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk20: (sdv) ST8000AS0002-1NA17Z_Z840P04T size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk21: (sdw) ST8000AS0002-1NA17Z_Z840P8W8 size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk22: (sdx) ST8000AS0002-1NA17Z_Z8410NWK size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk23: (sdy) ST8000AS0002-1NA17Z_Z8410P11 size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk24: (sdz) ST8000AS0002-1NA17Z_Z8410Q6E size: 7814026532 Apr 1 13:55:47 REPOSITORY kernel: md: import disk25: (sdaa) ST8000AS0002-1NA17Z_Z840P8XR size: 7814026532 Apr 1 13:55:47 REPOSITORY kernel: md: import disk26: (sdab) ST8000AS0002-1NA17Z_Z840P0LC size: 7814026532 Apr 1 13:55:47 REPOSITORY kernel: md: import disk27: (sdu) ST8000AS0002-1NA17Z_Z840Q6YA size: 7814026532 Apr 1 13:55:47 REPOSITORY kernel: md: import disk28: (sdt) ST8000NM000A-2KE101_WKD151FK size: 7814026532 Cache pool: Apr 1 13:55:47 REPOSITORY emhttpd: import 30 cache device: (sdb) 512GB_QLC_SATA_SSD_AF20061200152 Apr 1 13:55:47 REPOSITORY emhttpd: import 31 cache device: (nvme1n1) PM951_NVMe_SAMSUNG_512GB_S29PNX0H801455 Apr 1 13:55:47 REPOSITORY emhttpd: import 32 cache device: (nvme0n1) PM951_NVMe_SAMSUNG_512GB_S29PNX0H617859 Apr 1 13:55:47 REPOSITORY emhttpd: import 33 cache device: (sde) INTEL_SSDSC2BB240G4_PHWL4493025V240NGN 1 Quote Link to comment
Keek Uras Posted April 5, 2023 Author Share Posted April 5, 2023 On 4/3/2023 at 9:51 AM, JorgeB said: Yes, you can create a new flash drive then assign all the devices as they were and check "parity is already valid" before array start, all data/pool disks will be imported, if you don't know the assignments then can be seen on the diags posted, disk0 is parity: Apr 1 13:55:46 REPOSITORY kernel: md: import disk0: (sdm) WDC_WD160EMFZ-11AFXA0_2CG607NR size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk1: (sdk) TOSHIBA_MG08ACA16TE_91D0A0SUFWTG size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk2: (sdg) WDC_WD140EDFZ-11A0VA0_9LG79M3G size: 13672382412 Apr 1 13:55:46 REPOSITORY kernel: md: import disk3: (sdi) TOSHIBA_MG08ACA16TE_91L0A23XFWTG size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk4: (sdh) TOSHIBA_MG08ACA16TE_91D0A12BFWTG size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk5: (sdj) TOSHIBA_MG08ACA16TE_91L0A41XFWTG size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk6: (sdf) WDC_WD140EDFZ-11A0VA0_QBJW606T size: 13672382412 Apr 1 13:55:46 REPOSITORY kernel: md: import disk7: (sdl) TOSHIBA_MG08ACA16TE_91L0A30LFWTG size: 15625879500 Apr 1 13:55:46 REPOSITORY kernel: md: import disk8: (sdc) WDC_WD140EDFZ-11A0VA0_9KGVYJ9L size: 13672382412 Apr 1 13:55:46 REPOSITORY kernel: md: import disk9: (sdd) WDC_WD120EMFZ-11A6JA0_XJG0KLNM size: 11718885324 Apr 1 13:55:46 REPOSITORY kernel: md: import disk10: (sdr) WDC_WD120EMFZ-11A6JA0_9JHG38XT size: 11718885324 Apr 1 13:55:46 REPOSITORY kernel: md: import disk11: (sdq) WDC_WD120EMAZ-11BLFA0_8CK40JJE size: 11718885324 Apr 1 13:55:46 REPOSITORY kernel: md: import disk12: (sdn) WDC_WD120EMAZ-11BLFA0_8CJWDE6E size: 11718885324 Apr 1 13:55:46 REPOSITORY kernel: md: import disk13: (sdp) HGST_HUS728T8TALE6L4_VDGMW6LD size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk14: (sdac) HGST_HUS728T8TALE6L4_VDGLS39D size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk15: (sdae) HGST_HUS728T8TALE6L4_VDKZ3DUM size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk16: (sdad) HGST_HUS728T8TALE6L4_VDGMZGJD size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk17: (sdag) HGST_HUS728T8TALE6L4_VDKZS7MM size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk18: (sdaf) HGST_HUS728T8TALE6L4_VDGN090D size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk19: (sdo) WDC_WD60EFRX-68L0BN1_WD-WX11D38E2D7P size: 5860522532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk20: (sdv) ST8000AS0002-1NA17Z_Z840P04T size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk21: (sdw) ST8000AS0002-1NA17Z_Z840P8W8 size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk22: (sdx) ST8000AS0002-1NA17Z_Z8410NWK size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk23: (sdy) ST8000AS0002-1NA17Z_Z8410P11 size: 7814026532 Apr 1 13:55:46 REPOSITORY kernel: md: import disk24: (sdz) ST8000AS0002-1NA17Z_Z8410Q6E size: 7814026532 Apr 1 13:55:47 REPOSITORY kernel: md: import disk25: (sdaa) ST8000AS0002-1NA17Z_Z840P8XR size: 7814026532 Apr 1 13:55:47 REPOSITORY kernel: md: import disk26: (sdab) ST8000AS0002-1NA17Z_Z840P0LC size: 7814026532 Apr 1 13:55:47 REPOSITORY kernel: md: import disk27: (sdu) ST8000AS0002-1NA17Z_Z840Q6YA size: 7814026532 Apr 1 13:55:47 REPOSITORY kernel: md: import disk28: (sdt) ST8000NM000A-2KE101_WKD151FK size: 7814026532 Cache pool: Apr 1 13:55:47 REPOSITORY emhttpd: import 30 cache device: (sdb) 512GB_QLC_SATA_SSD_AF20061200152 Apr 1 13:55:47 REPOSITORY emhttpd: import 31 cache device: (nvme1n1) PM951_NVMe_SAMSUNG_512GB_S29PNX0H801455 Apr 1 13:55:47 REPOSITORY emhttpd: import 32 cache device: (nvme0n1) PM951_NVMe_SAMSUNG_512GB_S29PNX0H617859 Apr 1 13:55:47 REPOSITORY emhttpd: import 33 cache device: (sde) INTEL_SSDSC2BB240G4_PHWL4493025V240NGN This was not the easiest way to get back up and working but in the end, I'm back where I needed to be. Thanks! 1 Quote Link to comment
Recommended Posts
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.