RE: Reading beyond the end of drive again - solution

2003-10-10 Thread Sergey Melikhov
Just to have the solution in the archive:

Earlier this month I wrote about Linux reading beyond
the end of the disk partition:

QUOTE
root l440gx /]# dd bs=10k skip=1200 of=/dev/null
if=/dev/hdg1
dd: reading `/dev/hdg1': Input/output error
5371+1 records in
5371+1 records out

There were errors in /var/log/messages as well:
Oct  5 21:10:28 localhost kernel: attempt to access
beyond end of device
Oct  5 21:10:28 localhost kernel: 22:01: rw=0,
want=120053716, limit=120053713
Oct  5 21:10:28 localhost kernel: attempt to access
beyond end of device
Oct  5 21:10:28 localhost kernel: 22:01: rw=0,
want=120053716, limit=120053713

END OF QUOTE.

The problem was with the drive. It was initially used
with Windows XP, before being installed in Linux
machine. Windows wrote something on it, so the disk
was reporting wrong (well, _different_ from what
Maxtor thinks it should be) geometry to Linux. 

Solution was to low-level format the drive. If one has
MBR expertize, he/she can try first to clean MBR to
save time.

Thanks,

 Sergey 


__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list


Reading beyond the end of drive again

2003-10-05 Thread Sergey Melikhov
Hello to the List Members!

I was searching the Internet (and this list) for a
while, and found many people with similar symptoms. I
could find no satisfactory solutions to their
problems, though. So, I decided to ask here. 

I've got a RedHat 9.0 SMP system (L440GX motherboard,
2x650 Pentium III, 1GB RAM). There are two SCSI disk
drives and two IDE disk drives (connected to a Promise
ATA-100 card). 

Linux l440gx 2.4.20-20.9smp #1 SMP Mon Aug 18 11:32:15
EDT 2003 i686 i686 i386 GNU/Linux

The following is the fdisk -l output for the disk
drive in question (MAXTOR 120GB):

Disk /dev/hdg: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
 
   Device BootStart   EndBlocks   Id 
System
/dev/hdg1   1 14946 120053713+  83  Linux
 
Here is my problem. System worked OK for a while
(several months).  Recently, I found the file system
re-mounted read-only, and the following messages in
the syslog:

Sep 29 05:04:46 localhost kernel: hdg: dma_intr:
status=0x51 { DriveReady SeekComplete Error }
Sep 29 05:04:46 localhost kernel: hdg: dma_intr:
error=0x40 { UncorrectableError }, LBAsect=20793,
sector=20728
Sep 29 05:04:46 localhost kernel: end_request: I/O
error, dev 22:01 (hdg), sector 20728
Sep 29 05:04:46 localhost kernel:
journal_bmap_Rsmp_514801a1: journal block not found at
offset 2060 on ide3(34,1)
Sep 29 05:04:46 localhost kernel: Aborting journal on
device ide3(34,1).
Sep 29 05:04:46 localhost kernel: ext3_abort called.
Sep 29 05:04:46 localhost kernel: EXT3-fs abort
(device ide3(34,1)): ext3_journal_start: Detected
aborted journal
Sep 29 05:04:46 localhost kernel: Remounting
filesystem read-only

I booted from a floppy, and ran Maxtor's diagnostic
program (full scan) - no problems detected.

I ran 'badblocks' as well, on /dev/hdg, and it went
OK.

I successfully read the whole drive (

Then I tried to read /dev/hdg1 (the partition) with
dd, and got an error (this example skips most of the
drive, but when I read the whole drive, result is the
same)

[EMAIL PROTECTED] /]# dd bs=10k skip=1200 of=/dev/null
if=/dev/hdg1
dd: reading `/dev/hdg1': Input/output error
5371+1 records in
5371+1 records out

There were errors in /var/log/messages as well:
Oct  5 21:10:28 localhost kernel: attempt to access
beyond end of device
Oct  5 21:10:28 localhost kernel: 22:01: rw=0,
want=120053716, limit=120053713
Oct  5 21:10:28 localhost kernel: attempt to access
beyond end of device
Oct  5 21:10:28 localhost kernel: 22:01: rw=0,
want=120053716, limit=120053713

This condition is 100% reproduceable. This condition
does not exist on the second IDE drive, nor on any of
SCSI drives. 

I have tried the following:

* Create smaller partition (as small as 100MB in the
beginning of the drive) - the same error, dd tried to
read beyond of the partition.

Disk /dev/hdg: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
 
   Device BootStart   EndBlocks   Id 
System
/dev/hdg1 113104391   83 
Linux

Oct  5 21:16:23 localhost kernel: attempt to access
beyond end of device
Oct  5 21:16:23 localhost kernel: 22:01: rw=0,
want=104392, limit=104391
Oct  5 21:16:23 localhost kernel: attempt to access
beyond end of device
Oct  5 21:16:23 localhost kernel: 22:01: rw=0,
want=104392, limit=104391

* Fill the beginning of the drive with zeroes and
re-create partition table - no help either.

I don't know what to think in this situation. I don't
know I have this problem from the very beginning (and
just noticed it when the disk got filled up), or
something broke recently. I don't know if this is a
disk or RedHat problem.

Before I start trying different kernels, I would like
to know your opinion.

Any Help Would Be Greatly Appreciated !!!


Sincerely yours,

  Sergey 

__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list