SEO

Hi all!

quick recap. Two nights ago I started a Gentoo install, stage 1. The
bootstrap hadn't finished prior to my going to sleep. When I woke up, I
found I received an IOError. So yesterday, with nothing better to do than
watch the Leafs get pummeled (sp?) by the Devils, I decided to start from
scratch. Complete new reboot, delete the partitions, etc.

I'm running a P4 1.6 Ghz Gigabyte motherboard with 512 MB RDRAM. The hard
drive is the second HD in my system (first is Windows XP Pro), a 60 GB
Maxtor (probably 7200 rpm). And I have a Sympatico ADSL connection (High
speed, not Ultra high speed for anybody who knows). I have not overclocked
the chipset.

I partitioned:
hdb1 100M ext3,
hdb2 1024M swap
hdb3 the rest reiserfs

Good news is that it made it through the bootstrap in about 3 hours (6:30
pm - 9:30). The mirror site that was being used was OregonState.

So I started the next step in the instructions, and got to the "emerge
system" step. And I let it run. When I woke up this morning this error was
on my screen (about last 20 lines). Please excuse typos, this is a screen
to paper to screen process.
--------------------------
emerge system
.......
<<< obj /usr/lib/libopcodes-2.13.90.0.18.so
--- !mtime obj /usr/lib/libiberty.a
--- !mtime obj /usr/lib/libbfd.la
--- !mtime obj /usr/lib/libbfd.a
hdb: dma-intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma-intr: status=0x40 { UncorrectableError } LBAsect=2320860, sector
103872
end_request: I/O error, dev 3:43 (hdb), sector 103872
Traceback (most recent call last):
FILE "/usr/bin/emerge", line 1603 in unmerge
retval=portage.unmerge(mysplit[0], mysplit[1], portage.root,
unmerge_action not in ["clean","prune"])
FILE "/usr/lib/python2.2/site-packages/python.py" line 1960, in unmerge
mylink.unmerge(trimworld=mytrimworld)
FILE "/usr/lib/python2.2/site-packages/python.py" line 4469, in unmerge
mymd5=perform_md5(obj, calc_prelink=1)
FILE "/usr/lib/python2.2/site-packages/python.py" line 1951, in perform_md5
return perform_checksum(x,calc_prelink)[0]
FILE "/usr/lib/python2.2/site-packages/python.py" line 205, in
perform_checksum
return fchksum.fmd5t(filename)
IOError; [Errno 5] Input/output error: '/usr/lib/libbfd-2.13.90.0.18.so'
-------------------------------

It left me at the "cdimage portage #" prompt. An adsl-status run at this
point produced the following error:
bash adsl-status: command not found.

It seems to me the error is reporting bad sectors on the hard drive? I
could be wrong, of course. If so, please let me know.

So I have two questions. First, are there any tools that I can use to mark
bad sectors as unusable? Second, how do I start my adsl session again, and
then commence from the beginning of stage 2?

Any other comments/insights greatly appreciated.

cheers,
Matt.

A google showed me this:

I then took out SiS5513 support (CONFIG_BLK_DEV_SIS5513),

I don't know how to do this. If anyone thinks it's relevant, please let me
know.

cheers,
Matt.


"Matt." <matt_benvenuti_remove@hotmail.com> wrote in message
news:KhRjb.10198$PM2.1215688@news20.bellglobal.com ...
> Hi all!
>
> quick recap. Two nights ago I started a Gentoo install, stage 1. The
> bootstrap hadn't finished prior to my going to sleep. When I woke up, I
> found I received an IOError. So yesterday, with nothing better to do than
> watch the Leafs get pummeled (sp?) by the Devils, I decided to start from
> scratch. Complete new reboot, delete the partitions, etc.
>
> I'm running a P4 1.6 Ghz Gigabyte motherboard with 512 MB RDRAM. The hard
> drive is the second HD in my system (first is Windows XP Pro), a 60 GB
> Maxtor (probably 7200 rpm). And I have a Sympatico ADSL connection (High
> speed, not Ultra high speed for anybody who knows). I have not
overclocked
> the chipset.
>
> I partitioned:
> hdb1 100M ext3,
> hdb2 1024M swap
> hdb3 the rest reiserfs
>
> Good news is that it made it through the bootstrap in about 3 hours (6:30
> pm - 9:30). The mirror site that was being used was OregonState.
>
> So I started the next step in the instructions, and got to the "emerge
> system" step. And I let it run. When I woke up this morning this error
was
> on my screen (about last 20 lines). Please excuse typos, this is a screen
> to paper to screen process.
> --------------------------
> emerge system
> ......
> <<< obj /usr/lib/libopcodes-2.13.90.0.18.so
> --- !mtime obj /usr/lib/libiberty.a
> --- !mtime obj /usr/lib/libbfd.la
> --- !mtime obj /usr/lib/libbfd.a
> hdb: dma-intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma-intr: status=0x40 { UncorrectableError } LBAsect=2320860, sector
> 103872
> end_request: I/O error, dev 3:43 (hdb), sector 103872
> Traceback (most recent call last):
> FILE "/usr/bin/emerge", line 1603 in unmerge
> retval=portage.unmerge(mysplit[0], mysplit[1], portage.root,
> unmerge_action not in ["clean","prune"])
> FILE "/usr/lib/python2.2/site-packages/python.py" line 1960, in unmerge
> mylink.unmerge(trimworld=mytrimworld)
> FILE "/usr/lib/python2.2/site-packages/python.py" line 4469, in unmerge
> mymd5=perform_md5(obj, calc_prelink=1)
> FILE "/usr/lib/python2.2/site-packages/python.py" line 1951, in
perform_md5
> return perform_checksum(x,calc_prelink)[0]
> FILE "/usr/lib/python2.2/site-packages/python.py" line 205, in
> perform_checksum
> return fchksum.fmd5t(filename)
> IOError; [Errno 5] Input/output error: '/usr/lib/libbfd-2.13.90.0.18.so'
> -------------------------------
>
> It left me at the "cdimage portage #" prompt. An adsl-status run at this
> point produced the following error:
> bash adsl-status: command not found.
>
> It seems to me the error is reporting bad sectors on the hard drive? I
> could be wrong, of course. If so, please let me know.
>
> So I have two questions. First, are there any tools that I can use to
mark
> bad sectors as unusable? Second, how do I start my adsl session again,
and
> then commence from the beginning of stage 2?
>
> Any other comments/insights greatly appreciated.
>
> cheers,
> Matt.
>
>

On 2003-10-17, Matt. <matt_benvenuti_remove@hotmail.com> wrote:

> hdb: dma-intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma-intr: status=0x40 { UncorrectableError } LBAsect=2320860, sector
> 103872
> end_request: I/O error, dev 3:43 (hdb), sector 103872
> Traceback (most recent call last):
> FILE "/usr/bin/emerge", line 1603 in unmerge
> retval=portage.unmerge(mysplit[0], mysplit[1], portage.root,
> unmerge_action not in ["clean","prune"])
> FILE "/usr/lib/python2.2/site-packages/python.py" line 1960, in unmerge
> mylink.unmerge(trimworld=mytrimworld)
> FILE "/usr/lib/python2.2/site-packages/python.py" line 4469, in unmerge
> mymd5=perform_md5(obj, calc_prelink=1)
> FILE "/usr/lib/python2.2/site-packages/python.py" line 1951, in perform_md5
> return perform_checksum(x,calc_prelink)[0]
> FILE "/usr/lib/python2.2/site-packages/python.py" line 205, in
> perform_checksum
> return fchksum.fmd5t(filename)
> IOError; [Errno 5] Input/output error: '/usr/lib/libbfd-2.13.90.0.18.so'


Yep, your disk appears to be bad. You're going to want to run
'badblocks /dev/hdb' and see what it reports. It should return a list of
bad blocks.

If there are bad blocks, it's time to get a new disk.

--
Jon Portnoy
avenj/irc.freenode.net #gentoo, irc.oftc.net #cola
Opinions expressed are my own, not those of Gentoo Linux or any
other entity I am associated with unless stated otherwise.

Nooooooooooo!!!!

I've got a bootable Maxtor utility diskette that should let me restore the
disk to "factory greatness". I'll try doing that before trying any warranty
claims.

Thanks again!

cheers,
Matt.


"Jon Portnoy" <avenj@gentoo.org> wrote in message
news:slrnbp0fdp.ruf.jdpNOSPAM@eris.oppresses.us...
> On 2003-10-17, Matt. <matt_benvenuti_remove@hotmail.com> wrote:
>
> > hdb: dma-intr: status=0x51 { DriveReady SeekComplete Error }
> > hdb: dma-intr: status=0x40 { UncorrectableError } LBAsect=2320860,
sector
> > 103872
> > end_request: I/O error, dev 3:43 (hdb), sector 103872
> > Traceback (most recent call last):
> > FILE "/usr/bin/emerge", line 1603 in unmerge
> > retval=portage.unmerge(mysplit[0], mysplit[1], portage.root,
> > unmerge_action not in ["clean","prune"])
> > FILE "/usr/lib/python2.2/site-packages/python.py" line 1960, in unmerge
> > mylink.unmerge(trimworld=mytrimworld)
> > FILE "/usr/lib/python2.2/site-packages/python.py" line 4469, in unmerge
> > mymd5=perform_md5(obj, calc_prelink=1)
> > FILE "/usr/lib/python2.2/site-packages/python.py" line 1951, in
perform_md5
> > return perform_checksum(x,calc_prelink)[0]
> > FILE "/usr/lib/python2.2/site-packages/python.py" line 205, in
> > perform_checksum
> > return fchksum.fmd5t(filename)
> > IOError; [Errno 5] Input/output error: '/usr/lib/libbfd-2.13.90.0.18.so'
>
>
> Yep, your disk appears to be bad. You're going to want to run
> 'badblocks /dev/hdb' and see what it reports. It should return a list of
> bad blocks.
>
> If there are bad blocks, it's time to get a new disk.
>
> --
> Jon Portnoy
> avenj/irc.freenode.net #gentoo, irc.oftc.net #cola
> Opinions expressed are my own, not those of Gentoo Linux or any
> other entity I am associated with unless stated otherwise.

Yes, but if it's broken now, it'll still be broken. The Utility may do
something to make it look fixed - and it may be to some extent. However,
if the disk is getting bad blocks now , it will continue to do so. Replace
it now while you don't have data, etc. that you need.

Matt. wrote:

> Nooooooooooo!!!!
>
> I've got a bootable Maxtor utility diskette that should let me restore the
> disk to "factory greatness". I'll try doing that before trying any
> warranty claims.
>
> Thanks again!
>
> cheers,
> Matt.
>
>
> "Jon Portnoy" <avenj@gentoo.org> wrote in message
> news:slrnbp0fdp.ruf.jdpNOSPAM@eris.oppresses.us...
>> On 2003-10-17, Matt. <matt_benvenuti_remove@hotmail.com> wrote:
>>
>> > hdb: dma-intr: status=0x51 { DriveReady SeekComplete Error }
>> > hdb: dma-intr: status=0x40 { UncorrectableError } LBAsect=2320860,
> sector
>> > 103872
>> > end_request: I/O error, dev 3:43 (hdb), sector 103872
>> > Traceback (most recent call last):
>> > FILE "/usr/bin/emerge", line 1603 in unmerge
>> > retval=portage.unmerge(mysplit[0], mysplit[1], portage.root,
>> > unmerge_action not in ["clean","prune"])
>> > FILE "/usr/lib/python2.2/site-packages/python.py" line 1960, in unmerge
>> > mylink.unmerge(trimworld=mytrimworld)
>> > FILE "/usr/lib/python2.2/site-packages/python.py" line 4469, in unmerge
>> > mymd5=perform_md5(obj, calc_prelink=1)
>> > FILE "/usr/lib/python2.2/site-packages/python.py" line 1951, in
> perform_md5
>> > return perform_checksum(x,calc_prelink)[0]
>> > FILE "/usr/lib/python2.2/site-packages/python.py" line 205, in
>> > perform_checksum
>> > return fchksum.fmd5t(filename)
>> > IOError; [Errno 5] Input/output error:
>> > '/usr/lib/libbfd-2.13.90.0.18.so'
>>
>>
>> Yep, your disk appears to be bad. You're going to want to run
>> 'badblocks /dev/hdb' and see what it reports. It should return a list of
>> bad blocks.
>>
>> If there are bad blocks, it's time to get a new disk.
>>
>> --
>> Jon Portnoy
>> avenj/irc.freenode.net #gentoo, irc.oftc.net #cola
>> Opinions expressed are my own, not those of Gentoo Linux or any
>> other entity I am associated with unless stated otherwise.

--
Brett I. Holcomb
brettholcomb@R777charter.net
AKA Grunt <><
Registered Linux User #188143
Remove R777 to email

I recently had a HD go down. (Seagate IDE 8Mb)

I used PQ's Lost and Found to get copies of my win partition but it
could not access my ext3 partition.

Subsequently I used the excellent Seatools utility , free from the
SeaGate.com site . There is a linux file to create the needed floppy
image. This tool will detect bad sectors non-destructivly , so you get
a clear idea of the state of your disk. It will get the disk firmware
to reallocate sectors to extra free sectors to recover a fully working
disk.

This second function it can only do for SeaGate disks so see if your
manufacturer has a similar utility.

HTH


