@george1421 Ok, I scripted data collection and pulled fresh info for kernels a, b, c, and F27 Live. I also pulled dmidecode, full lshw ouput, and /proc/diskstats to additional log files. Let me know if they may be of any use I will upload them as well.
bzImage41713a.log
bzImage41713b.log
bzImage41713c.log
F27_4139300.log
@george1421 Sorry, got caught up with some other issues. I tried G, but it hangs at
Configuring (net0 xx:xx:xx:xx:xx:xx)... ok
http://ip.addr/fog/service/ipxe/boot.php... ok
bzImage41713g... ok
init.xz... ok
_
I have double checked and init.xz is still set as default.
Hang on, just found an issue with the BIOS. Testing D - G again to see if it had any effect.
@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.
@hlalex said in Dell Precision Tower 5820 - FlexBay MiniSAS PCIe NVMe SSD not recognized:
@george1421 Ok, F27 still installs and boots fine. When upgrading to F28, it fails to reboot and drops to a shell (:/#).
@george1421 Since none of the fresh install methods were working with F28, I tried F27 to make sure there it still worked properly (to rule out any settings/hardware changes). After getting F27 installed and booted properly, I then attempted to upgrade to F28 using the GUI software manager. This resulted in the same failure of F28 to boot as the fresh install method.
The logs I posted are from a fresh install of F28 on a SATA installed in one of the hot swap bays. And I completely agree on the oddness of this adapter. I can only assume they are trying to getthe most from the advertised 2700MB/s read & 1390MB/s write speeds of these drives, but in an easier to manage platform.
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
@george1421 Ok, F27 still installs and boots fine. When upgrading to F28, it fails to reboot and drops to a shell (:/#).
blkid returns:
[ 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 read
lsmod gives:
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 uas
journalctl | 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.
@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, 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.
@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 It connects directly to the MoBo beside the CPU slot, I posted a pic of the PCIE headers ~7 posts back.
@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.
@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
@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.
