bobrap Posted February 17, 2011 Share Posted February 17, 2011 I'm running v4.7 and have several drives that show HPA. I thought I read that if it's not on the parity drive, just leave 'em alone. Is this still the case? Thanks syslog-2011-02-17-5.txt Link to comment
dgaschk Posted February 17, 2011 Share Posted February 17, 2011 If your setup works don't mess with it. HPA take a tiny amount of space but otherwise does not effect performance. Many people with HPA cannot start their array and thus must remove the HPA. Link to comment
Joe L. Posted February 17, 2011 Share Posted February 17, 2011 If your setup works don't mess with it. HPA take a tiny amount of space but otherwise does not effect performance. Many people with HPA cannot start their array and thus must remove the HPA. You'll not be able to use the current 5.0beta4 with the HPA. Do not even try to use it as you'll not be able to start the array. Wait for at least 5.0beta5 to see if it handles HPA better. (The issue is the HPA occupies an odd number of sectors, and unRAID in 5.0b4 expected all its math for partition size to find an even number of sectors on a disk.) Link to comment
bobrap Posted February 17, 2011 Author Share Posted February 17, 2011 Is there an easy way to "zap" a disk and get rid of hpa and then copy data to it form another drive? One of my drives is empty and I would like to just migrate data a disc at a time. Link to comment
dgaschk Posted February 17, 2011 Share Posted February 17, 2011 See this post: http://lime-technology.com/forum/index.php?topic=10866.0 Copy the data from the HPA drive to your new drive and then remove the HPA. Link to comment
bobrap Posted February 18, 2011 Author Share Posted February 18, 2011 Well, it seems the reason I have a blank disc is I ran the hdparm -N method and it changed the drive size from 488,385,492 to 396,111,864 with 396,066,928 free. Link to comment
Joe L. Posted February 18, 2011 Share Posted February 18, 2011 Well, it seems the reason I have a blank disc is I ran the hdparm -N method and it changed the drive size from 488,385,492 to 396,111,864 with 396,066,928 free. It sounds as if you gave it the wrong size. I suggest you use an alternate tool. Joe L. Link to comment
bobrap Posted February 18, 2011 Author Share Posted February 18, 2011 I tried the HDAT2 Method and all I got were errors. I guess since the data is trashed, I'll just trash the drive! Link to comment
Joe L. Posted February 18, 2011 Share Posted February 18, 2011 I tried the HDAT2 Method and all I got were errors. I guess since the data is trashed, I'll just trash the drive! There's also SeaTools. Link to comment
Stucco Posted February 18, 2011 Share Posted February 18, 2011 Seatools for dos worked really well for me. couldn't find the command on the windows version. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.