Cache pool ssd marked as wrong after bios update

[Sherr0]

Hi guys I have a problem, after I updated my motherboard Bios both of my SSDs in my cache pool are marked as wrong. When i log in the array is stopped after reboot. They both seem to have the same names that they had when installed but unraid is expecting different drives.

when i start the array the pool looks to be working, I can browse the files and start and run docker containers that live on the cache.

 

I have tried using the new config tool preserving array allocations only to no avail.

 

any help would be appreciated

laurelin-diagnostics-20220910-1605.zip

[Sherr0]

So this is the contents of confg > pools > cache.cfg

 

should edit this file and remove the lines ?

 

diskId="SPCC_M.2_PCIe_SSD_296D07140E1E00218418"
diskId.1="SPCC_M.2_PCIe_SSD_BEE30727152300329023"

 

or am i on the wrong track ?

=========================================

diskFsType="btrfs"
diskComment=""
diskWarning=""
diskCritical=""
diskUUID="1d576a90-08fc-4b93-851e-0f7c1134e608"
diskShareEnabled="yes"
diskShareFloor="0"
diskExport="-"
diskFruit="no"
diskSecurity="public"
diskReadList=""
diskWriteList=""
diskVolsizelimit=""
diskCaseSensitive="auto"
diskExportNFS="-"
diskExportNFSFsid="0"
diskSecurityNFS="public"
diskHostListNFS=""
diskId="SPCC_M.2_PCIe_SSD_296D07140E1E00218418"
diskId.1="SPCC_M.2_PCIe_SSD_BEE30727152300329023"
diskIdSlot="Samsung_SSD_970_EVO_Plus_500GB_S4EVNX0T602292Z"
diskIdSlot.1="Samsung_SSD_970_EVO_Plus_500GB_S4EVNX0T602290A"
diskType="Cache"
diskType.1="Cache"
diskSpindownDelay="0"
diskSpindownDelay.1="0"
diskSpinupGroup=""
diskSpinupGroup.1=""

 

===============================================
 

[JorgeB]

Unassign both pool devices, start array, stop array, reassign both pool devices, start array, that should do it.

[Sherr0]

array wont start with none selected in both slots

 

can i do any harm by removing the phantom devices form the config file ?

I should add that i had replaced both of these ssd a week ago but have not had any problems until today.

Is it safe to asume that the phantom drives that the system is looking for where the old ones i took out ? and that is why i have two lots of entrys in the config file?

Edited September 10, 2022 by Sherr0

[MAM59]

you have to UNASSIGN the cache pool first.

This means, set all cache entries for all shares to NO.

(of couse you cannot start if there is still a dependency to the missing drives)

 

[Sherr0]

when i ticked the box that said remove the missing devices and start the array all was good 

stoped the array again and re-assigned the correct drives and restarted the array all fixed thanks a lot