I ran a DVD upgrade from 15.2 to 15.3 without any problems. But when I boot it stops at…
A start job is running for /dev/disk/by-id/ata-TOSHIBA_DT01ACA100_18K536JFS-part1 (15min 44s / no limit)
This is the swap partition. Before I started the upgrade I checked that everything worked by booting 15.2, then rebooted using the installation DVD which I have used successfully on another computer.
Hi
At grub, press e to edit and see if there is a resume=/dev/disk/by-id/ata-TOSHIBA_DT01ACA100_18K536JFS-part1 in the linux or linuxefi line, temporarily remove and press F10 to boot.
Thanks for the speedy response. It worked! Now how do I correct my grub data without disrupting the other distros that use the same swap partition?
Hi
Then if shared swap I would not use any resume… since it might be for a different OS session… edit in YaST Bootloader and if required, use the /dev/sdXn rather than UUID or for each OS check the output from the blkid command and update both grub and /etc/fstab with the correct reference.
That would suggest that I should have provided separate swap partitions. I was trying to keep things simple and had not considered that resuming might be from the wrong O.S. I haven’t had a problem as the other distros are not used frequently, mostly for comparing with Leap.
Thanks for the help and free education.
Hi
On my multiboot systems I do share swap, don’t use resume or sleep/hibernate etc, but on subsequent installs don’t format and it should stay the same UUID…
Odd. When I used /dev/sda1 in /etc/fstab and updated grub removing the resume with YaST it would not mount /dev/sda1 to swap. And even though I told YaST to probe foreign O.S.'es, it did not, only giving me the option to boot 15.3.
Yes I learned not to format the swap partition some time back.
Suddenly the computer locked up and I had to power down. When I restarted it seemed fine except that while checking status I got the following…
# fdisk -l
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: TOSHIBA DT01ACA1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x8b9b7eeb
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 8390655 8388608 4G 82 Linux swap / Solaris
/dev/sda2 * 8390656 71305215 62914560 30G 83 Linux
/dev/sda3 71305216 134219775 62914560 30G 83 Linux
/dev/sda4 134219776 1953525167 1819305392 867.5G f W95 Ext'd (LBA)
/dev/sda5 134221824 155193343 20971520 10G 83 Linux
/dev/sda6 155195392 176166911 20971520 10G 83 Linux
/dev/sda7 176168960 1953525167 1777356208 847.5G 83 Linux
Disk /dev/mapper/TOSHIBA_DT01ACA100_18K536JFS: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x8b9b7eeb
Device Boot Start End Sectors Size Id Type
/dev/mapper/TOSHIBA_DT01ACA100_18K536JFS-part1 2048 8390655 8388608 4G 82 Linux sw
/dev/mapper/TOSHIBA_DT01ACA100_18K536JFS-part2 * 8390656 71305215 62914560 30G 83 Linux
/dev/mapper/TOSHIBA_DT01ACA100_18K536JFS-part3 71305216 134219775 62914560 30G 83 Linux
/dev/mapper/TOSHIBA_DT01ACA100_18K536JFS-part4 134219776 1953525167 1819305392 867.5G f W95 Ext'
/dev/mapper/TOSHIBA_DT01ACA100_18K536JFS-part5 134221824 155193343 20971520 10G 83 Linux
/dev/mapper/TOSHIBA_DT01ACA100_18K536JFS-part6 155195392 176166911 20971520 10G 83 Linux
/dev/mapper/TOSHIBA_DT01ACA100_18K536JFS-part7 176168960 1953525167 1777356208 847.5G 83 Linux
I have never seen “/dev/mapper” before and don’t know what it means. It does not show up on my other box running 15.3. which also has a problem I will post separately. I have three desktops running 15.2 and I am trying to upgrade one at a time.
I have not seen that.
I do see “/dev/mapper” here, but that’s because I use encrypted partitions. In effect, “/dev/mapper” holds virtual disks mapped by other software (RAID or crypto or LVM volumes, for example).
In this case it looks as if there is a virtualized version of your entire hard drive. I have no idea why that happened.
Does the output of “df” indicate that you have those mapped partitions mounted anywhere?
It doesn’t look like my normal mount.
:~> df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 4096 0 4096 0% /dev
tmpfs 3782924 0 3782924 0% /dev/shm
tmpfs 1513172 18004 1495168 2% /run
tmpfs 4096 0 4096 0% /sys/fs/cgroup
/dev/mapper/TOSHIBA_DT01ACA100_18K536JFS-part2 30832548 9517344 19725956 33% /
/dev/mapper/TOSHIBA_DT01ACA100_18K536JFS-part5 10255636 1734340 7980624 18% /home
/dev/mapper/TOSHIBA_DT01ACA100_18K536JFS-part7 873679660 286059128 543170244 35% /home/ion/DATA
tmpfs 756584 64 756520 1% /run/user/1000
Could this have something connected to my changing my BIOS settings from Legacy and UEFI to only Legacy?
Show output of
dmsetup table
dmraid -r
As instructed…
:~> sudo dmsetup table[sudo] password for root:
TOSHIBA_DT01ACA100_18K536JFS-part2: 0 62914560 linear 254:0 8390656
TOSHIBA_DT01ACA100_18K536JFS-part1: 0 8388608 linear 254:0 2048
TOSHIBA_DT01ACA100_18K536JFS-part7: 0 1777356208 linear 254:0 176168960
TOSHIBA_DT01ACA100_18K536JFS: 0 1953525168 multipath 0 0 1 1 service-time 0 1 2 8:0 1 1
TOSHIBA_DT01ACA100_18K536JFS-part6: 0 20971520 linear 254:0 155195392
TOSHIBA_DT01ACA100_18K536JFS-part5: 0 20971520 linear 254:0 134221824
TOSHIBA_DT01ACA100_18K536JFS-part4: 0 2 linear 254:0 134219776
TOSHIBA_DT01ACA100_18K536JFS-part3: 0 62914560 linear 254:0 71305216
:~> sudo dmraid -r
ERROR: ddf1: seeking device "/dev/dm-4" to 18446744073709421056
ERROR: hpt37x: seeking device "/dev/dm-4" to 4608
ERROR: hpt45x: seeking device "/dev/dm-4" to 18446744073709547008
ERROR: pdc: seeking device "/dev/dm-4" to 137438913024
ERROR: pdc: seeking device "/dev/dm-4" to 137438920192
ERROR: pdc: seeking device "/dev/dm-4" to 137438927360
ERROR: pdc: seeking device "/dev/dm-4" to 137438934528
ERROR: sil: seeking device "/dev/dm-4" to 18446744073709289984
no raid disks
I doubt it. But that is certainly weird.
If this happens on future boots, then maybe a bug report is warranted.
Wat is in the fstab?
cat /etc/fstab
Is there file /etc/multipath.conf? Also “systemctl status multipathd.service”?
As instructed.
:~> cat /etc/fstab
UUID=fa051f29-8ce6-40c7-8c3f-ef8711d04603 swap swap defaults 0 0
UUID=fbaa72bd-5a15-4a86-8bb0-1e63465b7229 / ext4 defaults 0 1
UUID=fcc609db-a4f5-4919-8f87-aabfbc896d22 /home ext4 data=ordered 0 2
UUID=836254a0-b918-4ea1-86c3-a22595fe2f03 /home/ion/DATA ext4 data=ordered 0 2
Thanks. Alas, nowadays with the usage of UUIDs that does not say everything, my fault. So we also need e.g.
ls -l /dev/disk/by-uuid/
(And of course what @avidjaar says)
:~> ls /etc/multipath.conf
ls: cannot access '/etc/multipath.conf': No such file or directory
:~> systemctl status multipathd.service
● multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/usr/lib/systemd/system/multipathd.service; disabled; vendor preset: disabled)
Active: inactive (dead)
TriggeredBy: ● multipathd.socket
What about initrd? “lsinitrd /boot/initrd | grep multipath”?