Newsgroups: nl.comp.os.linux.overig,be.comp.os.linux
Subject: Partitie problemen
Reply-To: Bernhard@kotnet.org
Followup-To: 
Keywords: 
Summary: 

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
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=72694127, sector=2
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=72694127, sector=2
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=72694127, sector=2
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=72694127, sector=2
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=72694127, sector=2
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=72694127, sector=2
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=72694127, sector=2
ide0: reset: success
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
e2fsck: Attempt to read block from filesystem resulted in short read while
trying to open /dev/hdb17
Could this be a zero-length partition?

_fdisk_:
root@Viking:/root$ fdisk /dev/hdb

The number of cylinders for this disk is set to 4982.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Unable to read /dev/hdb


_gpart_:
Part of gpart output of the partitiontable like it is now:
   Logical partition (/dev/hdb15)
      type: 131(0x83)(Linux ext2 filesystem)
      size: 4102mb #s(8401932) s(55890198-64292129)
      chs:  (1023/254/63)-(1023/254/63)d (3479/1/1)-(4001/254/63)r
      hex:  00 FE FF FF 83 FE FF FF 3F 00 00 00 0C 34 80 00

   Logical partition (/dev/hdb16)
      type: 131(0x83)(Linux ext2 filesystem)
      size: 4102mb #s(8401932) s(64292193-72694124)
      chs:  (1023/254/63)-(1023/254/63)d (4002/1/1)-(4524/254/63)r
      hex:  00 FE FF FF 83 FE FF FF 3F 00 00 00 0C 34 80 00

   Logical partition (/dev/hdb17)
 no info?


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=66055240 bs=512 count=1
1+0 records in
1+0 records out
dd if=/dev/hdb of=/dev/null skip=66055241 bs=512 count=1
1+0 records in
1+0 records out
dd if=/dev/hdb of=/dev/null skip=66055242 bs=512 count=1
1+0 records in
1+0 records out
dd if=/dev/hdb of=/dev/null skip=66055243 bs=512 count=1
1+0 records in
1+0 records out
dd if=/dev/hdb of=/dev/null skip=66055244 bs=512 count=1
1+0 records in
1+0 records out
dd if=/dev/hdb of=/dev/null skip=66055245 bs=512 count=1
1+0 records in
1+0 records out
dd if=/dev/hdb of=/dev/null skip=66055246 bs=512 count=1
1+0 records in
1+0 records out
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
dd if=/dev/hdb of=/dev/null skip=66055249 bs=512 count=1
0+0 records in
0+0 records out
dd if=/dev/hdb of=/dev/null skip=66055250 bs=512 count=1
0+0 records in
0+0 records out
dd if=/dev/hdb of=/dev/null skip=66055251 bs=512 count=1
0+0 records in
0+0 records out
dd if=/dev/hdb of=/dev/null skip=66055252 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.

-- 
Bernhard

---- On the requirements it said: Windows 98 or better - so I installed Linux