thejellydude

Does RUFUS not do this? The drive should be bootable already since it launches the EFI shell, right? And I don't think it should need to be named UNRAID, since this is my FreeDOS boot drive. My UnRAID one works just fine.

I've been trying. Unfortunately it's not really pulling up anything useful. I'm pretty sure that my H310 used to be flashed with IT Mode and I think it somehow got messed up during the upgrade. It now shows up on my motherboard as an H310 device. It should do that if it's flashed with the P20 firmware, correct?

I attempted downgrading and that hasn't fixed the issue. If anyone knows why I'm getting an EFI shell instead of FreeDOS, the help would be appreciated.

I attempted to folIow the techmattr guide. The link to creating a bootable USB is no longer there, so I simple downloaded Rufus, ticked the "Download FreeDos option" and click "start". I think copied over the files from the guide. However, Ikeep getting an EFI shell instead of an actual DOS prompt. Does anyone have any idea why that might be the case?

I just realized you accidentally did the Techmattr thread twice instead of the reddit thread! Would you mind posting that one?

I managed to get it to post and now the 8TB drives show up! I'm going to try updating the H310 and see if the drives will show up using that again.

Good call! My backpane uses a molex connection, so I forgot my 12TB drives have the 3.3v issue. My 8TB drives also don't have the 3.3v issue however and I can use them to test. Right now I can't get my system to post at all though. I see the splash screen for a second, but it doesn't enter BIOS anymore. I regret upgrading so much.

Maybe the word "corrupted" would have been better. Do you have any suggestions? This is the case I have. Originally after the update my second data drive stopped working, so I removed it from the hot-swap bay and troubleshooted it. Eventually I decided to see if the part was dead, so I shuffled around the drives. This caused one of my parity drives to go offline as well. I now suspected that perhaps the backplane inside the case was faulty, so I removed four of the drives from the hotswap bays and connected them directly to the breakout cables from my Dell H310. Now even less drives were showing up. I guessed that maybe my H310 was faulty, so I unplugged my hard drives and plugged them into my motherboard directly. Still not luck. However, my cache drive is always detected by the bios. If I swap around the sata cables between the drives, the one that the cache drive is connected to always shows up in the BIOS.

Thank you, I will look at these in the future. Unfortunately, the drives aren't showing up in Bios when directly plugged into the system. I fear that the combination of the upgrade/troubleshooting may have somehow killed all my drives. I seriously hope that is not the case.

Would you possibly have instructions on how to do that?

Unfortunately I upgraded my board/cpu recently, and I can not for the life of me figure out where the drive information is located. I'll probably research that in a bit.

I thought that might be the issue, but that wouldn't affect the drives when plugged directly into the mothrboard, correct? I powered down the system, removed all the drives from the expansion card, and plugged four directly into the motherboard. Those drives did not show up.

I honestly have no idea what's going on. It started with one drive not working after the upgrade. Then I started troubleshooting (Powering off, reseating drives, unplugging and replugging in all cables, plugging in to mobo directly instead of expansion card, etc) and now only one of my eight drives shows up. Can someone please help? I have no idea why this is happening. nasbox-diagnostics-20210408-1635.zip

nasbox-diagnostics-20210306-1628.zip

Sorry, I was just clarifying because you suggested rebuilding both at the same time. My plan is to do the following: Plug in Parity Disk 1, let it be rebuilt as Data Disk 1. After it's done rebuilding, compare it to the original Data Disk 1, and if it looks good, use my original Data Disk 1 as Parity Disk 1. This makes more sense than rebuilding both at the same time, correct?

The only one that would fit my board is the Asmedia ASM1061/62, correct? As far as I could tell, none of the other cards listed would fit my ports.

What's best practice if I don't have a spare?

The problem is I don't have a spare disk laying around. I have the two disks on hand that I already have, and I don't currently have the funds to purchase another 12tb drive.

I've just learned that the Marvell controller that I have is an issue. I was looking at LSI controllers instead, but I just realized that my MOBO slots might be an issue. I have an ASUS B85M-G R2.0 which has the following slots available: PCI Express 3.0 x16: 1 x PCIe 3.0/2.0 x16 PCI Express x1: 2 x PCIe 2.0 x1 I would need at least 4 additional SATA slots. Any and all help would be greatly appreciated.

Yes, although I also see a "lost+found" folder. At this point I'm assuming the course of action I should take is to preclear my spare parity drive, remove my messed up data drive from the array, add the precleared parity drive back as a data drive, and then add the parity drive back in? Should I change anything else before I do that?

Should I enable any options when checking the filesystem other than -n? What am I looking for to determine the contents look correct?

@trurl I went ahead and swapped all the drives that were on the external controller and directly on the motherboard for the sake of testing. The same two drives are having issues. I've attached an updated report. nasbox-diagnostics-20210212-0029.zip

I'm assuming Marvel controller is the Sata expansion card I'm using? Is there an expansion card that's generally recommended by the community? I'll shut down the server and go into BIOS right now.

Not really sure what to do. Are the drives toast, or is there something I can do to salvage the content? nasbox-diagnostics-20210211-2035.zip

Sorry. I don't run any VMs. The box is strictly for UnRaid with docker containers. I'll check the bios on reboot and see if VT-d is enabled.