Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #179998 > unrolled thread
| Started by | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| First post | 2017-04-12 13:20 +0200 |
| Last post | 2017-05-04 19:20 +0200 |
| Articles | 20 on this page of 111 — 11 participants |
Back to article view | Back to linux.debian.user
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 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-15 19:50 +0200 |
| Message-ID | <twzZD-15i-5@gated-at.bofh.it> |
| In reply to | #180167 |
On Sat 15 Apr 2017 at 19:20:58 +0200, Pascal Hambourg wrote: > Le 15/04/2017 à 12:44, Brian a écrit : > > > >simple install=some control of d-i. > >expert install=total control of d-i. > > Expert install gives more control, but is far from granting total control. > The Debian installer still has many automated actions that you cannot > control even in expert mode. I had a feeling while writing that this response might come. It's correct. "much more" instead of "total"? -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-15 21:10 +0200 |
| Message-ID | <twBf3-22A-5@gated-at.bofh.it> |
| In reply to | #180170 |
Le 15/04/2017 à 19:42, Brian a écrit : > On Sat 15 Apr 2017 at 19:20:58 +0200, Pascal Hambourg wrote: >> >> Expert install gives more control, but is far from granting total control. >> The Debian installer still has many automated actions that you cannot >> control even in expert mode. > > I had a feeling while writing that this response might come. It's > correct. "much more" instead of "total"? I would not say "much more", just "more" or even "a bit more".
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-15 21:40 +0200 |
| Message-ID | <twBI5-2gF-3@gated-at.bofh.it> |
| In reply to | #180177 |
On Sat 15 Apr 2017 at 21:04:34 +0200, Pascal Hambourg wrote: > Le 15/04/2017 à 19:42, Brian a écrit : > >On Sat 15 Apr 2017 at 19:20:58 +0200, Pascal Hambourg wrote: > >> > >>Expert install gives more control, but is far from granting total control. > >>The Debian installer still has many automated actions that you cannot > >>control even in expert mode. > > > >I had a feeling while writing that this response might come. It's > >correct. "much more" instead of "total"? > > I would not say "much more", just "more" or even "a bit more". Contrasting "simple install" with "expert install" and "preseeded install" I'd agree and use "more" for "expert install". But that wasn't the original comparison. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-04-15 03:40 +0200 |
| Message-ID | <twkQW-gW-7@gated-at.bofh.it> |
| In reply to | #180136 |
On Fri 14 Apr 2017 at 12:05:38 (-0500), Richard Owlett wrote: > On 04/13/2017 05:55 PM, Brian wrote: > >On Thu 13 Apr 2017 at 20:05:22 +0200, Pascal Hambourg wrote: > > > >>David is right : you don't really boot from the SD card. > > > >The OP never claimed he was booting from the SD card. He particularly > >said he did not install GRUB to the card. > > > >>GRUB is on the HDD. The kernel is on the HDD. Only the root filesystem is on > >>the SD card. > > > >Yes. That's what the linux line says too. > > > > I'll try to clarify some details. > > My installation protocol. > 1. I always use "Expert" as that way the installer will > do fewer things I'm not aware of. > 2. I only install Grub the *first* time I do a Debian install. > By poor design Grub puts the current install first on menu. When are you going to let this drop? On Thu, 05 Jul 2012 08:23:19 (-0500), Richard Owlett wrote: | What I need: | 1. newest install to be on bottom of the list On Sat, 24 Nov 2012 15:33:49 (-0600), Richard Owlett wrote: | The GRUB team made many reasonable design decisions. | Though they match vast MAJORITY of users, their choices annoy me every | time I boot ;< | | What would fit best with my habits is that the precedence of OS to | boot would be | "first installed -> first boot choice" *NOT* "last installed -> first | boot choice". On Sat, 02 Feb 2013 08:47:37 (-0600), Richard Owlett wrote: | The latest installation goes to the top of the displayed list and is | also selected as the default OS to boot. | That is unsatisfactory as the first OS will will always be closest to | a standard install - i.e. most likely to run. On Sun, 24 Jul 2016 13:53:59 (-0500), Richard Owlett wrote: | What I *REQUIRE* is that GRUB2's menu list available OS monotonically | by partition number. For reasons of logic and sanity the menu items | should be in the order of | sda1, sda2, ..., sdaMAX. I could work with sdaMAX, ..., sda2, sda1 . | | The purpose AND rationale SHALL be that the default OS choice *SHALL | BE* the first OS installed. > When experimenting with configuration as I do, the least > likely install to be functional is the latest. > This requires me to run update-grub on the "good" install. > 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. It is simpler to edit only the > fstab of latest install than to edit those for all other > installs each time. > 4. All installs in this thread have been done using DVD 1 of > 13 of Debian 8.6.0 - thus all intrinsically use the same > kernel. > > I've done some additional observations and test installs. > 1. The BIOS of the Lenovo T510 can be directed to boot from > the CD/DVD drive, hard disk, or any attached USB flash > drive. It *cannot* be directed to boot from the SD card. > 2. I did an install to a USB flash drive including installing > Grub2 to the MBR of that flash drive. When selecting the > SD card from the grub menu I see nothing different. > 3. I did a new install to the SD card specifying a different set > of packages and installing grub to the MBR of the SD card. > Once again no behavioral difference. Observation 1 would make that inevitable, wouldn't it. Unless, of course, you stick your SD card in a card reader. These little gizmos used to be bundled with SD cards when you bought them; I don't know if they still are. I have a large one that came free with the first (only) SD card I bought, and a couple of tiny ones that came with SDmicros bought a long while back. The latter also come with converters so that you can put an SDmicro in the SD reader or an SD slot. > Does any of this justify a bug report. Especially as I do not > have the bandwidth to do a netinstall of a pre-release version? You've posted your grub.cfg but I haven't bothered to try and reverse engineer how you produced it. I haven't seen any behaviour yet that I would call a bug. What did you have in mind? You could say whether you think the bug is in the _generation_ of grub.cfg or in its _execution_ when you boot. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | GiaThnYgeia <GiaThnYgeia@openmailbox.org> |
|---|---|
| Date | 2017-04-17 23:20 +0200 |
| Message-ID | <txmdY-5LD-1@gated-at.bofh.it> |
| In reply to | #180136 |
Richard Owlett: > 4. All installs in this thread have been done using DVD 1 of > 13 of Debian 8.6.0 - thus all intrinsically use the same > kernel. Is this with the actual dvd or the image of the 1st DVD on a usb-stick? I assume once everything was installed and rebooted there was an upgrade to the latest Jessie which I am pretty sure incorporated a new version of grub-xxx and updates the grub.cfg based on the current state of that boot. During the installation it asks you to select and confirm where you want grub installed, but when it is upgraded as a package it bases its installation on previous options, except it reviews that the installed systems on partitions are actually there. > Does any of this justify a bug report. Especially as I do not > have the bandwidth to do a netinstall of a pre-release version? If your bug reporting is functional, go ahead it is FREE! :) I am saying this because it only works with the appropriate network/mail setup that Debian dictates. -- "The most violent element in society is ignorance" rEG "Who died and made you the superuser?" Brooklinux "keep rocking in the non-free world" Neilznotyoung
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-18 00:30 +0200 |
| Message-ID | <txnjI-6qF-11@gated-at.bofh.it> |
| In reply to | #180227 |
On 04/17/2017 04:11 PM, GiaThnYgeia wrote: > > > Richard Owlett: >> 4. All installs in this thread have been done using DVD 1 of >> 13 of Debian 8.6.0 - thus all intrinsically use the same >> kernel. > > Is this with the actual dvd or the image of the 1st DVD on a usb-stick? In this case a tautology. > I assume once everything was installed and rebooted there was an upgrade *ERROR* - All is from DVD - I have MINIMAL available band width ;/ > to the latest Jessie which I am pretty sure incorporated a new version > of grub-xxx and updates the grub.cfg based on the current state of that > boot. During the installation it asks you to select and confirm where > you want grub installed, but when it is upgraded as a package it bases > its installation on previous options, except it reviews that the > installed systems on partitions are actually there. > >> Does any of this justify a bug report. Especially as I do not >> have the bandwidth to do a netinstall of a pre-release version? > > If your bug reporting is functional, go ahead it is FREE! :) You err. A spurious bug report may cost me nothing. *HOWEVER* it costs OTHERS!!!!!!!!!!!!! > I am saying this because it only works with the appropriate network/mail > setup that Debian dictates. >
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-16 16:40 +0200 |
| Message-ID | <twTvj-4Lf-1@gated-at.bofh.it> |
| In reply to | #180098 |
On Thu 13 Apr 2017 at 20:05:22 +0200, Pascal Hambourg wrote: > Ok then, here is my full theory. You're not going to like it. > > We now know that the BIOS does not expose the SD card so GRUB cannot see it > and the search command fails and prints the error message. > > But then how does the system on the SD card boot ? > > The purpose of the search command is to set the $root variable value with > the device havind the searched UUID. As it fails, the variable remains > unmodified and keeps its previous value. The menu entry does not set a > default value for $root (which is rather unusual in my experience), so the > current value comes from a previous assignement in grub.cfg. It's probably > the root device of the system owning GRUB on the hard disk drive. $root not being set bothered me. Could this (from grub-pc's changelog.gz) be the reason? * util/grub.d/00_header.in: Only set root variable when GRUB_DRIVE could be identified by update-grub. A way to identify how the OS sees the card is to use 'lsblk' before and after inserting the card in the card reader. What GRUB makes of the OS device could be seen with grub-probe OS_device (/dev/sdc1, say) 'Twould be nice to know. > (In GRUB's shell, you can print the $root value with the "set" command, and > check that this partition contains a /boot/grub/vmlinuz-3.16.0-4-686-pae > file directory with the command "ls /boot/grub".) > > GRUB uses $root as a default device used in paths which do not specify a > device, such as the ones in the linux and initrd commands of the menu entry. > By chance, it seems that this location contains the same kernel as the one > on the SD card, so GRUB can load and boot it from the hard disk drive. But > GRUB passes the SD card partition as the root device root=/dev/mmcblk0p1 to > the kernel command line, so the kernel comes from the disk and the root > filesystem comes from the SD card. Unlike GRUB, the kernel does not rely on > the BIOS to access the SD card. > > David is right : you don't really boot from the SD card. > GRUB is on the HDD. The kernel is on the HDD. Only the root filesystem is on > the SD card. The ultimate outcome gives every sign of success. However, strange (and very often unwelcome) things can happen when the kernels on the HDD and the booting device are different. Upgrading the HDD OS to Stretch while leaving the distribution on the card at Jessie would very likely not lead to a good experience. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-16 17:10 +0200 |
| Message-ID | <twTYm-5aC-9@gated-at.bofh.it> |
| In reply to | #180192 |
On Sun 16 Apr 2017 at 15:31:56 +0100, Brian wrote: > What GRUB makes of the OS device could be seen with > > grub-probe OS_device (/dev/sdc1, say) Correction: grub-probe -d <OS_device> -t drive -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-04-13 19:40 +0200 |
| Message-ID | <tvQSS-6ep-45@gated-at.bofh.it> |
| In reply to | #180067 |
On Thu 13 Apr 2017 at 17:48:41 (+0200), Pascal Hambourg wrote: > Le 13/04/2017 à 13:40, Richard Owlett a écrit : > >On 04/12/2017 02:03 PM, Pascal Hambourg wrote: > >>Le 12/04/2017 à 20:33, Richard Owlett a écrit : > >>>On 04/12/2017 12:13 PM, Pascal Hambourg wrote: > > > >[snip] > >>>>- while the SD card is inserted, in the GRUB menu press "c" to enter a > >>>>GRUB shell and report the result of the "ls" command. > >>> > >>>(hd0) (hd0, msdos9) (hd0, msdos8) (hd0, msdos7) (hd0, msdos6) > >>>(hd0, msdos5) (hd0, msdos1) (hd1) (hd1, msdos1) > >> > >>Some BIOS expose a removable media only when booting from it, so my > >>theory was that your BIOS did not expose the SD card and GRUB could > >>not see it. The result of ls proves me wrong. > >> > >>Can you also report the output of "ls (hd1,msdos1)" to check what GRUB > >>sees of the partition on the card ? > > > >It gives the partitioning description, UUID, and label of the USB flash > >drive that was plugged in. It is FAT formatted and used to exchange > >information with my Windows machine. > > USB drive ? Then (hd1) is not the SD card ? If you boot with no USB > drive plugged in, there is no (hd1), right ? Then the SD card does > not appear as a usable device for GRUB and my twisted theory may > still be correct after all. This is just a guess. The OP says they "booted to the SD card". So presumably the SD card was plugged in, and we have seen mention of /dev/mmcblk0p1 which means it was plugged in when Grub made the grub.cfg file. But I'm not yet convinced that the machine is actually able to boot from an SD card (unless you put it in a USB card reader). The boot stanza contains: search --no-floppy --fs-uuid --set=root 380e2a6d-f851-4fd1-9db2-869a0982b511 [...] linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1 initrd /boot/initrd.img-3.16.0-4-686-pae So it's possible that the kernel and initrd are coming from the USB stick that the OP has left in, or even the hard drive. I normally expect to see search --no-floppy --foo --set=root bar [...] linux /boot/vmlinuz-... root=foo=bar where foo depends on whether you're using /dev/ or UUID or LABEL, and bar is the value appropriate to foo. That's not what the OP posted. Also their response > It gives the partitioning description, UUID, and label of the USB > flash drive that was plugged in. It is FAT formatted and used to > exchange information with my Windows machine. sadly lacks the actual information asked for as is often the case. What is the UUID/LABEL of the USB device? I'm not bothered about the Windows machine. > >>>Any suggested reading on the "BASH like shell" I just used? > >> > >>The GRUB manual at <https://www.gnu.org/software/grub/manual/grub.html> > > > >It was what prompted me to ask ;/ > > Sorry, I do not know any better documentation. I'm surprised the OP isn't best qualified to answer this question; battling with Grub goes back at least five years. Not being expert with Grub myself, I don't know how it reacts to a failure during the search. Just a quick glance at my own cfg shows that there are "set root" commands very early on in the file. So, again I'm guessing, this may explain where the kernel is being read from: one of those early commands has given Grub a fallback device. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-13 21:10 +0200 |
| Message-ID | <tvShX-7kd-5@gated-at.bofh.it> |
| In reply to | #180094 |
On Thu 13 Apr 2017 at 12:28:58 -0500, David Wright wrote: > Not being expert with Grub myself, I don't know how it reacts to a > failure during the search. Just a quick glance at my own cfg shows For the third time in this thread: GRUB reacts by shrugging its shoulders and booting whatever the linux and initrd say. If they are not sensible you can forget about booting. You can judge the importance of a search line in your grub.cfg after doing this. This is so easy to test. Just do some deletions by editing the GRUB menu when it appears. Anything between if....fi would do for a start. > that there are "set root" commands very early on in the file. So, > again I'm guessing, this may explain where the kernel is being > read from: one of those early commands has given Grub a fallback > device. What effect a USB hub or card reader has on the booting process I do not know. It could be a factor. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | songbird <songbird@anthive.com> |
|---|---|
| Date | 2017-04-12 21:30 +0200 |
| Message-ID | <tvw7L-64-5@gated-at.bofh.it> |
| In reply to | #180014 |
Richard Owlett wrote: ... ran across http://forums.debian.net/viewtopic.php?f=17&t=128777 not sure if will help or not, but does point to what i was thinking (bios, uefi, partition issue or module not being loaded by grub). ... > Any suggested reading on the "BASH like shell" I just used? > My initial DuckDuckGo search was *NOT* encouraging ;/ > If retirement is not for learning, what use is it? a simple thing like a "help" or "?" command working would be great huh? :) i ended up at the grub website trying to figure things out. i think hitting tab key once or twice may give full list of commands available. i don't want to reboot right now to find out... songbird
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-13 13:50 +0200 |
| Message-ID | <tvLqa-2qX-7@gated-at.bofh.it> |
| In reply to | #180021 |
On 04/12/2017 02:11 PM, songbird wrote: > Richard Owlett wrote: > ... > > ran across http://forums.debian.net/viewtopic.php?f=17&t=128777 > not sure if will help or not, but does point to what i > was thinking (bios, uefi, partition issue or module not > being loaded by grub). It will take me a while to visually parse that page to make it legible. Its miss-use of graphics is a prime example of why I avoid blogs in favor of mailing lists and USENET groups. YMMV ;)
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-12 21:30 +0200 |
| Message-ID | <tvw7L-64-9@gated-at.bofh.it> |
| In reply to | #180014 |
On Wed 12 Apr 2017 at 13:33:02 -0500, Richard Owlett wrote:
> On theory "too much better than too little" I see:
> <begin quote>
> ### BEGIN /etc/grub.d/20_linux_xen ###
>
> ### END /etc/grub.d/20_linux_xen ###
>
> ### BEGIN /etc/grub.d/30_os-prober ###
> menuentry 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' --class gnu-linux
> --class gnu --class os $menuentry_id_option
> 'osprober-gnulinux-simple-380e2a6d-f851-4fd1-9db2-869a0982b511' {
> insmod part_msdos
> insmod ext2
> if [ x$feature_platform_search_hint = xy ]; then
> search --no-floppy --fs-uuid --set=root
> 380e2a6d-f851-4fd1-9db2-869a0982b511
> else
> search --no-floppy --fs-uuid --set=root
> 380e2a6d-f851-4fd1-9db2-869a0982b511
> fi
> linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1
> initrd /boot/initrd.img-3.16.0-4-686-pae
> }
> <end quote>
GRUB is content to boot whatever is on the SD (as you observe) so must
be happy enough with the stanza above; there is no problem with booting
there. Actually, GRUB only uses
linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1
and
initrd /boot/initrd.img-3.16.0-4-686-pae
to get everything up and running. Without those two lines you would not
be booting.
So try this:
When the GRUB menu displays press the "e" key and remove the
search --no-floppy --fs-uuid --set=root 380e2a6d-f851-4fd1-9db2-869a0982b511
Then press the "F10" key. Can you still boot? Do you get the onscreen
message you are concerned about?
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2017-04-13 17:20 +0200 |
| Message-ID | <tvOHn-4KC-1@gated-at.bofh.it> |
| In reply to | #180022 |
On 04/12/2017 02:23 PM, Brian wrote:
> On Wed 12 Apr 2017 at 13:33:02 -0500, Richard Owlett wrote:
>
>> On theory "too much better than too little" I see:
>> <begin quote>
>> ### BEGIN /etc/grub.d/20_linux_xen ###
>>
>> ### END /etc/grub.d/20_linux_xen ###
>>
>> ### BEGIN /etc/grub.d/30_os-prober ###
>> menuentry 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' --class gnu-linux
>> --class gnu --class os $menuentry_id_option
>> 'osprober-gnulinux-simple-380e2a6d-f851-4fd1-9db2-869a0982b511' {
>> insmod part_msdos
>> insmod ext2
>> if [ x$feature_platform_search_hint = xy ]; then
>> search --no-floppy --fs-uuid --set=root
>> 380e2a6d-f851-4fd1-9db2-869a0982b511
>> else
>> search --no-floppy --fs-uuid --set=root
>> 380e2a6d-f851-4fd1-9db2-869a0982b511
>> fi
>> linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1
>> initrd /boot/initrd.img-3.16.0-4-686-pae
>> }
>> <end quote>
>
> GRUB is content to boot whatever is on the SD (as you observe) so must
> be happy enough with the stanza above; there is no problem with booting
> there. Actually, GRUB only uses
>
> linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1
>
> and
>
> initrd /boot/initrd.img-3.16.0-4-686-pae
>
> to get everything up and running. Without those two lines you would not
> be booting.
>
> So try this:
> When the GRUB menu displays press the "e" key and remove the
>
> search --no-floppy --fs-uuid --set=root 380e2a6d-f851-4fd1-9db2-869a0982b511
>
> Then press the "F10" key. Can you still boot? Do you get the onscreen
> message you are concerned about?
>
>
Something *ODD* is going on in that area.
As that string appears in both the "then" and "else" clauses I:
1. tried removing them individually leaving a blank line.
For both cases grub crashed with a syntax error.
2. removed entire if-then-else-fi construct.
That booted without the "device not found" message.
3. changed the last digit of the UUID.
That demonstrated that the "then" clause was the one executed.
4. used gparted to change the UUID of the SD card.
That crashed in ways seemingly unrelated to anything.
I'm going to update my preferred preseed.cfg and reinstall to
both /dev/sda1 and the SD card in a reproducible way.
What log files should I save after each test boot.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-13 18:30 +0200 |
| Message-ID | <tvPN8-5sD-17@gated-at.bofh.it> |
| In reply to | #180064 |
On Thu 13 Apr 2017 at 10:17:23 -0500, Richard Owlett wrote: > On 04/12/2017 02:23 PM, Brian wrote: > > > >So try this: > >When the GRUB menu displays press the "e" key and remove the > > > > search --no-floppy --fs-uuid --set=root 380e2a6d-f851-4fd1-9db2-869a0982b511 > > > >Then press the "F10" key. Can you still boot? Do you get the onscreen > >message you are concerned about? > > > Something *ODD* is going on in that area. > As that string appears in both the "then" and "else" clauses I: > 1. tried removing them individually leaving a blank line. > For both cases grub crashed with a syntax error. I'm not sure this would be a good idea without reconstructing the if...fi phrasing. > 2. removed entire if-then-else-fi construct. > That booted without the "device not found" message. This is a much better technique than the one I suggested, which is a little unclear as to what to remove. A GRUB stanza does not need a search line or what is between if and fi. It can be useful, but the linux and initrd lines are sufficient much of the time. > 3. changed the last digit of the UUID. > That demonstrated that the "then" clause was the one executed. This confirms your second point. > 4. used gparted to change the UUID of the SD card. > That crashed in ways seemingly unrelated to anything. > I'm going to update my preferred preseed.cfg and reinstall to > both /dev/sda1 and the SD card in a reproducible way. I'm afraid I'm not going to try this. Off the top my head I'd expect the device still to boot with a suitable GRUB stanza "Erroneous" isn't a bad description of the message. As you describe it the boot proceeds whether or not the "ENTER" key is pressed. It would be interesting to know why the UUID is not recognised. Perhaps a small bug in GRUB? It is a minor inconvenience. A LABEL is the way to go but I think 'update-grub' will only generate a search line with a UUID in it. > What log files should I save after each test boot. The issue arises with GRUB. The will be no records in the logs as the system has not booted. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | GiaThnYgeia <GiaThnYgeia@openmailbox.org> |
|---|---|
| Date | 2017-04-17 22:50 +0200 |
| Message-ID | <txlKV-5k6-3@gated-at.bofh.it> |
| In reply to | #180014 |
Richard Owlett: > On 04/12/2017 12:13 PM, Pascal Hambourg wrote: >> Le 12/04/2017 à 17:14, Richard Owlett a écrit : >>> >>> Whether initiated after power-on OR a restart the observed sequence is: >>> 1. Appearance of the Grub2 menu with a choice of 4 instances of Debian. >>> 2. Select instance installed on the SD card. >>> 3. Screen clears, this message appears against the Debian 8 background. >>> error: no such device: 380e2a6d-f851-4fd1-9db2-869a0982b511. >>> Press any key to continue ... >>> 4. Otherwise the instance of Debian on the SD card boots routinely. >> >> This is a GRUB error message which cannot find the UUID specified in a >> "search" command. >> >> In order to investigate, can you >> - report the menu entry code for the SD card system in >> /boot/grub/grub.cfg (the one from the system on the hard drive owning >> GRUB, not the one on the SD card) ; > > On theory "too much better than too little" I see: > <begin quote> > ### BEGIN /etc/grub.d/20_linux_xen ### > > ### END /etc/grub.d/20_linux_xen ### Wild shot of the blind helping the half blind here. If the uuid is correct but if sda and sdb are reversed the wrong partition is found on the crossed uuid. I couldn't reproduce it myself but there had been a couple of instances while messing with usb-mem-sticks and installing grub to the stick as if it was a real disk, that this happened. Booting from the bios command to choose between hdd or usb seemed more consistent than when bios was adjusted to automatically try to boot from usb if it existed before trying the hdd. I don't know whether your setup can relate. To make matters worse when the usb installed grub was crossed and the hdd became sdb I updated grub-pc which goes through the whole procedure of seeking installed systems on all drives and updating the usb-installed grub to where now it would seek hd installed systems in sdb! So now the correct booting order would not work and the default primary installed debian was not found on sda1 as it did not exist on the hd. So, I am speculating such crossing may have taken place between store and home that produced the mistake, sda and sdb were reversed. Now if you have 1 hdd and 2 usb drives/mem-sticks things can get really messy as grub is silly enough to think this is a fixed order of things. As you unplug sdb and reboot sdc has now become sdb even though it was never moved. But how did you install something on the usbdisk? Was it from a live usb-stick? If that stick is gone then your installed grub thinks that the HD is the usb/live stick that installed debian. I hope this makes some sense to someone. Does a usb memory stick really have an MBR? It may act like it. -- "The most violent element in society is ignorance" rEG "Who died and made you the superuser?" Brooklinux "keep rocking in the non-free world" Neilznotyoung
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2017-04-18 21:00 +0200 |
| Message-ID | <txGw3-1bd-21@gated-at.bofh.it> |
| In reply to | #180226 |
Le 17/04/2017 à 22:46, GiaThnYgeia a écrit : > > I hope this makes some sense to someone. Not to me. TL;DR. > Does a usb memory stick really have an MBR? Yes, if you write an MBR structure into the first sector.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-04-18 21:50 +0200 |
| Message-ID | <txHiq-1Gh-29@gated-at.bofh.it> |
| In reply to | #180253 |
On Tue 18 Apr 2017 at 20:55:43 +0200, Pascal Hambourg wrote: > Le 17/04/2017 à 22:46, GiaThnYgeia a écrit : > > > >I hope this makes some sense to someone. > > Not to me. TL;DR. TL is "too loquacious"? DR is "drivel"? -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2017-04-19 05:50 +0200 |
| Message-ID | <txOMV-6En-1@gated-at.bofh.it> |
| In reply to | #180256 |
[Multipart message — attachments visible in raw view] — view raw
On 2017-04-18 at 15:42, Brian wrote: > On Tue 18 Apr 2017 at 20:55:43 +0200, Pascal Hambourg wrote: > >> Le 17/04/2017 à 22:46, GiaThnYgeia a écrit : >>> >>> I hope this makes some sense to someone. >> >> Not to me. TL;DR. > > TL is "too loquacious"? DR is "drivel"? In case you're not being facetious: "TL;DR" is standard Internet shorthand for "too long; didn't read". The reaction which it represents is a peculiar combination of "frequently understandable" with "usually kind of rude". -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | GiaThnYgeia <GiaThnYgeia@openmailbox.org> |
|---|---|
| Date | 2017-04-19 09:50 +0200 |
| Message-ID | <txSxd-Ad-39@gated-at.bofh.it> |
| In reply to | #180261 |
The Wanderer: > On 2017-04-18 at 15:42, Brian wrote: > >> On Tue 18 Apr 2017 at 20:55:43 +0200, Pascal Hambourg wrote: >> >>> Le 17/04/2017 à 22:46, GiaThnYgeia a écrit : >>>> >>>> I hope this makes some sense to someone. >>> >>> Not to me. TL;DR. Question: You have a system with everything on a HD /dev/sda, you use /dev/sdb a live disk to boot and install debian on /dev/sdc including the grub on /dev/sdc You unplug the live disk and reboot, what will grub do by default, what systems will it show, by default? I did not specify whether there is grub installed on /dev/sda or not, so there are two variations. I suspect based on Bios settings the system will either go to hd or to usb to boot, and that will be sda -- "The most violent element in society is ignorance" rEG "Who died and made you the superuser?" Brooklinux "keep rocking in the non-free world" Neilznotyoung
[toc] | [prev] | [next] | [standalone]
Page 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
Back to top | Article view | linux.debian.user
csiph-web