It looks like you're new here. If you want to get involved, click one of these buttons!
In order to better support our growing community we've set up a new more powerful forum.
The new forum is at: http://community.covecube.com
The new forum is running IP.Board and will be our primary forum from now on.
This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.
Thank you,
hi there
I have five wd 3tb red drives which all seem ok
but the six one is connected via a silicon image raid card and that says has a file system damage
how do I clear that and also the smart data says its using the wd blue
interpretation
is this correct ?
Comments
Just looked at your screen shot your drive temp is very high mine run at about 27 max lowest is 22 all 24 of them that high temp can't be good for the drive just a thought
Lee
maybe connected to my issue
drive 5 is actually a wd 3tb red but if you look closely the drive appears to have a 250gb size and serial number
the same as another drive
just updated both scanner and drivepool and the issue is still there
i will report the issue this weekend
device manager list correctly but if you look closeron the above picture two 250 hard drives also have the same serial number :-(
FYI, I removed the front cover off my 4-bay MediaSonic ProBox, and the temps are 7 degrees cooler! I guess the little vent slits they added are not enough. Since I'm not concerned with aesthetics already being in a closed cabinet I'll leave it off.
I've tested the Mediasonic ProBox 3.5" SATA Hard Drive Enclosure - USB 3.0 SuperSpeed (K32-SU3) and have added the necessary data to BitFlock.com.
Just restart the StableBit Scanner service (or reboot) and you should now have full IDENTIFY and SMART data.
(and so will everyone else)
This is better than Unsafe, because it doesn't have to "probe" the enclosure which could crash it. It simply asks our cloud for the correct method to use.
Make sure that you're on the latest version of the Scanner, earlier builds had problems with the USB cloud feature.
Regards,"