February 19, 201214 yr the Smart Screen under myMain in unMenu shows "HPA?" next to a 32GB SSD I just installed. It's brand new drive, cleared through unRAID, but not precleared (per recommendations on here). is that just because the structure of an SSD is different? I'm not sure how it could have HPA on it. It's a Torqx2 drive by Patriot.
February 19, 201214 yr the Smart Screen under myMain in unMenu shows "HPA?" next to a 32GB SSD I just installed. It's brand new drive, cleared through unRAID, but not precleared (per recommendations on here). is that just because the structure of an SSD is different? I'm not sure how it could have HPA on it. It's a Torqx2 drive by Patriot. Probably it does not recognize its size. Do you have a Gigabyte motherboard? Do you want to post the smart report? or just have us guess at the size it is presenting?
February 19, 201214 yr Any drive can have an HPA, be it SSD or HDD. myMain will flag an HPA anytime the reported size is smaller than the actual size of the drive. As Joe mentioned, the likely culprit is a Gigabyte motherboard that was connected to the SSD at some point.
February 19, 201214 yr For SSDs sometimes the reported size is smaller because the drive keeps some space for garbage/trim Josh
February 22, 201214 yr Author Any drive can have an HPA, be it SSD or HDD. myMain will flag an HPA anytime the reported size is smaller than the actual size of the drive. As Joe mentioned, the likely culprit is a Gigabyte motherboard that was connected to the SSD at some point. Sorry, hadn't been on here in a couple days. This is a brand new drive out of the box. I have a Biostar board and don't have this trouble with any other drives. It has never been in another machine.
February 22, 201214 yr Author For SSDs sometimes the reported size is smaller because the drive keeps some space for garbage/trim Josh So this is just the architecture of the drive and i should ignore it?
February 22, 201214 yr I ignored mine, brand new kingston 32gb shows as 30gb, a lot of ssd's keep a part of the space aside for garbage collection. I think in mymain you can set the flag so that it doesn't show up as hpa anymore. You'd have to search as I don't remember off the top of my head. Josh
February 23, 201214 yr Author I ignored mine, brand new kingston 32gb shows as 30gb, a lot of ssd's keep a part of the space aside for garbage collection. I think in mymain you can set the flag so that it doesn't show up as hpa anymore. You'd have to search as I don't remember off the top of my head. Josh Is there any way to "know" that this won't affect my parity? Seems like I read that HPA could cause problems with the accuracy of parity and that's why is dangerous. It doesn't sound like thesis HPA to me either, but would like to "know" for sure.
February 23, 201214 yr I ignored mine, brand new kingston 32gb shows as 30gb, a lot of ssd's keep a part of the space aside for garbage collection. I think in mymain you can set the flag so that it doesn't show up as hpa anymore. You'd have to search as I don't remember off the top of my head. Josh Is there any way to "know" that this won't affect my parity? Seems like I read that HPA could cause problems with the accuracy of parity and that's why is dangerous. It doesn't sound like thesis HPA to me either, but would like to "know" for sure. type hdparm -N /dev/sdX if the physical and logical sizes are the same, no HPA.
February 25, 201214 yr Author type hdparm -N /dev/sdX if the physical and logical sizes are the same, no HPA. I got max sectors - 62533296/12201648(62533296?), HPA setting seems invalid (buggy kernal device driver?) Based on what I read elsewhere in the forums, the fact that the first number and the number in () match, means there is no HPA correct? So should I ignore this or should I be concerned about effect on my parity? Do much appreciate the help all. After two lashings from Joe for not having enough information the past few days Syslog attached. Smartview attached. HDparm report from unmenu: ATA device, with non-removable media Model Number: Patriot Torqx 2 32GB SSD Serial Number: BA140721090800019963 Firmware Revision: S5FAM014 Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6 Standards: Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 62533296 LBA48 user addressable sectors: 62533296 Logical Sector size: 512 bytes Physical Sector size: 512 bytes Logical Sector-0 offset: 0 bytes device size with M = 1024*1024: 30533 MBytes device size with M = 1000*1000: 32017 MBytes (32 GB) cache/buffer size = unknown Form Factor: 2.5 inch Nominal Media Rotation Rate: Solid State Device Smart Status Statistics for /dev/sdb Patriot_Torqx_2_BA140721090800019963 smartctl -a -d ata /dev/sdb smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: Patriot Torqx 2 32GB SSD Serial Number: BA140721090800019963 Firmware Version: S5FAM014 User Capacity: 32,017,047,552 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Feb 24 23:43:31 2012 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 255) seconds. Offline data collection capabilities: (0x1b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. No Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 2) minutes. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 189 12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 7 168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0 170 Unknown_Attribute 0x0003 100 100 010 Pre-fail Always - 8589934633 173 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 65545 192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 2 218 Unknown_Attribute 0x000b 100 100 050 Pre-fail Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 134 - Device does not support Selective Self Tests/Logging Did I miss anything that time Thanks again Joe for your time. Syslog_2012_02_24.txt
February 25, 201214 yr Author Afterthought. The data intended to be kept on this drive really doesn't need to be in the protected array. If there is any doubt it could be affecting the integrity of the parity (whatever is causing the hpa flag), then I could pull it out. Thoughts? Or confirmation everything is OK as is based on the above?
February 25, 201214 yr Afterthought. The data intended to be kept on this drive really doesn't need to be in the protected array. If there is any doubt it could be affecting the integrity of the parity (whatever is causing the hpa flag), then I could pull it out. Thoughts? Or confirmation everything is OK as is based on the above? Everything looks perfectly fine. It does not appear as if you have an HPA on the disk, it is only that the myMain add-on does not recognize the size of that disk. Set the ignore flag in myMain, and get on with the use of your server. Its "warning of HPA?" has absolutely nothing to affect parity. In myMain.conf you'll see the list of disk sizes it uses to determine if an HPA is present, or not. #----------------------- # Used to check for HPA #----------------------- SetConstant(ValidPartitionSizes, "MX200G=199148512, 200G=195360952, MX250G=245117344, MX300G=293057320, SG300G=293036152, 320G=312571192, 400G=390711352, 640G=625131832, \ 8G=8257000, MX40G=40146592, 60G=58615672, WD74G=72613024, 80G=78150712, SM120G=117246496, WD120G=117220792, MX160G=160086496, 160G=156290872, \ 3T=2930266532,") Your size of 62533296 is not in the list, therefore was flagged as suspect. if you like, send a PM to myMain's author and request your SSD's size be added. Might help someone else in the future. Joe L.
February 26, 201214 yr Author Afterthought. The data intended to be kept on this drive really doesn't need to be in the protected array. If there is any doubt it could be affecting the integrity of the parity (whatever is causing the hpa flag), then I could pull it out. Thoughts? Or confirmation everything is OK as is based on the above? Everything looks perfectly fine. It does not appear as if you have an HPA on the disk, it is only that the myMain add-on does not recognize the size of that disk. Set the ignore flag in myMain, and get on with the use of your server. Its "warning of HPA?" has absolutely nothing to affect parity. In myMain.conf you'll see the list of disk sizes it uses to determine if an HPA is present, or not. #----------------------- # Used to check for HPA #----------------------- SetConstant(ValidPartitionSizes, "MX200G=199148512, 200G=195360952, MX250G=245117344, MX300G=293057320, SG300G=293036152, 320G=312571192, 400G=390711352, 640G=625131832, \ 8G=8257000, MX40G=40146592, 60G=58615672, WD74G=72613024, 80G=78150712, SM120G=117246496, WD120G=117220792, MX160G=160086496, 160G=156290872, \ 3T=2930266532,") Your size of 62533296 is not in the list, therefore was flagged as suspect. if you like, send a PM to myMain's author and request your SSD's size be added. Might help someone else in the future. Joe L. Thanks again, and for the explanation. Gives me much needed peace of mind!
Archived
This topic is now archived and is closed to further replies.