September 22, 20232 yr Getting some issues with a fresh unraid install/setup using unraid 6.12.4 and problems with the ssd cache, Ive tried different file systems on it, but regardless of what I choose Im unable to do anything with it. Weird part is that the overall Monitoring now shows everything as green and ok. Any advice moving forward? Dont want to start moving data on to this until Ive got it fixed. jupiter-diagnostics-20230922-0747.zip jupiter-smart-20230922-0755.zip Edited September 22, 20232 yr by RoyBatty added smart report
September 22, 20232 yr Author Tried a reboot, still getting the same message, uploaded a new diagnosis jupiter-diagnostics-20230922-0943.zip Edited September 22, 20232 yr by RoyBatty
September 22, 20232 yr Community Expert Don't see any format attempt after the reboot, please confirm.
September 22, 20232 yr Author Just getting : Sep 22 12:23jupiter-diagnostics-20230922-1231.zip:33 Jupiter root: wipefs: error: /dev/sdc: probing initialization failed: Device or resource busy Edited September 22, 20232 yr by RoyBatty
September 22, 20232 yr Community Expert That's not in the diags posted, post them just to see if there's something else.
September 22, 20232 yr Author 17 minutes ago, JorgeB said: Does blkdiscard -f /dev/sdc work? Afraid not Just to be clear, there is no data on the drive or the array atm which I need to keep. jupiter-diagnostics-20230922-1346.zip Edited September 22, 20232 yr by RoyBatty
September 22, 20232 yr Community Expert Solution You will need to try and wipe that device with a different OS, for some reason Unraid cannot do it.
September 22, 20232 yr Author Thats the weird thing, Windos insists that the device doesent contain anything. I'll see if I can run fdisk towards it and get it wiped that way.
September 22, 20232 yr Community Expert According to Linux the device has two partitions: Sep 22 09:41:17 Jupiter kernel: sdc: sdc1 sdc2 Post the output of fdisk -l /dev/sdc
September 22, 20232 yr Author Finally, after some tinkering with the drive ,it seems as if it was an ev0l Windows boot partition which was the culprate, I did away with it using dispart on the windoze comp. Removed it there and it came right up once I started the array. Edited September 22, 20232 yr by RoyBatty
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.