thejellydude
-
Posts
38 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by thejellydude
-
-
1 hour ago, Frank1940 said:
I don't have an answer but when I am confronted with this type of situation, I turn to Google. Use terms like 'EFI shell' 'FreeDos' and the name of the program you used to generate a boot disk.
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?
-
1 hour ago, Hoopster said:
Here is one guide:
Here is another:
And here is a reddit thread from someone who tried both tutorials and ran into a problems which were solved with the help of others:
There are many threads about cross-flashing a RAID controller to IT mode in the unRAID forums. Here is a very long one on the subject:
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.
-
33 minutes ago, Frank1940 said:
Google '3.3 volt pin problem'. That is one 'gotcha' that can bite one's posterior..
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.
-
4 minutes ago, trurl said:
I seriously doubt it is the case. Killing all your actual disks would require a serious hardware malfunction, such as incompatible power cables.
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. -
4 minutes ago, Hoopster said:
Here is one guide:
Here is another:
And here is a reddit thread from someone who tried both tutorials and ran into a problems which were solved with the help of others:
There are many threads about cross-flashing a RAID controller to IT mode in the unRAID forums. Here is a very long one on the subject:
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.
-
2 hours ago, Hoopster said:
OK. When other issues are resolved, you really should consider cross-flashing that H310 with IT firmware version 20.0.7.0 (the latest). It will make your life a lot easier.
Would you possibly have instructions on how to do that?
-
13 minutes ago, Hoopster said:
Correct. Should not affect drives attached directly to the motherboard.
However, if they do not show up in the motherboard BIOS/UEFI, they will not show up in unRAID. Go into your BIOS and see if the drives show up there.
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.
-
1 minute ago, Hoopster said:
Has your Dell H310 always been in RAID mode? If so, the only way to get drives to show up with the Megaraid driver is if each drive is configured as a separate RAID 0 or in JBOD mode if that is supported. Drives attached to a controller in RAID mode do not generally show up in unRAID. Megaraid driver and unRAID is usually a problematic combination.
This is your controller (note it is using the MegaRAID driver):
01:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS 2008 [Falcon] [1000:0073] (rev 03)
Subsystem: Dell PERC H310 [1028:1f78]
Kernel driver in use: megaraid_sas
Kernel modules: megaraid_sasWhatever mode your card is in, loading the MegaRAID driver only shows one drive recognized:
ASBOX kernel: megaraid_sas 0000:01:00.0: pci id : (0x1000)/(0x0073)/(0x1028)/(0x1f78) Apr 8 14:33:25 NASBOX kernel: megaraid_sas 0000:01:00.0: unevenspan support : no Apr 8 14:33:25 NASBOX kernel: megaraid_sas 0000:01:00.0: firmware crash dump : no Apr 8 14:33:25 NASBOX kernel: megaraid_sas 0000:01:00.0: JBOD sequence map : disabled Apr 8 14:33:25 NASBOX kernel: scsi host1: Avago SAS based MegaRAID driver Apr 8 14:33:25 NASBOX kernel: i2c i2c-0: Successfully instantiated SPD at 0x50 Apr 8 14:33:25 NASBOX kernel: RAPL PMU: hw unit of domain package 2^-14 Joules Apr 8 14:33:25 NASBOX kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules Apr 8 14:33:25 NASBOX kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules Apr 8 14:33:25 NASBOX kernel: scsi 1:0:7:0: Direct-Access ATA WDC WD80EFAX-68L 0A83 PQ: 0 ANSI: 5I happen to have the same card in my server but I have it cross-flashed to IT mode where it becomes a pure HBA (no RAID support) that passes through each disk to unRAID without issues. Note that in IT mode is is loading the mpt3sas driver.
For the record, I am also running the latest version of unRAID; 6.9.2
Here are my controller details also for a Dell H310:
02:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03)
DeviceName: Onboard SAS
Subsystem: Dell 6Gbps SAS HBA Adapter [1028:1f1c]
Kernel driver in use: mpt3sas
Kernel modules: mpt3sasUpgrading unRAID should have had no effect upon the firmware on your Dell H310, but, it is possible that Linux kernel changes between versions have affected how the driver behaves.
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.
-
-
4 hours ago, trurl said:
That is the spare I assumed you were going to use for the rebuild of the data disk. Since we don't believe there is anything wrong with any of the disks, you could just rebuild both disabled disks to the original disks, but using a spare for the disabled data disk rebuild will let you compare the results to the original disk. There is nothing to be gained by using that spare disk to rebuild parity since parity contains no data.
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? -
12 minutes ago, ChatNoir said:
You can start by checking this :
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.
-
1 hour ago, JorgeB said:
If you have a spare rebuild to the spare then check the data on the old disk, you can do that with UD but need to change the UUID to be possibly to mount with the array started, then you can compared data from both disks to see if anything is missing.
What's best practice if I don't have a spare?
-
1 hour ago, trurl said:
Unnecessary unless you just want to test it since rebuild will completely overwrite it anyway.
Unraid only requires a clear disk when ADDING to a NEW data slot in an array that already has valid parity. A clear disk is all zeros and so has no effect on parity. That is the only scenario where a clear disk is needed, and Unraid will clear the disk itself if it isn't already clear.
Rebuilding to the spare will give you exactly what the repaired emulated disk contains. This is a good approach because it will let you compare the original disk to the rebuilt disk to see what was lost+found.
You can rebuild that disabled parity disk at the same time as rebuilding that data disk, and no reason not to.
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 x1I would need at least 4 additional SATA slots. Any and all help would be greatly appreciated.
-
6 hours ago, itimpi said:
When you later restart the array in normal mode does the ‘emulated’ drive mount OK, and if you click on the folder icon against that drive does it show the folders/files you expect to see?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? -
1 hour ago, JorgeB said:
Once a disk gets disable it needs to be rebuilt, check filesystem on disk1, if after that contents look correct you can rebuild.
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.
-
2 hours ago, trurl said:
Are your disabled disks on the Marvell controller? Marvell is not recommended.
Since you aren't using VMs you might have better luck with that controller if you disable VT-d in the BIOS.
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?
-
33 minutes ago, trurl said:
Do you know the answer to this question I have asked
twicethrice now?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.
Upgraded to 6.9.2, and now none of my drives show up. I have been troubleshooting for hours and nothing is working. Please help!
in General Support
Posted
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.