apefray

@SpaceInvaderOne Anybody else having an issue with installing the Docker? Every time I start the Docker to install the VM instance, I just get the following:

😳 Ahhhh, you would be correct in assuming a controller failure of some sorts. I have an external 4 bay drive enclosure, which I thought was set to auto start when power returns, just like the unraid server. The server did indeed start, but the external enclosure didn't, hence me being slightly embarrassed. So yes, you are correct in the sense that it was a controller failure, but only because the external bay hadn't powered on..... Lesson learned, check before posting........

Hi. I have just recovered my unraid server from a major power cut (I do have battery backup, but this only lasts an hour, and the power was off for nearly 3 hours). Everything is up and running again, unraid is running fine, and the array has started, except the 4 unassigned disks I have. All 4 are now showing under Historical Devices instead of under unassigned devices, ready for me to mount. How can I get them back under Unassigend Devices? Please ignore the disk ending H45A as this is a failed disk from the array that I need to remove. Cheers

Cheers guys..... Its doing the parity as we speak, following @itimpiadvice above. I have now removed the offending drive, and the data is intact on Drive 4, so nothing was lost.

I used Unbalance to copy the data from the emulated disk to disk 4 so I have the data on another disk (Im guessing its still being emulated as well until a parity check is done) I can now remove the failed disk, but just need to do a parity check so that the parity now sees disk 4 with the data.

Just a thought on this, but seeing as the data is now residing on disk 4 and removed from disk 5 (the failed disk), could I follow this: If i can remove the failed disk, then force a parity sync, could this resolve my issue?

