Intermittent Shut Down (after 30 mins) - Only Happens When Array is Started

[icarus44_zer0]

It all started when I bought some new drives. They would not add to the array. After preclear failed... I was able to diagnose that I had a bad memory module on one of my dims. After weeks of Downtime (I'm very busy) and now I'm just looking to start from scratch. 

 

Bought 3 new drive. Pre cleared all of them. They all passed. However Failed to format. But show as XSF. However the amount used is kind of sketchy. However this may be an inaccurate reading.  

 

 

Now the fun stuff starts. The server shuts down after 30 mins.  Here's the syslog... Searching online hasn't brought much luck so far. Again the server was up for two days clearing the drive... Added them to the array and now she shuts down after ~30 mins.  I'm willing to start from scratch. I pulled the drive that had my data on them when things started getting really weird. Hopefully I can rebuild the server then migrate my data back onto the array. So much has gone wrong not sure what on earth to do next.

 

Thanks in advance,

The_Crimson_King_19

 

Mar 16 11:37:07 Kronos kernel: ACPI: EC: interrupt unblocked
Mar 16 11:37:07 Kronos kernel: pcieport 0000:00:1c.0: Enabling MPC IRBNCE
Mar 16 11:37:07 Kronos kernel: pcieport 0000:00:1c.3: Enabling MPC IRBNCE
Mar 16 11:37:07 Kronos kernel: pcieport 0000:00:1c.0: Intel PCH root port ACS workaround enabled
Mar 16 11:37:07 Kronos kernel: pcieport 0000:00:1c.4: Enabling MPC IRBNCE
Mar 16 11:37:07 Kronos kernel: pcieport 0000:00:1c.3: Intel PCH root port ACS workaround enabled
Mar 16 11:37:07 Kronos kernel: pcieport 0000:00:1c.4: Intel PCH root port ACS workaround enabled
Mar 16 11:37:07 Kronos kernel: pci 0000:01:00.0: can't change power state from unknown to D0 (config space inaccessible)
Mar 16 11:37:07 Kronos kernel: pcieport 0000:00:1c.7: Enabling MPC IRBNCE
Mar 16 11:37:07 Kronos kernel: pcieport 0000:00:1c.7: Intel PCH root port ACS workaround enabled
Mar 16 11:37:07 Kronos kernel: pci 0000:01:00.1: can't change power state from unknown to D0 (config space inaccessible)
Mar 16 11:37:07 Kronos kernel: ACPI: EC: event unblocked
Mar 16 11:37:07 Kronos kernel: sd 4:0:0:0: [sdb] Starting disk
Mar 16 11:37:07 Kronos kernel: sd 9:0:0:0: [sdc] Starting disk
Mar 16 11:37:07 Kronos kernel: sd 10:0:0:0: [sdd] Starting disk
Mar 16 11:37:07 Kronos kernel: serial 00:06: activated
Mar 16 11:37:07 Kronos kernel: r8169 0000:06:02.0 eth1: Link is Down
Mar 16 11:37:07 Kronos kernel: ata8: SATA link down (SStatus 0 SControl 300)
Mar 16 11:37:07 Kronos kernel: ata7: SATA link down (SStatus 0 SControl 300)
Mar 16 11:37:07 Kronos kernel: ata6: SATA link down (SStatus 0 SControl 300)
Mar 16 11:37:07 Kronos kernel: ata3: SATA link down (SStatus 0 SControl 300)
Mar 16 11:37:07 Kronos kernel: ata1: SATA link down (SStatus 0 SControl 300)
Mar 16 11:37:07 Kronos kernel: ata5: SATA link down (SStatus 0 SControl 300)
Mar 16 11:37:07 Kronos kernel: ata2: SATA link down (SStatus 0 SControl 300)
Mar 16 11:37:07 Kronos kernel: e1000e 0000:00:19.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 16 11:37:07 Kronos kernel: ata4: link is slow to respond, please be patient (ready=0)
Mar 16 11:37:07 Kronos kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 16 11:37:07 Kronos kernel: ata10.00: configured for UDMA/133
Mar 16 11:37:07 Kronos kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 16 11:37:07 Kronos kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Mar 16 11:37:07 Kronos kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Mar 16 11:37:07 Kronos kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Mar 16 11:37:07 Kronos kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Mar 16 11:37:07 Kronos kernel: ata4.00: configured for UDMA/133
Mar 16 11:37:07 Kronos kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 16 11:37:07 Kronos kernel: ata9.00: configured for UDMA/133
Mar 16 11:37:07 Kronos kernel: OOM killer enabled.
Mar 16 11:37:07 Kronos kernel: Restarting tasks ... done.
Mar 16 11:37:07 Kronos kernel: PM: suspend exit

 

syslog.txt

[JorgeB]

8 minutes ago, icarus44_zer0 said:

However the amount used is kind of sketchy.

It's normal for new xfs formatted drives.

 

As for the other issue, try uninstalling the s3 sleep plugin, it has known issues with v6.9.

[icarus44_zer0]

17 minutes ago, JorgeB said:

It's normal for new xfs formatted drives.

 

As for the other issue, try uninstalling the s3 sleep plugin, it has known issues with v6.9.

 I have removed the S3 sleep plugin thanks for the tip.