-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum has become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
2 hpt 2760sgl
- Thread starter Drk
- Start date
- Status
Hey cyberjock,
I didn't have any issues running the smartctl. Mines works after I did the whole disable and reenable for each drives and service. Yes, for my drive i use smartctl -t short-d hpt, 1/1 /dev/hpt27xx. I had a post in the smartd email script thread on how I edit it to suit my drives. I can show you my result. I been performing short test. Though I would also like to know how to clear the self-test log.
my sector size says
Sector Sizes: 512 bytes logical, 4096 bytes physical
smart -a says
Code:
SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 112 099 006 Pre-fail Always - 47826696 3 Spin_Up_Time 0x0003 091 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 116 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 070 060 030 Pre-fail Always - 11300173 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2056 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 116 183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 190 Airflow_Temperature_Cel 0x0022 071 051 045 Old_age Always - 29 (Min/Max 25/29) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 113 193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 3797 194 Temperature_Celsius 0x0022 029 049 000 Old_age Always - 29 (0 13 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 1926h+28m+04.799s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 4170739305 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2123417385 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% 2008 - # 2 Short offline Completed without error 00% 2001 - # 3 Short offline Completed without error 00% 1271 - # 4 Short offline Completed without error 00% 1247 - # 5 Short offline Completed without error 00% 1103 - # 6 Short offline Completed without error 00% 935 - # 7 Short offline Completed without error 00% 768 - # 8 Short offline Completed without error 00% 600 - # 9 Short offline Completed without error 00% 504 - #10 Short offline Completed without error 00% 432 - #11 Short offline Completed without error 00% 264 - #12 Short offline Completed without error 00% 108 - #13 Short offline Completed without error 00% 48 - #14 Short offline Completed without error 00% 48 - #15 Short offline Completed without error 00% 48 - #16 Short offline Completed without error 00% 41 - #17 Short offline Completed without error 00% 41 - #18 Short offline Completed without error 00% 39 -
Hey Drk,
I ran that command. Mines says 512 for the sector size too. I think i have a 4k sector size according to the smartd and the specs from seagate for the drive themselves.
How would you make freenas 9.1 to use sector size of 4k without encryption. That was the only way to do it that I found people saying online.
tanik1,
You are the first person I've seen that had SMART work with Highpoint.. LOL! Count yourself lucky! I just might have to pull out my 4520 and try it again for good measure. Damn you!!!
As for the 4k thing, FreeBSD 9 has a blacklist of hard drives that lie about their sector size.
You can check your vdevs by querying the ashift value(zdb -C <yourzpoolname> | grep ashift). The ashift is the power of 2, so 9 = 512bytes and 12=4k. In FreeNAS 9 it "should" be smart enough to get it right. If it doesn't, you don't really have any choice except to do it from the command line. I put in a ticket for this issue already with FreeNAS 9. http://support.freenas.org/ticket/2404. Hopefully it will make it into the next version of FreeNAS.
My issue, if you read that ticket, is that I want the option of forcing 4k even if I'm using 512bytes per sector disks because I want some forward thinking options. I also question how complete the blacklist is and I'd hate to be that sucker that happens to not be on the blacklist. Ashifts can't be changed once the vdev is created. So you have to choose wisely.
As far as I know you can't clear the self test log. That's stored on the hard drive itself and I've never seen any option to clear it. My drives keep the most recent 100(or 20 for some of my drives) test results. I know if I connect to the controller's serial port and issue commands to the drive I can wipe(or change) any raw SMART parameter that I want. But it's not something I'd ever recommend anyone do, especially if you haven't done it before. You can permanently damage a hard drive if you aren't very careful.
Drk,
If you run the ashift command I mentioned above you can see if your zpool is aligned to 512 bytes or 4k sectors.
If you have a 4k drive with a 512 byte alignment, the performance penalty can vary from 1-5% to 40% or more depending on your work load. If you have a 512 byte drive with 4k alignment you have a performance loss of 5-10% and you lose some disk space due to the wrong alignment. Those numbers are off the top of my head, so I may have them wrong.
Personally, I always choose 4k right off the bat just to be "future proof".
You are the first person I've seen that had SMART work with Highpoint.. LOL! Count yourself lucky! I just might have to pull out my 4520 and try it again for good measure. Damn you!!!
As for the 4k thing, FreeBSD 9 has a blacklist of hard drives that lie about their sector size.
You can check your vdevs by querying the ashift value(zdb -C <yourzpoolname> | grep ashift). The ashift is the power of 2, so 9 = 512bytes and 12=4k. In FreeNAS 9 it "should" be smart enough to get it right. If it doesn't, you don't really have any choice except to do it from the command line. I put in a ticket for this issue already with FreeNAS 9. http://support.freenas.org/ticket/2404. Hopefully it will make it into the next version of FreeNAS.
My issue, if you read that ticket, is that I want the option of forcing 4k even if I'm using 512bytes per sector disks because I want some forward thinking options. I also question how complete the blacklist is and I'd hate to be that sucker that happens to not be on the blacklist. Ashifts can't be changed once the vdev is created. So you have to choose wisely.
As far as I know you can't clear the self test log. That's stored on the hard drive itself and I've never seen any option to clear it. My drives keep the most recent 100(or 20 for some of my drives) test results. I know if I connect to the controller's serial port and issue commands to the drive I can wipe(or change) any raw SMART parameter that I want. But it's not something I'd ever recommend anyone do, especially if you haven't done it before. You can permanently damage a hard drive if you aren't very careful.
Drk,
If you run the ashift command I mentioned above you can see if your zpool is aligned to 512 bytes or 4k sectors.
If you have a 4k drive with a 512 byte alignment, the performance penalty can vary from 1-5% to 40% or more depending on your work load. If you have a 512 byte drive with 4k alignment you have a performance loss of 5-10% and you lose some disk space due to the wrong alignment. Those numbers are off the top of my head, so I may have them wrong.
Personally, I always choose 4k right off the bat just to be "future proof".
Wow, I am glad to be the lucky one with a working high point. I was almost at the point of giving up on it but then it would of been a waste of money. So I just kept it and always looked into it. If you pull out yours you could probably add more drives in your nas. lol I am also pretty sure others out there have it working too but not saying anything haha. But maybe the problem was resolved as freenas was always updating too. I will need to check that ashift thing later on. I didn't really put anything important on my nas yet because I was still playing around with 9.1 and now the stable release is out I was going to upgrade to that. So if its not 4k sectors I will just rebuild like you mentioned.
For the test log, I thought there was a way to clear it. But thats fine if it doesn't keep all the logs. I thought clearing it was something manual but if it does it automatically that will working for me.
i hate to ask another question here but maybe you can answer it quickly if possible if not I will check the forum and maybe post a thread for it.
I was able to acquire a new system with quad core amd a8-6800k with 16gb of memory. Which I am making the new freenas from. I was looking at the reporting for memory usage I see that it utilize the memory when being used like transferring files, watching movies through dlna and other stuff. But when its not being under load I never see the memory usage graph go back down. It seems as if the memory is always high. And only a reboot clears it back. Just wondering if that was normal?
And thanks for all the help. Will check the ashift later tonight.
For the test log, I thought there was a way to clear it. But thats fine if it doesn't keep all the logs. I thought clearing it was something manual but if it does it automatically that will working for me.
i hate to ask another question here but maybe you can answer it quickly if possible if not I will check the forum and maybe post a thread for it.
I was able to acquire a new system with quad core amd a8-6800k with 16gb of memory. Which I am making the new freenas from. I was looking at the reporting for memory usage I see that it utilize the memory when being used like transferring files, watching movies through dlna and other stuff. But when its not being under load I never see the memory usage graph go back down. It seems as if the memory is always high. And only a reboot clears it back. Just wondering if that was normal?
And thanks for all the help. Will check the ashift later tonight.
- Status
