I wanted to update my unraid install, never had any issues previously but i really wanted to get the connectivity back with my docker containers via wireguard and due to macvlan issues that feature went away when macvlan was disabled in my installation.

 

Anyway, when i upgraded everything went fine but when i mounted the array it looked like this:

 

 

I reconsidered and downgraded back to 6.11.5 without doing anything as i ended up installing wireguard directly in my router instead to maintain docker connectivity from wireguard (no longer having to have unraid act as a router for that traffic).

 

But i am concerned for when i want eventually to upgrade, why would this occur? Why would my simple luks xfs encrypted array mount using the right key yet say the drives are unmountable and want to format them? Sorry for not being able to provide any logs, i'm just curious to what i should consider looking into once i decide to try to upgrade again and have more time to put into fixing my unraid install if it breaks.

 

Edited December 18, 20241 yr by je82

Please post the diagnostics.
 

11 hours ago, JorgeB said:

Please post the diagnostics.
 

Sorry i downgraded before i had time to do diagnostics, but i captured this log during the error if it can be any clue to what may have happened, the upgrade went fine, and booting unraid was error free, it happened when i mounted the array after typing my xfs encrypted password, i simply just demounted everything and shut it down and went to restore from backup because i didn't actually have time to resolve the issues at that time.

 

Dec 17 22:48:49 NAS kernel: md: unRAID driver removed
Dec 17 22:48:49 NAS emhttpd: shcmd (591): /sbin/modprobe md-mod super=/boot/config/super.dat
Dec 17 22:48:49 NAS root: modprobe: FATAL: Module md-mod not found in directory /lib/modules/6.1.118-Unraid
Dec 17 22:48:49 NAS emhttpd: shcmd (591): exit status: 1
Dec 17 22:48:49 NAS emhttpd: Device inventory:
Dec 17 22:48:49 NAS emhttpd: ST12000VN0008-2JH101_ZHZ0N2G3 (sdm) 512 23437770752
Dec 17 22:48:49 NAS emhttpd: WDC_WD121KRYZ-01W0RB0_5PK8RJ8B (sdj) 512 23437770752
Dec 17 22:48:49 NAS emhttpd: TOSHIBA_HDWG21C_20M0A084FP8G (sdk) 512 23437770752
Dec 17 22:48:49 NAS emhttpd: WDC_WD121KRYZ-01W0RB0_5PK8Y41B (sdh) 512 23437770752
Dec 17 22:48:49 NAS emhttpd: ST12000VN0007-2GS116_ZJV2ZREA (sdg) 512 23437770752
Dec 17 22:48:49 NAS emhttpd: ST12000NM001G-2MV103_WL208842 (sdd) 512 23437770752
Dec 17 22:48:49 NAS emhttpd: TOSHIBA_HDWG21C_29G0A003FP8G (sde) 512 23437770752
Dec 17 22:48:49 NAS emhttpd: Samsung_SSD_870_EVO_1TB_S6PUNM0T420275J (sdb) 512 1953525168
Dec 17 22:48:49 NAS emhttpd: ST12000VN0007-2GS116_ZJV1T8QS (sdf) 512 23437770752
Dec 17 22:48:49 NAS emhttpd: ST12000VN0007-2GS116_ZJV2ZQVR (sdc) 512 23437770752
Dec 17 22:48:49 NAS emhttpd: ST16000NE000-2RW103_ZL2PXKS1 (sdn) 512 31251759104
Dec 17 22:48:49 NAS emhttpd: Micron_7450_MTFDKBA800TFS_2328428C3699 (nvme0n1) 512 1562824368
Dec 17 22:48:49 NAS emhttpd: Micron_7450_MTFDKBA800TFS_2328428C36B6 (nvme1n1) 512 1562824368
Dec 17 22:48:49 NAS emhttpd: ST8000VN0022-2EL112_ZA1EKX8Z (sdo) 512 15628053168
Dec 17 22:48:49 NAS emhttpd: ST12000VN0007-2GS116_ZJV2ZQGK (sdl) 512 23437770752
Dec 17 22:48:49 NAS emhttpd: TOSHIBA_HDWG21C_20M0A098FP8G (sdi) 512 23437770752
Dec 17 22:48:49 NAS emhttpd: SanDisk_Ultra_Fit_4C530000070715103045-0:0 (sda) 512 30031872
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: error: mdcmd, 4179: No such file or directory (2): open
Dec 17 22:48:49 NAS emhttpd: rdevStatus.1 not found

 

12 hours ago, je82 said:

Dec 17 22:48:49 NAS root: modprobe: FATAL: Module md-mod not found in directory /lib/modules/6.1.118-Unraid

Looks like the flash drive wasn't correctly created, it was missing the Unraid driver.

8 hours ago, JorgeB said:

Looks like the flash drive wasn't correctly created, it was missing the Unraid driver.

Interesting, i did upgrade via the interface and the interface did notify me it was done upgrading and requiring a reboot so i did, i have previously upgraded manually by just replacing the *bz files on the usb over smb.

 

Good to know that it was probably pretty simple to solve, i might try my luck updating at a later time when i have more time to deal with eventual problems, thanks for the help.