Jon Portnoy <avenj@gentoo.org> wrote in message news:<slrnbp0fdp.ruf.jdpNOSPAM@eris.oppresses.us>. ..
> On 2003-10-17, Matt. <matt_benvenuti_remove@hotmail.com> wrote:
>
> > hdb: dma-intr: status=0x51 { DriveReady SeekComplete Error }
> > hdb: dma-intr: status=0x40 { UncorrectableError } LBAsect=2320860, sector
> > 103872
> > end_request: I/O error, dev 3:43 (hdb), sector 103872
> > Traceback (most recent call last):
> > FILE "/usr/bin/emerge", line 1603 in unmerge
> > retval=portage.unmerge(mysplit[0], mysplit[1], portage.root,
> > unmerge_action not in ["clean","prune"])
> > FILE "/usr/lib/python2.2/site-packages/python.py" line 1960, in unmerge
> > mylink.unmerge(trimworld=mytrimworld)
> > FILE "/usr/lib/python2.2/site-packages/python.py" line 4469, in unmerge
> > mymd5=perform_md5(obj, calc_prelink=1)
> > FILE "/usr/lib/python2.2/site-packages/python.py" line 1951, in perform_md5
> > return perform_checksum(x,calc_prelink)[0]
> > FILE "/usr/lib/python2.2/site-packages/python.py" line 205, in
> > perform_checksum
> > return fchksum.fmd5t(filename)
> > IOError; [Errno 5] Input/output error: '/usr/lib/libbfd-2.13.90.0.18.so'
>
>
> Yep, your disk appears to be bad. You're going to want to run
> 'badblocks /dev/hdb' and see what it reports. It should return a list of
> bad blocks.
>
> If there are bad blocks, it's time to get a new disk.

"Matt." <matt_benvenuti_remove@hotmail.com> wrote in message
news:KhRjb.10198$PM2.1215688@news20.bellglobal.com ...
> Hi all!
>
> quick recap. Two nights ago I started a Gentoo install, stage 1. The
> bootstrap hadn't finished prior to my going to sleep. When I woke up, I
> found I received an IOError. So yesterday, with nothing better to do than
> watch the Leafs get pummeled (sp?) by the Devils, I decided to start from
> scratch. Complete new reboot, delete the partitions, etc.
>
> I'm running a P4 1.6 Ghz Gigabyte motherboard with 512 MB RDRAM. The hard
> drive is the second HD in my system (first is Windows XP Pro), a 60 GB
> Maxtor (probably 7200 rpm). And I have a Sympatico ADSL connection (High
> speed, not Ultra high speed for anybody who knows). I have not
overclocked
> the chipset.
>
> I partitioned:
> hdb1 100M ext3,
> hdb2 1024M swap
> hdb3 the rest reiserfs
>
> Good news is that it made it through the bootstrap in about 3 hours (6:30
> pm - 9:30). The mirror site that was being used was OregonState.
>
> So I started the next step in the instructions, and got to the "emerge
> system" step. And I let it run. When I woke up this morning this error
was
> on my screen (about last 20 lines). Please excuse typos, this is a screen
> to paper to screen process.
> --------------------------
> emerge system
> ......
> <<< obj /usr/lib/libopcodes-2.13.90.0.18.so
> --- !mtime obj /usr/lib/libiberty.a
> --- !mtime obj /usr/lib/libbfd.la
> --- !mtime obj /usr/lib/libbfd.a
> hdb: dma-intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma-intr: status=0x40 { UncorrectableError } LBAsect=2320860, sector
> 103872
> end_request: I/O error, dev 3:43 (hdb), sector 103872
> Traceback (most recent call last):
> FILE "/usr/bin/emerge", line 1603 in unmerge
> retval=portage.unmerge(mysplit[0], mysplit[1], portage.root,
> unmerge_action not in ["clean","prune"])
> FILE "/usr/lib/python2.2/site-packages/python.py" line 1960, in unmerge
> mylink.unmerge(trimworld=mytrimworld)
> FILE "/usr/lib/python2.2/site-packages/python.py" line 4469, in unmerge
> mymd5=perform_md5(obj, calc_prelink=1)
> FILE "/usr/lib/python2.2/site-packages/python.py" line 1951, in
perform_md5
> return perform_checksum(x,calc_prelink)[0]
> FILE "/usr/lib/python2.2/site-packages/python.py" line 205, in
> perform_checksum
> return fchksum.fmd5t(filename)
> IOError; [Errno 5] Input/output error: '/usr/lib/libbfd-2.13.90.0.18.so'
> -------------------------------
>
> It left me at the "cdimage portage #" prompt. An adsl-status run at this
> point produced the following error:
> bash adsl-status: command not found.
>
> It seems to me the error is reporting bad sectors on the hard drive? I
> could be wrong, of course. If so, please let me know.
>
> So I have two questions. First, are there any tools that I can use to
mark
> bad sectors as unusable? Second, how do I start my adsl session again,
and
> then commence from the beginning of stage 2?
>
> Any other comments/insights greatly appreciated.
>
> cheers,
> Matt.
>
>

I case anybody is still interested, the drive was determined to be
defective, and has been returned to Maxtor as it was still under warranty.
I expect a replacement in about 2 weeks or so.

cheers,
Matt.