ijuarez Posted March 5, 2021 Share Posted March 5, 2021 array consists of 1 parity 1 cache and 17 disks. Nothing fancy pci cards lsi raid card (LSI SAS 9211-8i 6GB/s 8 Port PCIe) HBA that connects all of the drives ( HP 24 Port PCI-E 3Gb SAS Standard Profile Expander) Intel quad nic add in firewire card. everything working prior to update, update, reboot all disk are missing Its like systems does not see the HBA card. diags taken right after update and notice disks missing. I've uninstalled the vfio-pci pluggin and deleted the binding since i was not using it any more. I figure i post before i revert to 6.8.3 lahomamediacenter-diagnostics-20210304-2307.zip Quote Link to comment
JorgeB Posted March 5, 2021 Share Posted March 5, 2021 Don't see any errors, HBA is initializing correctly, do the disks show up if you go back to v6.8? Quote Link to comment
ijuarez Posted March 5, 2021 Author Share Posted March 5, 2021 (edited) Well this is very odd, so after I posted I went ahead and left the server alone went to bed, I have been doing some maintenance converting my xfs to encrypted so the server being offline a few more days was not a problem. Woke up got my day going then happened to notice telegram send me notices that all disks were ok. I'm like WTH, so remote in and sure enough all the disks are present and the array is ready to start. I don't know. before I start the array i did another diag download and I'm posting for science. lahomamediacenter-diagnostics-20210305-0832.zip Edited March 5, 2021 by ijuarez engrish Quote Link to comment
JorgeB Posted March 5, 2021 Share Posted March 5, 2021 Yep, disks were detected about 10 minutes after boot, 🤷 Quote Link to comment
ijuarez Posted March 5, 2021 Author Share Posted March 5, 2021 1 hour ago, JorgeB said: Yep, disks were detected about 10 minutes after boot, 🤷 crazy Quote Link to comment
ijuarez Posted March 5, 2021 Author Share Posted March 5, 2021 aww man so I was about to start the array and just happened to look at the disk sdX and they were in the incorrect spots. I had a screenshot and proceeded to put them back until one of the was missing from the list to pick (lesson to be learned by noobs) it catalogue the disk with different sdX that could have been disastrous with serial in hand to the correct spots. Quote Link to comment
itimpi Posted March 5, 2021 Share Posted March 5, 2021 The sdX identifiers are not relevant to unRaid as it identifies disks by serial number (and the sdX designation is allocated dynamically and can change between boots). The only time it matters is if the disk drops offline after boot and then comes back with a different sdX designation as that scenario is not handled by unRaid. Quote Link to comment
ijuarez Posted March 5, 2021 Author Share Posted March 5, 2021 3 minutes ago, itimpi said: The sdX identifiers are not relevant to unRaid as it identifies disks by serial number (and the sdX designation is allocated dynamically and can change between boots). The only time it matters is if the disk drops offline after boot and then comes back with a different sdX designation as that scenario is not handled by unRaid. got them correct spot and started the array and prayers sent Quote Link to comment
ijuarez Posted March 8, 2021 Author Share Posted March 8, 2021 So I rebooted the array by mistake and again once up disks were missing, stated a "stale config" about 10 minutes later they appear. I pretty sure this is not by design but i'm no sure its a bug. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.