dscline

I guess what I'm still not clear on is how are these methods different than what I'm already doing with Smartmontools by specifying that these specific drives need the SCSI to ATA translation to read the SMART data. Or is it the same?

Ok thanks, I've installed it, we'll see what happens. Large logs aren't really a concern, but I guess there's no way to direct where they go?

Thanks drashna, I saw that in the other threads, but at this time I'm a bit reluctant due to the "Methods that have been known to cause a system crash on a small percentage of machines ..." clause in those instructions. I might try it at a later time, but don't want to introduce too many new variables right now. From what I can tell, it's an "all or nothing" setting (you enable it if you have any drives that it can't read SMART values for). With Smartmontools, I simply tell it specifically which drives to use SCSI to ATA Translation on, and it works. What exactly is "UnsafeDirectIo" doing?

I've just had this happen again on another drive: Got an email saying a drive was expected to fail within 24hrs, but nothing concerning in the dashboard. In this case, I have four of the drives that correspond to the same model that the email is referring to: two of them the dashboard says there's no indication of any problems, the other two it says it's not predicting any immanent disk failure, but some SMART attributes are showing signs the disk could be failing. The only SMART issues are some reallocated sectors: 1 on one of them, and 6 on the other. In both cases, those sectors were reallocated when the drives were relatively new, about 3 years ago. I don't understand why I'm getting these "the sky is falling' emails, then everything seems fine in the dashboard. As far as the first drive, I'm not sure what to think about that one. In my initial panic I pulled the drive and started testing it on my client PC, where I didn't have any SMART software. I downloaded Crystaldisk, and THOUGHT I saw 200 reallocated sectors, but that was the only time. So I'm not sure if it has changed, or if I just mis-read it. Since the emails don't provide a S/N, I'm not even certain that "failing within 24hrs" email was referring to the same drive.

I have a bunch of drives on an IBM m1015 flashed to an LSI9211-8i in IT mode. Stablebit can not read the SMART data on any of those drives. But I know it's available, as it can be read in FlexRAID (which I believe uses smartctl) by specifying the SAT device type. Is there any way to also pick this up in Stablebit? Thanks! EDIT: I see there are some topics in the compatability forum regarding this. I will work through those.

I just had a similar thing happen. I've just upgraded my server from WHS v1 to WHS v2. In the process I've also switched from FlexRAID RAID-F snapshot to FlexRAID tRAID, so my parity had to be rebuilt. During the process, one of my drives started getting errors. I removed it & put it in my client PC and ran a full chkdsk + surface scan on it. It came back clean from that, but I also queried it with Crystaldisk, and I could swear I saw 200 reallocated sectors on it. I put it back in the server, and re-created the parity without issue. I also got Stablebit Scanner set up, and let it start scanning the drives again. Strangely, both Stablebit and Flexraid show no reallocated sectors on the drive now. I got an email this morning that a Samsung HD204 is expected to fail within 24hrs. That's the same model as the drive I had to pull, though I don't know for SURE it's the same drive I had problems with yesterday, as I have a couple of that model. But looking at Stablebit on the server, both of them still seem fine.