Dell Precision Tower 5820 - FlexBay MiniSAS PCIe NVMe SSD not recognized
-
@george1421
What I understand, out of dell 5820 owners manual:
https://topics-cdn.dell.com/pdf/precision-5820-workstation_owners-manual2_en-us.pdfODD is Optical Disk Drive. Maybe wrong assembly.
I can confirm, capture and deploy task, no issue. OK.
I will update this on the hardware id question… -
Because they’re marked as ODD, they might be on a different controller altogether and possibly with more limited functionality too.
-
@matijn I actually did not have issues with the ODD ports (when used with 2.5 SSDs), they connect the two SATA ports on our 5820s. The two FlexBay ports are connected to PCIE0 and PCIE1, which are a mini-sas type connector (pic below). I can’t remember if I tried moving the flexbay NVMe to the standard hot swap bays, but I don’t believe I did.
-
@hlalex This is all great info guys. Thank you.
Its hard without having the hardware in hand for the developers to find out what’s missing. Seeing is better than trying to imagine what things look like.
-
-
@george1421 I got another system with the flex bay adapter via mini-sas port (Precision 7820). I was able to persuade the owner of said system to let me borrow the flex bay adapter for testing Fog. I now have a 5820 installed with the flex bay if you have any tests you would like to run
-
@hlalex So how does this flex bay adapter interface with the mobo? Is it via the connectors mentioned below?
-
@george1421 Ok, so the NVMe drive fits into a proprietary carrier, which then slides into a 3.5" SAS adapter (pics below). That slides into one of the two top hot swap bays on the 5820. The backplane on those bays connects to the MoBo via mini-SAS headers that Dell labels PCIe0 & PCIe1 (previous post).
EDIT: Forgot to mention, Windows recognizes the disk as @Matijn posted (PC400 NVMe SK hynix…). Not sure where to look for information on the actual hardware connection. Also, If i plug the 3.5" adapter into one of the bottom hotswap ports (SATA/SAS MoBo connection) it is not recognized at all.
-
@hlalex Those pictures are very helpful. I still have the question on how does this carrier connect into the motherboard or is it via a sas riser card?
-
@george1421 It connects directly to the MoBo beside the CPU slot, I posted a pic of the PCIE headers ~7 posts back.
-
@hlalex ok thank you for the clarity. Between your pictures and a few Dell youtube videos I understand how everything plugs in.
I’ve been trying to think of a solution to get us where we need to be. I’m wondering if you have time, can you install fedora 28 on that workstation? Then upgrade the kernel to 4.18.x if its not already there? https://fedoraproject.org/wiki/Kernel
If this works with fedora 28 and linux kernel 4.18.x then maybe we can reverse engineer what is missing. We’ll need you to run the same collection scripts you had before because that collected exactly what we needed. If it works the only additional output would be a lsmod command to find out what modules were currently loaded.
If you did not want to write to the nvme disks, installing fedora on a sata disk would also work as long as the nvme tray disk is installed and detected by the OS.
-
This post is deleted! -
@matijn OK I’ve read your post 6 times and I don’t understand what you are saying. Sorry I feel I need more coffee this morning.
Are you saying that the latest FOG kernel at 4.18.11 works with this flexbay NVMe?
-
Haha, so many questions here.
And so little answers. Its actually rather funny how long this whole conversation has been going for.
Good luck in figuring this out ! -
@george1421 Sorry for the delay, I had a drive fail in an array that has been taking up a lot of my time trying.
I missed @matijn’s last post and it has been deleted now… I will try to get those logs uploaded today.
-
@george1421 Ok, I have tried both the live installer and net installer for F28. Both methods detect the drive during the installation process. After the reboot, I get dumped to a dracut shell complaining that /dev/mapper/xxx root and swap does not exist.
-
@hlalex Oh so close. Are you installing to the flexbay nvme or a sata disk? Its promising that FC28 sees the disk. We just need to find out what module its loading. When you run some installers, when in installer mode you can press alt-f2 or crlt-f2 to open a new console window to see what is going on in the background. From your error it sounds like the proper driver isn’t loaded into the boot partition for FC28 to see the disk. (but that is only a guess)
-
@george1421 I am attempting to install directly to the NVMe flexbay. To rule out any extraneous variables I am going back to the F27 4.13.9-300 Live install that was previously working with this drive arrangement. If it installs and boots, then I will try upgrading to F28 and pull logs. Then I will go back to trying to get logs for F28.
-
@george1421 Ok, F27 still installs and boots fine. When upgrading to F28, it fails to reboot and drops to a shell (:/#).
blkidreturns:[ 989.751061] Buffer I/O error on dev dm-0, logical block 13107184, async page read [ 989.751677] Buffer I/O error on dev dm-1, logical block 4092912, async page readlsmodgives:Module Size Used By hid_apple 16384 0 nouveau 2187264 1 video 45056 1 nouveau mxm_wmi 16384 1 nouveau i2c_algo_bit 16384 1 nouveau drm_kms_helper 196608 1 nouveau ttm 126976 1 nouveau drm 475136 4 drm_kms_helper,ttm,nouveau e1000e 282624 0 nvme 36864 1 crc32c_intel 24576 0 nvme_core 81920 3 nvme serio_raw 16384 0 wmi 28672 2 mxm_wmi,nouveau uas 69632 1 uasjournalctl | grep -i error:kernel: print_req_error: I/O error, dev nvme0n1, sector 34844272 kernel: Buffer I/O error on dev dm-1, logical block 4092878, async page read # multiple iterations of ^ this error with different block #'s & dm-1/dm-0 systemd-fschk[564]: fsck: error 2 (No such file or directory) while executing fsck.ext2 for /dev/mapper/fedora-root mount[569]: mount: /systoot: wrong fs type, bad option, bad superblock on /dev/mapper/fedora-root, missing codepage or helper program, or other error.EDIT: Installing F28 to SATA drive now. I will pull logs and upload them when finished.
-
F28_4.18.16-200 running from SATA drive, does not detect NVMe with lsblk or blkid…
4.18.16-200.fc28.x86_64.log
4.18.16-200.fc28.x86_64_lsmod.log
