On Fri, May 22, 2009 at 09:10:01AM -0700, Tony Godshall wrote:
> On Fri, May 22, 2009 at 3:43 AM, Andrew Robert Nicols
> wrote:
> > For the record, I'm seeing exactly the same thing too here. I'm booting off
> > a pendrive with the debian installer on it so the pen-drive is clearly
> > being recog
On Fri, May 22, 2009 at 3:43 AM, Andrew Robert Nicols
wrote:
> On Wed, May 20, 2009 at 09:04:38AM -0700, Tony Godshall wrote:
>> Reboot with USB stick plugged in: now I get a long pause immediately
>> after "md: raid1 personality registered for level 1"
>>
>> I look in dmesg for a usb-storage devi
On Wed, May 20, 2009 at 09:04:38AM -0700, Tony Godshall wrote:
> Reboot with USB stick plugged in: now I get a long pause immediately
> after "md: raid1 personality registered for level 1"
>
> I look in dmesg for a usb-storage device: nothing. I look for
> /dev/sd[a-z]*: nothing
>
> So I can't m
On Wed, May 20, 2009 at 8:48 AM, Tony Godshall wrote:
> [me]
> ...
>>> Perhaps if I could figure out how to grab the dmesg output from
>>> initramfs environment, I could then compare the amd64 kernel
>>> output to the 686-bigmem kernel output... :-/
>
> [martin f krafft]
>> Append 'break=bottom de
[me]
...
>> Perhaps if I could figure out how to grab the dmesg output from
>> initramfs environment, I could then compare the amd64 kernel
>> output to the 686-bigmem kernel output... :-/
[martin f krafft]
> Append 'break=bottom debug' to the kernel line and at the shell do
> something like
>
>
also sprach Tony Godshall [2009.05.12.2003 +0200]:
> Yes, I see that it's optional, and actually rather pointless in my
> case since I'm booting off the RAID partition, unless grub reads
> mdadm.conf . But grub only reads /boot, not /etc, right? /etc
> would not be available until /etc/fstab is
On Tue, May 12, 2009 at 9:11 AM, martin f krafft wrote:
> also sprach Tony Godshall [2009.05.11.2058 +0200]:
>> They are *not*. That would seem to be the nub of the problem. No
>> base partitions, thus no RAID. Good, thanks, that's progress. Might
>> be good for md to report that that a littl
also sprach Tony Godshall [2009.05.11.2058 +0200]:
> They are *not*. That would seem to be the nub of the problem. No
> base partitions, thus no RAID. Good, thanks, that's progress. Might
> be good for md to report that that a little better (see screenshot).
> Oh, duh, I moved /etc/mdadm/mdadm
...
> Sorry. We got off on a bad start. I'll review your stuff tomorrow
> and then let's start afresh.
OK
> By the time you get dumped into the busybox prompt during initramfs
> time, are /dev/sd[abcd] present?
They are *not*. That would seem to be the nub of the problem. No
base partitions, t
On Mon, May 11, 2009 at 9:55 AM, martin f krafft wrote:
> also sprach Tony Godshall [2009.05.11.1843 +0200]:
>> I filed the report because I want to see Debian work great on all
>> configurations, with all CPUs, with all RAID configurations, off the
>> bat, without tweaking. And I'm trying to do
also sprach Tony Godshall [2009.05.11.1843 +0200]:
> I filed the report because I want to see Debian work great on all
> configurations, with all CPUs, with all RAID configurations, off the
> bat, without tweaking. And I'm trying to do what small part I can.
> With the limited access to the equip
Did I say I was looking for help?
As I said before, I am fine running with a 32 bit kernel.
I filed the report because I want to see Debian work great on all
configurations, with all CPUs, with all RAID configurations, off the
bat, without tweaking. And I'm trying to do what small part I can.
Wi
also sprach Tony Godshall [2009.05.11.1819 +0200]:
> > retitle 526525 amd64 kernel cannot find bnx2 PCI device base address
>
> Um. BNX2 is the network card? WTF does it have to do with being able
> to mount and boot off RAID in 64-bit mode only?
I don't know, but your attitude does not make m
On Sat, May 9, 2009 at 12:35 AM, martin f krafft wrote:
> retitle 526525 amd64 kernel cannot find bnx2 PCI device base address
Um. BNX2 is the network card? WTF does it have to do with being able
to mount and boot off RAID in 64-bit mode only?
> also sprach Tony Godshall [2009.05.09.0117 +020
retitle 526525 amd64 kernel cannot find bnx2 PCI device base address
thanks
also sprach Tony Godshall [2009.05.09.0117 +0200]:
> > If you cannot boot, append break=mount to the kernel line, and at
> > the initramfs prompt, type
> >
> > rm /etc/mdadm/mdadm.conf
> > /scripts/local-top/mdadm
> >
On Fri, May 8, 2009 at 12:45 AM, martin f krafft wrote:
> also sprach Tony Godshall [2009.05.08.0055 +0200]:
>> bnx2 :01:00.1: Cannot find PCI device base address, aborting.
>> mptbase: ioc0: ERROR - : ERROR - Unable to map adapter memory!
>> mptbase: ioc1: ERROR - : ERROR - Unable to map ada
also sprach Tony Godshall [2009.05.08.0055 +0200]:
> bnx2 :01:00.1: Cannot find PCI device base address, aborting.
> mptbase: ioc0: ERROR - : ERROR - Unable to map adapter memory!
> mptbase: ioc1: ERROR - : ERROR - Unable to map adapter memory!
> mdadm: No devices listed in conf file were foun
Ah, I guess you refer to bug 433905. Trying your suggestions.
rootdelay=10 does not help. Neither does rootdelay=30
Other interesting things:
bnx2 :01:00.1: Cannot find PCI device base address, aborting.
mptbase: ioc0: ERROR - : ERROR - Unable to map adapter memory!
mptbase: ioc1: ERROR - :
On Fri, May 01, 2009 at 11:22:47AM -0700, Tony Godshall wrote:
> Package: linux-image-2.6.26-2-amd64
> Version: 2.6.26-15
> Severity: important
>
>
>
> Kernel from linux-image-2.6.26-2-amd64 does not see
> root RAID device /dev/md0 so boot sequence drops
> busybox shell. 2.6.26-2-686-bigmem and
Package: linux-image-2.6.26-2-amd64
Version: 2.6.26-15
Severity: important
Kernel from linux-image-2.6.26-2-amd64 does not see
root RAID device /dev/md0 so boot sequence drops
busybox shell. 2.6.26-2-686-bigmem and 2.6.26-2-686
work properly.
This is after an install with no issues from the st
20 matches
Mail list logo
