There’s some really weird stuff going on with my system and I’m going nuts trying to get it to work right…
I have four SSD drives installed in my system.
sda contains Windows.
sdb is the drive with the usual uefi, swap, root and home partitions.
sdc has three partitions for data.
sdd has four partitions for data.
If I add the partitions in /etc/fstab and reboot, the system will not come up and I need to give it the root password and use vim to comment out the partitions on sdc and sdd and reboot.
If I add the data partitions back, one at a time, I can get it to reboot however there is a 3 minute udev process during boot each time and the system is unstable until I again do a cold reboot. When I finally get to the last partition, I can’t get it to boot at all.
So, I changed the settings in /etc/fstab and now, after three cold boots. the system comes up just fine but without the data drives mounted. I can use Konsole and mount the partitions without problems.
Here is /etc/fstab:
bart@UNIVAC:~> cat /etc/fstab
# This is the main drive for UNIVAC Currently sdb
LABEL=LEAP-SWAP swap swap defaults 0 0
UUID=59d8fa9a-61b3-4bca-8793-77b51ad832df / ext4 defaults 0 1
UUID=2199df87-4e56-4534-9f44-08da582bfcab /home ext4 data=ordered 0 2
LABEL=UEFI /boot/efi vfat codepage=437 0 2
# This is the second drive Currently sdc
UUID=566979f5-22dd-49c3-90ca-7a13d9ddbab5 /mnt/Videos ext4 noauto,nofail,user,data=ordered 0 2
UUID=8dd702f5-1277-4232-b2e7-b9d6f51f810c /mnt/Pictures ext4 noauto,nofail,user,data=ordered 0 2
UUID=fdb7bee5-4e34-4596-b1fd-c089f334f5de /mnt/Spare-0 ext4 noauto,nofail,user,data=ordered 0 2
# This is the third drive Currently sdd
UUID=fda7c74b-4c4c-4404-80cf-896d689ac830 /mnt/Modelrailroad ext4 noauto,nofail,user,data=ordered 0 2
UUID=84d13a86-54bf-4de9-b1b6-8e24e7c887fc /mnt/Develop ext4 noauto,nofail,user,data=ordered 0 2
UUID=5ffe3a27-2774-442a-a07b-afcd45618d7b /mnt/Spare-1 ext4 noauto,nofail,user,data=ordered 0 2
UUID=c2396264-a9d4-46b8-93e1-ea6ea80c69b3 /mnt/Spare-2 ext4 noauto,nofail,user,data=ordered 0 2
# This is the drive on the Server.
Server:/home/common /mnt/Server nfs noauto,nofail,user 0 0
bart@UNIVAC:~>
Now, I need to automate the mount process after KDE is completely up, so I created a .desktop file and installed it in /etc/xdg/autostart.
bart@UNIVAC:~> cat /etc/xdg/autostart/DriveMount.desktop
[Desktop Entry]
Comment[en_US]=
Comment=
Exec=mount Videos
Exec=mount Pictures
Exec=mount Spare-0
Exec=mount Modelrailroad
Exec=mount Develop
Exec=mount Spare-1
Exec=mount Spare-2
Exec=mount Server
GenericName[en_US]=
GenericName=
MimeType=
Name[en_US]=DriveMount
Name=DriveMount
Path=
StartupNotify=true
Terminal=false
TerminalOptions=
Type=Application
X-DBUS-ServiceName=
X-DBUS-StartupType=
X-KDE-SubstituteUID=false
X-KDE-Username=
X-KDE-autostart-after=panel
bart@UNIVAC:~>
It mounts only the last drive in the list. Are you allowed only one exec= statement in a .desktop file?
The sdb site suggests putting an executable script in ~/.kde/Autostart however this directory doesn’t exist. So I did a find for ?utostart and found three potential places: ~/.config/autostart, /usr/share/autostart and /etc/xdg/autostart.
Should I create an executable script, place it somewhere like /usr/bin and call it from the .desktop file in /etc/xdg/autostart?
The man page for fstab says the order of the entries is important. Could I have one wrong?
What is going on with that 3 minute udev start process that takes place when I boot and why is my system unstable for two or three cold boots after?
All suggestions are more than welcome, they’re encouraged!
A couple of other things. I replaced the main drive (sdb) with a new drive and did a fresh install and configuration, saving only the data in /home. the drive sdc had been in use for some time, so I replaced it as well. The processor in this machine is an Intel 8 core, 16 thread thingy so I wonder if there isn’t some race condition during boot as there’s a lot of stuff going on at the same time.
Bart
