* [gentoo-user] 2.6.9-r1 kernel bug?
@ 2004-12-08 8:34 Arctic Paintball Oy
2004-12-08 10:45 ` Nicolai Guba
2004-12-08 14:50 ` Billy
0 siblings, 2 replies; 4+ messages in thread
From: Arctic Paintball Oy @ 2004-12-08 8:34 UTC (permalink / raw
To: gentoo-user
Couldnt find anything on this googling around. Am I missing something or
is this a bug?
How is it possible to try to read beyond the end of device on the loop
device? Or should i use dd? Is this a bug or are the files damaged. I cant
check the old contents any longer so md5sum is not an option.
To bad this packaging is totaly idiotic (i mean iso image of bin/cue
;-) ). I was trying to make it a little easier to use without double
packaging
dmesg output:
attempt to access beyond end of device
loop0: rw=0, want=790536, limit=790528
Buffer I/O error on device loop0, logical block 197633
umount temp/
mount image.iso temp/ -t iso9660 -o loop
cp temp/* .
cp: reading `temp/image.bin': Input/output error
cp: reading `temp/image.cue': Input/output error
TIA
Christian
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] 2.6.9-r1 kernel bug?
2004-12-08 8:34 [gentoo-user] 2.6.9-r1 kernel bug? Arctic Paintball Oy
@ 2004-12-08 10:45 ` Nicolai Guba
2004-12-08 11:43 ` Arctic Paintball Oy
2004-12-08 14:50 ` Billy
1 sibling, 1 reply; 4+ messages in thread
From: Nicolai Guba @ 2004-12-08 10:45 UTC (permalink / raw
To: gentoo-user
Arctic Paintball Oy wrote:
> How is it possible to try to read beyond the end of device on the loop
> device? Or should i use dd? Is this a bug or are the files damaged. I cant
> check the old contents any longer so md5sum is not an option.
Hmmm, I had some oddities with LILO too. Similar stuff. I noticed that
just letting it time out and then load the default kernel always works.
However, on selecting it and pressing enter it has problems with the
initrd.
Absolutely no clue what causes this.
This is my first post to this list. So hello everyone :)
--
=NPG=
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] 2.6.9-r1 kernel bug?
2004-12-08 10:45 ` Nicolai Guba
@ 2004-12-08 11:43 ` Arctic Paintball Oy
0 siblings, 0 replies; 4+ messages in thread
From: Arctic Paintball Oy @ 2004-12-08 11:43 UTC (permalink / raw
To: gentoo-user
Ah, my memory doesnt serve too well, this machine has 2.6.8-r3 and that
had some issues with a lot of stuff... Going to upgrade and try again...
Christian
On Wed, 8 Dec 2004, Nicolai Guba wrote:
>
> Hmmm, I had some oddities with LILO too. Similar stuff. I noticed that
> just letting it time out and then load the default kernel always works.
> However, on selecting it and pressing enter it has problems with the
> initrd.
>
> Absolutely no clue what causes this.
>
> This is my first post to this list. So hello everyone :)
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] 2.6.9-r1 kernel bug?
2004-12-08 8:34 [gentoo-user] 2.6.9-r1 kernel bug? Arctic Paintball Oy
2004-12-08 10:45 ` Nicolai Guba
@ 2004-12-08 14:50 ` Billy
1 sibling, 0 replies; 4+ messages in thread
From: Billy @ 2004-12-08 14:50 UTC (permalink / raw
To: gentoo-user
Arctic Paintball Oy wrote:
> umount temp/
> mount image.iso temp/ -t iso9660 -o loop
> cp temp/* .
> cp: reading `temp/image.bin': Input/output error
> cp: reading `temp/image.cue': Input/output error
If this was a torrent download, you may not have a full file. Either
way, it looks like your iso is corrupted.
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-12-08 14:51 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-08 8:34 [gentoo-user] 2.6.9-r1 kernel bug? Arctic Paintball Oy
2004-12-08 10:45 ` Nicolai Guba
2004-12-08 11:43 ` Arctic Paintball Oy
2004-12-08 14:50 ` Billy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox