Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #179998 > unrolled thread

Possibly erroneous "device not present" message during boot

Started byRichard Owlett <rowlett@cloud85.net>
First post2017-04-12 13:20 +0200
Last post2017-05-04 19:20 +0200
Articles 20 on this page of 111 — 11 participants

Back to article view | Back to linux.debian.user


Contents

  Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-12 13:20 +0200
    Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-12 14:50 +0200
      Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-12 17:20 +0200
        Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-12 19:20 +0200
          Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-12 20:40 +0200
            Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-12 21:10 +0200
              Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-13 13:50 +0200
                Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-13 17:50 +0200
                  Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-13 19:40 +0200
                    Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-13 20:10 +0200
                      Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-14 01:20 +0200
                        Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-14 19:10 +0200
                          Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-14 20:40 +0200
                            Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-15 18:40 +0200
                              Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 20:10 +0200
                              Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-15 20:20 +0200
                              Re: customized Grub (was: Possibly erroneous "device not present...) Felix Miata <mrmazda@earthlink.net> - 2017-04-15 21:00 +0200
                                Re: customized Grub (was: Possibly erroneous "device not present...) Brian <ad44@cityscape.co.uk> - 2017-04-15 21:20 +0200
                                  Re: customized Grub Richard Owlett <rowlett@cloud85.net> - 2017-04-15 22:40 +0200
                                    Re: customized Grub Curt <curty@free.fr> - 2017-04-16 11:40 +0200
                          Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 00:10 +0200
                            Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-17 21:10 +0200
                              Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-18 00:10 +0200
                                Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-18 00:40 +0200
                                Re: Possibly erroneous "device not present" message during boot Lisi Reisz <lisi.reisz@gmail.com> - 2017-04-18 00:50 +0200
                                Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-18 20:50 +0200
                              Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-18 20:50 +0200
                                Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-18 21:30 +0200
                          Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-15 02:20 +0200
                            Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 02:50 +0200
                              Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 11:10 +0200
                                Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 16:40 +0200
                                  Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 19:20 +0200
                                    Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-15 20:20 +0200
                                      Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 23:20 +0200
                                    Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 23:00 +0200
                                      Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-16 00:00 +0200
                                        Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-17 03:40 +0200
                                          Re: Possibly erroneous "device not present" message during boot Curt <curty@free.fr> - 2017-04-17 10:50 +0200
                                            Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-17 21:10 +0200
                                              Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-18 20:40 +0200
                                                Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-18 21:20 +0200
                                                  Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-19 00:20 +0200
                                                    Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-19 00:30 +0200
                                                      Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-19 20:40 +0200
                                                        Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-19 21:40 +0200
                                                          Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-19 22:20 +0200
                                                            Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 13:50 +0200
                                                              Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-22 19:00 +0200
                                                                Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 20:10 +0200
                                                                  Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 20:20 +0200
                                                                  Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-22 20:40 +0200
                                                                    Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 21:10 +0200
                                                                    Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-22 23:30 +0200
                                  Re: Possibly erroneous "device not present" message during boot Doug <dmcgarrett@optonline.net> - 2017-04-15 21:30 +0200
                                    Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 22:20 +0200
                            Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 13:10 +0200
                              Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-15 16:10 +0200
                                Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 19:30 +0200
                              Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 19:30 +0200
                                Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 19:50 +0200
                                  Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-15 21:10 +0200
                                    Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 21:40 +0200
                          Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 03:40 +0200
                          Re: Possibly erroneous "device not present" message during boot GiaThnYgeia <GiaThnYgeia@openmailbox.org> - 2017-04-17 23:20 +0200
                            Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-18 00:30 +0200
                      Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-16 16:40 +0200
                        Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-16 17:10 +0200
                  Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-13 19:40 +0200
                    Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-13 21:10 +0200
            Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-12 21:30 +0200
              Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-13 13:50 +0200
            Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-12 21:30 +0200
              Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-13 17:20 +0200
                Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-13 18:30 +0200
            Re: Possibly erroneous "device not present" message during boot GiaThnYgeia <GiaThnYgeia@openmailbox.org> - 2017-04-17 22:50 +0200
              Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-18 21:00 +0200
                Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-18 21:50 +0200
                  Re: Possibly erroneous "device not present" message during boot The Wanderer <wanderer@fastmail.fm> - 2017-04-19 05:50 +0200
                    Re: Possibly erroneous "device not present" message during boot GiaThnYgeia <GiaThnYgeia@openmailbox.org> - 2017-04-19 09:50 +0200
                      Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-19 20:30 +0200
                        Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-22 00:20 +0200
                          Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-22 15:50 +0200
          Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-12 21:00 +0200
            Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-13 18:00 +0200
              Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-14 20:00 +0200
                Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-14 20:50 +0200
        Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-14 19:50 +0200
          Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-14 20:40 +0200
            Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 12:50 +0200
              Re: Possibly erroneous "device not present" message during boot songbird <songbird@anthive.com> - 2017-04-15 16:10 +0200
              Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-15 19:00 +0200
                Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 19:30 +0200
                  Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-15 20:10 +0200
                    Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-15 21:00 +0200
                      Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-15 23:40 +0200
                        Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-16 00:30 +0200
                          Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-20 04:20 +0200
                            Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-20 08:00 +0200
                              Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-20 17:20 +0200
                            Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 15:00 +0200
                              Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-22 15:40 +0200
                                Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-22 15:50 +0200
                                  Re: Possibly erroneous "device not present" message during boot Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-04-22 16:00 +0200
                                  Re: Possibly erroneous "device not present" message during boot Richard Owlett <rowlett@cloud85.net> - 2017-04-22 16:50 +0200
                                    Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-27 18:20 +0200
    Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-23 21:50 +0200
      Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-24 20:40 +0200
        Re: Possibly erroneous "device not present" message during boot David Wright <deblis@lionunicorn.co.uk> - 2017-04-24 22:20 +0200
          Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-04-25 15:10 +0200
            Re: Possibly erroneous "device not present" message during boot Brian <ad44@cityscape.co.uk> - 2017-05-04 19:20 +0200

Page 2 of 6 — ← Prev page 1 [2] 3 4 5 6  Next page →


#180144

FromPascal Hambourg <pascal@plouf.fr.eu.org>
Date2017-04-15 00:10 +0200
Message-ID<twhzI-6JW-11@gated-at.bofh.it>
In reply to#180136
Le 14/04/2017 à 19:05, Richard Owlett a écrit :
>
>  2. I only install Grub the *first* time I do a Debian install.
>     By poor design Grub puts the current install first on menu.

It's not poor design. It is perfectly normal that the system which 
installs GRUB is first in the menu. If you don't like it, you can change it.

>     When experimenting with configuration as I do, the least
>     likely install to be functional is the latest.

When experimenting, it is wise not to replace the existing working boot 
loader with a new one which depends on the newly installed system. It 
has nothing to do with GRUB's supposedly poor design.

>  3. Similarly a swap partition is specified only on the first
>     install as the installer insists on destroying the UUID of
>     the existing swap partition.

No, it doesn't insist. It just marks the existing swaps as to be used by 
default, which in turns marks them to be formatted with a new UUID. You 
are free to mark them as not to be used and they won't be reformatted. 
It just insist on using a swap, but it does not have to be any of the 
existing ones.

> Does any of this justify a bug report.

No. The only bug is that the system installed on the SD card boots while 
it should not.

[toc] | [prev] | [next] | [standalone]


#180222

FromBrian <ad44@cityscape.co.uk>
Date2017-04-17 21:10 +0200
Message-ID<txkca-4vI-11@gated-at.bofh.it>
In reply to#180144
On Sat 15 Apr 2017 at 00:07:39 +0200, Pascal Hambourg wrote:

> Le 14/04/2017 à 19:05, Richard Owlett a écrit :
> 
> >Does any of this justify a bug report.
> 
> No. The only bug is that the system installed on the SD card boots while it
> should not.

Why shouldn't the system boot? It has the same kernel that is on the
hard disk, And the GRUB versions are the same. Does it matter where the
booted kernel resides?

Ok. The OP was lucky. Another arrangement between the booted OS and GRUB
on the hard disk would possibly have led to a loss of sale for the store.
Never using anything but Jessie installs (which is what the OP does) is
a disadvantage when GRUB is involved.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]


#180230

FromRichard Owlett <rowlett@cloud85.net>
Date2017-04-18 00:10 +0200
Message-ID<txn0m-6jY-17@gated-at.bofh.it>
In reply to#180222
On 04/17/2017 02:04 PM, Brian wrote:
> On Sat 15 Apr 2017 at 00:07:39 +0200, Pascal Hambourg wrote:
>
>> Le 14/04/2017 à 19:05, Richard Owlett a écrit :
>>
>>> Does any of this justify a bug report.
>>
>> No. The only bug is that the system installed on the SD card boots while it
>> should not.
>
> Why shouldn't the system boot? It has the same kernel that is on the
> hard disk, And the GRUB versions are the same. Does it matter where the
> booted kernel resides?
>
> Ok. The OP was lucky. Another arrangement between the booted OS and GRUB
> on the hard disk would possibly have led to a loss of sale for the store.
> Never using anything but Jessie installs (which is what the OP does) is
> a disadvantage when GRUB is involved.
>

Not quite correct.
I performed what *I* considered a *WORST CASE TEST*.
It passed.
My *minimal* criterion was the ability to read *AND* write the device.

CAVEAT LECTORS
  Before retirement I frequently served in QA/QC roles
    NOTE BENE: QC is NOT identical to QA
                though "pickers of nits" frequent both

Please note my usage of "criterion" rather than "criteria".
Side note: I am an alumnus of "Venatores Verborum"

may dictator lapidum rip

[toc] | [prev] | [next] | [standalone]


#180233

FromBrian <ad44@cityscape.co.uk>
Date2017-04-18 00:40 +0200
Message-ID<txntn-6u0-15@gated-at.bofh.it>
In reply to#180230
On Mon 17 Apr 2017 at 17:04:57 -0500, Richard Owlett wrote:

> On 04/17/2017 02:04 PM, Brian wrote:
> >On Sat 15 Apr 2017 at 00:07:39 +0200, Pascal Hambourg wrote:
> >
> >>Le 14/04/2017 à 19:05, Richard Owlett a écrit :
> >>
> >>>Does any of this justify a bug report.
> >>
> >>No. The only bug is that the system installed on the SD card boots while it
> >>should not.
> >
> >Why shouldn't the system boot? It has the same kernel that is on the
> >hard disk, And the GRUB versions are the same. Does it matter where the
> >booted kernel resides?
> >
> >Ok. The OP was lucky. Another arrangement between the booted OS and GRUB
> >on the hard disk would possibly have led to a loss of sale for the store.
> >Never using anything but Jessie installs (which is what the OP does) is
> >a disadvantage when GRUB is involved.
> 
> Not quite correct.
> I performed what *I* considered a *WORST CASE TEST*.
> It passed.
> My *minimal* criterion was the ability to read *AND* write the device.

You haven't quite absorbed and understood

https://lists.debian.org/debian-user/2017/04/msg00430.html

I'd suggest you get to grip with its contents.

> CAVEAT LECTORS
>  Before retirement I frequently served in QA/QC roles
>    NOTE BENE: QC is NOT identical to QA
>                though "pickers of nits" frequent both
> 
> Please note my usage of "criterion" rather than "criteria".

I did. I also noted your use of "minimal" rather than "minimum". (I would
not normally point out things like this but times are hard. :) )

-- 
Brian

[toc] | [prev] | [next] | [standalone]


#180234

FromLisi Reisz <lisi.reisz@gmail.com>
Date2017-04-18 00:50 +0200
Message-ID<txnD3-6xJ-3@gated-at.bofh.it>
In reply to#180230
On Monday 17 April 2017 23:04:57 Richard Owlett wrote:
> Please note my usage of "criterion" rather than "criteria".

Sorry Richard.  I would certainly have noted if you hadn't.  It would have 
screamed at me.  I'm afraid that I don't always notice in passing when words 
are used correctly!  Nor do I see any need to note, as requested, that you 
know the difference between one and more of something. ;-)

Lisi

[toc] | [prev] | [next] | [standalone]


#180250

FromPascal Hambourg <pascal@plouf.fr.eu.org>
Date2017-04-18 20:50 +0200
Message-ID<txGmm-17N-19@gated-at.bofh.it>
In reply to#180230
Le 18/04/2017 à 00:04, Richard Owlett a écrit :
>
> My *minimal* criterion was the ability to read *AND* write the device.

Well then, installing a Debian system on it and booting it was overkill.
You could have just performed some reads and writes on the device from 
any of the systems installed on the internal drive.

[toc] | [prev] | [next] | [standalone]


#180251

FromPascal Hambourg <pascal@plouf.fr.eu.org>
Date2017-04-18 20:50 +0200
Message-ID<txGmm-17N-33@gated-at.bofh.it>
In reply to#180222
Le 17/04/2017 à 21:04, Brian a écrit :
> On Sat 15 Apr 2017 at 00:07:39 +0200, Pascal Hambourg wrote:
>
>> No. The only bug is that the system installed on the SD card boots while it
>> should not.
>
> Why shouldn't the system boot? It has the same kernel that is on the
> hard disk

