[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#520923: marked as done (live-initramfs: booting with a bad disk in the system takes forever)

Your message dated Mon, 15 Jun 2009 11:14:50 +0200
with message-id <4A36110A.4050900@debian.org>
and subject line Re: live-initramfs: booting with a bad disk in the system takes forever
has caused the Debian Bug report #520923,
regarding live-initramfs: booting with a bad disk in the system takes forever
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
520923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520923
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: live-initramfs
Severity: normal


The initramfs scripts cause Linux to read quite a few sectors from disk
repeatedly. As a result the boot sequence is _very_ long if a disk is
bad and returns I/O errors with delay.


-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.28-macmini (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
Hi,

first, in the case that you have a disk where you don't know that it's
broken, there's nothing we can do about it.

second, in the case where you know which disk is broken, you can either
boot with frommedia so that live-initramfs searches for the rootfs on a
particular device (a non broken one :).

third, if you don't use persistency, you can boot with nopersistent in
order to avoid accessing other devices than the device where the rootfs
lies.

Summarizing: there's nothing to do about it in live-initramfs, therefore
closing this bug.

Regards,
Daniel

-- 
Address:        Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:          daniel.baumann@panthera-systems.net
Internet:       http://people.panthera-systems.net/~daniel-baumann/

--- End Message ---
Reply to: