Re: UEFI secure boot issue

[Bhasker C V]

On Thu, Jun 20, 2024 at 3:57 PM Jeffrey Walton  wrote:
>
> On Thu, Jun 20, 2024 at 9:23 AM Bhasker C V  wrote:
> >
> > I generated a pr/pk pair and the kernel is signed. Placed them in the
> > kernel tree and compiled the kernel.
>
> I don't think you are supposed to check-in/compile-in the private key.
> It is usually supposed to stay private.
>
> > Could someone tell me what am I doing wrong please ?
> >
> > Below is the status (I am using loader.efi from linuxfoundation)
> > When i boot debian stock kernel signed, i see that the secure boot
> > gets enabled (hence bios and everything else seems to be fine with the
> > same UEFI loader).
> > However, when I boot the compiled kernel I get
> >
> > $ dmesg | grep -i secure
> > [0.007085] Secure boot could not be determined
> >
> >
> > $ sbverify --list bootx64.efi
> > warning: data remaining[91472 vs 101160]: gaps between PE/COFF sections?
> > signature 1
> > image signature issuers:
> >  - /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft
> > Corporation UEFI CA 2011
> > image signature certificates:
> >  - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft
> > Corporation/OU=MOPR/CN=Microsoft Windows UEFI Driver Publisher
> >issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft
> > Corporation/CN=Microsoft Corporation UEFI CA 2011
> >  - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft
> > Corporation/CN=Microsoft Corporation UEFI CA 2011
> >issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft
> > Corporation/CN=Microsoft Corporation Third Party Marketplace Root
> > $ sbverify  --list ./loader.efi
> > signature 1
> > image signature issuers:
> >  - /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
> > image signature certificates:
> >  - subject: /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
> >issuer:  /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
> > $ sbverify  --list ../../linux/k.bcv
> > signature 1
> > image signature issuers:
> >  - /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
> > image signature certificates:
> >  - subject: /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
> >issuer:  /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
>
>
> Have a look at , and the use of
> the Machine Owner Key (MOK).

Thanks Jeff. I did follow this.
Like I had mentioned before, the stock kernel still works in
locked-down mode with secure boot whereas the kernel I have compiled
and signed does not.
Is there a way to debug this on why exactly does this not work ?

>
> Jeff

Re: UEFI secure boot issue

[Jeffrey Walton]

On Thu, Jun 20, 2024 at 9:23 AM Bhasker C V  wrote:
>
> I generated a pr/pk pair and the kernel is signed. Placed them in the
> kernel tree and compiled the kernel.

I don't think you are supposed to check-in/compile-in the private key.
It is usually supposed to stay private.

> Could someone tell me what am I doing wrong please ?
>
> Below is the status (I am using loader.efi from linuxfoundation)
> When i boot debian stock kernel signed, i see that the secure boot
> gets enabled (hence bios and everything else seems to be fine with the
> same UEFI loader).
> However, when I boot the compiled kernel I get
>
> $ dmesg | grep -i secure
> [0.007085] Secure boot could not be determined
>
>
> $ sbverify --list bootx64.efi
> warning: data remaining[91472 vs 101160]: gaps between PE/COFF sections?
> signature 1
> image signature issuers:
>  - /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft
> Corporation UEFI CA 2011
> image signature certificates:
>  - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft
> Corporation/OU=MOPR/CN=Microsoft Windows UEFI Driver Publisher
>issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft
> Corporation/CN=Microsoft Corporation UEFI CA 2011
>  - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft
> Corporation/CN=Microsoft Corporation UEFI CA 2011
>issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft
> Corporation/CN=Microsoft Corporation Third Party Marketplace Root
> $ sbverify  --list ./loader.efi
> signature 1
> image signature issuers:
>  - /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
> image signature certificates:
>  - subject: /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
>issuer:  /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
> $ sbverify  --list ../../linux/k.bcv
> signature 1
> image signature issuers:
>  - /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
> image signature certificates:
>  - subject: /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
>issuer:  /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv


Have a look at , and the use of
the Machine Owner Key (MOK).

Jeff

UEFI secure boot issue

[Bhasker C V]

Hi,

I generated a pr/pk pair and the kernel is signed. Placed them in the
kernel tree and compiled the kernel.


Could someone tell me what am I doing wrong please ?

Below is the status (I am using loader.efi from linuxfoundation)
When i boot debian stock kernel signed, i see that the secure boot
gets enabled (hence bios and everything else seems to be fine with the
same UEFI loader).
However, when I boot the compiled kernel I get

$ dmesg | grep -i secure
[0.007085] Secure boot could not be determined


$ sbverify --list bootx64.efi
warning: data remaining[91472 vs 101160]: gaps between PE/COFF sections?
signature 1
image signature issuers:
 - /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft
Corporation UEFI CA 2011
image signature certificates:
 - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft
Corporation/OU=MOPR/CN=Microsoft Windows UEFI Driver Publisher
   issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft
Corporation/CN=Microsoft Corporation UEFI CA 2011
 - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft
Corporation/CN=Microsoft Corporation UEFI CA 2011
   issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft
Corporation/CN=Microsoft Corporation Third Party Marketplace Root
$ sbverify  --list ./loader.efi
signature 1
image signature issuers:
 - /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
image signature certificates:
 - subject: /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
   issuer:  /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
$ sbverify  --list ../../linux/k.bcv
signature 1
image signature issuers:
 - /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
image signature certificates:
 - subject: /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv
   issuer:  /C=GB/ST=England/L=London/O=BHASKER/CN=bcvm.bcvm.bcv

Re: Boot issue

[Tom Browder]

On Sun, Aug 27, 2023 at 22:51 David Wright  wrote:

