What doed this smart results indicate?



  • Can anyone tell me what the S.M.A.R.T attributes reflect?Pic attached



  • Your drive is old, and has indications it's going to fail soon. If it's a critical system, replace the drive ASAP. If you can take a failure whenever it eventually dies, just be prepared to replace it, reinstall, and restore a config backup.



  • @mafiosa:

    Can anyone tell me what the S.M.A.R.T attributes reflect?Pic attached

    CMB is right, you have a lot of bad sectors, so it looks like that drive is toast…

    At 24/day service, it has less than 60 days of running time.  (What make/model is it?  Seagate?)

    Unless you've had it sitting in a drawer for a long time, or it only runs for short periods of time, you should be able to RMA it and get a replacement drive.  Make a copy of the smart info to send to the manufacturer when you submit your RMA request.  Even if you can't afford to wait for a replacement to arrive, at least you'll have a spare or can sell it.

    Good luck



  • @guardian:

    @mafiosa:

    Can anyone tell me what the S.M.A.R.T attributes reflect?Pic attached

    CMB is right, you have a lot of bad sectors, so it looks like that drive is toast…

    At 24/day service, it has less than 60 days of running time.  (What make/model is it?  Seagate?)

    Unless you've had it sitting in a drawer for a long time, or it only runs for short periods of time, you should be able to RMA it and get a replacement drive.  Make a copy of the smart info to send to the manufacturer when you submit your RMA request.  Even if you can't afford to wait for a replacement to arrive, at least you'll have a spare or can sell it.

    Good luck

    This is a seagate external drive that i ripped out from its case, its a 1tb hdd.Are the sectors recoverable by software?



  • @mafiosa:

    This is a seagate external drive that i ripped out from its case, its a 1tb hdd.Are the sectors recoverable by software?

    No. Bad sectors are physical defects, software can only map out the bad sectors (hide them from the system) but it won't negate the fact that the drive is failing.

    It's a very good idea to replace the harddisk, especially to an internal drive that receives cooling. Most portable drives aren't meant to run 24/7 and heat is a big issue once you do that.



  • @dreamslacker:

    @mafiosa:

    This is a seagate external drive that i ripped out from its case, its a 1tb hdd.Are the sectors recoverable by software?

    No. Bad sectors are physical defects, software can only map out the bad sectors (hide them from the system) but it won't negate the fact that the drive is failing.

    It's a very good idea to replace the harddisk, especially to an internal drive that receives cooling. Most portable drives aren't meant to run 24/7 and heat is a big issue once you do that.

    Exactly. Though it sounds like he's running it as a normal internal drive, pulled from the external enclosure (at which point it's no diff from any internal drive). Still, it's old and dying fast, nothing software can do about that.



  • If you don't need the space - for packages like SQUID, SNORT, SURICATA etc. A good option will be to just use NanoBSD on a thumbdrive.

    Further, you can go sign up for pfSense Gold to support the project (didn't need the webminars but I still signed for it) - this gives you access to AutoConfigBackup (ACB) and the Guidebook + webminars lends a lot of insights and working knowledge into deploying pfSense in practical environments.
    ACB makes life real easy if your thumbdrive ever fails. Just load another cheap thumbdrive up, connect it to the internet and use ACB to restore your configuration.



  • @mafiosa:

    @guardian:

    @mafiosa:

    Can anyone tell me what the S.M.A.R.T attributes reflect?Pic attached

    CMB is right, you have a lot of bad sectors, so it looks like that drive is toast…

    At 24/day service, it has less than 60 days of running time.  (What make/model is it?  Seagate?)

    Unless you've had it sitting in a drawer for a long time, or it only runs for short periods of time, you should be able to RMA it and get a replacement drive.  Make a copy of the smart info to send to the manufacturer when you submit your RMA request.  Even if you can't afford to wait for a replacement to arrive, at least you'll have a spare or can sell it.

    Good luck

    This is a seagate external drive that i ripped out from its case, its a 1tb hdd.Are the sectors recoverable by software?

    Too bad you can't RMA it, but under the circumstances you're stuck.  What model is the drive (It's in the ID section of the smartctl report you've chopped off).  I've stopped using Seagate because of poor quality and low duty cycle (that's why they are cheap!).  Our cable company buys these garbage PVRs from Cisco that uses them, and they are pretty much guaranteed to fail just shortly after they are done with warranty.

    A lot of those drives are not rated to spin 24/7 (what a joke)…look in the specs--Power On Hours 2400 (300 8 Hour Work Days/Year)--You need a drive rated at 8760 Hours.  These low duty cycle drives either need to spend most of their time spun down, or they are going to die pretty quick.  Running 24/7 in a router box is likely not going to last a year.

    If you don't care if the drive fails again without notice (cause you religiously back up your config file, and you don't care about logs and such), and you can't afford to buy a new drive then you should be able to run a utility to mark the sectors bad so they won't cause problems.  I think fsck can do this for you, but I'll defer to someone who is good with BSD.

    You'll be fine until you get another bad sector... might happen tomorrow, might be months... no way to tell.

    I had one of those drives that I did that with... got a about 8 bad sectors... I used a utility called SpinRite... marked them bad/offline... got 2 years out of the drive before I took it out of service to upgrade to larger capacity drive.  In my case the drive was 3TB at a time when the Seagate drive was about $200 new, and a good quality WD drive was $300.  I had 4 of them is RaidZ2 (which means I could survive 2 drive failures).  Was very light duty in a home application, and I got away with it for about 2 years or so.  Finally upgraded to 4 4TB Red Drives which are great.

    Hope you or someone else finds these comments useful.

    Good luck.



  • Meh. 8 pending sectors and 8 offline uncorrectable sectors. Not great but not a big deal if you ask me. Line five doesn't show any realocated sectors so I'd chalk this one up to "keep an eye on it and see if it gets worse".

    You wanna see a bad smart output take a look at the drive currently in my pfsense rig.  ;D

    smartctl 6.4 2015-06-04 r4109 [FreeBSD 10.3-RELEASE-p3 amd64] (local build)
    Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Model Family:     Seagate Barracuda 7200.8
    Device Model:     ST3250823AS
    Serial Number:    3ND01VNZ
    Firmware Version: 3.01
    User Capacity:    250,058,268,160 bytes [250 GB]
    Sector Size:      512 bytes logical/physical
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   ATA/ATAPI-7 (minor revision not indicated)
    Local Time is:    Fri Jul 22 16:25:04 2016 EDT
    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:  (0x82)	Offline data collection activity
    					was completed without error.
    					Auto Offline Data Collection: Enabled.
    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: 		(  430) seconds.
    Offline data collection
    capabilities: 			 (0x5b) 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.
    					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: 	 (  84) minutes.
    SCT capabilities: 	       (0x0001)	SCT Status supported.
    
    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   052   045   006    Pre-fail  Always       -       0
      3 Spin_Up_Time            0x0003   098   097   000    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   093   093   020    Old_age   Always       -       7171
      5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x000f   078   060   030    Pre-fail  Always       -       77504160
      9 Power_On_Hours          0x0032   026   026   000    Old_age   Always       -       65385
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   094   094   020    Old_age   Always       -       7018
    194 Temperature_Celsius     0x0022   036   055   000    Old_age   Always       -       36 (0 14 0 0 0)
    195 Hardware_ECC_Recovered  0x001a   052   045   000    Old_age   Always       -       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
    200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
    202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0
    
    SMART Error Log Version: 1
    ATA Error Count: 835 (device log contains only the most recent five errors)
    	CR = Command Register [HEX]
    	FR = Features Register [HEX]
    	SC = Sector Count Register [HEX]
    	SN = Sector Number Register [HEX]
    	CL = Cylinder Low Register [HEX]
    	CH = Cylinder High Register [HEX]
    	DH = Device/Head Register [HEX]
    	DC = Device Command Register [HEX]
    	ER = Error register [HEX]
    	ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    
    Error 835 occurred at disk power-on lifetime: 31001 hours (1291 days + 17 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      10 51 01 2e 51 1c ed
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      37 00 01 2e 51 1c ed 00      20:04:23.699  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      27 00 00 2e 51 1c e0 00      20:04:23.572  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      37 00 00 2e 51 1c ed 00      20:04:23.572  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      27 00 01 2e 51 1c e0 00      20:04:21.433  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      37 00 01 2e 51 1c ed 00      20:04:21.433  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    
    Error 834 occurred at disk power-on lifetime: 31001 hours (1291 days + 17 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      10 51 01 2e 51 1c ed
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      37 00 01 2e 51 1c ed 00      20:04:18.465  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      27 00 00 2e 51 1c e0 00      20:04:18.464  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      37 00 00 2e 51 1c ed 00      20:04:18.464  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      27 00 01 6f 59 1c e0 00      20:04:21.433  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      29 00 01 6f 59 1c e0 00      20:04:21.433  READ MULTIPLE EXT
    
    Error 833 occurred at disk power-on lifetime: 30994 hours (1291 days + 10 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      10 51 01 2e 51 1c ed
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      37 00 01 2e 51 1c ed 00      12:54:15.930  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      27 00 00 2e 51 1c e0 00      12:54:15.930  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      37 00 00 2e 51 1c ed 00      12:54:20.716  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      27 00 01 2e 51 1c e0 00      12:54:20.716  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      37 00 01 2e 51 1c ed 00      12:54:20.589  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    
    Error 832 occurred at disk power-on lifetime: 30994 hours (1291 days + 10 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      10 51 01 2e 51 1c ed
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      37 00 01 2e 51 1c ed 00      12:54:15.930  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      27 00 00 2e 51 1c e0 00      12:54:15.930  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      37 00 00 2e 51 1c ed 00      12:54:15.930  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      27 00 01 6f 59 1c e0 00      12:54:15.483  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      29 00 01 6f 59 1c e0 00      12:54:15.483  READ MULTIPLE EXT
    
    Error 831 occurred at disk power-on lifetime: 30994 hours (1291 days + 10 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      10 51 01 2e 51 1c ed
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      37 00 01 2e 51 1c ed 00      12:50:41.622  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      27 00 00 2e 51 1c e0 00      12:50:41.622  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      37 00 00 2e 51 1c ed 00      12:50:39.483  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      27 00 01 2e 51 1c e0 00      12:50:39.483  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
      37 00 01 2e 51 1c ed 00      12:50:39.357  SET NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    
    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%     65278         -
    # 2  Extended offline    Completed without error       00%     63303         -
    # 3  Short offline       Completed without error       00%     63301         -
    
    SMART Selective self-test log data structure revision number 1
     SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
        1        0        0  Not_testing
        2        0        0  Not_testing
        3        0        0  Not_testing
        4        0        0  Not_testing
        5        0        0  Not_testing
    Selective self-test flags (0x0):
      After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    


  • Hi, my first post. And first time user of pfSense :)
    So far I'm very happy with pfSense.

    I also like to put my smart results of my disk.

    
    smartctl 6.4 2015-06-04 r4109 [FreeBSD 10.3-RELEASE-p3 amd64] (local build)
    Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF INFORMATION SECTION ===
    Model Family:     Seagate Barracuda 7200.14 (AF)
    Device Model:     ST500DM002-1BD142
    Serial Number:    W2AP4F58
    LU WWN Device Id: 5 000c50 05e1f1ee4
    Firmware Version: KC45
    User Capacity:    500,107,862,016 bytes [500 GB]
    Sector Sizes:     512 bytes logical, 4096 bytes physical
    Rotation Rate:    7200 rpm
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   ATA8-ACS T13/1699-D revision 4
    SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is:    Fri Jul 22 23:08:28 2016 CEST
    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:  (0x82)    Offline data collection activity
                        was completed without error.
                        Auto Offline Data Collection: Enabled.
    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:         (  600) seconds.
    Offline data collection
    capabilities:              (0x7b) SMART execute Offline immediate.
                        Auto Offline data collection on/off support.
                        Suspend Offline collection upon new
                        command.
                        Offline surface scan supported.
                        Self-test supported.
                        Conveyance Self-test supported.
                        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:      (  83) minutes.
    Conveyance self-test routine
    recommended polling time:      (   2) minutes.
    SCT capabilities:            (0x303f)    SCT Status supported.
                        SCT Error Recovery Control supported.
                        SCT Feature Control supported.
                        SCT Data Table supported.
    
    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   111   099   006    Pre-fail  Always       -       30316936
      3 Spin_Up_Time            0x0003   100   100   000    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1430
      5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x000f   081   060   030    Pre-fail  Always       -       4451986274
      9 Power_On_Hours          0x0032   089   089   000    Old_age   Always       -       10285
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1422
    183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
    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   099   000    Old_age   Always       -       0 0 6
    189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
    190 Airflow_Temperature_Cel 0x0022   062   056   045    Old_age   Always       -       38 (Min/Max 31/39)
    194 Temperature_Celsius     0x0022   038   044   000    Old_age   Always       -       38 (0 15 0 0 0)
    195 Hardware_ECC_Recovered  0x001a   033   026   000    Old_age   Always       -       30316936
    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      -       10284h+54m+36.643s
    241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       2787711386
    242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       2969075091
    
    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%      9926         -
    
    SMART Selective self-test log data structure revision number 1
     SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
        1        0        0  Not_testing
        2        0        0  Not_testing
        3        0        0  Not_testing
        4        0        0  Not_testing
        5        0        0  Not_testing
    Selective self-test flags (0x0):
      After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    
    


  • @CiscoX:

    I also like to put my smart results of my disk.

    So far so good… everything looks fine with the smart results.  Only challange I see with that drive is that it's not rated to be running 24x7.

    If you look at the specs:
    http://www.seagate.com/files/staticfiles/docs/pdf/datasheet/disc/barracuda-ds1737-1-1111us.pdf
    you'll see Power-On Hours 2400.  Which is 8 hours/day 5 days/week.

    It may not have a great lifespan given that a pf box will have the drive spinning 24x7x365… unless you turn stuff off.



  • @guardian:

    @CiscoX:

    I also like to put my smart results of my disk.

    So far so good… everything looks fine with the smart results.  Only challange I see with that drive is that it's not rated to be running 24x7.

    If you look at the specs:
    http://www.seagate.com/files/staticfiles/docs/pdf/datasheet/disc/barracuda-ds1737-1-1111us.pdf
    you'll see Power-On Hours 2400.  Which is 8 hours/day 5 days/week.

    It may not have a great lifespan given that a pf box will have the drive spinning 24x7x365… unless you turn stuff off.

    Thank you very much. I think have to replace this disk then. Maybe WD RED (NAS disk) or what about SSD. Do you have any suggestions? :)

    Thanks in advanced



  • @CiscoX:

    @guardian:

    @CiscoX:

    I also like to put my smart results of my disk.

    So far so good… everything looks fine with the smart results.  Only challange I see with that drive is that it's not rated to be running 24x7.

    If you look at the specs:
    http://www.seagate.com/files/staticfiles/docs/pdf/datasheet/disc/barracuda-ds1737-1-1111us.pdf
    you'll see Power-On Hours 2400.  Which is 8 hours/day 5 days/week.

    It may not have a great lifespan given that a pf box will have the drive spinning 24x7x365… unless you turn stuff off.

    Thank you very much. I think have to replace this disk then. Maybe WD RED (NAS disk) or what about SSD. Do you have any suggestions? :)

    Thanks in advanced

    Replacing the disk is a good idea if high reliability is important.  The bulk of the drive is for logs, packet logging, and rulesets, so there isn't anything that really needs protecting other than the configuration.  As long as you keep a backup of your configuration, it shouldn't matter much.  If the disk fails, you reinstall a fresh copy and reload the config and you're done.  (Might be a good idea to keep a fairly recent copy of the installer on your local computer as if pfSense dies, you won't have any internet unless you have a router you can swap in till you get it fixed.)

    I'd recommend you use an SSD as speed will help if you are logging packets.  Also quiet and cooler with no moving parts - if you buy a decent brand, an  SSD will likely last a lot longer than a mechanical disk, but you never know.  For mechanical disks, I'd recommend Western Digital.  Seagate were good once , but lately I've had way too much BAD experience with  them-Seagate seem to be going for cheap/volume.  Don't know if their enterprise stuff is better, but I've never had any experience with it.  WD Blacks in PC's - WD Reds in NAS - Samsung SSDs for boot drive and embedded devices like pfSense box.  (May be better SSD choices, I bought based on speed/performance ratings from test sites-can't comment about longevity since none of the ones I own are over 1 year old.)

    If you do use an SSD make sure you enable trim (wear leveling) to make sure you get best life/use out of the disk.

    I used these instructions and based on personal experience they worked no problem with a Samsung 850 EVO SSD.

    Original Source: https://forum.pfsense.org/index.php?topic=114202.msg634936#msg634936```

    I enabled TRIM on the Samsung SSD as follows.  Below is compiled from several other posters here..so thanks!

    1.  booted pfSense from USB stick and installed pfSense to SSD

    2.  Used Putty to connect to the box, fired up the shell and obtained ufsid by showing the fstab file:
            [2.2.4-RELEASE][root@pfSense.localdomain]/root: cat /etc/fstab
            # Device                Mountpoint      FStype  Options        Dump    Pass#
            /dev/ufsid/576dca6e13175d08            /              ufs    rw              1      1

    3.  booted pfSense from USB stick into single-user mode

    4.  at the # prompt, the following was issued:
          /sbin/tunefs -t enable /dev/ufsid/576dca6e13175d08 (your ufsid will be different!
          /sbin/reboot

    5.  booted pfSense from SSD.  Again using putty, ran this command from shell to see if TRIM was enabled.
          /sbin/tunefs -p /

    
    Hope this helps.


  • @guardian:

    @CiscoX:

    @guardian:

    @CiscoX:

    I also like to put my smart results of my disk.

    So far so good… everything looks fine with the smart results.  Only challange I see with that drive is that it's not rated to be running 24x7.

    If you look at the specs:
    http://www.seagate.com/files/staticfiles/docs/pdf/datasheet/disc/barracuda-ds1737-1-1111us.pdf
    you'll see Power-On Hours 2400.  Which is 8 hours/day 5 days/week.

    It may not have a great lifespan given that a pf box will have the drive spinning 24x7x365… unless you turn stuff off.

    Thank you very much. I think have to replace this disk then. Maybe WD RED (NAS disk) or what about SSD. Do you have any suggestions? :)

    Thanks in advanced

    Replacing the disk is a good idea if high reliability is important.  The bulk of the drive is for logs, packet logging, and rulesets, so there isn't anything that really needs protecting other than the configuration.  As long as you keep a backup of your configuration, it shouldn't matter much.  If the disk fails, you reinstall a fresh copy and reload the config and you're done.  (Might be a good idea to keep a fairly recent copy of the installer on your local computer as if pfSense dies, you won't have any internet unless you have a router you can swap in till you get it fixed.)

    I'd recommend you use an SSD as speed will help if you are logging packets.  Also quiet and cooler with no moving parts - if you buy a decent brand, an  SSD will likely last a lot longer than a mechanical disk, but you never know.  For mechanical disks, I'd recommend Western Digital.  Seagate were good once , but lately I've had way too much BAD experience with  them-Seagate seem to be going for cheap/volume.  Don't know if their enterprise stuff is better, but I've never had any experience with it.  WD Blacks in PC's - WD Reds in NAS - Samsung SSDs for boot drive and embedded devices like pfSense box.  (May be better SSD choices, I bought based on speed/performance ratings from test sites-can't comment about longevity since none of the ones I own are over 1 year old.)

    If you do use an SSD make sure you enable trim (wear leveling) to make sure you get best life/use out of the disk.

    I used these instructions and based on personal experience they worked no problem with a Samsung 850 EVO SSD.

    Original Source: https://forum.pfsense.org/index.php?topic=114202.msg634936#msg634936```

    I enabled TRIM on the Samsung SSD as follows.  Below is compiled from several other posters here..so thanks!

    1.  booted pfSense from USB stick and installed pfSense to SSD

    2.  Used Putty to connect to the box, fired up the shell and obtained ufsid by showing the fstab file:
            [2.2.4-RELEASE][root@pfSense.localdomain]/root: cat /etc/fstab
            # Device                Mountpoint      FStype  Options        Dump    Pass#
            /dev/ufsid/576dca6e13175d08            /              ufs    rw              1      1

    3.  booted pfSense from USB stick into single-user mode

    4.  at the # prompt, the following was issued:
          /sbin/tunefs -t enable /dev/ufsid/576dca6e13175d08 (your ufsid will be different!
          /sbin/reboot

    5.  booted pfSense from SSD.  Again using putty, ran this command from shell to see if TRIM was enabled.
          /sbin/tunefs -p /

    
    Hope this helps.
    

    Thank you so much for the information.
    I do run backup almost every day of my pfSense :)
    I will probably go for the WD Red or Samsung SSD 850 EVO(run this one on my other computers, never experienced any kind of problem with them) when my Seagate is "dead" :)


Log in to reply