Justin Piszcz wrote:
>
>
> On Thu, 5 Apr 2007, Justin Piszcz wrote:
>
>> Had a quick question, this is the first time I have seen this happen,
>> and it was not even under during heavy I/O, hardly anything was going
>> on with the box at the time.
>
> .. snip ..
>
> # /usr/bin/time badblocks -b 512 -s -v -w /dev/sdl
> Checking for bad blocks in read-write mode
> From block 0 to 293046768
> Testing with pattern 0xaa: done
> Reading and comparing: done
>
> Not a single bad block on the drive so far. I have not changed anything
> the box physically, with the exception of the BIOS version to V1666 for
> an Intel P965 motherboard (DG965WHMKR). Any idea what or why this
> happened? Is it a kernel or actual HW issue? What caused this to
> occur? Any thoughts or ideas?
My bet is on harddisk firmware acting weird. You can prove this by
reconnecting the disk to known working port without cutting power. Or,
you can prove that the original port works by removing the harddisk and
putting a different one. You'll need to issue manual scan using SCSI
sysfs node. It's very rare but some drives do choke like that.
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
