-
Posts
6,582 -
Joined
-
Days Won
8
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by BRiT
-
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
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. -
LSI Controller FW updates IR/IT modes
BRiT replied to madburg's topic in Storage Devices and Controllers
You can still use them, you merely need to control drive spin down some other way. -
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
At this point on unRAID 5.0 I'd go the other way ... try running smartctl without any "-d" options at all and detect errors to try it with "-d ata". -
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
You merely read the following summary: -
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
1. Use the -c option (lowercase c) followed by the cycle count. -
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
I know the OCZ SandForce-based drives have their own meaning to the SMART attributes. My OCZ Indilinx Vertex 1 drive barely implements SMART and the values it returns have no meaning to consumers. EDIT: Here's the SandForce SMART information: http://www.ocztechnologyforum.com/forum/showthread.php?75786-SMART-Attributes-for-Sandforce-SSD-s-%28Agility2-Vertex2-VertexLE%29 -
HPA a.k.a. why are two identical drives different sizes?
BRiT replied to Rajahal's topic in Storage Devices and Controllers
Another possible means of determining if you have HPA is manually issuing the following command. This will probe all of your drives, including your USB Flash drive, so it's natural to see an HDIO_DRIVE_CMD failed for that drive. This takes the guesswork out of knowing what your drives are. hdparm -N /dev/[hs]d[a-z] /dev/sda: max sectors = 312581808/312581808, HPA is disabled /dev/sdb: max sectors = 3907029168/3907029168, HPA is disabled /dev/sdc: max sectors = 3907029168/3907029168, HPA is disabled /dev/sdd: max sectors = 3907029168/3907029168, HPA is disabled /dev/sde: max sectors = 3907029168/3907029168, HPA is disabled /dev/sdf: HDIO_DRIVE_CMD(identify) failed: Invalid argument /dev/sdg: max sectors = 3907029168/3907029168, HPA is disabled /dev/sdh: max sectors = 3907029168/3907029168, HPA is disabled -
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
Usually the fix is they are actually reallocated. It's a little odd that they were removed from the pending reallocation list but were not actually reallocated. Perhaps they were able to be properly read during the preclear and thus removed from the pending list. I would run another preclear cycle on the drive to see how it behaves. Maybe Joe L or someone else would know better. -
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
The new report format of the preclear_disk.sh is all you need to look at to determine if things are good or not. -
[SOLVED] Headless System - Beep When Booted sucesfully
BRiT replied to hernandito's topic in General Support (V5 and Older)
Feel free to modify your own "go" script to use the /bin/beep command. For instance: beep -f 700 ; beep -f 500 ; beep -f 700 ; beep -f 500 -
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
The first version to support advanced format drives also includes the new report format as well. It was released on Jan 14, 2011 as Version .9.9. I know it at least displays the results to standard out. All you have to do is look at the display used to invoke the script. In my syslog I also have the human readable results, it's listed as "preclear_disk-diff". How did you invoke the script? -
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
I'm sorry to hear about your Vista grief. I wish everyone could have the kind of success I have with my Windows and Linux systems. I've had success with my Windows 7 development environments. The only need to reboot is for the rare installing of new devices that require additional device drivers or system services which is the same case for Linux. Sometimes I don't need to reboot in Windows 7 with some of the device driver upgrades, like for the NICs and Graphic Cards. Anyways, back on topic... Any thoughts to having preclear_disk.sh do a quick version check on startup against the unMENU repository to see if there's a newer version available, if so prompt the user if they would like to continue anyways? I'm not proposing a self-updating feature, just a quick warning to the users to upgrade. It's been nearly two weeks since your report simplifications and there's still people asking for feedback on the old formats. Now I know this won't help those running the older versions, but it would cut down on this sort of thing in the future. -
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
To be fair, the latest versions of Windows hardly need reboot either. -
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
For future reference, always upgrade to the latest version of preclear_disk.sh available at the time BEFORE you start your preclear cycle(s). The new results format enable you to self diagnose with ease. We can not tell if your disk is good since you did not include the full SMART report. We can only tell you that 3 attributes changed normalized values that are no where near their thresholds. If the disk was failing before the preclear on some attributes they're failing the same way after the preclear. If the disk was not failing before the preclear on some attributes, they're not failing the same way after the preclear. -
Preclear.sh results - Questions about your results? Post them here.
BRiT replied to jbuszkie's topic in User Customizations
For future reference, always upgrade to the latest version of preclear_disk.sh available at the time BEFORE you start your preclear cycle(s). The new results format enable you to self diagnose with ease. Your friend's drive is fine.