andrewb

Hey guys I have a WD15EARS HDD, that I precleared with the -A option, a while ago to use as my parity drive. I had precleared it on a gigabyte board outside of my server so when it said it had HPA I figured it was possible but I left it alone cause it wasnt causing a problem without any other disks in the system bigger than 1TB. I picked up a seagate 1.5TB drive as I am out of space and my cache drive is almost full too. So i precleared that drive last night and shutdown my server while its down i figured I would remove the HPA on the WD drive.. The problem is HDAT2 says there is no HPA... So is this something that starting on sector 64 caused or is it just random flaw? I am using unraid version 4.7 and dont have any real issues but I would like to upgrade to 5 in the future and have read that I should get rid of HPA before I do that.. Thanks!

I am pretty sure it was the right drive as it is the only 1.5Tb drive i have in the system. The reason for the lack of the third HPA in the second syslog is because I unassigned the parity drive from the array and then restarted it in hopes that it was just that it hadnt been restarted that the hdparm didnt work. It turns out thats when it said it was only ~400GB. I tried hdat2 on the drive and it gave me an error also. then I tried the auto remove in hpa and it said it worked so I tried it in unraid again but it still says it has HPA.. I think I am just gonna sync parity and leave it for now.. I dont have any other drive in the array bigger than 1TB and I'm hoping to upgrade to a few 2TB drives in the next few months so I will just replace the parity drive then with a fresh drive. Thanks for the help guys I appreciate it.

Alright so I restarted my server and now the 1.5T disk is only recognized as ~400GB. Im guessing my hdparm number was wrong? EDIT: Attached a syslog from after i restarted. As I was scrolling through it a couple things jumped out at me though honestly I have no idea what they really mean... these two lines: Apr 5 16:17:15 Tower kernel: pci 0000:00:1d.7: EHCI: BIOS handoff failed (BIOS bug?) 01010001 (Minor Issues) <--- Is this possibly a BIOS issue? Should i look into updating my BIOS? Apr 5 16:17:15 Tower kernel: scst: ***WARNING***: Patch io_context was not applied on your kernel. SCST will be working with not the best performance. syslog.txt

I ran hdparm -N p2930277168 /dev/sdj I got the 2930277168 from the syslog. The syslog is after i tried to run hdparm yes but before I rebooted the array. I shut down the server after I tried hdparm and havent restarted it since.

Hey guys, I had a disk go bad on me and the replacement I had from a previous RMA was a WD 1.5T drive that I had been using in my i5, with a Gigabyte GA P55M-UD2 mobo, desktop for a bit. Well after a bit of maneuvering I was able to move everything off of the failed drive and ran initconfig and proceeded to preclear the 1.5T WD15EARS with the 4k alignment. I assigned it to the array and rebuilt parity and it seems to be working fine. This just happened a couple days ago, and yesterday i was looking at mymain and noticed it said there was a possible hpa on my parity drive. I have had a couple drives with hpa for a while though I know when i upgraded to 4.7 those were not there. They most likely were added into the array after the upgrade. C2SEE-O-P, Celeron 420, 4gb ram, adaptec 1430SA,SUPERMICRO AOC-SASLP-MV8 I tried hdparm -N and it didnt seem to work, so I am wondering if this is a false positive because of the 4k alignment or if I should pull the disk and try to remove the hpa outside the array. Also, I was going through my syslog which I admit is like trying to read heiroglyphics for me but I noticed a bunch of errors. This was the most disturbing block of errors.. Not sure why it says C2SEA there cause its clearly marked C2SEE on the board... Sorry for the rambling guys just trying to make sure I include pertinent information... Ive attached a full syslog also though it goes back a few days. Thanks for any help guys. syslog.zip