On 03/24/2009 10:28 PM, Michael Prokop wrote:
[Cc-ing 520...@bugs.debian.org]
* Michal Suchanek<michal.sucha...@ruk.cuni.cz> [20090324 18:53]:
On 03/23/2009 11:28 PM, Michael Prokop wrote:
An approach could be to use bootfrom=.../live-media=... in such a
situation. Michal, does this help? Would be great if you could try
this in your 'I/O error' setup.
I am booting from the network so the drives should not be read to find the
squashfs image, right?
Looking at the source code live-initramfs *shouldn't* be responsible
in this case. Might be some other script like lvm, mdadm,
cryptsetup,.. Do you have LVM, SW-RAID or something like that on
your box?
Unfortunately I cannot reproduce the problem anymore because I have overwritten a part of the disk
and it is not as bad as it used to be.
My guess is that this could be caused by some dm stuff which is standard part of Debian or the
live-initramfs searching for something like squashfs, persistent data or swap.
The bad thing is that Linux diligently retries each block three times (at least it does so for
FUSE), and when a new tool tries to look at the same sector it retries again. The later does happen
because there is about a dozen sectors tried, most of them twice.
As I do not use either the solution for me is probably to weed out dm and
persistence.
Thanks
Michal
--
Michal Suchánek
Univerzita Karlova v Praze
Ǔstav Výpočetní Techniky
Ovocný trh 3
Praha 1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