By chance. In a more general case, it would not boot.

If the distribution installed on the SD card had a different kernel, or 
located in a different path, or if the initramfs on the internal drive 
did not include generic drivers but only the ones needed to mount the 
root filesystem from the internal drive (MODULES=dep instead of 
MODULES=most in /etc/initramfs-tools/initramfs.conf), it would not boot.

[toc] | [prev] | [next] | [standalone]


#180255

FromBrian <ad44@cityscape.co.uk>
Date2017-04-18 21:30 +0200
Message-ID<txGZ3-1zP-1@gated-at.bofh.it>
In reply to#180251
On Tue 18 Apr 2017 at 20:42:40 +0200, Pascal Hambourg wrote:

> Le 17/04/2017 à 21:04, Brian a écrit :
> >On Sat 15 Apr 2017 at 00:07:39 +0200, Pascal Hambourg wrote:
> >
> >>No. The only bug is that the system installed on the SD card boots while it
> >>should not.
> >
> >Why shouldn't the system boot? It has the same kernel that is on the
> >hard disk
> 
> By chance. In a more general case, it would not boot.

Agreed. I've said as much elsewhere. Indeed, the OP never uses anything
but Jessie so luck was involved - there is no kernel/initrd mismatch.

What is intriguing is that the search error message was not observed at
the store.

