HUH721010AL4200 turns off when I try to make ext4 partition

[Metallikus]

Hello everyone. There is a problem with one of the SAS disks (HUH721010AL4200). The drive turns off on power when I try to format it to ext4 or create a lvm. I go to the disk shelf - the diode is off and the disk becomes unavailable in the system. But in exfat it is formatted successfully. I tried to use the logical unit size 4k and 512 - the result is the same.

The long smarttest was successful, sg_format worked without errors - the issue persisted.

SMART of defective drive:

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.7-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: HGST
Product: HUH721010AL4200
Revision: A384
Compliance: SPC-4
User Capacity: 10 000 831 348 736 bytes [10,0 TB]
Logical block size: 4096 bytes
LU is fully provisioned
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000cca2567bed50
Serial number: some_serial_number
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Wed Dec 22 16:02:43 2021 +04
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Grown defects during certification = 0
Total blocks reassigned during format = 0
Total new blocks reassigned = 0
Power on minutes since format = 13445
Current Drive Temperature: 37 C
Drive Trip Temperature: 85 C

Accumulated power on time, hours:minutes 33139:47
Manufactured in week 04 of year 2017
Specified cycle count over device lifetime: 50000
Accumulated start-stop cycles: 60
Specified load-unload count over device lifetime: 600000
Accumulated load-unload cycles: 453
Elements in grown defect list: 0

Vendor (Seagate Cache) information
Blocks sent to initiator = 7074505713254400

Error counter log:
Errors Corrected by Total Correction Gigabytes Total
ECC rereads/ errors algorithm processed uncorrected
fast | delayed rewrites corrected invocations [10^9 bytes] errors
read: 0 134 0 134 12068655 459457,082 0
write: 0 0 0 0 522171 66964,356 0
verify: 0 0 0 0 3049 39,392 0

Non-medium error count: 0

SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Completed - 33109 - [- - -]
# 2 Background short Completed - 33091 - [- - -]

I have another HUH721010AL4200 and it has no this issue
SMART of normal drive:

=== START OF INFORMATION SECTION ===
Vendor: HGST
Product: HUH721010AL4200
Revision: A21D
Compliance: SPC-4
User Capacity: 10 000 831 348 736 bytes [10,0 TB]
Logical block size: 4096 bytes
LU is fully provisioned
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000cca25159d240
Serial number: some_serial_number
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Wed Dec 22 16:20:33 2021 +04
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature: 34 C
Drive Trip Temperature: 85 C

Accumulated power on time, hours:minutes 32240:35
Manufactured in week 51 of year 2016
Specified cycle count over device lifetime: 50000
Accumulated start-stop cycles: 23
Specified load-unload count over device lifetime: 600000
Accumulated load-unload cycles: 1360
Elements in grown defect list: 0

Vendor (Seagate Cache) information
Blocks sent to initiator = 18823197088546816

Error counter log:
Errors Corrected by Total Correction Gigabytes Total
ECC rereads/ errors algorithm processed uncorrected
fast | delayed rewrites corrected invocations [10^9 bytes] errors
read: 0 0 0 0 5628539 89295,454 0
write: 0 0 0 0 222726 503466,414 0
verify: 0 0 0 0 120354 0,034 0

Non-medium error count: 0

I use the LSI9200-8e controller and Huawei Openstor S2300 jbods.

I tried to format from an ubuntu, manjaro - the result is the same. From a windows it is formatted normally (from a linux it is also formatted normally to exfat). Has anyone come across something similar? What could be the reason and how to eliminate it?

[Metallikus]

I have successfully overwritten the disk with zeros today

~$: sudo sg_dd bs=4096 blk_sgio=1 if=/dev/zero of=/dev/sdy --verbose --progress
2440220288+0 records in
2440220288+0 records out
time to copy data: 53808.188477 secs at 185.86 MB/sec
...
Completed:
2441609216+0 records in
2441609216+0 records out

But attempts to create an ext4 partition are unsuccessful:

~$: sudo parted /dev/sdy
> mklabel gpt
> mkpart primary ext4 0 10GB

~$: sudo mkfs.ext4 -T largefile4 /dev/sdy1
mke2fs 1.46.4 (18-Aug-2021)
Creating filesystem with 2441401 4k blocks and 2400 inodes
Filesystem UUID: a5354a16-baf8-4ad9-8165-d172b6935b8b
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: mkfs.ext4: IO error while writing out and closing file system

The output of the DMESG is:

[323714.732758] sd 8:0:41:0: device_block, handle(0x0022)
[323716.483086] sd 8:0:41:0: device_unblock and setting to running, handle(0x0022)
[323716.496064] sd 8:0:41:0: Power-on or device reset occurred

After that I went to jbod - the diode does not light. Let me remind you that I can create the exfat section successfully. WTF?