Q. Bios reports 739GB drive mounted on an esata connected Mediasonic external raid device and reports a "reset Port Error", but Vista 64 shows the correct volume size of 2.72TB drive.
Read and writes are fine through windows and tested pass the 2TB mark. Should I be worried about the error msg as well as the reported size? (story below)
------------
Its been an exciting week as I re-discovered the joys of Raiding
I bought the Mediasonic HFR2-S3B with great trepidation as most esata external Raid boxes these days requires an internal PM (port multiplier) PCI-E raid controller.
However, I was estatic when my first test run with 4x500GB drives in raid 5 showed up as a single esata drive with no problems.
The problems began, after I added 4x1TB WD green drives to the unit.
My bios (specs below), gave me a "Reset Port Error" and showed the mounted Mediasonic as configured as a 739GB external drive (wrap around). However after booting to vista 64 ultimate, the drive was properly speced at a 2.72TB drive.
I had no problems writing and reading past 2TB as I filled the drive up with data however since I was using Intel Matrix Storage console 7.5, I would get BSOD when hotswapping esata devices of which my HD docking station was also on one of my esata ports.
So with one too many BSOD, my mediasonic raid drive became dirty and windows in its infinite wisdom asked if it can perform a chkdsk on my drive before booting up. Not thinking at that point in time, I allowed it to.... and watched in horror as it attempted to recover lost clusters from a 2.72TB drive thinking it was a 739GB drive. I immediately powered off the pc, however the damage was done.
After booting up the next time, I performed a proper chkdsk; after windows had loaded the proper drivers. It found all my orphan files....
I then upgraded my intel matrix console to v8.8 and continued to copy data over to the drive at which I found a few directory to be inaccessible reporting that the directory structure was invalid. I attempted to delete them, and at times I used the shift key to delete permanently; bad mistake as I'm sure this was what caused my MBR to be deleted?.
I decided in my wisdom, that perhaps I should reboot and perhaps the problem would go away....
Well, my problem did go away in the form of loosing the whole drive. Windows reported that the device was not formatted and would I like to?
After many reboots and re-tries.... I finally gave in and reformatted the drive.... and proceeded to fill it up with data again; except this time I am using Intel Matrix 8.8 which doesn't give me the BSOD when hotswapping my drives.
So far, the mediasonic has been working properly without any problems. Every so often, I would perform a chkdsk (via windows) on the device.
However it is disconceerting to see the bios reporting 739GB on this external device and....
HD Tune Pro seems to be reading the bios to get the drive size reporting that it is a 800GB drive.
I figure that as long as I stop any chkdsk at boot time.... this drive should survive for a few months of usage.
What do you guys think?
System specs:
Shuttle SP35P2V2 with "latest bios", build-in ICH9R raid chipset
8GB of mem
4x1TB internal raid 5 with 100GB reserved for boot OS and 2.62TB data space
Mediasonic HFR2-S3B Pro Raid Box
connected through one of the shuttle ESATA ports
4x1TB WD green drives