Jump to content

joeyke87

Members
 View Profile  See their activity

  • Posts

    74

  • Joined

  • Last visited

 Content Type 

Posts posted by joeyke87

    Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

    in User Customizations

    Posted

    I just received my motherboard back from rma. Here's the thing: i've precleared 4 disks succesfully. Now when i add the fifth it's not sda, sdb etc. but hde, it's the same drive as the other ones...could it be that it's because port 5 and 6 are on a different chipset? Just asking because i don't want to start off the wrong foot.

    It indicates the second chipset is configured in your BIOS in Legacy mode where it is emulating an old IDE controller   (IDE devices show as "hda, hdb,etc").

     

    You should change the option in your BIOS to AHCI mode and get it out of legacy mode.   Many BIOS have a setting for each of their disk controllers.   The Legacy mode is enabled by default on many motherboards to allow them to boot older microsoft operating systems.  Win-XP and prior have no SATA drivers, and therefore could not boot windows if the chipset was in SATA mode.   This is not an issue with Linux or unRAID.

     

    All that said, either setting will work, and you can change the mode later with no effect or impact on your stored files.  It is just that the emulated legacy mode is frequently slower, as it does not take advantage of the features available in modern drives.   

     

    Joe L.

     

    I understand, i was already preclearing the disk but i'll set it to ahci after preclearing. Thanks :)

    Preclear.sh results - Questions about your results? Post them here.

    in User Customizations

    Posted

    Just finished my second disk:

     

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: S.M.A.R.T. error count differences detected after pre-clear

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: note, some 'raw' values may change, but not be an indication of a problem

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: 54c54

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: <  1 Raw_Read_Error_Rate    0x002f  100  253  051    Pre-fail  Always      -      0

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: ---

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: >  1 Raw_Read_Error_Rate    0x002f  200  200  051    Pre-fail  Always      -      0

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: 63c63

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: < 193 Load_Cycle_Count        0x0032  200  200  000    Old_age  Always      -      8

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: ---

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: > 193 Load_Cycle_Count        0x0032  200  200  000    Old_age  Always      -      12

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: 67c67

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: < 199 UDMA_CRC_Error_Count    0x0032  200  253  000    Old_age  Always      -      0

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: ---

    Oct 22 13:31:27 Tower preclear_disk-diff[6462]: > 199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

     

    After reading the links provided i'm guessing this is good right? But if the 100 current value would go below 051 it's an rma? I hope someone can clear this out for me so that i don't have to ask this anymore.

     

     

×
×
  • Create New...