Above, Steve Langasek (vorlon) wrote on 2009-10-10:
"Effectively, this is by design; filesystems that aren't required
to bring up the desktop should not block the desktop, they should be
handled in parallel."
My boot disk partition is DB001_F1, which contains the system files and
${HOME} directory.
However, my installation is configured such that the all the other
directories under the ${HOME} directory are on a second partition,
namely
Desktop -> /DB001_F2/home/ericthered.Desktop
Not every time, but often enough, when I do a pushbutton boot (cold) or
a warm boot (restart), it appears that the system mounts the ${HOME}
directory as if it were my Desktop, and I have to rebuild my Desktop
from scratch (please don't ask me the steps, because I always have to
muddle thru to get it back to how I want it.
Is there some setting, configuration or switch that I can set to force
the boot process to wait until it can access all disks properly, BEFORE
it attempts to build the GDM environment ?
System: Host: OasisMega1 Kernel: 5.4.0-67-generic x86_64 bits: 64 Desktop:
MATE 1.24.0
Distro: Ubuntu 20.04.2 LTS (Focal Fossa)
Machine: Type: Desktop Mobo: ASUSTeK model: M4A78-E v: Rev 1.xx serial:
101048580000313
BIOS: American Megatrends v: 2603 date: 04/13/2011
CPU: Quad Core: AMD Phenom II X4 810 type: MCP speed: 800 MHz
min/max: 800/2600 MHz
Graphics: Device-1: AMD RS780D [Radeon HD 3300] driver: radeon v: kernel
Display: server: X.Org 1.20.9 driver: ati,radeon unloaded:
fbdev,modesetting,vesa
resolution: 1440x900~60Hz
OpenGL: renderer: AMD RS780 (DRM 2.50.0 / 5.4.0-67-generic LLVM
11.0.0) v: 3.3 Mesa 20.2.6
Info: Processes: 248 Uptime: 24m Memory: 2.92 GiB used: 1.24 GiB
(42.5%) Shell: bash inxi: 3.0.38
Filesystem Size Used Avail Use% Mounted on
/dev/sdb3 192G 16G 167G 9% /
/dev/sdb7 289G 153G 122G 56% /DB001_F2
/dev/sdb8 289G 246G 29G 90% /DB001_F3
/dev/sdb9 289G 258G 17G 95% /DB001_F4
/dev/sdb12 193G 29G 154G 16% /DB001_F5
/dev/sdb13 193G 149G 35G 82% /DB001_F6
/dev/sdb14 289G 166G 109G 61% /DB001_F7
/dev/sdb4 92G 35G 53G 40% /DB001_F8
/dev/sdc2 99G 60M 94G 1% /site/DB003_F1
/dev/sdc3 357G 67M 338G 1% /site/DB003_F2
/dev/sda2 108G 7.0G 96G 7% /site/DB004_F1
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/439604
Title:
boot process isn't paused while fsck runs on partition: boot process
is completed with fsck running in the background preventing partition
from mounting
Status in Release Notes for Ubuntu:
Fix Released
Status in mountall package in Ubuntu:
Fix Released
Status in util-linux package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: usplash
I had a problem mounting my /dev/sdb1 partition the last couple of
times after booting up Ubuntu. I got the following error when trying
to mount the partition:
mount: /dev/sdb1 already mounted or /media/data busy
so I tried issuing the following command and I could see that fsck was
running in the background, without having notified me, checking
/dev/sdb1, and not while showing the splash screen and a progress bar
like it usually does:
rune@runescomp:~$ sudo fuser -m /dev/sdb1
/dev/sdb1: 804
rune@runescomp:~$ ps aux | grep 804
root 804 5.0 3.4 72528 71164 ? D 21:29 0:50 fsck.ext3 -a
/dev/sdb1
rune@runescomp:~/Desktop$ lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10
rune@runescomp:~/Desktop$ apt-cache policy usplash
usplash:
Installed: 0.5.39
Candidate: 0.5.39
Version table:
*** 0.5.39 0
500 http://archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status
ProblemType: Bug
Architecture: i386
Date: Wed Sep 30 21:54:05 2009
DistroRelease: Ubuntu 9.10
MachineType: . .
NonfreeKernelModules: kvm_intel kvm fglrx
Package: usplash 0.5.39
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic
root=UUID=55bcb986-d698-4aea-a3bb-c581262ea713 ro quiet splash elevator=deadline
ProcEnviron:
LANG=en_DK.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: usplash
Uname: Linux 2.6.31-11-generic i686
UsplashConf:
# Usplash configuration file
# These parameters will only apply after running update-initramfs.
xres=1920
yres=1440
dmi.bios.date: 05/26/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: IP35 Pro XE(Intel P35-ICH9R)
dmi.board.vendor: http://www.abit.com.tw/
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: System Enclosure Manufacter
dmi.chassis.version: OEM
dmi.modalias:
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/26/2008:svn.:pn.:pvrSystemVersion:rvnhttp//www.abit.com.tw/:rnIP35ProXE(IntelP35-ICH9R):rvr1.0:cvnSystemEnclosureManufacter:ct3:cvrOEM:
dmi.product.name: .
dmi.product.version: System Version
dmi.sys.vendor: .
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/439604/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