> If the distribution installed on the SD card had a different kernel, or
> located in a different path, or if the initramfs on the internal drive did
> not include generic drivers but only the ones needed to mount the root
> filesystem from the internal drive (MODULES=dep instead of MODULES=most in
> /etc/initramfs-tools/initramfs.conf), it would not boot.

True. I've experienced all of this.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]


#180148

Fromsongbird <songbird@anthive.com>
Date2017-04-15 02:20 +0200
Message-ID<twjBv-803-3@gated-at.bofh.it>
In reply to#180136
Richard Owlett wrote:
...
[file a bug?]

  i'm not sure this is a bug.  you've
done an expert install, but not let grub
finish so by my estimate you've left the
install where manual patching is needed.

  right now this thread is showing up via
go ogle so people will find it if they have
similar issues and they can maybe sort it
out.

  what i would do for grins is unplug the
devices other than the SSD and the installation 
media and then do a base system (simple install 
- not expert) and see what the installer does 
detect and writes in the fstab and grub menu 
(it may even boot).  you may then use those 
things in the previously installed grub and
fstab files (for the system which boots and
runs but does not mount the SSD).

  if you do this report the contents of the 
fstab and the grub.cfg


> Especially as I do not
> have the bandwidth to do a netinstall of a pre-release version?

  that's really unfortunate.


  songbird

[toc] | [prev] | [next] | [standalone]


#180149

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2017-04-15 02:50 +0200
Message-ID<twk4x-89Y-1@gated-at.bofh.it>
In reply to#180148
On Fri 14 Apr 2017 at 20:02:11 (-0400), songbird wrote:
> Richard Owlett wrote:
> ...
> [file a bug?]
> 
>   i'm not sure this is a bug.  you've
> done an expert install, but not let grub
> finish so by my estimate you've left the
> install where manual patching is needed.

I would agree with that. It's not clear to me why an SD is being used
in this way as the OP has at last revealed that the computer is unable
to boot from an SD plugged in directly. (Of course, an SD card can be
made to look like a USB stick just by sticking it in a card reader.
Then it will boot.)

