sechs
Storage? I am Storage!
Upon test by Seatools. one of my 15k.4s returns the result "Self Test Segment 0 Failed." What does this mean?
The long story:
Yesterday, I was making some changes in the case of this computer. Among these was turning over one of drives which had previously been mounted upside down; the upside-down mounting was causing vibrations and noise not commensurate with the additional cooling gained. Although all appeared well, apparently I had left the cable was lose. According to Windows logs, the drive started throwing errors at about 3:00AM, followed by controller errors, and the log stopping abruptly at about 4:30AM. At that point Windows appears to have decided upon a spontaneous reboot.
When I get to the computer in the morning, it is unable to finish starting Windows, as the volume is hopelessly corrupt. The volume is so corrupt, that attempts to mount it lead to crashing and freezing in all attempted operating systems. Thanks to the suck that is Adaptec, I end up converting my test Windows installation on another disk to FAT32, disabling the NTFS filesystem driver, and using that to run chkdsk on the volume. It finds the expected orphan files and bad indexes, but also notes nine sectors added to the volume bitmap as bad. Not a good sign.
After seeing this, I run Seatools, getting the above error. However, I am able to successfully boot the copy of Windows on the volume with no apparent issues. The system event log notes bad block errors, and the Adaptec Storage Manager shows media error warning, although no SMART errors.
What I am looking at doing now is imaging this drive to my spare, to take its place, and wiping this one with Seatools, and see if that alleviates the errors.
The long story:
Yesterday, I was making some changes in the case of this computer. Among these was turning over one of drives which had previously been mounted upside down; the upside-down mounting was causing vibrations and noise not commensurate with the additional cooling gained. Although all appeared well, apparently I had left the cable was lose. According to Windows logs, the drive started throwing errors at about 3:00AM, followed by controller errors, and the log stopping abruptly at about 4:30AM. At that point Windows appears to have decided upon a spontaneous reboot.
When I get to the computer in the morning, it is unable to finish starting Windows, as the volume is hopelessly corrupt. The volume is so corrupt, that attempts to mount it lead to crashing and freezing in all attempted operating systems. Thanks to the suck that is Adaptec, I end up converting my test Windows installation on another disk to FAT32, disabling the NTFS filesystem driver, and using that to run chkdsk on the volume. It finds the expected orphan files and bad indexes, but also notes nine sectors added to the volume bitmap as bad. Not a good sign.
After seeing this, I run Seatools, getting the above error. However, I am able to successfully boot the copy of Windows on the volume with no apparent issues. The system event log notes bad block errors, and the Adaptec Storage Manager shows media error warning, although no SMART errors.
What I am looking at doing now is imaging this drive to my spare, to take its place, and wiping this one with Seatools, and see if that alleviates the errors.