> On Sun 27 Aug 2023 at 14:27:09 (-0500), Tom Browder wrote:
> > On Sun, Aug 27, 2023 at 13:27 Greg Wooledge  wrote:
> >
> > > On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> > > > When I boot the system, then the drives are not mounted as set in
> > > /etc/fstab.
> > > > For example, the SDD should mounted to /space, and the unencrypted
> HDD
> >
> > ...
> >
> > > Use UUIDs or Labels instead.  These won't change, while the device
> names
> > > *will* change.
> >
> >
> > Please remind me of when they might change.
>
> As and when the kernel discovers them, ie at boot for those fitted,
> and when you plug them is for any others.
>
> > I'm pretty sure on my latest
> > host the debian installer used /dev/sda (and partions 1 and 2) instead
> of a
> > label or UUID.
>
> It might be possible to mistakenly read /etc/fstab as showing that,
> because of the comment line above the active line:
>
>   #
>   # / was on /dev/sda4 during installation
>   UUID=a1b2c3d4-e5f6-1234-dcba-a1b2c3d4e5f6 /   ext4
> errors=remount-ro 0   1
>   /dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0
>
> BTW I've not seen the d-i use LABELs, I presume because it can't be
> certain that they're always going to be unique.
>
> > Of course I do want to add drives eventually, so maybe I do need to
> change
> > to do that safely.
>
> Some computers can give the user a rude awakening when the kernel
> unexpectedly discovers a plugged-in device before the internal drive.


Ah, it's been awhile. Yes, I see the comments in /etc/fstab.

Thank you for reminding me. Usually I just do "df" and that always shows me
the /dev/sdaX so I forget about looking closer.

Cheers!

-Tom

Re: Boot issue

[David Wright]

On Sun 27 Aug 2023 at 14:27:09 (-0500), Tom Browder wrote:
> On Sun, Aug 27, 2023 at 13:27 Greg Wooledge  wrote:
> 
> > On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> > > When I boot the system, then the drives are not mounted as set in
> > /etc/fstab.
> > > For example, the SDD should mounted to /space, and the unencrypted HDD
> 
> ...
> 
> > Use UUIDs or Labels instead.  These won't change, while the device names
> > *will* change.
> 
> 
> Please remind me of when they might change.

As and when the kernel discovers them, ie at boot for those fitted,
and when you plug them is for any others.

> I'm pretty sure on my latest
> host the debian installer used /dev/sda (and partions 1 and 2) instead of a
> label or UUID.

It might be possible to mistakenly read /etc/fstab as showing that,
because of the comment line above the active line:

  #
  # / was on /dev/sda4 during installation
  UUID=a1b2c3d4-e5f6-1234-dcba-a1b2c3d4e5f6 /   ext4
errors=remount-ro 0   1
  /dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0

BTW I've not seen the d-i use LABELs, I presume because it can't be
certain that they're always going to be unique.

> Of course I do want to add drives eventually, so maybe I do need to change
> to do that safely.

Some computers can give the user a rude awakening when the kernel
unexpectedly discovers a plugged-in device before the internal drive.

Cheers,
David.

Re: Boot issue

[Tom Browder]

On Sun, Aug 27, 2023 at 13:27 Greg Wooledge  wrote:

> On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> > When I boot the system, then the drives are not mounted as set in
> /etc/fstab.
> > For example, the SDD should mounted to /space, and the unencrypted HDD

...

> Use UUIDs or Labels instead.  These won't change, while the device names
> *will* change.


Please remind me of when they might change. I'm pretty sure on my latest
host the debian installer used /dev/sda (and partions 1 and 2) instead of a
label or UUID.

Of course I do want to add drives eventually, so maybe I do need to change
to do that safely.

Thanks.

-Tom

[SOLVED] Re: Boot issue

[Hans]

I am answering myself. It must be the opened UUID. Looks like this problem is 
solved. 

Thank you all for the fast response! I hope, my question was not too annoying.

But I am very very happy, to get this little issue so easily solved - and 
learned something, too.

Thank you all, you made a man happy!

Best regards

Hans

Am Sonntag, 27. August 2023, 21:12:30 CEST schrieb Hans:
> So, now I added all UUIDs. But I am not quite sure for the enrcypted /home
> partition. The UUID changes when the device is luks-opened.
> 
> Which one must be in the fstab? The one from "lsblk -f /dev/sda4" or
> "lsblk -f /dev/mapper/home"?
> 
> Am Sonntag, 27. August 2023, 20:26:46 CEST schrieb Greg Wooledge:
> > On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> > > When I boot the system, then the drives are not mounted as set in
> > > /etc/fstab. For example, the SDD should mounted to /space, and the
> > > unencrypted HDD shall be mounted to /daten.
> > > 
> > > But it seems, sometimes the mountpoints are not correct, so the SDD is
> > > not
> > > mounted to /space, but to /daten.
> > 
> > This sounds like you used the dynamically assigned device names (e.g.
> > /dev/sda1 and so on) in fstab.  If that's what you did, stop doing that.
> > 
> > Use UUIDs or Labels instead.  These won't change, while the device names
> > *will* change.

Re: Boot issue

[Hans]

So, now I added all UUIDs. But I am not quite sure for the enrcypted /home 
partition. The UUID changes when the device is luks-opened.

Which one must be in the fstab? The one from "lsblk -f /dev/sda4" or 
"lsblk -f /dev/mapper/home"?

   

Am Sonntag, 27. August 2023, 20:26:46 CEST schrieb Greg Wooledge:


> On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> > When I boot the system, then the drives are not mounted as set in
> > /etc/fstab. For example, the SDD should mounted to /space, and the
> > unencrypted HDD shall be mounted to /daten.
> > 
> > But it seems, sometimes the mountpoints are not correct, so the SDD is not
> > mounted to /space, but to /daten.
> 
> This sounds like you used the dynamically assigned device names (e.g.
> /dev/sda1 and so on) in fstab.  If that's what you did, stop doing that.
> 
> Use UUIDs or Labels instead.  These won't change, while the device names
> *will* change.