>   right now this thread is showing up via
> go ogle so people will find it if they have
> similar issues and they can maybe sort it
> out.
> 
>   what i would do for grins is unplug the
> devices other than the SSD and the installation 
> media and then do a base system (simple install 
> - not expert) and see what the installer does 
> detect and writes in the fstab and grub menu 
> (it may even boot).  you may then use those 
> things in the previously installed grub and
> fstab files (for the system which boots and
> runs but does not mount the SSD).

Googling may now throw up this thread when people are searching for
SSD installation. SSDs are a different animal from SD cards.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#180152

FromPascal Hambourg <pascal@plouf.fr.eu.org>
Date2017-04-15 11:10 +0200
Message-ID<twrSp-4Iv-1@gated-at.bofh.it>
In reply to#180149
Le 15/04/2017 à 02:37, David Wright a écrit :
>
> Of course, an SD card can be
> made to look like a USB stick just by sticking it in a card reader.

I guess you mean "in a USB-to-SD card adapter", which translates a SD 
card into a USB mass storage device (/dev/sd*).
A SD card reader such as the one the OP has just exposes the SD card as 
what it is, a SD/MMC card (/dev/mmcblk*).

[toc] | [prev] | [next] | [standalone]


#180159

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2017-04-15 16:40 +0200
Message-ID<twx1L-7H3-7@gated-at.bofh.it>
In reply to#180152
On Sat 15 Apr 2017 at 11:05:12 (+0200), Pascal Hambourg wrote:
> Le 15/04/2017 à 02:37, David Wright a écrit :
> >
> >Of course, an SD card can be
> >made to look like a USB stick just by sticking it in a card reader.
> 
> I guess you mean "in a USB-to-SD card adapter", which translates a
> SD card into a USB mass storage device (/dev/sd*).

Yes, you guess correctly. Writing 40 years ago, I would use those same
words to describe a washing-machine sized object for reading punched
cards. Nowadays, if you type "card reader" into google, you will be
proffered several more sophisticated ones than mine, together with
some different varieties of credit card reader.

> A SD card reader such as the one the OP has just exposes the SD card
> as what it is, a SD/MMC card (/dev/mmcblk*).

I assumed that the OP, writing about a laptop, had no card reader,
and was inserting the SD card directly into the computer.

As it happens, if you do this with the ancient laptop I'm typing on,
it has the functionality of a card reader built into it and you get
a /dev/sd*, and that can be boot an SD card directly.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#180165

FromPascal Hambourg <pascal@plouf.fr.eu.org>
Date2017-04-15 19:20 +0200
Message-ID<twzwB-Vi-7@gated-at.bofh.it>
In reply to#180159
Le 15/04/2017 à 16:28, David Wright a écrit :
> On Sat 15 Apr 2017 at 11:05:12 (+0200), Pascal Hambourg wrote:
>
>> A SD card reader such as the one the OP has just exposes the SD card
>> as what it is, a SD/MMC card (/dev/mmcblk*).
>
> I assumed that the OP, writing about a laptop, had no card reader,
> and was inserting the SD card directly into the computer.

How do you name that slot on the laptop or desktop where you insert the 
SD card, if not an embedded card reader ?

> As it happens, if you do this with the ancient laptop I'm typing on,
> it has the functionality of a card reader built into it and you get
> a /dev/sd*, and that can be boot an SD card directly.

So there seems to be at least two kinds of SD card reader : those which 
expose themselves as a USB mass storage device and those which expose 
themselves as a SD/MMC device.

I have a couple of desktops with an embedded multi-card reader, 
connected to an internal USB port on the motherboard. But I do not have 
any SD card (no use), so I never checked to see what kind they are.

[toc] | [prev] | [next] | [standalone]


#180174

FromRichard Owlett <rowlett@cloud85.net>
Date2017-04-15 20:20 +0200
Message-ID<twAsF-1uC-7@gated-at.bofh.it>
In reply to#180165
On 04/15/2017 12:14 PM, Pascal Hambourg wrote:
> Le 15/04/2017 à 16:28, David Wright a écrit :
>> On Sat 15 Apr 2017 at 11:05:12 (+0200), Pascal Hambourg wrote:
>>
>>> A SD card reader such as the one the OP has just exposes the SD card
>>> as what it is, a SD/MMC card (/dev/mmcblk*).
>>
>> I assumed that the OP, writing about a laptop, had no card reader,
>> and was inserting the SD card directly into the computer.
>
> How do you name that slot on the laptop or desktop where you insert the
> SD card, if not an embedded card reader ?
>
>> As it happens, if you do this with the ancient laptop I'm typing on,
>> it has the functionality of a card reader built into it and you get
>> a /dev/sd*, and that can be boot an SD card directly.
>
> So there seems to be at least two kinds of SD card reader : those which
> expose themselves as a USB mass storage device and those which expose
> themselves as a SD/MMC device.
>
> I have a couple of desktops with an embedded multi-card reader,
> connected to an internal USB port on the motherboard. But I do not have
> any SD card (no use), so I never checked to see what kind they are.
>
>

 From https://www.cnet.com/products/lenovo-thinkpad-t510/specs/
I apparently have

Card Reader
   Type                 5 in 1 card reader
   Supported Flash      Memory Stick, Memory Stick PRO, MultiMediaCard,
     Memory             SD Memory Card, SDHC Memory Card

[toc] | [prev] | [next] | [standalone]


#180184

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2017-04-15 23:20 +0200
Message-ID<twDgR-3m7-1@gated-at.bofh.it>
In reply to#180174
On Sat 15 Apr 2017 at 13:16:54 (-0500), Richard Owlett wrote:
> On 04/15/2017 12:14 PM, Pascal Hambourg wrote:
> >Le 15/04/2017 à 16:28, David Wright a écrit :
> >>On Sat 15 Apr 2017 at 11:05:12 (+0200), Pascal Hambourg wrote:
> >>
> >>>A SD card reader such as the one the OP has just exposes the SD card
> >>>as what it is, a SD/MMC card (/dev/mmcblk*).
> >>
> >>I assumed that the OP, writing about a laptop, had no card reader,
> >>and was inserting the SD card directly into the computer.
> >
> >How do you name that slot on the laptop or desktop where you insert the
> >SD card, if not an embedded card reader ?
> >
> >>As it happens, if you do this with the ancient laptop I'm typing on,
> >>it has the functionality of a card reader built into it and you get
> >>a /dev/sd*, and that can be boot an SD card directly.
> >
> >So there seems to be at least two kinds of SD card reader : those which
> >expose themselves as a USB mass storage device and those which expose
> >themselves as a SD/MMC device.
> >
> >I have a couple of desktops with an embedded multi-card reader,
> >connected to an internal USB port on the motherboard. But I do not have
> >any SD card (no use), so I never checked to see what kind they are.
> >
> >
> 
> From https://www.cnet.com/products/lenovo-thinkpad-t510/specs/
> I apparently have
> 
> Card Reader
>   Type                 5 in 1 card reader
>   Supported Flash      Memory Stick, Memory Stick PRO, MultiMediaCard,
>     Memory             SD Memory Card, SDHC Memory Card

If I were you, I would try inserting your SD card and _then_ booting
it up. It's quite usual for bootable devices to appear in the BIOS's
Setup Menu only if a device is actually present. (Don't even rely on
a Boot Menu like F12 sometimes gives: check the Setup Menu itself.)
If it's there, promote it to first device to boot, and then boot.
(Don't rely on the promotion to be "sticky". If you ever boot
without a card plugged in, it may be demoted whenever you next plug
one in.)

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#180183

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2017-04-15 23:00 +0200
Message-ID<twCXv-2XV-5@gated-at.bofh.it>
In reply to#180165

[Multipart message — attachments visible in raw view] — view raw

On Sat 15 Apr 2017 at 19:14:24 (+0200), Pascal Hambourg wrote:
> Le 15/04/2017 à 16:28, David Wright a écrit :
> >On Sat 15 Apr 2017 at 11:05:12 (+0200), Pascal Hambourg wrote:
> >
> >>A SD card reader such as the one the OP has just exposes the SD card
> >>as what it is, a SD/MMC card (/dev/mmcblk*).
> >
> >I assumed that the OP, writing about a laptop, had no card reader,
> >and was inserting the SD card directly into the computer.
> 
> How do you name that slot on the laptop or desktop where you insert
> the SD card, if not an embedded card reader ?

A slot, or an SD slot (as on this Dell), or a micro SD slot.

You seem to have had some difficulty with this part of my post:

| It's not clear to me why an SD is being used in this way as the OP
| has at last revealed that the computer is unable to boot from an SD
| plugged in directly. (Of course, an SD card can be made to look like a
| USB stick just by sticking it in a card reader. Then it will boot.)

I would be happy to go through it and detail all the referents
if you can't judge them from the context.

> >As it happens, if you do this with the ancient laptop I'm typing on,
> >it has the functionality of a card reader built into it and you get
> >a /dev/sd*, and that can be boot an SD card directly.
> 
> So there seems to be at least two kinds of SD card reader : those
> which expose themselves as a USB mass storage device and those which
> expose themselves as a SD/MMC device.
> 
> I have a couple of desktops with an embedded multi-card reader,
> connected to an internal USB port on the motherboard. But I do not
> have any SD card (no use), so I never checked to see what kind they
> are.

I would imagine that most people wouldn't want to disassemble to check
this. The internal connections are likely subminiature anyway, so it
would be difficult to see how any card will appear to the user without
just inserting one.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#180186

FromPascal Hambourg <pascal@plouf.fr.eu.org>
Date2017-04-16 00:00 +0200
Message-ID<twDTz-3AT-3@gated-at.bofh.it>
In reply to#180183
Le 15/04/2017 à 22:50, David Wright a écrit :
> On Sat 15 Apr 2017 at 19:14:24 (+0200), Pascal Hambourg wrote:
>> Le 15/04/2017 à 16:28, David Wright a écrit :
>>> On Sat 15 Apr 2017 at 11:05:12 (+0200), Pascal Hambourg wrote:
>>>
>>>> A SD card reader such as the one the OP has just exposes the SD card
>>>> as what it is, a SD/MMC card (/dev/mmcblk*).
>>>
>>> I assumed that the OP, writing about a laptop, had no card reader,
>>> and was inserting the SD card directly into the computer.
>>
>> How do you name that slot on the laptop or desktop where you insert
>> the SD card, if not an embedded card reader ?
>
> A slot, or an SD slot (as on this Dell), or a micro SD slot.

Behind the slot is a SD card reader. Lenovo names it a card reader.

> You seem to have had some difficulty with this part of my post:
>
> | It's not clear to me why an SD is being used in this way as the OP
> | has at last revealed that the computer is unable to boot from an SD
> | plugged in directly.

IIUC, at first the OP did not know that the computer was unable to boot 
from the internal SD card reader and discovered it during this thread.

> (Of course, an SD card can be made to look like a
> | USB stick just by sticking it in a card reader. Then it will boot.)

Obviously not with the OP's laptop internal card reader, which does not 
make the SD card look like a USB mass storage class device.

[toc] | [prev] | [next] | [standalone]


#180200

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2017-04-17 03:40 +0200
Message-ID<tx3O1-2Cp-3@gated-at.bofh.it>
In reply to#180186
On Sat 15 Apr 2017 at 23:52:30 (+0200), Pascal Hambourg wrote:
> Le 15/04/2017 à 22:50, David Wright a écrit :
> >On Sat 15 Apr 2017 at 19:14:24 (+0200), Pascal Hambourg wrote:
> >>Le 15/04/2017 à 16:28, David Wright a écrit :
> >>>On Sat 15 Apr 2017 at 11:05:12 (+0200), Pascal Hambourg wrote:
> >>>
> >>>>A SD card reader such as the one the OP has just exposes the SD card
> >>>>as what it is, a SD/MMC card (/dev/mmcblk*).
> >>>
> >>>I assumed that the OP, writing about a laptop, had no card reader,
> >>>and was inserting the SD card directly into the computer.
> >>
> >>How do you name that slot on the laptop or desktop where you insert
> >>the SD card, if not an embedded card reader ?
> >
> >A slot, or an SD slot (as on this Dell), or a micro SD slot.
> 
> Behind the slot is a SD card reader. Lenovo names it a card reader.

