KYThrill Posted May 23, 2011 Share Posted May 23, 2011 I have used preclear 1.11 to clear two drives now. On both, it hasn't showed any preclear status on MyMain. Is there some configuration that I'm missing, or should it automatically get displayed in MyMain? Did you update unmenu to use the new MyMain? It should show: 07-unmenu-mymain.awk: 1.53 - changes for myMain 3-10-11 release, contributed by bjp999 - 5.0b6 support - Revision: 223 when you click on the "about" link. If you did, there is already one other person reporting it is not displaying their disk's pre-clear status. Might be the same bug. Joe L. Joe, My unMenu install just shows version 1.5, not 1.53. Where can I download MyMain 1.53. I thought it was all integrated into unMenu, but I have installed the latest unMenu package from your Google site and it only installs version 1.5 of MyMain. Quote Link to comment
KYThrill Posted May 23, 2011 Share Posted May 23, 2011 Nevermind, I didn't even realize you could check for updates within unMenu. I thought updates were only available when a new unMenu installer was released. I got the update and preclear status appears to be showing fine. Thanks! Quote Link to comment
madburg Posted May 27, 2011 Share Posted May 27, 2011 Would there be a way to see what controller the drive is tied too OR detect the SMART failure and then proceed to attempt to run via –D on its own? There by automating it to the next level for members. Probably can detect the failure and try without the "-d ata" Not a bad idea for the next version. Thanks for the feedback. How are you Joe L., two questions, did the above make it into any of the releases after 1.9 (1.10 or 1.11)? If i am currently running a preclear (using version 1.9) can I update the preclear_disk.sh file on my key to the lastest version, or is it in use and not a good idea. Or just not a good idea at all while a preclear cycle is currently running? Quote Link to comment
Joe L. Posted May 27, 2011 Share Posted May 27, 2011 Would there be a way to see what controller the drive is tied too OR detect the SMART failure and then proceed to attempt to run via –D on its own? There by automating it to the next level for members. Probably can detect the failure and try without the "-d ata" Not a bad idea for the next version. Thanks for the feedback. How are you Joe L., two questions, did the above make it into any of the releases after 1.9 (1.10 or 1.11)? If i am currently running a preclear (using version 1.9) can I update the preclear_disk.sh file on my key to the lastest version, or is it in use and not a good idea. Or just not a good idea at all while a preclear cycle is currently running? I did not yet add the logic, so your version is as good as any. The big difference between 1.9 and 1.11 is the ability to monitor the progress on the MyMain screen. 1.10 was never released, it was an internal version number. Do not change the script while it is running. Just let the current pre-clears you have running complete. Thanks for the reminder though, I had not been thinking of the change to add that logic much... Joe L. Quote Link to comment
aRe-eYe-pEa Posted May 27, 2011 Share Posted May 27, 2011 Have you given any thought to setting up a way to donate to the cause? I have been able to save myself $$$ on more than on occasion. Quote Link to comment
madburg Posted May 28, 2011 Share Posted May 28, 2011 Would there be a way to see what controller the drive is tied too OR detect the SMART failure and then proceed to attempt to run via –D on its own? There by automating it to the next level for members. Probably can detect the failure and try without the "-d ata" Not a bad idea for the next version. Thanks for the feedback. How are you Joe L., two questions, did the above make it into any of the releases after 1.9 (1.10 or 1.11)? If i am currently running a preclear (using version 1.9) can I update the preclear_disk.sh file on my key to the lastest version, or is it in use and not a good idea. Or just not a good idea at all while a preclear cycle is currently running? I did not yet add the logic, so your version is as good as any. The big difference between 1.9 and 1.11 is the ability to monitor the progress on the MyMain screen. 1.10 was never released, it was an internal version number. Do not change the script while it is running. Just let the current pre-clears you have running complete. Thanks for the reminder though, I had not been thinking of the change to add that logic much... Joe L. Thanks Joe L. I will hang tight until it finishes before upgrading to v1.11, another question (I may have missed it if it was already stated) If you are preclearing more than one drive will the results for all (each) of the drives display in the MyMain page OR at this time the design is only capable of displaying the results of one drive preclearing? I like BRiTs comment after my requests as to making the -D option the standard as well, but I am keeping in mind to be fair with all, an auto detect funtionality would serve both worlds better. And I would think many members have setups where they start with onboard sata ports first and then only expanded to these newer sas cards (just guessing here). Would changing (for me) the line "device_type="-d ata"" to "device_type="-D"" accomplish this goal for the time being? until you whip up something cool. Quote Link to comment
Joe L. Posted May 28, 2011 Share Posted May 28, 2011 Would there be a way to see what controller the drive is tied too OR detect the SMART failure and then proceed to attempt to run via –D on its own? There by automating it to the next level for members. Probably can detect the failure and try without the "-d ata" Not a bad idea for the next version. Thanks for the feedback. How are you Joe L., two questions, did the above make it into any of the releases after 1.9 (1.10 or 1.11)? If i am currently running a preclear (using version 1.9) can I update the preclear_disk.sh file on my key to the lastest version, or is it in use and not a good idea. Or just not a good idea at all while a preclear cycle is currently running? I did not yet add the logic, so your version is as good as any. The big difference between 1.9 and 1.11 is the ability to monitor the progress on the MyMain screen. 1.10 was never released, it was an internal version number. Do not change the script while it is running. Just let the current pre-clears you have running complete. Thanks for the reminder though, I had not been thinking of the change to add that logic much... Joe L. Thanks Joe L. I will hang tight until it finishes before upgrading to v1.11, another question (I may have missed it if it was already stated) If you are preclearing more than one drive will the results for all (each) of the drives display in the MyMain page OR at this time the design is only capable of displaying the results of one drive preclearing? It will show multiple. I like BRiTs comment after my requests as to making the -D option the standard as well, but I am keeping in mind to be fair with all, an auto detect funtionality would serve both worlds better. And I would think many members have setups where they start with onboard sata ports first and then only expanded to these newer sas cards (just guessing here). Would changing (for me) the line "device_type="-d ata"" to "device_type="-D"" accomplish this goal for the time being? until you whip up something cool. I would change it to device_type="" Quote Link to comment
axeman Posted May 28, 2011 Share Posted May 28, 2011 are people really running several cycles my 3x 2TB drives took a little over 30hrs to complete (running simultaneously). not sure that I want to run/start another cycle if not neccesary.. Quote Link to comment
axeman Posted May 28, 2011 Share Posted May 28, 2011 So here are my results - any input would be greatly appreciated. there are three drives - sda, sdb, and sdc. WD20EARS, 2.0TB drives. Command I used was from config tutorial: ./preclear_disk.sh -A -M 4 /dev/sda (thru sdc). sdc Initial: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 966 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 15 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 1 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 13 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 12 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 17 194 Temperature_Celsius 0x0022 117 117 000 Old_age Always - 33 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 sdc final: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 966 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 15 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 26 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 13 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 12 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 17 194 Temperature_Celsius 0x0022 113 111 000 Old_age Always - 37 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 sda initial: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1008 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 15 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 1 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 13 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 12 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 17 194 Temperature_Celsius 0x0022 114 114 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 sda final: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1008 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 15 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 29 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 13 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 12 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 17 194 Temperature_Celsius 0x0022 111 109 000 Old_age Always - 39 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 sdb initial: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 958 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 17 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 2 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 15 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 14 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 194 Temperature_Celsius 0x0022 118 115 000 Old_age Always - 32 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 sdb final: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 958 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 17 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 30 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 15 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 14 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 194 Temperature_Celsius 0x0022 116 113 000 Old_age Always - 34 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Quote Link to comment
Superorb Posted May 28, 2011 Share Posted May 28, 2011 are people really running several cycles my 3x 2TB drives took a little over 30hrs to complete (running simultaneously). not sure that I want to run/start another cycle if not neccesary.. I used to only run 1 cycle, but now I run 3 cycles on all new disks and 1 cycle on disks I've been using in other PC's for a while. Quote Link to comment
Superorb Posted May 28, 2011 Share Posted May 28, 2011 So here are my results - any input would be greatly appreciated. there are three drives - sda, sdb, and sdc. WD20EARS, 2.0TB drives. Command I used was from config tutorial: ./preclear_disk.sh -A -M 4 /dev/sda (thru sdc). It has been posted several times, but RAW numbers don't mean anything except to the manufacturer. If the script said all drives Passed you're good to go. What does it say for reallocated sectors? You might want to look at drive cooling, 39C is getting close to the 40C threshold that you don't really want to go over. Quote Link to comment
BRiT Posted May 28, 2011 Share Posted May 28, 2011 are people really running several cycles my 3x 2TB drives took a little over 30hrs to complete (running simultaneously). not sure that I want to run/start another cycle if not neccesary.. Yes. I now run at least 3 preclear cycles on all new drives. I've had a drive or two pass the first pass but die on the second or third. Hard drives failures tend to fall into the bath-tub curve. It's best to get past the initial part before you trust it with your data. The last drives I added to the array went through 5 cycles. Yes, that's around 150 hours of preclear on each one. Fortunately you can run preclear on different drives at the same time. Quote Link to comment
axeman Posted May 28, 2011 Share Posted May 28, 2011 thanks - going to fire off another 2 rounds. the 40c has me concerned also. it was the 1 drive that's at the top of the drive rack. and coincidentally is "missed" by the intake fan on the bottom of the case (Cooler master storm scout). I have the drives spaced out so that there's a gap between them. before i fire off the next round, i'm going to put them closer together so they all get hit with the intake air. bad thing is i think I'm going to need to get a sata backplane or something when i decide to add more drives. I have 3x 1TB drives that would be in here by about december or so. Scout can hold 6x 3.5" but it would be too tight and would probably melt if i ran a pre-clear. Oh - I was also hoping that the temp wouldn't be too bad during regular non-stress use. thanks BRiT and Superorb. I planned on finishing up the ESXi + UnRaid build this weekend. I guess it's just pre-clears. :-) Quote Link to comment
axeman Posted May 28, 2011 Share Posted May 28, 2011 Okay so stackin' em didn't help much. more airflow, but temps are still same (perhaps a bit higher when it goes over to the write stage). SOO... the drive that is getting the highest (over 40C).. should I make that my parity drive, or keep it as a data drive? I saw a posting on here, about two types of drives - ones that have failed already, and ones that will fail. And high temps lead to failure... so is it better for a parity drive to fail or a data drive? right now it's on stock case fan. I can add two more to the side as exhaust and perhaps swap out the front one with a noctua or something. OH BTW, the reallocated sectors are at 0 so far. thanks for everyone's help still learning the ropes around here. Quote Link to comment
Superorb Posted May 28, 2011 Share Posted May 28, 2011 ^^ What case are you using, do you have any pics we can look at? You shouldn't have ANY drive running over 40C, it doesn't matter what its use will be. Quote Link to comment
axeman Posted May 28, 2011 Share Posted May 28, 2011 it's the Cooler master Storm scout: http://www.newegg.com/Product/Product.aspx?Item=N82E16811119196 I know it's not ideal, but didn't think drives would get this HOT. Pic below is from NE's stock photo. Sorry it's a bad scribble using win7 snipping tool. I can't get good photo of the actual unit w.o. moving it a good amount. wit the HD light solid, prolly shouldn't. Thanks for lookin @ it. Quote Link to comment
CHBMB Posted May 28, 2011 Share Posted May 28, 2011 Recently bought 3 Samsung F4s, all updated with the new firmware. First two precleared and the only attribute that was changed was the temperature. The third disk had Raw Read Error Rate, Hardware ECC Recovered and Multizone Error Rate all changed from 252 to 100 and UDMA CRC Error Count changed from 200 to 100. Should I be concerned? I should probably add, I've now got a niggling doubt that I didn't update the firmware on this drive but will before putting it to use. Logs of preclear for that drive attached below. preclear_start__S2H7JD2B227368_2011-05-26.txt preclear_finish__S2H7JD2B227368_2011-05-26.txt preclear_rpt__S2H7JD2B227368_2011-05-26.txt Quote Link to comment
Superorb Posted May 29, 2011 Share Posted May 29, 2011 Should I be concerned? I should probably add, I've now got a niggling doubt that I didn't update the firmware on this drive but will before putting it to use. I wouldn't worry about it. The important things are if you've got a growing number of reallocated sectors, or if it doesn't pass the preclear. Just make sure you do the JP1 firmware before you put it into production. Quote Link to comment
Superorb Posted May 29, 2011 Share Posted May 29, 2011 Pic below is from NE's stock photo. Sorry it's a bad scribble using win7 snipping tool. I can't get good photo of the actual unit w.o. moving it a good amount. wit the HD light solid, prolly shouldn't. I'd say either buy a 5in3 cage or make sure that all of your drives are behind that single fan in front of the hard drive bays. Quote Link to comment
axeman Posted May 29, 2011 Share Posted May 29, 2011 I'd say either buy a 5in3 cage or make sure that all of your drives are behind that single fan in front of the hard drive bays. i've been thinking of a 5in3 for when I "release" the 1TB drives. After your first reply, i moved them so that they are in front- and on the pre-read cycles, i'm getting 39, 38, and 36 (top to bottom). Going to go dig for a decent 5in3. my machine sits in Living Room so need something not so funky on the look. Quote Link to comment
Superorb Posted May 29, 2011 Share Posted May 29, 2011 i've been thinking of a 5in3 for when I "release" the 1TB drives. After your first reply, i moved them so that they are in front- and on the pre-read cycles, i'm getting 39, 38, and 36 (top to bottom). Going to go dig for a decent 5in3. my machine sits in Living Room so need something not so funky on the look. If the drives are still that warm even in front of the fan, maybe your ambient temps are too high to begin with. What is room temperature? Quote Link to comment
axeman Posted May 29, 2011 Share Posted May 29, 2011 If the drives are still that warm even in front of the fan, maybe your ambient temps are too high to begin with. What is room temperature? sda is now at 40c on the zeroing disk process, 25% it IS a bit warm - right now, the room is 80F or 26.6C. Is there a way for me to get case temp from unraid or this linux distro? Cpu is at: +56.0 C, +55.0 C, +54.0 C, +52.0 C. perhaps first I can try throw two fans on the side? Or maybe just get a 5in3 and put 1 or two HDs in there? Quote Link to comment
prostuff1 Posted May 29, 2011 Share Posted May 29, 2011 ^^ What case are you using, do you have any pics we can look at? You shouldn't have ANY drive running over 40C, it doesn't matter what its use will be. 45 and 50 is more in the "don't want to touch range" I have a couple drives that hit about 43C when doing a parity check. The parity check happens once a month so I am not to concerned about that temp for an 8ish hour period of time. Quote Link to comment
axeman Posted May 29, 2011 Share Posted May 29, 2011 funny thing the Post Read stage is running now and i've got 36c, 35c, and 34c all between 74MB and 78MB read speed.... looks like sticking them together, but in front of the fan has helped keep it below 40.. havent' broken that since this cycle started yesterday. Quote Link to comment
madburg Posted May 31, 2011 Share Posted May 31, 2011 Would there be a way to see what controller the drive is tied too OR detect the SMART failure and then proceed to attempt to run via –D on its own? There by automating it to the next level for members. Probably can detect the failure and try without the "-d ata" Not a bad idea for the next version. Thanks for the feedback. How are you Joe L., two questions, did the above make it into any of the releases after 1.9 (1.10 or 1.11)? If i am currently running a preclear (using version 1.9) can I update the preclear_disk.sh file on my key to the lastest version, or is it in use and not a good idea. Or just not a good idea at all while a preclear cycle is currently running? I did not yet add the logic, so your version is as good as any. The big difference between 1.9 and 1.11 is the ability to monitor the progress on the MyMain screen. 1.10 was never released, it was an internal version number. Do not change the script while it is running. Just let the current pre-clears you have running complete. Thanks for the reminder though, I had not been thinking of the change to add that logic much... Joe L. Thanks Joe L. I will hang tight until it finishes before upgrading to v1.11, another question (I may have missed it if it was already stated) If you are preclearing more than one drive will the results for all (each) of the drives display in the MyMain page OR at this time the design is only capable of displaying the results of one drive preclearing? It will show multiple. I like BRiTs comment after my requests as to making the -D option the standard as well, but I am keeping in mind to be fair with all, an auto detect funtionality would serve both worlds better. And I would think many members have setups where they start with onboard sata ports first and then only expanded to these newer sas cards (just guessing here). Would changing (for me) the line "device_type="-d ata"" to "device_type="-D"" accomplish this goal for the time being? until you whip up something cool. I would change it to device_type="" Thank you as always! Updated to the lastest unmenu, preclear_disk.sh v1.11, updated smartctl drive db (for my Hitachi's). Runing it on two new drives. unMenu shows the preclear stats, very nice guys! Between kicking these off with screen and then email alerts (-M 4) and now unMenu integration, pretty sweet. Thank you all very much. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.