Re: Boot issue

[Hans]

Here it is:





# /etc/fstab: static file system information. 
# 
# 
proc/proc   procdefaults0   0 
# /dev/sda3  /  ext4defaults,errors=remount-ro 0   1 
UUID=819bf8ae-a727-4b5e-97f8-007f58e98f74  /ext4
defaults,errors=remount-ro 
0   1 
# /dev/sda1   /boot   ext2defaults0   2 
UUID=069980b1-f1d9-4a11-9e24-147d08b2073f   /boot   ext2
defaults0   2 
# /dev/sda2   noneswapsw  0   0 
UUID=2e42eec8-29ed-41d3-8fa6-2869e32605e4   noneswapsw  
0   0 
/dev/mapper/home /home  ext4defaults0   0 
# /dev/hdd/media/cdrom0   udf,iso9660 user,noauto 0   0 
/dev/cdrom/media/cdrom0   udf,iso9660 user,noauto 0   0 
# /dev/fd0/media/floppy0  autorw,user,noauto  0   0 
# /dev/sda1   /home/ullhan63/games   ext3rw,user,noauto
0  0 
# /dev/disk/by-label/UIT-KEY  /media  vfat
noauto,errors=remount-ro0   0 
/dev/sdc1   /space   ext4defaults0  0






> [...]
> 
> Show us your /etc/fstab.
> 
> Cheers


It might be as Greg mentioned: devicename instead of UUID.

Hans

Re: Boot issue on system with four SATA devices

[Geert Stappers]

On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> Dear list, 
> 
> there is a little issue, which I try to solve. On my desptop computer I have 
> 4 
> harddrives:
> 
> SATA 0: HDD 300 GB with Debian + GRUB on MBR (parted in /boot, /, /home 
> (luks), /var (luks) and /usr (luks)
> SATA 1: HDD 300 GB with Win10
> SATA 2: SDD 128 GB (as simple data storage)
> SATA 3: HDD 1,5 TB (as simple data storage, splitted as 1TB encrypted and 500 
> GB unencrypted)
> 
> Now the issue: 
> 
> When I boot the system, then the drives are not mounted as set in /etc/fstab. 

What is the content of the expected /etc/fstab?


> For example, the SDD should mounted to /space, and the unencrypted HDD shall 
> be mounted to /daten.
> 
> But it seems, sometimes the mountpoints are not correct, so the SDD is not 
> mounted to /space, but to /daten.
> 
> Also some harddrives are not recognized at all and I then must boot several 
> times, that all drives and partitions are seen.
> 
> Question one: Is this a problem of the BIOS and motherboard, or a kernel 
> problem? 
> 
> Question two: I remeber to have read, as soon as the kernel hast started (and 
> it is always starting) the BIOS has no more influence to the hardware. Is 
> this 
> correct? If yes, then it is definately a kernel issue. What can I do?

Try to understand what is going on ...

 
> I suppose, if this is a hardware issue (I am thinking of, that there is a 
> timing problem due to speed differences among the slow HDD and the fast SDD), 
> is there anything I can do (except of replacing the HDD with SDD)?

Share with us the content of the /etc/fstab

 
> Any hints welcome!

Subject lines that express that some effort has been made.


> Best regards
> Hans 


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Boot issue

[Felix Miata]

Hans composed on 2023-08-27 20:19 (UTC+0200):

> When I boot the system, then the drives are not mounted as set in /etc/fstab. 
> For example, the SDD should mounted to /space, and the unencrypted HDD shall 
> be mounted to /daten.

> But it seems, sometimes the mountpoints are not correct, so the SDD is not 
> mounted to /space, but to /daten.

> Also some harddrives are not recognized at all and I then must boot several 
> times, that all drives and partitions are seen.

Please show output from lsblk -f and content of /etc/fstab.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: Boot issue

[tomas]

On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> Dear list, 
> 
> there is a little issue, which I try to solve. On my desptop computer I have 
> 4 
> harddrives:
> 
> SATA 0: HDD 300 GB with Debian + GRUB on MBR (parted in /boot, /, /home 
> (luks), /var (luks) and /usr (luks)
> SATA 1: HDD 300 GB with Win10
> SATA 2: SDD 128 GB (as simple data storage)
> SATA 3: HDD 1,5 TB (as simple data storage, splitted as 1TB encrypted and 500 
> GB unencrypted)
> 
> Now the issue: 
> 
> When I boot the system, then the drives are not mounted as set in /etc/fstab. 
> For example, the SDD should mounted to /space, and the unencrypted HDD shall 
> be mounted to /daten.

[...]

Show us your /etc/fstab.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Boot issue

[Greg Wooledge]

On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> When I boot the system, then the drives are not mounted as set in /etc/fstab. 
> For example, the SDD should mounted to /space, and the unencrypted HDD shall 
> be mounted to /daten.
> 
> But it seems, sometimes the mountpoints are not correct, so the SDD is not 
> mounted to /space, but to /daten.

This sounds like you used the dynamically assigned device names (e.g.
/dev/sda1 and so on) in fstab.  If that's what you did, stop doing that.

Use UUIDs or Labels instead.  These won't change, while the device names
*will* change.

Re: Boot issue

[Stefan Monnier]

> When I boot the system, then the drives are not mounted as set in /etc/fstab. 

I suspect that showing us your `/etc/fstab` would help,


Stefan

Boot issue

[Hans]

Dear list, 

there is a little issue, which I try to solve. On my desptop computer I have 4 
harddrives:

SATA 0: HDD 300 GB with Debian + GRUB on MBR (parted in /boot, /, /home 
(luks), /var (luks) and /usr (luks)
SATA 1: HDD 300 GB with Win10
SATA 2: SDD 128 GB (as simple data storage)
SATA 3: HDD 1,5 TB (as simple data storage, splitted as 1TB encrypted and 500 
GB unencrypted)

Now the issue: 

When I boot the system, then the drives are not mounted as set in /etc/fstab. 
For example, the SDD should mounted to /space, and the unencrypted HDD shall 
be mounted to /daten.

But it seems, sometimes the mountpoints are not correct, so the SDD is not 
mounted to /space, but to /daten.

Also some harddrives are not recognized at all and I then must boot several 
times, that all drives and partitions are seen.

Question one: Is this a problem of the BIOS and motherboard, or a kernel 
problem? 

Question two: I remeber to have read, as soon as the kernel hast started (and 
it is always starting) the BIOS has no more influence to the hardware. Is this 
correct? If yes, then it is definately a kernel issue. What can I do?

I suppose, if this is a hardware issue (I am thinking of, that there is a 
timing problem due to speed differences among the slow HDD and the fast SDD), 
is there anything I can do (except of replacing the HDD with SDD)?

Any hints welcome! It is no burning problem, but I would like to understand, 
what is going on.

Best regards

Hans 

Re: First boot issue

[Patrick Bartek]

On Sat, 23 Nov 2019 22:25:01 -0800
Kord  wrote:

> Hi,
> 
> I recently installed Debian 10.2 as a dual boot on a second HDD separate
> from windows 10, and when booting from grub, have not been able to get
> pass the “ [ ok ]  gnome display manager”. Is there any fix for this?  
> Thanks

Without more details . . . .  Who can say?  Try turning off Fastboot and
Secureboot to begin with.  Even though Buster has a signed kernel to
work with Secureboot, it's a place to start troubleshooting.

B

Re: First boot issue

[riveravaldez]

On 11/24/19, Kord  wrote:
> I recently installed Debian 10.2 as a dual boot on a second HDD separate
> from windows 10, and when booting from grub, have not been able to get pass
> the “ [ ok ]  gnome display manager”. Is there any fix for this?

You could try Ctrl+Alt+F1 (or F2) to test if you have CLI access to a
booted system and the issue is just something with Gnome shell maybe?

Boot issue - machine ends up in Busybox

[X]

Hi,

On Wed, I upgraded my debian box (unstable) using aptitude and then shut
it down. On booting, it gave me an alert about a disk it couldn't find
and brought up the Busybox prompt. I have /boot as a normal partition
and other partitions (/, /home, /tmp, /usr, /var, etc.) in a LVM group. 

On checking the LVM partitions, everything seemed to be fine. Then I did
a lvm vgchange -ay and exit, the machine booted up fine after that. I
rebooted the machine and had to do the activate the volumegroup again to
be able to boot!

Why isn't it able to scan the lvm groups and volumes? Is it something to
do with systemd?

The message before it goes to busybox is shown below if it is helpful. 


Gave up waiting for root device. Common problems:
Boot args (cat /proc/cmdline )
Check root delay = (did the system wait long enough)
Check root= (did the system wait for the right device?)
Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/66743620-9332-4a1e-a8b1-933eeab1fd89 does not
exist.
Dropping to shell!
modprobe: module ehci-orion not found in modules.dep
*

-- 
  KS
  list...@fastmail.fm

-- 
http://www.fastmail.fm - Or how I learned to stop worrying and
  love email again


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1394995221.18926.95145181.11899...@webmail.messagingengine.com

Re: Boot issue - machine ends up in Busybox

[KS]

On 16/03/14 02:40 PM, X wrote:
 Hi,
 
 On Wed, I upgraded my debian box (unstable) using aptitude and then shut
 it down. On booting, it gave me an alert about a disk it couldn't find
 and brought up the Busybox prompt. I have /boot as a normal partition
 and other partitions (/, /home, /tmp, /usr, /var, etc.) in a LVM group. 
 
 On checking the LVM partitions, everything seemed to be fine. Then I did
 a lvm vgchange -ay and exit, the machine booted up fine after that. I
 rebooted the machine and had to do the activate the volumegroup again to
 be able to boot!
 
 Why isn't it able to scan the lvm groups and volumes? Is it something to
 do with systemd?
 
 The message before it goes to busybox is shown below if it is helpful. 
 
 
 Gave up waiting for root device. Common problems:
 Boot args (cat /proc/cmdline )
 Check root delay = (did the system wait long enough)
 Check root= (did the system wait for the right device?)
 Missing modules (cat /proc/modules; ls /dev)
 ALERT! /dev/disk/by-uuid/66743620-9332-4a1e-a8b1-933eeab1fd89 does not
 exist.
 Dropping to shell!
 modprobe: module ehci-orion not found in modules.dep
 *
 
More system info:
Linux localhost 3.13-1-686-pae #1 SMP Debian 3.13.5-1 (2014-03-04) i686
GNU/Linux

$ apt-cache policy lvm2
lvm2:
  Installed: 2.02.104-2
  Candidate: 2.02.104-2
  Version table:
 *** 2.02.104-2 0
500 http://ftp.ca.debian.org/debian/ unstable/main i386 Packages
500 http://ftp.de.debian.org/debian/ unstable/main i386 Packages
100 /var/lib/dpkg/status

$ apt-cache policy systemd
systemd:
  Installed: 204-7
  Candidate: 204-7
  Version table:
 *** 204-7 0
500 http://ftp.ca.debian.org/debian/ unstable/main i386 Packages
500 http://ftp.de.debian.org/debian/ unstable/main i386 Packages
100 /var/lib/dpkg/status

$ sudo /sbin/lvdisplay -c
  /dev/lvm-gp/glvm01:lvm-gp:3:1:-1:2:3899392:476:-1:0:-1:254:0
  /dev/lvm-gp/glvm02:lvm-gp:3:1:-1:1:3899392:476:-1:0:-1:254:1
  /dev/lvm-gp/glvm03:lvm-gp:3:1:-1:1:39059456:4768:-1:0:-1:254:2
  /dev/lvm-gp/glvm04:lvm-gp:3:1:-1:1:9764864:1192:-1:0:-1:254:3
  /dev/lvm-gp/glvm05:lvm-gp:3:1:-1:1:9764864:1192:-1:0:-1:254:4
  /dev/lvm-gp/glvm06:lvm-gp:3:1:-1:1:312500224:38147:-1:0:-1:254:5
  /dev/lvm-gp/glvm07:lvm-gp:3:1:-1:1:97648640:11920:-1:0:-1:254:6


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5325f90a.4090...@fastmail.fm

Re: Boot issue - machine ends up in Busybox

[Joe]

On Sun, 16 Mar 2014 14:40:21 -0400
X list...@fastmail.fm wrote:

 Hi,
 
 On Wed, I upgraded my debian box (unstable) using aptitude and then
 shut it down. On booting, it gave me an alert about a disk it
 couldn't find and brought up the Busybox prompt. I have /boot as a
 normal partition and other partitions (/, /home, /tmp, /usr, /var,
 etc.) in a LVM group. 
 
 On checking the LVM partitions, everything seemed to be fine. Then I
 did a lvm vgchange -ay and exit, the machine booted up fine after
 that. I rebooted the machine and had to do the activate the
 volumegroup again to be able to boot!
 
 Why isn't it able to scan the lvm groups and volumes? Is it something
 to do with systemd?
 
 The message before it goes to busybox is shown below if it is
 helpful. 
 
 
 Gave up waiting for root device. Common problems:
 Boot args (cat /proc/cmdline )
 Check root delay = (did the system wait long enough)
 Check root= (did the system wait for the right device?)
 Missing modules (cat /proc/modules; ls /dev)
 ALERT! /dev/disk/by-uuid/66743620-9332-4a1e-a8b1-933eeab1fd89 does not
 exist.
 Dropping to shell!
 modprobe: module ehci-orion not found in modules.dep
 *
 

Been there, done that, reported the bug. I'm surprised how few people
this has hit. In my case, the /boot and all the LVM partitions except
swap are reiserfs, and in its faulty state, it can see the reiserfs
/boot and the LVM swap but not the LVM reiserfs partitions.

It appears to be an issue with the new grub-pc-bin 2.02~beta2-7. I
downgraded to 2.00-22 along with grub-common, and it booted again. I
then downgraded two other 2.02 packages marked as broken, and all was
well again.

-- 
Joe


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140316202645.03442...@jretrading.com

Re: Boot issue - machine ends up in Busybox

[KS]

On 16/03/14 04:26 PM, Joe wrote:
 
 It appears to be an issue with the new grub-pc-bin 2.02~beta2-7. I
 downgraded to 2.00-22 along with grub-common, and it booted again. I
 then downgraded two other 2.02 packages marked as broken, and all was
 well again.
 

Pinned packages and reinstalled 2.00-22 for
The following NEW packages will be installed:
  grub-common{a} grub-pc grub-pc-bin{a} grub2-common{a}

Rebooting...


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53262fc5.8080...@fastmail.fm

Re: Boot issue - machine ends up in Busybox

[KS]

On 16/03/14 07:12 PM, KS wrote:
 On 16/03/14 04:26 PM, Joe wrote:

 It appears to be an issue with the new grub-pc-bin 2.02~beta2-7. I
 downgraded to 2.00-22 along with grub-common, and it booted again. I
 then downgraded two other 2.02 packages marked as broken, and all was
 well again.

 
 Pinned packages and reinstalled 2.00-22 for
 The following NEW packages will be installed:
   grub-common{a} grub-pc grub-pc-bin{a} grub2-common{a}
 
 Rebooting...
 
 
Reboot works normally now. Staying with 2.00-22 for now.

Thanks,
KS


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5326349e.3080...@fastmail.fm

Re: GRUB2 boot issue

[John W Foster]

On Sun, 2010-12-19 at 14:36 -0500, Tom H wrote: 
 On Sun, Dec 19, 2010 at 12:26 PM, John Foster jfoster81...@gmail.com wrote:
 
  Here's a new one for you GRUB2 gurus. I left my office attended by my 2 (5 
  7 yr. old very curious) grandsons. When about 3 minutes later I returned, my
  system ( which is a multiple boot of Debian Linux SID, Windows 7 Pro, 
  Ubuntu 9,) had been rebooted form Windows7 to the GRUB2 rescue mode 
  stalled there. I figure one of them pushed the soft reboot button 
  restarted the system. Now I had it set to boot to Debian Linux
  automatically, but as I recall the GRUB2 boot-loader had beside the previous
  listed OS's, another load item on the menu. Which was GRUB2 rescue mode; Now
  I have been unable to boot the system into anything except the rescue mode
  The error message given is: GRUB can't find required file: x.updates. Now as
  I,m at work  not looking at the exact message returned, I may be off a bit
  on the verbiage. If anyone has any ideas I would appreciate a reply to me
  directly as sometimes the filters get list replies.
 
 There's never any grub2 rescue mode entry; you must mean recovery
 mode, which boots into single-user mode.
 
 This is the grub2 manual resolution:
 http://www.gnu.org/software/grub/manual/grub.html#GRUB-only-offers-a-rescue-shell
 
 (By the way, your reply-to address is John Foster@liszt.debian.org
 rather than your sending address, jfoster81...@gmail.com.)
 
 
OK I read the link info  I do not think that an incorrect installation
is the issue. I used Super Grub2 disk to start my Debian Linux  mixed
Sid/squeeze installation  Linux works fine from there as I'm using it
to send this. exact message that I get when grub2 tries to boot the
computer is;

rescue error: symbol not found: 'grub_xputs'

so the system has defaulted to drop me into the rescue mode as there is
a file needed for proper bootin, missing. I did try completely removing
all of the grub-common  everything with grub2 or grub in the name or
description, Then reinstalled everything. I still having the same
problem.  thanks Tom for the tip re e-mail; I have it set this way so I
will get my mail regardless of whether or not I get a list feed. Thanks!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1292860298.4209.15.ca...@beast.johnwfoster.info

Re: GRUB2 boot issue

[Tom H]

On Mon, Dec 20, 2010 at 10:51 AM, John W Foster jfoster81...@gmail.com wrote:
 On Sun, 2010-12-19 at 14:36 -0500, Tom H wrote:
 On Sun, Dec 19, 2010 at 12:26 PM, John Foster jfoster81...@gmail.com wrote:

 Here's a new one for you GRUB2 gurus. I left my office attended by my 2 (5 
 7 yr. old very curious) grandsons. When about 3 minutes later I returned, my
 system (which is a multiple boot of Debian Linux SID, Windows 7 Pro, 
 Ubuntu 9,) had been rebooted form Windows7 to the GRUB2 rescue mode 
 stalled there. I figure one of them pushed the soft reboot button 
 restarted the system. Now I had it set to boot to Debian Linux
 automatically, but as I recall the GRUB2 boot-loader had beside the previous
 listed OS's, another load item on the menu. Which was GRUB2 rescue mode; Now
 I have been unable to boot the system into anything except the rescue mode
 The error message given is: GRUB can't find required file: x.updates. Now as
 I,m at work  not looking at the exact message returned, I may be off a bit
 on the verbiage. If anyone has any ideas I would appreciate a reply to me
 directly as sometimes the filters get list replies.

 There's never any grub2 rescue mode entry; you must mean recovery
 mode, which boots into single-user mode.

 This is the grub2 manual resolution:
 http://www.gnu.org/software/grub/manual/grub.html#GRUB-only-offers-a-rescue-shell

 (By the way, your reply-to address is John Foster@liszt.debian.org
 rather than your sending address, jfoster81...@gmail.com.)

 OK I read the link info  I do not think that an incorrect installation
 is the issue. I used Super Grub2 disk to start my Debian Linux mixed
 Sid/squeeze installation  Linux works fine from there as I'm using it
 to send this. exact message that I get when grub2 tries to boot the
 computer is;

 rescue error: symbol not found: 'grub_xputs'

 so the system has defaulted to drop me into the rescue mode as there is
 a file needed for proper bootin, missing. I did try completely removing
 all of the grub-common  everything with grub2 or grub in the name or
 description, Then reinstalled everything. I still having the same
 problem.  thanks Tom for the tip re e-mail; I have it set this way so I
 will get my mail regardless of whether or not I get a list feed. Thanks!

You're welcome about the reply-to address.

I thought that the resolution of the grub rescue prompt was the
above routine (which I've used once). It seems that it works if
there's no error message (and perhaps for some/all error messages
other than symbol not found: 'grub_xputs'...).

I've googled 'grub_xputs' and there are Debian and Ubuntu bug reports
about it, the resolution of which is the re-installation of grub.

How did you re-install? Did you boot from a CD, chroot, and purge and
re-install grub-common and grub-pc? (You could've just - theoretically
- run grub-install /dev/sdX after chrooting.)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlkti=vstrhreb0ko8ugqmvbdhgxukegww2vp6wz...@mail.gmail.com

GRUB2 boot issue

[John Foster]

Here's a new one for you GRUB2 gurus. I left my office attended by my 2 
(5  7 yr. old very curious) grandsons. When about 3 minutes later I 
returned, my system ( which is a multiple boot of Debian Linux SID, 
Windows 7 Pro,  Ubuntu 9,) had been rebooted form Windows7 to the GRUB2 
rescue mode  stalled there. I figure one of them pushed the soft reboot 
button  restarted the system. Now I had it set to boot to Debian Linux 
automatically, but as I recall the GRUB2 boot-loader had beside the 
previous listed OS's, another load item on the menu. Which was GRUB2 
rescue mode; Now I have been unable to boot the system into anything 
except the rescue mode The error message given is: GRUB can't find 
required file: x.updates. Now as I,m at work  not looking at the exact 
message returned, I may be off a bit on the verbiage. If anyone has any 
ideas I would appreciate a reply to me directly as sometimes the filters 
get list replies.

--
John Foster


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4d0e405b.8010...@gmail.com

Re: GRUB2 boot issue

[Tom H]

On Sun, Dec 19, 2010 at 12:26 PM, John Foster jfoster81...@gmail.com wrote:

 Here's a new one for you GRUB2 gurus. I left my office attended by my 2 (5 
 7 yr. old very curious) grandsons. When about 3 minutes later I returned, my
 system ( which is a multiple boot of Debian Linux SID, Windows 7 Pro, 
 Ubuntu 9,) had been rebooted form Windows7 to the GRUB2 rescue mode 
 stalled there. I figure one of them pushed the soft reboot button 
 restarted the system. Now I had it set to boot to Debian Linux
 automatically, but as I recall the GRUB2 boot-loader had beside the previous
 listed OS's, another load item on the menu. Which was GRUB2 rescue mode; Now
 I have been unable to boot the system into anything except the rescue mode
 The error message given is: GRUB can't find required file: x.updates. Now as
 I,m at work  not looking at the exact message returned, I may be off a bit
 on the verbiage. If anyone has any ideas I would appreciate a reply to me
 directly as sometimes the filters get list replies.

There's never any grub2 rescue mode entry; you must mean recovery
mode, which boots into single-user mode.

This is the grub2 manual resolution:
http://www.gnu.org/software/grub/manual/grub.html#GRUB-only-offers-a-rescue-shell

(By the way, your reply-to address is John Foster@liszt.debian.org
rather than your sending address, jfoster81...@gmail.com.)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktik=r5iqo9ha-ooing=cvvlaqwlcpbs5d=2m4...@mail.gmail.com

Re: Boot issue, new installation of Lenny with mirrored /boot and mirrored lvm2

[Frank Lin PIAT]

Hi,

On Fri, 2009-07-03 at 12:53 +1000, Andrew McGlashan wrote:
 
 I have 2x IBM xSeries 346 servers, one has a RAID card (let's call this 
 machine 346a) and the other only has onboard SCSI (346b).
 
 [..] it stops at a 
 special initramfs sh after giving up on the lvm volume group (not found) ... 
 from there I can activate the md0 and md1 mirrors and activate the lvm2 
 logical volumes, I then exit the sh and boot continues as normal.
 
 I've checked the kernel and module files for each machine, they are 100% 
 identical.  I've checked all files in /boot and /boot/grub and the 
 differences don't give me any clues.

Your problem is probably inside your /boot/initrd... file

You might want to rebuild it, using update-initramfs

Also, did you read /usr/share/doc/mdadm/rootraiddoc.97.html (which is
outdated, but gives good overview)

Hope this helps,

Franklin


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Boot issue, new installation of Lenny with mirrored /boot and mirrored lvm2

[Andrew McGlashan]

Hi Franklin,

On Fri, July 3, 2009 4:36 pm, Frank Lin PIAT wrote:
 Your problem is probably inside your /boot/initrd... file

 You might want to rebuild it, using update-initramfs

Tried that, multiple ways:

update-initramfs -u -k all
update-initramfs -n -k all

 Also, did you read /usr/share/doc/mdadm/rootraiddoc.97.html (which is
 outdated, but gives good overview)

No, not yet.  But the other 346 machine is working fine and I don't think
that I have anything missing in my understanding other than why mdadm
isn't assembling the drives as it should on the 'bad' machine when the
processes are exactly the same and work fine on the 'good' machine.

 Hope this helps,

Thanks.

Kind Regards
AndrewM

Andrew McGlashan
Broadband Solutions now including VoIP



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Boot issue, new installation of Lenny with mirrored /boot and mirrored lvm2

[Andrew McGlashan]

Hi,

I have 2x IBM xSeries 346 servers, one has a RAID card (let's call this 
machine 346a) and the other only has onboard SCSI (346b).


Both have two RAID1 software mirrors -- one for /boot (/dev/md0) and the 
other for lvm2 use (/dev/md1).


Both are running the same amd64 Debian release (Lenny).

346a will boot entirely without issues whatsoever, but 346b stops at a 
special initramfs sh after giving up on the lvm volume group (not found) ... 
from there I can activate the md0 and md1 mirrors and activate the lvm2 
logical volumes, I then exit the sh and boot continues as normal.


I've checked the kernel and module files for each machine, they are 100% 
identical.  I've checked all files in /boot and /boot/grub and the 
differences don't give me any clues.


I've even md5 check summed every file in /boot and disassembled the 
initramfs image files to compare them.  Every difference seems to be 
perfectly acceptable and explainable.


346a is running with 300GB SCSI drives, each set as a single drive on the 
hardware (IBM) RAID controller with software RAID in use.


346b is running with 73GB SCSI drives, no RAID controller -- but using 
software RAID as per 346a.


346b can have all drives / file system areas fully accessible via Ubuntu 
live CD (with addition of mdadm and lvm2, plus a little setup).  It is also 
fully accessible using Debian rescue from the installer (netinst) disk.  And 
as I mentioned above, it is recoverable from the initramfs sh environment, 
but it won't boot up without intervention.


I have since added debug to the cmdline and found that the issue is 
definitely due to a failure to activate the mirrors.


extract
+ /scripts/local-top/mdadm
Begin: LoadingSuccess: loaded module raid1.
done.
Begin: Assembling all MD arrays ... mdadm: No devices listed in conf file
were found.
Failure: failed to assemble all arrays.
done.
/extract

Inside the initramfs file system, the /etc/mdadm/mdadm.conf file looks 
fine -- it includes the correct details including the UUID of each mirror.


Kind Regards
AndrewM

Andrew McGlashan
Broadband Solutions now including VoIP


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Debian boot issue.

[Wouter Hanegraaff]

On Fri, Jan 14, 2000 at 02:01:43PM -0900, Christopher S. Swingley wrote:
  
  Any idea ?
 
 I had the same problem with an Adaptex 2910C.  I think your problem is 
 a kernel issue -- the 2.0.36 kernel that is loaded from the Debian CD 
 doesn't support the newer Adaptec cards.  This is why it worked when you 
 used a different distro (probably using a newer kernel).
 
 What I did was download the boot floppies from potato (unstable Debian) 
 and used those.  

Another possible solution, if you can't install from the net, is to use
the slink r4 boot floppies, they have kernel 2.0.38 which might also
solve this problem. After that, you can just use the slink cd's (even if
your cd's aren't release 4) 

Wouter.

Debian boot issue.

[Francis Pirotton]

Hello,

I try to install slink (debian 2.1), booting from the cd-rom 1, and I
have no
problem until the system tries to detect the scsi devices.

My PC is an Pentium 200MHz (non MMX) with 128MB
I have a SCSI controller which is an AHA-2940A
   a PLEXTOR   Model: CD-ROM PX-40TSRev: 1.00 (SCSI)
   a QUANTUM   Model: FIREBALL SE8.4S   Rev: PJ09 (SCSI)
   a QUANTUM   Model: FIREBALL SE4.3S   Rev: PJ09 (SCSI)
   and a Hewlett-Packard CD-Writer Plus 8100, ATAPI CDROM drive
   The video card is an ExpertColor DSV 3968P.

Here you have the message I get when I boot from the CDROM

...
md driver 0.36.3 MAX_MD_DEV=4, MAX_REAL=8
(scsi0) Adaptec AHA-2940A Ultra SCSI host adapter found at PCI 17/0
(scsi0) Narrow Channel, SCSI ID=7, 3/255 SCBs
(scsi0) Warning - detected auto-termination
(scsi0) Please verify driver detected settings are correct.
(scsi0) If not, then please properly set the device termination
(scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A when prompted
(scsi0) during machine bootup.
(scsi0) Cables present (Int-50 YES, Ext-50 NO)
(scsi0) Downloading sequencer code... 419 instructions downloaded

- After the 'Download sequencer code...' message the boot is
completely stuck.

I have also tried the boot parameters like

boot: linux aic7xxx=extended,no_reset
or without the no_reset but no improve.
With the no_reset I am just stuck after the warning message telling
to use it only if you know what you are doing ...

Now I have tried to boot from a TOMSRBT disk and the messages are the
following :
(As you will see no problem ...)

Memory: sized by int13 0e801h
Console: 16 point font, 480 scans
Console: colour VGA+ 80x30, 1 virtual console (max 63)
pcibios_init : BIOS32 Service Directory structure at 0x000fdb60
pcibios_init : BIOS32 Service Directory entry at 0xfdb70
pcibios_init : PCI BIOS revision 2.10 entry at 0xfdb91
Probing PCI hardware.
Calibrating delay loop.. ok - 80.08 BogoMIPS
Memory: 127684k/131072k available (816k kernel code, 384k reserved,
2188k data)
Swansea University Computer Society NET3.035 for Linux 2.0
NET3: Unix domain sockets 0.13 for Linux NET3.035.
Swansea University Computer Society TCP/IP for NET3.034
IP Protocols: ICMP, UDP, TCP
Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.

Checking 'hlt' instruction... Ok.
Intel Pentium with F0 0F bug - workaround enabled.
alias mapping IDT readonly ...  ... done
Linux version 2.0.37 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #13 Fri Oct 15
19:41:45 EDT 1999
Starting kswapd v 1.4.2.2
Serial driver version 4.13p1 with no serial options enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Ramdisk driver initialized : 16 ramdisks of 4096K size
loop: registered device at major 7
hdc: Hewlett-Packard CD-Writer Plus 8100, ATAPI CDROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Floppy drive(s): fd0 is 1.44M
FDC 0 is an 8272A
scsi : 0 hosts.
scsi : detected total.
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
3c59x.c:v0.99H 11/17/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
Partition check:
VFS: Disk change detected on device 02:3c
RAMDISK: Compressed image found at block 518
VFS: Mounted root (minix filesystem).
scsi : 0 hosts.
scsi : 0 hosts.
scsi : 0 hosts.
(scsi0) Adaptec AHA-2940A Ultra SCSI host adapter found at PCI 17/0
(scsi0) Narrow Channel, SCSI ID=7, 3/255 SCBs
(scsi0) Warning - detected auto-termination
(scsi0) Please verify driver detected settings are correct.
(scsi0) If not, then please properly set the device termination
(scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A when prompted
(scsi0) during machine bootup.
(scsi0) Cables present (Int-50 YES, Ext-50 NO)
(scsi0) Downloading sequencer code... 419 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.13/3.2.4
   Adaptec AHA-2940A Ultra SCSI host adapter
scsi : 1 host.
  Vendor: PLEXTOR   Model: CD-ROM PX-40TSRev: 1.00
  Type:   CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
  Vendor: QUANTUM   Model: FIREBALL SE8.4S   Rev: PJ09
  Type:   Direct-Access  ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 4, lun 0
  Vendor: QUANTUM   Model: FIREBALL SE4.3S   Rev: PJ09
  Type:   Direct-Access  ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 5, lun 0
(scsi0:0:4:0) Synchronous at 20.0 Mbyte/sec, offset 15.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 16777215 [8191 MB]
[8.2 GB]
 sda: sda1 sda2  sda5 sda6 
(scsi0:0:5:0) Synchronous at 20.0 Mbyte/sec, offset 15.
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8418816 [4110 MB] [4.1
GB]
 sdb: sdb1  sdb5 sdb6 sdb7 sdb8 
EATA0: address 0x7c10 in use, skipping probe.
EATA0: address 0x7c88 in use, skipping probe.
EATA0: address 0x170 in use, skipping probe.
scsi : 1 host.
scsi : 1 host.
scsi : 1 host.
ppa: Version 1.42
ppa: Probing 

Re: Debian boot issue.

[Christopher S. Swingley]

 I try to install slink (debian 2.1), booting from the cd-rom 1, and I
 have no
 problem until:

 (scsi0) Adaptec AHA-2940A Ultra SCSI host adapter found at PCI 17/0
 (scsi0) Warning - detected auto-termination
 (scsi0) Downloading sequencer code... 419 instructions downloaded
 
 - After the 'Download sequencer code...' message the boot is
 completely stuck.
 
 Any idea ?

I had the same problem with an Adaptex 2910C.  I think your problem is 
a kernel issue -- the 2.0.36 kernel that is loaded from the Debian CD 
doesn't support the newer Adaptec cards.  This is why it worked when you 
used a different distro (probably using a newer kernel).

What I did was download the boot floppies from potato (unstable Debian) 
and used those.  I had only one problem with this: after the base system 
was installed, the script to start dselect (where it lets you pick the 
type of install) crashed.  I just started dselect from another console 
and continued the install using the apt-get method.

Potato seems very stable to me, but you'd need to install it from the
network because there aren't CD's for it (as far as I know).

Another alternative would be to remove the SCSI card, install Debian
2.1, download and compile a 2.2.x kernel (with the correct Adaptec
driver built in), then install the SCSI card and devices.

Chris
-- 
Christopher S. Swingley   tel: 907-474-2689 fax: 474-2643
930 Koyukuk Drive, Suite 408C email: [EMAIL PROTECTED]
University of Alaska Fairbankswww.frontier.iarc.uaf.edu:8080/
Fairbanks, AK  99775 ~cswingle

PGP key: http://www.frontier.iarc.uaf.edu:8080/~cswingle/pubkey.asc