Ok, ok. You're angling for congratulations for guessing what
Amazon and I call a card reader is what you prefer to call a
USB-to-SD card adapter.

Congratulations.

> >You seem to have had some difficulty with this part of my post:
> >
> >| It's not clear to me why an SD is being used in this way as the OP
> >| has at last revealed that the computer is unable to boot from an SD
> >| plugged in directly.
> 
> IIUC, at first the OP did not know that the computer was unable to
> boot from the internal SD card reader and discovered it during this
> thread.

_I_ didn't know whether the OP knew, suspected, or guessed one way
or the other when taking the card on approval. The later assertion
could be correct or incorrect: the experiment and observations
aren't reported. Other people in other places have reported
difficulties booting with /dev/mmcblk-style devices so I'm not
optimistic.

I can't experiment with my own hardware because my mmcblk-style
Dell laptop has a fault (which will probably lead to its demise)
meaning that the screen is only occasionally readable for about
one second at a time, and its VGA output is only turned on after
the kernel has loaded. So no CMOS screens, no Boot Menu, and no
Grub menu, as I don't have photographic recall.

> >(Of course, an SD card can be made to look like a
> >| USB stick just by sticking it in a card reader. Then it will boot.)
> 
> Obviously not with the OP's laptop internal card reader, which does
> not make the SD card look like a USB mass storage class device.

In the laptop's slot, it would appear not. If the methodology I
outlined elsewhere in the thread fails, then it would seem that
whatever is behind this slot needs an OS to read the card, whereas
the BIOS can be persuaded to read a USB stick without the need
for any OS.

Oddly, this ancient laptop (Acer) has a slot that makes the SD card
look like a /dev/sdX disk, and the BIOS is happy to boot from it.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#180202

FromCurt <curty@free.fr>
Date2017-04-17 10:50 +0200
Message-ID<txawa-6Xn-5@gated-at.bofh.it>
In reply to#180200
On 2017-04-17, David Wright <deblis@lionunicorn.co.uk> wrote:
>
> Oddly, this ancient laptop (Acer) has a slot that makes the SD card
> look like a /dev/sdX disk, and the BIOS is happy to boot from it.

I have an Acer X1430 with an internal "Multi-in-1 Media Card Reader" for
which an SD card inserted into the reader is recognized by the kernel as
as a /dev/sdX disk.

I would be happy to trade with the OP if he would be willing to come out
of retirement.

-;)

> Cheers,
> David.
>
>


-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

[toc] | [prev] | [next] | [standalone]


#180223

FromBrian <ad44@cityscape.co.uk>
Date2017-04-17 21:10 +0200
Message-ID<txkca-4vI-9@gated-at.bofh.it>
In reply to#180202
On Mon 17 Apr 2017 at 08:48:50 +0000, Curt wrote:

> On 2017-04-17, David Wright <deblis@lionunicorn.co.uk> wrote:
> >
> > Oddly, this ancient laptop (Acer) has a slot that makes the SD card
> > look like a /dev/sdX disk, and the BIOS is happy to boot from it.
> 
> I have an Acer X1430 with an internal "Multi-in-1 Media Card Reader" for
> which an SD card inserted into the reader is recognized by the kernel as
> as a /dev/sdX disk.

You have to be careful here to distinguish between what the OS can
recognise and what GRUB can see. The kernel will be using the Multimedia
Card device drivers to detect the device and assign a name to it.  Check
the modules are loaded with

 lsmod | grep mmc

On the other hand, GRUB can only boot from a device when information
is provided to it by the BIOS [1]. Using the normal GRUB setup [2] that
Debian provides, the command

 ls

at the GRUB command prompt (press "c" within the GRUB menu for this)
will show whether a device equivalent to the kernel's /dev/sdX is
discovered.

[1] Not completely correct, but it will do for the point I want to make.

[2] The "normal" setup does not load GRUB's nativedisk module.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]


Page 2 of 6 — ← Prev page 1 [2] 3 4 5 6  Next page →

Back to top | Article view | linux.debian.user


csiph-web