Messages in this thread | | | Date | Fri, 03 Mar 2000 20:36:07 -0800 | From | "Jack (Butch) Griffin" <> | Subject | Re: Maxtor 40 gig troubles |
| |
I had all kind of troubles with this drive. When I created a linux partition much greater than 8 gybtes, it would need to fsck and would find errors every time I booted. Also, I could not get lilo to boot properly with these drives, but I think that was a combination of my BIOS and the drive. There were quite a few different versions of the geometry floating around between the BIOS, linux, DOS, and lilo.
Finally I got a SCSI drive and I boot from the SCSI. I have added hda=4980,255,634 hdb=4980,255,63 to my kernel command line (via lilo). By forcing this geometry, I am now able to partition the entire disk as a single partition and use it that way. I also have had two 20 GByte partitoins as well and they work great too.
The SCSI works so much faster though that I bought a second SCSI and just use the two SCSI drives now :)
Thanks Jack (Butch) Griffin
----- Original Message ----- From: "Guest section DW" <dwguest@win.tue.nl> To: "Bernhard Dobbels" <Bernhard@dobbels.com>; <linux-kernel@vger.rutgers.edu> Sent: Friday, March 03, 2000 5:08 PM Subject: Re: Maxtor 40 gig troubles
> On Fri, Mar 03, 2000 at 04:52:36PM +0100, Bernhard Dobbels wrote: > > > In short: i can mount all my partitions exept the last one, and i'm wandering > > if i had some kind of a diskcrash, because yesterday everything was fine. > > It could be that it's a bug in the IDE driver also, so i post it here. > > > > Just bought my new Maxtor yesterday. I had to flash my bios, and upgrade to > > kernel 2.2.14. Everything fine. The disk worked also perfect, all of it. > > > > To day i had to reset after a memory-halt (bad apacer memory). > > Now my disk gives errors. I did some test to give more information. First i > > thought my partitiontable was broken, but now i suspect a diskcrash: > > > > _e2fsck_: > > root@Viking:/root$ e2fsck /dev/hdb17 > > e2fsck 1.12, 9-Jul-98 for EXT2 FS 0.5b, 95/08/09 > > hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } > > hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=72694127, sector=2 > > end_request: I/O error, dev 03:51 (hdb), sector 2 > > > > Then i wanted to read the first sector of /dev/hdb17 to see if i could repair > > it, but i couldn't read it. Then i teste from where on i couldn't read it > > anymore: > > > > dd if=/dev/hdb of=/dev/null skip=66055247 bs=512 count=1 > > 1+0 records in > > 1+0 records out > > dd if=/dev/hdb of=/dev/null skip=66055248 bs=512 count=1 > > 0+0 records in > > 0+0 records out > > > > $ uname -a > > Linux Viking 2.2.14 #1 SMP Thu Mar 2 08:14:39 CET 2000 i686 unknown > > > > Any information if this could be a hardware problem would be nice. > > Funny - the first problem occurs almost precisely at the 65536*16*63 > boundary (namely, at sector 65531*16*63). > You did not run this Maxtor utility that clips the disk? > > What are the kernel boot messages? ("dmesg | grep hdb") > What does hdparm -i /dev/hdb say? > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.tux.org/lkml/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |