Prev: Why's this look like gibberish to me?
Next: sound?
From: Dexter Filmore on 4 May 2008 19:00
Am Sonntag, 4. Mai 2008 14:49:19 schrieb martin f krafft:
> also sprach Dexter Filmore <Dexter.Filmore(a)gmx.de> [2008.05.03.1723 +0100]:
> > initrd has its own log...?
>
> No, it just prints to the console.
>
> I suggest you add break=bottom to the kernel command line (and
> remove the raid=noautodetect, which you don't need) and then reboot,
> inspect the console output and tell us what it says.
>
> You can exit the shell to continue the boot.

Well, it works now that I switched to assembling from rcS.d and I really don't
wanna degrade the array on purpose again. The error message loosk like in the
dmesg output I posted in reply to your first answer.

Dex


--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.vorratsdatenspeicherung.de


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Dexter Filmore on 4 May 2008 19:10
Am Freitag, 2. Mai 2008 22:47:07 schrieb Alex Samad:
> On Fri, May 02, 2008 at 02:45:04PM +0200, Dexter Filmore wrote:
> > So here's the story:
>
> [snip]
>
> > Now: what's going on here? both onboard 3114 and pci 3114 controllers are
> > handled by the same kernel module, so either initrd sees all or none.
> > Why would it not wanna see the 5th disk from initrd, but when I manually
> > assemble, it's fine?
> >
> > Dex
>
> Used to have a similar problem.
>
> look in /etc/mdadm/mdadm.conf make sure the arrays is defined properly
> in there also make sure you have
> DEVICE partitions
>
> or at least have it pointing to all the right devices/partitions
>
> then update your initramfs
>
> from memory the problem i had was I had not fully specified my array in
> /etc/mdadm/mdadm.conf. Another way to put it they array information in
> the initram fs was from an old array specification and only part of the
> array would get started.

Array info was all fine.
I had an issue with 2.6.18 that it wouldn't see all partitions, I fixed that
by going 2.6.22 (and yes, I fixed the shutdown issue with hddown).

>
> another thing you can try is entering busybox during the initrd process
> just before it starts/load /
>

How exactly do I enter Busybox?


--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.vorratsdatenspeicherung.de


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Alex Samad on 5 May 2008 01:50
On Mon, May 05, 2008 at 12:59:52AM +0200, Dexter Filmore wrote:
> Am Freitag, 2. Mai 2008 22:47:07 schrieb Alex Samad:
> > On Fri, May 02, 2008 at 02:45:04PM +0200, Dexter Filmore wrote:
> > > So here's the story:
> >
> > [snip]
>
> >
> > another thing you can try is entering busybox during the initrd process
> > just before it starts/load /
> >
>
> How exactly do I enter Busybox?

been a while, but I think it is an option on the console as it comes up

>
>
> --
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.12
> GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
> w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
> b++(+++) DI+++ D- G++ e* h>++ r* y?
> ------END GEEK CODE BLOCK------
>
> http://www.vorratsdatenspeicherung.de
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
>
>

--
"But all in all, it's been a fabulous year for Laura and me."

- George W. Bush
12/20/2001
Washington, DC
summing up his first year in office, three months after the 9/11 attacks
 | 
Pages: 1
Prev: Why's this look like gibberish to me?
Next: sound?