Need a little/lot of help with a hard drive issue

[Riffy]

So I will be honest I am still new to linux and mostly used Arch. However when I learning hypervisors I started using proxmox which is Debian and that is the system I am having an issue with. Currently I got four 16tb wd red drives on an HBA card, 2 m.2 drives, and a single 10tb WD red on the motherboards sata controller. When I boot currently I am passing nothing but the video card to a VM so all the drives show up in lsblk. But any attempt to do ANYTHING to the 10tb drive, currently /dev/sda fails. I had this issue before and RMA'ed the drive but this one is also acting up. I tried it on a different machine which only saw it once but also failed to write to it or format it.

When trying to run fdisk -l /dev/sda I get "cannot open /dev/sda: Input/output error" so I ran dmesg and got some output I am not sure how to interpret as I've never seen it before. I've included the bottom chunk of it. So at this point I am trying to work out if the drive is bad, did I brick the drive, or is the motherboard having issues since I think this started when I added the HBA card.

[47493.275023] ata7.00: ATA Identify Device Log not supported
[47493.275900] ata7.00: failed to enable AA (error_mask=0x1)
[47493.276141] ata7.00: Read log 0x00 page 0x00 failed, Emask 0x1
[47493.276143] ata7.00: NCQ Send/Recv Log not supported
[47493.276385] ata7.00: Read log 0x00 page 0x00 failed, Emask 0x1
[47493.276387] ata7.00: NCQ Send/Recv Log not supported
[47493.276625] ata7.00: Read log 0x00 page 0x00 failed, Emask 0x1
[47493.276626] ata7.00: ATA Identify Device Log not supported
[47493.276867] ata7.00: configured for UDMA/133 (device error ignored)
[47493.276879] ata7: EH complete
[47493.297941] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[47493.297946] ata7.00: irq_stat 0x40000001
[47493.297950] ata7.00: failed command: READ DMA
[47493.297951] ata7.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 16 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
[47493.297956] ata7.00: status: { DRDY ERR }
[47493.297957] ata7.00: error: { ABRT }
[47493.298306] ata7.00: failed to enable AA (error_mask=0x1)
[47493.298554] ata7.00: Read log 0x00 page 0x00 failed, Emask 0x1
[47493.298555] ata7.00: NCQ Send/Recv Log not supported
[47493.298798] ata7.00: Read log 0x00 page 0x00 failed, Emask 0x1
[47493.298799] ata7.00: NCQ Send/Recv Log not supported
[47493.299041] ata7.00: Read log 0x00 page 0x00 failed, Emask 0x1
[47493.299042] ata7.00: ATA Identify Device Log not supported
[47493.299910] ata7.00: failed to enable AA (error_mask=0x1)
[47493.300152] ata7.00: Read log 0x00 page 0x00 failed, Emask 0x1
[47493.300154] ata7.00: NCQ Send/Recv Log not supported
[47493.300394] ata7.00: Read log 0x00 page 0x00 failed, Emask 0x1
[47493.300395] ata7.00: NCQ Send/Recv Log not supported
[47493.300634] ata7.00: Read log 0x00 page 0x00 failed, Emask 0x1
[47493.300635] ata7.00: ATA Identify Device Log not supported
[47493.300872] ata7.00: configured for UDMA/133 (device error ignored)
[47493.300886] sd 6:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[47493.300888] sd 6:0:0:0: [sda] tag#16 Sense Key : Illegal Request [current]
[47493.300889] sd 6:0:0:0: [sda] tag#16 Add. Sense: Unaligned write command
[47493.300890] sd 6:0:0:0: [sda] tag#16 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[47493.300891] blk_update_request: I/O error, dev sda, sector 0 op 0x0READ) flags 0x0 phys_seg 1 prio class 0
[47493.300894] Buffer I/O error on dev sda, logical block 0, async page read
[47493.300899] ata7: EH complete
root@proxmox:~#

 

[MattWinter]

Did you set up a file system on these drives?

 

[Brickwizard]

Have you run a health check on the hard-drive, smartctl. is a good one

https://linuxconfig.org/how-to-check-an-hard-drive-health-from-the-command-line-using-smartctl

 

[Riffy]

Did you set up a file system on these drives?

No, I just plugged it in and tried the initialize disk with gpt inside proxmox and get error 4 if I believe was the error.

Have you run a health check on the hard-drive, smartctl. is a good one

https://linuxconfig.org/how-to-check-an-hard-drive-health-from-the-command-line-using-smartctl

Yes, however outside of the eprom I don't get anything. I removed the serial number from the post myself, it does show up in smartctl.

root@proxmox:~# smartctl -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.104-1-pve] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: WDC WD101EFBX-68B0AN0
Serial Number:
LU WWN Device Id: 5 000cca 0c8c9f320
Firmware Version: 85.00A85
User Capacity: 10,000,831,348,736 bytes [10.0 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Apr 5 10:05:21 2023 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Read SMART Data failed: scsi error badly formed scsi parameters

=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error badly formed scsi parameters
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

Read SMART Log Directory failed: scsi error badly formed scsi parameters

Read SMART Error Log failed: scsi error badly formed scsi parameters

Read SMART Self-test Log failed: scsi error badly formed scsi parameters

Selective Self-tests/Logging not supported

root@proxmox:~#

 

[Deleted member 108694]

failed to enable AA (error_mask=0x1)

This points to a problem with your hardware, be it the cables, the hard drive or the motherboard. The only way to fix it, is diagnostic each piece of hardware individually as far as I know

 

[Riffy]

This points to a problem with your hardware, be it the cables, the hard drive or the motherboard. The only way to fix it, is diagnostic each piece of hardware individually as far as I know

That is the plan, since my windows PC also wouldn't really see or use the drive I am assuming it's the drive but I am sure I got some POS seagate laying around I can test the server with. Just to rule it out, the HBA card wouldn't be messing with the onboard sata controller would it?

So I got a 3rd drive last night and it first went into the windows PC and was working fine, formatted to ntfs before putting it in the server which also sees it fine. Now to reformat it and use it. I just find it weird to get two WD red duds in a row.