tower-diagnostics-20230805-1329.zip Thanks @itimpi That makes perfect sense now. So, I've moved the drive that has been disabled from bay 5 (thinking it maybe an issue with a cable) to bay 14 of the server. Unraid, again, has restarted a re-build after assigning the drive back to Disk 5, but yet again, it stopped rebuilding after 26 minutes and has disabled the drive. Remember, this drive is now in another bay in the server so isn't on the same cable as previously. So, what next..... As @JorgeB says, it appears the disk looks healthy so not sure why Unraid keeps disabling it. I have attached another diagnostics, so someone might be able to tell what is going on. Remember also, I do have 2 empty drives (disk's 4 & 6, although one of them is holding the data that I copied using unbalance from the emulated drive) that I could utilise, however both are 3TB drives, whereas the drive that is giving me issues is a 6TB drive, but it only contains 1.03TB of data. The disk causing the issue is currently empty, as Unraid thinks the data now resides on Disk 4, but its the parity I'm trying to sort out to protect the data.

@JorgeB Why, if I have a parity drive installed (as per picture above) am I now only seeing Read-Check instead of Parity Check and am unable to run a parity check either manually or through the scheduler. On the Main Page, the check button starts a Read-Check, and if I set it under schedule, as you quite rightly pointed out, it also only does a Read-Check even though I have a parity drive? As can be seen, parity checks were working perfectly until this drive was disabled? Am I missing something?

Actually, just a thought. If I stop whatever is running (parity or read check), shutdown the server move disk 5 to an empty Bay, then follow your link to rebuild, that should do the trick shouldn't it? I can delete the data on disk 4 once the rebuild has finished. Doing this should get me back up and running and will confirm if its the power or Sata cable that is causing the issue.

Funny you say that, as I scheduled the parity check to start at 18:30, which it did. But like you, I am a little confused as it says that mover is disabled due to parity check running, but it also says read-check is running. For clarification, I did not manually start the supposed parity check manually, I started it through the scheduler. I want to remove the disk that is causing an issue anyway as its old, hence me copying data onto the spare disk. I'm not too worried about losing the data on that disk anyway, I just want to get unraid into a stable state as soon as possible as I only have the one parity disk and am vunreable at present. Oh, and by the way, I had already followed the procedure to rebuild it as per your link, but it got to about 6% then disabled the disk again. Hence proceeding with the above.

I logged into unraid (6.12.3) last night to find disk 5 with a red x and disabled with the message that it is being emulated. Using Unbalance i have copied the data from disk 5 (I assume through emulation) to a spare disk that was in the server (for this precise scenario). The data is intact and sitting on the spare disk with no issues. I then stopped the array, unassigned disk 5 so that it now shows 'Not Installed', restarted the array and have started a parity check. I assume that once the parity check (although instead of start parity, it now shows read-check one the main page, I guess this is the same thing?) then I should be back up and running? Disk 5 is now shown under Unassigned Devices where I will leave it until I get the chance to remove the drive. Im not fussed about reusing it or its data, as I have copied the data to disk 4 tower-diagnostics-20230730-1955.zip

Slight correction to yesterdays post as per: The controller is in: PCI Express 3.0 x16 Slot (PCIE2, Blue) from CPU_BSP1 The expander is in: PCI Express 3.0 x 4 Slot (PCIE6, White) from CPU_BSP1 (As the expander only require's power) With an Nvidia 1650 TI graphics card in: PCI Express 3.0 x16 Slot (PCIE4, Blue) from CPU_BSP1 (As the graphics card takes up two slots, 3 & 4) (PCI Express 3.0 x16 Slot (PCIE5, Blue) from CPU_AP1, cannot be used as Im not using a 2nd CPU currently.) It makes me wonder if I should remove the graphics card, and put the controller in PCIE 4 as according to the BIOS, you can control both the link speed and width on: PCIE3 & PCIE4 Link Width This allows you to select PCIE 3 & PCIE 4 Link Width. PCIE3 & PCIE4 Link Speed This allows you to select PCIE 3 & PCIE 4 Link Speed.

Thanks, will have a look in the bios as per:

As requested: lspci -d 1000: -vv 03:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05) Subsystem: Super Micro Computer Inc Onboard SAS2308 PCI-Express Fusion-MPT SAS-2 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: I/O ports at e000 Region 1: Memory at fba40000 (64-bit, non-prefetchable) Region 3: Memory at fba00000 (64-bit, non-prefetchable) Expansion ROM at fb900000 [disabled] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [68] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 4096 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0W DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset- MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L0s, Exit Latency L0s <64ns ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 5GT/s (downgraded), Width x8 TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range BC, TimeoutDis+ NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- TPHComp- ExtTPHComp- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 10BitTagReq- OBFF Disabled, AtomicOpsCtl: ReqEn- LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1- EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest- Retimer- 2Retimers- CrosslinkRes: unsupported Capabilities: [d0] Vital Product Data pcilib: sysfs_read_vpd: read failed: No such device Not readable Capabilities: [a8] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [c0] MSI-X: Enable+ Count=16 Masked- Vector table: BAR=1 offset=0000e000 PBA: BAR=1 offset=0000f000 Capabilities: [100 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: 00000000 00000000 00000000 00000000 Capabilities: [1e0 v1] Secondary PCI Express LnkCtl3: LnkEquIntrruptEn- PerformEqu- LaneErrStat: 0 Capabilities: [1c0 v1] Power Budgeting <?> Capabilities: [190 v1] Dynamic Power Allocation <?> Capabilities: [148 v1] Alternative Routing-ID Interpretation (ARI) ARICap: MFVC- ACS-, Next Function: 0 ARICtl: MFVC- ACS-, Function Group: 0 Kernel driver in use: mpt3sas Kernel modules: mpt3sas

@JorgeB I've now done the upgrade, but am a little confused as to why diskspeed is showing the following on the controller: SAS2308 PCI-Express Fusion-MPT SAS-2 Super Micro Computer Inc (Broadcom / LSI) Serial Attached SCSI controller Type: Onboard Controller Current Link Speed: (downgraded) width (ok) ( max throughput) Maximum Link Speed: 8GT/s width x8 (7.88 GB/s max throughput) Why would it show the Current Link Speed as dowgraded? Diskspeed also reports the following: Slight variations between runs and minor improvements in all drives being read at once vs a single drive is normal. The average difference between the single drive and all drive read speeds is 1.0% Your controller is not bottle-necking. Which suggests the controller and SAS expander are working, as previously, before the upgrade, it was shown as 'Bottle Necked' just not sure why it shows the Current Link speed as downgraded. The controller is in: PCI Express 3.0 x16 Slot (PCIE2, Blue) from CPU_BSP1 The expander is in: PCI Express 3.0 x16 Slot (PCIE4, Blue) from CPU_BSP1 With an Nvidia 1050 TI graphics card in: PCI Express 3.0 x16 Slot (PCIE3, Blue) from CPU_BSP1