ReLe

Just an update, after moving to LSI9207, from LSI2008 on 3.11.2022, no errors after switch to this date. But, who knows what it really was in my case and when the Ironwolf disks start to act again.

Quite interesting thread. Came here trough Google when searching what to do in my situation. I thought that it would be possible somehow do this or at least maybe it would be implemented. I have to migrate my unraid to mATX case when we move for 2 months to escape apartment water pipes renovation. I can't take the array disks with me (power consumption and there is no room for large tower) but I need to run the vm's. Currently thinking of moving mobo (small B660 with 12100) and only vm ssd + os ssd to small case and install proxmox to run the vm's. After I move back I probably will run Unraid as vm in proxmox with nic&hba passthrough, going forward to get around the vm debacle. I have had my fights with array before, having to run repairs etc to disks and I can't have the downtime for the vm's during those periods.

I'm having the same issue. Started happening last saturday 26.11. Noticed this on the log from last night. 2022-11-28 04:27:40 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2022-11-28 04:27:40 information: xxxyyyy is shut off. vm desired state is shut off. can_backup_vm set to y. 2022-11-28 04:27:40 information: actually_copy_files is 1. 2022-11-28 04:27:40 information: can_backup_vm flag is y. starting backup of xxxyyyy configuration, nvram, and vdisk(s). 2022-11-28 04:27:40 information: copy of xxxyyyy.xml to /mnt/user/backup/xxxyyyy/20221128_0400_xxxyyyy.xml complete. 2022-11-28 04:27:40 information: copy of /etc/libvirt/qemu/nvram/XXXXX_VARS-pure-efi.fd to /mnt/use r/backup/xxxyyyy/20221128_0400_XXXXX_VARS-pure-efi.fd complete. 2022-11-28 04:50:14 information: copy of /mnt/disks/XXXXXDISK/domains/Ubuntu/vdisk1.img to /mnt/user/backup/xxxyyyy/20221128_ 0400_vdisk1.img complete. 2022-11-28 04:50:15 information: backup of /mnt/disks/XXXXXDISK/domains/Ubuntu/vdisk1.img vdisk to /mnt/user/backup/xxxyyyy/2 0221128_0400_vdisk1.img complete. 2022-11-28 04:50:15 information: extension for /mnt/cache/gparted-live-1.1.0-1-i686.iso on xxxyyyy was found in vdisks_extensions_ to_skip. skipping disk. 2022-11-28 04:50:15 information: the extensions of the vdisks that were backed up are img. 2022-11-28 04:50:15 information: vm_state is shut off. vm_original_state is shut off. not starting xxxyyyy. 2022-11-28 04:50:15 information: backup of xxxyyyy to /mnt/user/backup/xxxyyyy completed. So apparently somehow the script fails to write the on/off state prior backing up, since it states "vm_state is shut off. vm_original_state is shut off. not starting xxxyyyy." Other vm's get properly booted up. EDIT: Works again after rebooting

My latest fails were on H310 crossflash LSI 2008 based card and Unraid version 6.11.1. On 3.11.2022 switched to LSI9207 and time will tell if this helps.

Thanks for the reply. Just to rule out possible issues with the controller, I just ordered a refurbished 9207 (server pull from reputable seller) and will see if problems will get resolved.

Again had issues with my iron wolf drives. Have disabled low power spin with seachest (epc is not found on my drives feature list). Eventually I'm going to move to WD red plus drives, but in meantime I was wondering that is this issue with all LSI controllers. Would it help if I would switch from H310 2008 based controller to 9207-8i? I have the latest FW on my current LSI.

