Griminal

This is the way. CONFIRMED!!!! Thank you. I knew it had to be something simple.

I just tried that. No love unfortunately.

I'm using a 32GB Samsung Fit drive. I used the UnRAID tool to create it. In my troubleshooting, I took a known good USB2 with UnRAID on it running on a MicroServer Gen8 and tried to use that to boot into the F4-424 Max... no resolution. I still had to go into the BIOS first.

Is there a USB distro or tool that we could use to boot into UnRAID in the interim? Basically have two USB sticks and the first one tells the system to use the 2nd UnRAID stick. I need to install this headless, unfortunately.

I sent my own finely crafted email to their support. Hoping I don't have to return this unit. Its the perfect box for my installation needs.

Just picked up a F4-424 MAX today. Luckily I stumbled on this post. Could not understand why the system wouldn't boot without going into the BIOS first. Following this thread.

Sorry. I ran the script with both of the variables set to "yes" and it reclaimed the space. Forgot to mention that.

Hey there. Sorry if this is a FAQ. Search didn't come up with much for me. I had a Docker image go rogue on me and stole 14GB of my docker image. I've ran SpaceInvader's script with the variables set to "yes" and it reclaimed the space I've stopped and started the Docker service but all the local volumes still show up in the report. Do I need to stop/restart the array? There are 11 Images taking up ......4.829GB There are 11 Containers taking up ......698.6MB There are 1228 Local Volumes taking up ......14.24GB There are 0 Build Cache taking up ......0B The majority of the output is like this: ID 0ac4de6fbf18978129a5b73e4aa5b43079b0ad7f085e0ca086f1cbe5dfd37873 This volume connected to has a size of 0 ID 0b826c844421dc7beea0d20b65da805b4e9067da4e3a21ad54a78f1b5528be5e This volume connected to has a size of 0 ID 0b9063d6e0ab478a2c754c49325d5327dc2092c00d0eadbd10a6c727dd719ea7 This volume connected to has a size of 0

I have not. I suppose I could try that.

Disk2 decided it wanted to be corrupt too. I haven't fixed that one yet. Questioning my hardware at this point. I will respond back when I figure out what to do. Thank you.

I appreciate the help. Attached diagnostics. I'll hold off on a "new config" until I hear if you all have any concerns. hyde-diagnostics-20240326-1218.zip

Hello. So I had a HBA die out on me. Disk3 became disabled. I removed Disk3 from the array, attempted to mount it, and it failed. I performed a check on it and everything repaired successfully. I'm able to mount and browse the disk now. My concern, if I add the drive back to the array, will it overwrite all the files on it? If a parity check happens, will it consider all the files currently on the drive? Right now, my shares are missing a lot of files... because they were stored on Disk3. I had to do a lot of reboots diagnosing the HBA issue. Sorry for my vague questions. The old brain isn't working like it used to.

I ended up downgrading to Version: 6.12.4 after the file check. No more problems so far.

So I moved Disk2 to a mobo SATA port, away from the LSI controller. Parity is at ~20% at this time. I'm keeping an active browser window up to capture the logs. I'm seeing this thus far. Its been rebuilding for 5 hours. Feb 1 18:26:50 hyde kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Feb 1 18:26:50 hyde kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Feb 1 18:26:50 hyde kernel: mpt2sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: mpt2sas_cm0: log_info(0x31110d01): originator(PL), code(0x11), sub_code(0x0d01) Feb 1 18:26:55 hyde kernel: sd 9:0:4:0: Power-on or device reset occurred Feb 1 18:26:56 hyde kernel: sd 9:0:4:0: Power-on or device reset occurred

What would have filled up the logs in a 12 hour period? Maybe my LSI card is having issues? Maybe the breakout cable is going? What recommendations do you have for me to go forward after I reboot?