> I have encountered some really strange oddities with
> my two-year-old FUJITSU MPB3032ATU 3,2Gb ide-drive.
>
> Kernel? Which version?
Sorry for the inconvenience. Iīm using 2.2.10.
> This disk has jumpers.
> The default is 6704/15/63 but you can jumper it to 4092/16/63,
> as you probably did. The jumper settings are:
Nope. I jumpered it to 1.., just like the documentation proposes.
122
> How do you start Linux? (From Windows? From a cold machine?)
I use īloadlinī and added a menu-entry to "config.sys".
But even if I use a so-called "rescue-disk" from my
distribution kit (2.2.10, too) and start with a cold
machine, the results are the same.
> What are the kernel boot messages? (dmesg | grep hdc)
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hdc: FUJITSU MPB3032ATU, ATA DISK drive
hdc: FUJITSU MPB3032ATU, 2014MB w/0kB Cache, CHS=4092/16/63, (U)DMA
hdc: hdc1
> (And when you give hdparm output, give both hdparm -i and hdparm -I;
> in some kernel versions the kernel itself fiddles with the hdparm -i
> report, so that it no longer represents what the disk said.)
michael:/home/michael # hdparm -i /dev/hdc
/dev/hdc:
Model=FUJITSU MPB3032ATU, FwRev=2009, SerialNo=01138683
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=4092/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=0(?), BuffSize=0kB, MaxMultSect=16, MultSect=off
DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=0(slow)
CurCHS=4092/16/63, CurSects=4124736, LBA=yes, LBAsects=4124736
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
IORDY=yes, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
Ok, now have a look at this. I donīt know why the "-I"
parameter screws things up like this:
michael:/home/michael # hdparm -I /dev/hdc
/dev/hdc:
Model=UFIJST UPM3B30A2UT , FwRev=0290 ,
SerialNo=
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=4092/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=0(?), BuffSize=0kB, MaxMultSect=16, MultSect=?0?
DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=0(slow)
CurCHS=4364/15/63, CurSects=4123980, LBA=yes, LBAsects=4124736
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
IORDY=yes, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
> Not so pessimistic. You can (i) change the jumpers, or (ii) give the
> kernel explicit boot parameters, or (iii) give fdisk explicit geometry
> parameters.
Ok, I tried the "extra functionality menu" of "fdisk"
with no success.After changing the C/H/S to 6704/15/63,
syncing (and even rebooting) still the same results.
In fact: when "fdisk" has finished changing and syncing and I start it
again, it still says "4092/16/32". Because of this, it is
impossible to use "mke2fs"...
So I suppose that it is some hd-failure (perhaps the drive does not
report is geometry correctly) and so both Linux and Windows
fail. Of course, Linux is smarter than Windows and can use the
drive anyway... (at least if it is formatted with fat32)
Btw: I am using
michael:/home/michael # fdisk -v
fdisk v2.9t
> Andries
CU,
Michael.
-
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/