Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #171616 > unrolled thread
| Started by | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| First post | 2016-08-31 16:20 +0200 |
| Last post | 2016-09-01 11:20 +0200 |
| Articles | 6 on this page of 26 — 12 participants |
Back to article view | Back to linux.debian.user
Jessie (8.0) slow to boot Richard Owlett <rowlett@cloud85.net> - 2016-08-31 16:20 +0200
Re: Jessie (8.0) slow to boot Greg Wooledge <wooledg@eeg.ccf.org> - 2016-08-31 16:30 +0200
Re: Jessie (8.0) slow to boot Richard Owlett <rowlett@cloud85.net> - 2016-08-31 17:00 +0200
Re: Jessie (8.0) slow to boot Greg Wooledge <wooledg@eeg.ccf.org> - 2016-08-31 17:10 +0200
Re: Jessie (8.0) slow to boot Greg Wooledge <wooledg@eeg.ccf.org> - 2016-08-31 18:10 +0200
Re: Jessie (8.0) slow to boot Richard Owlett <rowlett@cloud85.net> - 2016-08-31 18:10 +0200
Re: Jessie (8.0) slow to boot Felix Miata <mrmazda@earthlink.net> - 2016-08-31 17:50 +0200
Re: Jessie (8.0) slow to boot Richard Owlett <rowlett@cloud85.net> - 2016-08-31 18:30 +0200
Re: Jessie (8.0) slow to boot Felix Miata <mrmazda@earthlink.net> - 2016-08-31 18:50 +0200
Re: Jessie (8.0) slow to boot Richard Owlett <rowlett@cloud85.net> - 2016-09-01 13:00 +0200
Re: Jessie (8.0) slow to boot Gene Heskett <gheskett@shentel.net> - 2016-09-01 16:00 +0200
Re: Jessie (8.0) slow to boot David Wright <deblis@lionunicorn.co.uk> - 2016-08-31 20:50 +0200
Problem source verified -Re: Jessie (8.0) slow to boot Richard Owlett <rowlett@cloud85.net> - 2016-09-01 14:10 +0200
Re: Problem source verified -Re: Jessie (8.0) slow to boot Darac Marjal <mailinglist@darac.org.uk> - 2016-09-01 14:20 +0200
Re: Problem source verified -Re: Jessie (8.0) slow to boot David Wright <deblis@lionunicorn.co.uk> - 2016-09-01 16:50 +0200
Re: Problem source verified -Re: Jessie (8.0) slow to boot Michael Biebl <biebl@debian.org> - 2016-09-02 09:50 +0200
Re: Problem source verified -Re: Jessie (8.0) slow to boot David Wright <deblis@lionunicorn.co.uk> - 2016-09-02 17:40 +0200
Re: Problem source verified -Re: Jessie (8.0) slow to boot Nicolas George <george@nsup.org> - 2016-09-02 17:50 +0200
Re: Problem source verified -Re: Jessie (8.0) slow to boot David Wright <deblis@lionunicorn.co.uk> - 2016-09-02 21:40 +0200
Re: Problem source verified -Re: Jessie (8.0) slow to boot Curt <curty@free.fr> - 2016-09-02 18:30 +0200
Re: Problem source verified -Re: Jessie (8.0) slow to boot claude juif <claude.juif@gmail.com> - 2016-09-01 16:00 +0200
Re: Problem source verified -Re: Jessie (8.0) slow to boot Richard Owlett <rowlett@cloud85.net> - 2016-09-02 15:10 +0200
Re: Jessie (8.0) slow to boot Dominic Knight <dominicknight@gmx.com> - 2016-08-31 18:20 +0200
Re: Jessie (8.0) slow to boot Darac Marjal <mailinglist@darac.org.uk> - 2016-08-31 17:10 +0200
Re: Jessie (8.0) slow to boot Alan McConnell <alan@his.com> - 2016-08-31 20:50 +0200
Re: Jessie (8.0) slow to boot Darac Marjal <mailinglist@darac.org.uk> - 2016-09-01 11:20 +0200
Page 2 of 2 — ← Prev page 1 [2]
| From | claude juif <claude.juif@gmail.com> |
|---|---|
| Date | 2016-09-01 16:00 +0200 |
| Subject | Re: Problem source verified -Re: Jessie (8.0) slow to boot |
| Message-ID | <scAH7-2zZ-5@gated-at.bofh.it> |
| In reply to | #171663 |
[Multipart message — attachments visible in raw view] — view raw
2016-09-01 14:02 GMT+02:00 Richard Owlett <rowlett@cloud85.net>: > On 8/31/2016 11:25 AM, Richard Owlett wrote: > >> On 8/31/2016 10:44 AM, Felix Miata wrote: >> >>> Richard Owlett composed on 2016-08-31 09:58 (UTC-0500): >>> ... >>> >>>> Aug 31 09:13:32 deb8-2ndtry systemd[1]: Job >>>> dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x2daf89\x2d33ba51934630.de >>>> >>>> >>>> Aug 31 09:13:32 deb8-2ndtry systemd[1]: Timed out waiting for >>>> device dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x >>>> Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for >>>> /dev/disk/by-uuid/0a344714-ae06-43ed-af89-33ba5193463 >>>> Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for >>>> Swap. >>>> >>> >>> Which was installed last, Squeeze, or Jessie? You can expect this >>> message trying to boot the earlier installed installation after >>> having done the later install. Unless you take affirmative action >>> to deny it, an existing swap partition used by the earlier >>> installation will be reformatted by the later installation. >>> Reformatting creates a new UUID, thus making the UUID referring >>> to it in the earlier installation's fstab invalid. The earlier >>> needs to have its fstab edited to use the correct swap partition >>> UUID, or volume label, or device name, if swap is actually >>> desired or needed. >>> >> >> There may be some subtle problems still lurking somewhere which >> show up only for people like me doing many installs of *nearly* >> identical systems. >> >> Commenting out the line in /etc/fstab DID allow it to boot >> without warning messages. >> >> However,taking into account Darac's comments, does this now mean >> that the machines are now operating without a swap partition? >> >> IIRC the current instance of Jessie on the laptop was the >> chronologically the last OS installed so by the comments in this >> thread should not have had the problem. The laptop is my >> designated "Guinea pig" so I'll do a fresh install to see if >> problem persists. >> > > My procedure was: > 1. Using the Live edition of Gparted, remove all partitions on hard disk. > 2. Using install DVD 1 of Debian 8.0.0 > a. install Debian to /dev/sda1 > b. create swap on /dev/sda2 > 3. Verify Debian boots without problems > 4. Using the same DVD > a. install Debian to /dev/sda5 > b. re-create swap on /dev/sda2 > 5. Attempt to boot both instances > a. Booting the install on /dev/sda1 generates the warning message and > use > of free shows swap does not exist. > b. Booting the install on /dev/sda5 generates no warning message and use > of free shows swap does exist. > > I believe this justifies a bug report against the installer. > It is not a bug. If you want to use the same swap partition with multiple install, then you should not reformat the swap partition. How can the installer guess that you want to use the same swap partition for multiple OS. (reinstalling the same system is a common task -- but i always wonder why ...) Maybe you want to add warning message before formatting like "Care, a swap partition already exist at /dev/sdaXX, would you like to reformat it ?" IMO, you should know what you're doing. It's not the installer job to "think" for you ! The installer just does what you ask him to do ! > My expected behavior would be to check to see if a swap area already > exists before "creating" a swap partition. Especially since replacing a > swap partition can break a previously functioning install in a multi-boot > situation. > By the way you can have a look at debootstrap if you want multiple debian install, (only one booted OS, but multiple Debian OS accessible with chroot) If you want more powerfull way of doing this you can check lxc, and docker. Today multiboot seem really deprecated (unless you have windows) > > Comments? > > Regards,
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2016-09-02 15:10 +0200 |
| Subject | Re: Problem source verified -Re: Jessie (8.0) slow to boot |
| Message-ID | <scWoh-8kI-19@gated-at.bofh.it> |
| In reply to | #171666 |
On 9/1/2016 8:56 AM, claude juif wrote: > > By the way you can have a look at debootstrap if you want > multiple debian install, (only one booted OS, but multiple Debian > OS accessible with chroot)If you want more powerfull way of doing > this you can check lxc, and docker. Today multiboot seem really > deprecated (unless you have windows) I looked at https://en.wikipedia.org/wiki/LXC and http://www.docker.com/. Neither of them, nor virtual machines &/or chroot, are suitable for me. Multiboot is explicitly the tool of choice. Think of Windows(TM) as only tip of iceberg.
[toc] | [prev] | [next] | [standalone]
| From | Dominic Knight <dominicknight@gmx.com> |
|---|---|
| Date | 2016-08-31 18:20 +0200 |
| Message-ID | <scgp4-4D4-7@gated-at.bofh.it> |
| In reply to | #171617 |
On Wed, 2016-08-31 at 10:24 -0400, Greg Wooledge wrote: > On Wed, Aug 31, 2016 at 09:16:00AM -0500, Richard Owlett wrote: > > > > What's going on? > > Are the messages that scroll past preserved anywhere? > > When booting with systemd, the boot messages are stored in RAM > automatically, and can be viewed by running "journalctl" as root. > I'd definitely start there. If it is the swap partition, it has probably been given a new UUID when you installed a new/additional version of Debian. I use gparted to look up the current UUID and then paste that over the relevant UUID in /etc/fstab Take care when using both gparted and writing to fstab. Regards.
[toc] | [prev] | [next] | [standalone]
| From | Darac Marjal <mailinglist@darac.org.uk> |
|---|---|
| Date | 2016-08-31 17:10 +0200 |
| Message-ID | <scfjk-40K-49@gated-at.bofh.it> |
| In reply to | #171616 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, Aug 31, 2016 at 09:16:00AM -0500, Richard Owlett wrote: >I have Jessie installed on a desktop and a laptop. They both take >about 105-110 seconds to boot. Squeeze on the desktop takes ~15 >seconds to boot. > >Most of the delay seems to be in something that states approximately >"A start job is running for dev-disk-by\x2duuid?????.device (ttttt}" >Where ????? is a long alphanumeric string > ttttt is a timer display >That is followed by two message identified as "Warning" in bright >yellow.[they pass by to fast to read]. > >What's going on? UUID is considered to be the most reliable way to locate a disk, given modern kernels' asynchronous device discovery. It is no longer considered "safe" to assume that /dev/sda is your main hard drive. On small systems, it probably won't change, but if you have several drives, they can start at different times, and the order in which they get enumerated may change. Therefore, Linux now tends to refer to disks by UUID (Universally Unique IDentifier). The boot process now involves various methods for finding that UUID and, as you see above, waiting some considerable time for the device to appear (the device might be dependant on another host, or it might be on a relatively slow bus such as USB or SCSI-1 etc) Now, there are a number of reasons why you might get the messages above, but one common 'gotcha' is that systemd is more strict about what devices are needed to boot the system. Basically, systemd assumes that, if you've listed a device in /etc/fstab and you've not told it otherwise, then that device is necessary for the system to boot. The two main ways to disabuse it of this notion are to either add the option "noauto", in which case the device will not get mounted at boot but you can still invoke "mount /path/to/mountpoint" once the system is up, or else you can add the option "nofail" which tells systemd that a failure to mount the device should not lead to a failure of the service (and thus booting can continue). Another reason, and this may well be something you're hitting, is that the UUID doesn't match any devices on the system. UUIDs are, typically, created by mkfs (or mkswap). If you reformat a partition, the UUID will probably change, and your /etc/fstab might be pointing to the old device. If, say, you create filesystems and restore a backup to them, then /etc/fstab can be pointing to UUIDs which no longer exist; if that's the case, then consider using LABEL=something in /etc/fstab instead. UUIDs are reliable, but they are computer generated. Sometimes a maintainer-generated identifier is better. >Are the messages that scroll past preserved anywhere? >TIA > > -- For more information, please reread.
[toc] | [prev] | [next] | [standalone]
| From | Alan McConnell <alan@his.com> |
|---|---|
| Date | 2016-08-31 20:50 +0200 |
| Message-ID | <sciKe-5ZB-13@gated-at.bofh.it> |
| In reply to | #171616 |
On Wed, Aug 31, 2016 at 09:16:00AM -0500, Richard Owlett wrote:
> I have Jessie installed on a desktop and a laptop. They both take about
> 105-110 seconds to boot. Squeeze on the desktop takes ~15 seconds to boot.
My jessie install also takes a long time to boot. A lot of it
is because of attempts to start/stop/do something with
COMRESET. Eventually, after a minute, the boot process 'gives
up'.
What is COMRESET? What does it do? can I get rid of these
attempts?
TIA for anticipated information/help.
Alan McConnell
--
Alan McConnell : http://globaltap.com/~alan/
Memory says, "I did that." Pride replies, "I could not have
done that." Eventually, Memory yields.(Friederich Nietzsche)
[toc] | [prev] | [next] | [standalone]
| From | Darac Marjal <mailinglist@darac.org.uk> |
|---|---|
| Date | 2016-09-01 11:20 +0200 |
| Message-ID | <scwk9-7Sa-7@gated-at.bofh.it> |
| In reply to | #171646 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, Aug 31, 2016 at 02:49:05PM -0400, Alan McConnell wrote: >On Wed, Aug 31, 2016 at 09:16:00AM -0500, Richard Owlett wrote: >> I have Jessie installed on a desktop and a laptop. They both take about >> 105-110 seconds to boot. Squeeze on the desktop takes ~15 seconds to boot. > My jessie install also takes a long time to boot. A lot of it > is because of attempts to start/stop/do something with > COMRESET. Eventually, after a minute, the boot process 'gives > up'. > > What is COMRESET? What does it do? can I get rid of these > attempts? A quick search of the internet leads me to https://askubuntu.com/questions/174137/should-i-be-concerned-about-comreset-errors-with-my-ssd which suggests that COMRESET is the kernel RESETing COMmunications with an ata device (a hard disk). If you have one message, such as the linked poster had, then it's probably not a problem. If you see a lot of them, then you may have a bad cable (or a bad hard disk, or a bad disk controller). > >TIA for anticipated information/help. > >Alan McConnell > >-- >Alan McConnell : http://globaltap.com/~alan/ > Memory says, "I did that." Pride replies, "I could not have > done that." Eventually, Memory yields.(Friederich Nietzsche) > -- For more information, please reread.
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.debian.user
csiph-web