Thanks @optiman I tried with the 2019 version got same error as before. EPC feature is not listed with info command. I tested the drive with (Asus Deluxe X79) motherboard integraded ?marvell? sata controller and also intel sata ports and neither controller paired with the Seagate disk lists EPC in info. Info: SeaChest_Info_150_11923_64 -d /dev/sg4 -i ========================================================================================== SeaChest_Info - Seagate drive utilities - NVMe Enabled Copyright (c) 2014-2019 Seagate Technology LLC and/or its Affiliates, All Rights Reserved SeaChest_Info Version: 1.5.0-1_19_23 X86_64 Build Date: Jun 10 2019 Today: Fri Dec 10 20:13:30 2021 ========================================================================================== /dev/sg4 - ST4000VN008-2DR166 - xxxxxxxx - ATA Model Number: ST4000VN008-2DR166 Serial Number: xxxxxxxxxx Firmware Revision: SC60 World Wide Name: 5000C500C97E2CB5 Drive Capacity (TB/TiB): 4.00/3.64 Native Drive Capacity (TB/TiB): 4.00/3.64 Temperature Data: Current Temperature (C): 28 Highest Temperature (C): 41 Lowest Temperature (C): 0 Power On Time: 85 days 23 hours 43 minutes Power On Hours: 2063.72 MaxLBA: 7814037167 Native MaxLBA: 7814037167 Logical Sector Size (B): 512 Physical Sector Size (B): 4096 Sector Alignment: 0 Rotation Rate (RPM): 5980 Form Factor: 3.5" Last DST information: DST has never been run Long Drive Self Test Time: 10 hours 9 minutes Interface speed: Max Speed (Gb/s): 6.0 Negotiated Speed (Gb/s): 3.0 Annualized Workload Rate (TB/yr): 123.25 Total Bytes Read (TB): 20.87 Total Bytes Written (TB): 8.17 Encryption Support: Not Supported Cache Size (MiB): 64.00 Read Look-Ahead: Enabled Write Cache: Enabled Low Current Spinup: Disabled SMART Status: Good ATA Security Information: Supported Firmware Download Support: Full, Segmented, Deferred, DMA Specifications Supported: ACS-3 ACS-2 ATA8-ACS ATA/ATAPI-7 ATA/ATAPI-6 ATA/ATAPI-5 ATA/ATAPI-4 SATA 3.1 SATA 3.0 SATA 2.6 SATA 2.5 SATA II: Extensions SATA 1.0a ATA8-AST Features Supported: Sanitize SATA NCQ SATA Rebuild Assist SATA Software Settings Preservation [Enabled] SATA Device Initiated Power Management HPA Power Management Security SMART [Enabled] DCO 48bit Address PUIS APM [Enabled] GPL Streaming SMART Self-Test SMART Error Logging Write-Read-Verify Sense Data Reporting [Enabled] SCT Write Same SCT Error Recovery Control SCT Feature Control SCT Data Tables Host Logging Seagate In Drive Diagnostics (IDD) However, I noticed that when I run the info, I get following errors to dmesg: ata5.00: invalid command format 2 Every Seagate disk queryed with the seachest_info gives that error to dmesg from their ata address.

Tried the EPC disabling when one of my relatively new Seagate Iron wolf drives got disabled in Unraid 6.9.2 and LSI controller, detailed info below Num Ctlr FW Ver NVDATA x86-BIOS PCI Addr ---------------------------------------------------------------------------- 0 SAS2008(B2) 20.00.07.00 14.01.00.08 No Image 00:03:00:00 SeaChest_PowerControl_x86_64-redhat-linux --scan --onlySeagate ATA /dev/sg11 ST4000VN008-2DR166 SC60 SeaChest_PowerControl_x86_64-redhat-linux -d /dev/sg11 --EPCfeature disable ========================================================================================== SeaChest_PowerControl - Seagate drive utilities - NVMe Enabled Copyright (c) 2014-2021 Seagate Technology LLC and/or its Affiliates, All Rights Reserved SeaChest_PowerControl Version: 3.0.2-2_2_3 X86_64 Build Date: Jun 17 2021 Today: Fri Dec 10 01:53:39 2021 User: root ========================================================================================== /dev/sg11 - ST4000VN008-2DR166 - ZDH9N576 - ATA Failed to send EPC command to /dev/sg11. EPC Feature set might not be supported. Or EPC Feature might already be in the desired state. Did I miss something? I dont see EPC in info listing and I am unable to set EPC. Is this because drive is connected to LSI controller?