ooimo Posted March 26, 2020 Share Posted March 26, 2020 Hi All, Recently I had the configuration issue plugin tell me that HPA was enabled on my data and parity drives. When I went through the process of removing it by running the hdparm command I found that it was in my controller having issues and wrongly reporting on the drives and not HPA. Issuing the hdparm command through the faulty controller has set the HPA at 8Gb into the drives and when I attempt to fix this I get an error shown below. james@linuxws:~$ sudo hdparm -N /dev/sda /dev/sda: max sectors = 16777215/15628053168, HPA is enabled james@linuxws:~$ sudo hdparm -N p15628053168 /dev/sda /dev/sda: setting max visible sectors to 15628053168 (permanent) SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 16777215/15628053168, HPA is enabled I realise this was pretty stupid and I shouldn't have rushed into sending dangerous hdparm commands, but if there is another way to fix the drives I am all ears. I have already tried ATA tool from a windows machine and made sure the drive is not frozen. Loss of data is not an issue due to the tested backups I have. Cheers, Quote Link to comment
Vr2Io Posted March 26, 2020 Share Posted March 26, 2020 Pls try other controller i.e. onboard. And also try plug in SATA connector after OS bootup. Quote Link to comment
ooimo Posted March 26, 2020 Author Share Posted March 26, 2020 I'm getting the same response from the drive using a different controller james@linuxws:~$ sudo hdparm -N /dev/sda /dev/sda: max sectors = 16777215/15628053168, HPA is enabled james@linuxws:~$ sudo hdparm -N 15628053168 /dev/sda /dev/sda: setting max visible sectors to 15628053168 (temporary) SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 16777215/15628053168, HPA is enabled Is there a way to decode the response? Quote Link to comment
Vr2Io Posted March 27, 2020 Share Posted March 27, 2020 It is sda, does you boot OS by this disk ? Pls don't boot OS by this disk and try plug the SATA link after boot up. Quote Link to comment
ooimo Posted March 28, 2020 Author Share Posted March 28, 2020 No, the OS is booting from a different disk. When I connect the disk after boot up it is not detected by the OS. Below is the output when booting without the faulty disk connected. I have also tried running the following command which should scan for disks. james@linuxws:~$ for host in /sys/class/scsi_host/*; do echo "- - -" | sudo tee $host/scan; ls /dev/sd* ; done - - - /dev/sda /dev/sda1 /dev/sda2 - - - /dev/sda /dev/sda1 /dev/sda2 - - - /dev/sda /dev/sda1 /dev/sda2 - - - /dev/sda /dev/sda1 /dev/sda2 - - - /dev/sda /dev/sda1 /dev/sda2 - - - /dev/sda /dev/sda1 /dev/sda2 james@linuxws:~$ lsblk -S NAME HCTL TYPE VENDOR MODEL REV TRAN sda 4:0:0:0 disk ATA SAMSUNG MZMTD128 1K0Q sata Quote Link to comment
Vr2Io Posted March 28, 2020 Share Posted March 28, 2020 1 hour ago, ooimo said: When I connect the disk after boot up it is not detected by the OS. So weird. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.