The laptops went in clean and no after install problems that I can see so far.
But the HP Compaq dc7700 desktop is another story.
With 15 it booted well and fairly fast even with having a windows storage drive mounted at boot.
Seldom did I get messages about ‘ada4’(the storage drive) and a LOT of messages about ‘a start job running for LVM2 monitoring …’, and another ‘start job running…’ related to a drive(the storage drive probably). I have looked for the exact phrasing in the log file(s), but haven’t found them yet/
After the upgrade, my boot times have gone up significantly(from 25 to 40 seconds to over a minute or more) due to all the ‘start jobs running for???..’ what ever reason.
I have since removed the windows storage drive from fstab, and now I am still getting all that ‘start job running for LVM2…’ , AND a popup after it finally boots asking for root OK mounting that drive.
I don’t want it mounted at boot until I can get the boot process running smoothly again(wish I knew how!), and I don’t want that popup asking for root ID.
Twice I was informed I needed to input root ID, or Control-D to continue,but that just got me a command line prompt.
Both of the laptops and ‘storage partitions’ mounted at boot, and neither of them are having boot problems.
So I am considering starting all over with a bootable USB for Leap15.1 to see if that helps the long and mostly problem plagued boot on the desktop. No big deal, I would use the NET iso file so it gets all the latest it needs to do the install.(another thread asks about the USB creation for MBR/UEFI).
So, advice->> continue investigating or re-install and start from scratch?
Or is there a way to ‘zypper dup’ it again to reinstall?
The HP problem might be solvable if you paste here content of fstab, and output from blkid taken with the external HD connected and powered on. Please remember to use code tags. Because of the PATA host, output from lsscsi and more might be required before this is over. New installation might be easier, but what fun is not trying?
linux-ipxi:~ # lsscsi
[1:0:0:0] disk ATA WDC WD1600AAJB-0 7H00 /dev/sda **<<<< Leap on this HDD**
[2:0:0:0] disk ATA ST500NM0011 BB4A /dev/sdb **<<<< Windows HDD**
[3:0:0:0] disk ATA SAMSUNG HD080HJ/ 0-51 /dev/sdc **<<<< Storage HDD**
[3:0:1:0] cd/dvd PLDS DVD+-RW DH-16A6S YD12 /dev/sr0
OK, after I finish an ‘upgrade’ over the top of 15.1 I had already upgraded from a USB DVD version.
I was/am having a lot of app crashes and the system was very slow at times, and often got unresponsive.
I am trying to find out how to do a disk surface check in Leap. I think that 80GB storage drive has a problem, but not sure.
It has problems mounting/unmounting, sometimes taking over 10 minutes. Gparted took about 12 minutes to read it’s single partition. I will probably disconnect it from the MOBO to see if it is in fact a problem child.
I took out the 80GB storage HDD, It would not mount nor unmount in Leap with out causing problems.
I tried booting up WIn10, and it took over 15 minutes to boot! No system problems after it did boot, just slow and sluggish like I was having in Leap.
So I removed the 80GB HDD, and Leap and Win10 start well and run well. Time will tell.
I did do an ‘upgrade’ to Leap 15.1 using a USB DVD version, and it now starts with out the ‘start job running for …’ messages.
I should have expected a hardware problem!
I will still get you the information you asked for if you still want it.
It’s a delicate balance between making changes (like removing drives, changing configurations, etc) and understanding consequences.
So, for instance it’s likely that when you booted Windows that last time, it might have gone through a silent diskchk if the file system was suspected corrupted or if any changes were made to the boot sequence or file system. And, Windows boot “learns” its boot profile, so will gradually work out its own problems over maybe 5 boots before you’ll see something permanent.
There is a tool that can help analyze your openSUSE bootup problems… At least identify which sequences are causing more problems than others…
