Problem Booting an install after partition work using GPARTED

sudo fdisk -l[sudo] password for root: 
Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500NM0011     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000001

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sdb1  *           64    204863    204800   100M  7 HPFS/NTFS/exFAT
/dev/sdb2          208845 174288895 174080051    83G  7 HPFS/NTFS/exFAT **<<Windows 10**
/dev/sdb3       531282528 976769071 445486544 212.4G  7 HPFS/NTFS/exFAT **<<Windows 7**

**This is a SATA HDD I added to do a fresh install**
Disk /dev/sdc: 149.01 GiB, 160000000000 bytes, 312500000 sectors
Disk model: ST3160815AS     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd0f4738c

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sdc1            2048  16779263  16777216    8G 82 Linux swap / Solaris
/dev/sdc2  *     16779264 100665343  83886080   40G 83 Linux   "/"
/dev/sdc3       100665344 312499999 211834656  101G 83 Linux   '/home'

**THIS DISK is the PATA HDD on a PCI card - I did some partiton work using gparted, now won't boot!**
Disk /dev/sda: 149.05 GiB, 160041885696 bytes, 312581808 sectors
Disk model: WDC WD1600AAJB-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xfb30b87c

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1            2048  16779263  16777216    8G 82 Linux swap / Solaris
/dev/sda2  *     16779264 121143295 104364032 49.8G 83 Linux         **<< Should be '/**'
/dev/sda3       121145344 311871487 190726144 90.9G 83 Linux        **<< Should be '/home**'

Supporting images
This shows problm install mounted at /run/media/…https://susepaste.org/56855326

From Yast Partioner <** NO Mount points shown**https://susepaste.org/4720205

From YaST Partioner showing Newer SATA HDD install with correct mount points.https://susepaste.org/56976050

The first image is the PATA HDD showing ‘/’ and ‘/home’ as being on /run/media/Bill/‘UUID’ numbers.

Can I correct the PATA HDD mount points in GRUB or some other config file?

I have made a ‘blank’ partition on the main HDD with Windows on it, and plan on installing Leap 15.3 there. (KEEPING Windows 10 and 7)
I want to keep the PATA drive active as PLAN B, but need it to be recognized by the boot system.
Currently when I try to boot it, eventually a bunch of longish code that ends with ‘has no systemd installed’ and gives me a few CLI things, but basically all I can do is boot the SATA drive(it has a few problems I didn’t know about, and want to remove the drive from the tower).
Leaving the (planned) install on the 500GB Windows HDD and the /dev/sda in case of problems.

I have been through the GRUB2 Tutorial, and my eyes are glazing.

I need to get rid of /dev/sdc. keep /dev/sda. keep /dev/sdb(Windows)

Iwas very late at night, and I made the mistake of going to bed instead of ‘checking’ the boot(s). No excuses, I screwed things up.

Let me know what else ya’ll may need to help.
TIA
Bill_L

Hi
Remove sdc then? Unplug both sdb and sdc. Install linux on your sda disk and setup it up. Once that’s done, plug in sdb again and ensure the BIOS is set to boot sda, then when in linux run as root the command os-prober and see what it detects as far as the windows installs.

In a nut shell unplug your windows drive and the drive you don’t want and install linux on the one you want and get that working. Can sort out the windows booting later.

Windows boots fine, in fact that is where I SHOULD have doen the partionting work in AOMIE(Faster and easier to work with).
There is blank partition on the Windows drive that I want to put Linux on, so I need to keep it.

What I DO need is to get the Leap I have on the PATA drive working again. That is the problem disk now. But i has my data on it that I need to keep. BUT it won’t boot!
Probably because I did the partitioning work in gparted instead of just leaving it alone!

I tried to take HDD sdc out of the machine, but then I get NO Leap boot at all. Just that ‘systemd in not installed’ message.
My guess is grub got really messed up during the gparted partitioning stuff, and I don’t know how to fix it.

I can backup the ‘/home’ on the PATA HDD(/dev/sda3), and install fresh there again. But will have to be careful about what I bring back in from the backup. THat is the the Leap 15’s that inisist on starting a session for UID 65534 which takes over 2 minutes to boot, and even longer to shutdown.

Thanks for the response.

I’m in Leap on /dev/sdc
‘os-prober’ output is:

sudo os-prober
[sudo] password for root:  
/dev/sda2:openSUSE Leap 15.3:openSUSE:linux
/dev/sdb1:Windows 10:Windows:chain

so the system recognizes that the install on the PATA drive as being Leap on /dev/sda
It is there but I can’t get it to boot.

What exactly does “some partiton work” mean? When did you do “some” work, before or after installing openSUSE on it? Where is the Grub that’s intended to boot it installed? What does the fstab on it contain? What does lsblk -f for it show?

I will do my best to answer your questions.

‘ some partition work ‘ means I shrunk the ‘/home’ partition AND APPLIED THAT OPERATION using gparted
Then I ‘added(merged?) the now empty space from the shrunk partition’ to ‘/‘ AND APPLIED THAT OPERATION using gparted.
Gparted indicated each operation was SUCCESSFUL.

The “some work” was LONG after installing Opensuse on it!

I don’t know where ‘the GRUB’ that boots that OS is(WAS) located, since I can’t boot it to try to find it.
Again, since it won’t boot, I can’t find fstab on that HDD!

Don’t I have to be in that OPERATING SYSTEM to do the **lsblk -f **?
The output for this CLI on my laptop does not shows if partitions are ‘swap’ ‘/home’, or ‘/‘. for /dev/sda/.
I’m on my iPad now, and if you still want to see it, I’ll get on a working Leap and paste the results here!

IF that HDD would actually boot, I would not have posted the problem of it NOT booting.
And how to find and edit GRUB.

But moot point now! I am in process of doing a fresh install on that PATA HDD, and the GRUB2 boot menu STILL has it shown.

SO where do I look for GRUB?
the Windows HDD?
the used SATA HDD that does have a bootable Leao 15.3?

Right now I just need to find GRUB to edit it to remove /dev/sda/,
or does that happen in ‘fstab’?

Here are the output for the** lsblk -f** command:(if you’re still interested in them).

@localhost:~> lsblk -fNAME   FSTYPE FSVER LABEL                   UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                                             
├─sda1 swap   1                             10eeefbd-69d9-4817-bde9-b8510b793867                
├─sda2 ext3   1.0                           4d138ffa-b9ff-4263-9518-77a5be7aadfc                
└─sda3 ext3   1.0                           cf6e80ae-40b3-4252-a285-45d72525695d   71.8G    15% /run/media/Bill/cf6e80ae-40b3-4252-a285-45d72525695d
sdb                                                                                             
├─sdb1 ntfs         System Reserved         1A0CB3280CB2FE37                                    
├─sdb2 ntfs         Windows 10 Home Release 0FCB1B290FCB1B29                                    
└─sdb3 ntfs         Windows 7 64 Home       ACB2B4EEB2B4BDE0                                    
sdc                                                                                             
├─sdc1 swap   1                             d0b0f5b7-e063-4cc2-a770-d737673deb29                [SWAP]
├─sdc2 ext4   1.0                           28c84369-7b44-4d67-b063-c33988c1c7bd   29.6G    19% /
└─sdc3 ext4   1.0                           581f4039-96f9-4267-be88-33b4d1698ba5   84.6G     9% /home
sr0 

I HAVE NO idea what that ‘sr0’ at the end of the output is!
/dev/sda2 is suppose to be ‘/’

This is the 'current state of ‘fdisk -l’ showing where the ‘*’ boot indicators are located.

localhost:~> sudo fdisk -l
**Disk /dev/sda: 149.05 GiB, 160041885696 bytes, 312581808 sectors**
Disk model: WDC WD1600AAJB-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xfb30b87c

**Device****Boot****    Start****      End****  Sectors**** Size****Id****Type**
/dev/sda1            2048  16779263  16777216    8G 82 Linux swap / Solaris
/dev/sda2  *     16779264 121143295 104364032 49.8G 83 Linux
/dev/sda3       121145344 311871487 190726144 90.9G 83 Linux


**Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors**
Disk model: ST500NM0011      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000001

**Device****Boot****    Start****      End****  Sectors****  Size****Id****Type**
/dev/sdb1  *           64    204863    204800   100M  7 HPFS/NTFS/exFAT
/dev/sdb2          208845 174288895 174080051    83G  7 HPFS/NTFS/exFAT
/dev/sdb3       531282528 976769071 445486544 212.4G  7 HPFS/NTFS/exFAT


**Disk /dev/sdc: 149.01 GiB, 160000000000 bytes, 312500000 sectors**
Disk model: ST3160815AS      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd0f4738c

**Device****Boot****    Start****      End****  Sectors**** Size****Id****Type**
/dev/sdc1            2048  16779263  16777216    8G 82 Linux swap / Solaris
/dev/sdc2  *     16779264 100665343  83886080   40G 83 Linux
/dev/sdc3       100665344 312499999 211834656  101G 83 Linux 

It is back up and booting. STILL has that UID_65534 in the boot process.
i put the install USB stick in and went through an ‘UPGRADE’.

Now to bring in my backed up things.

I will do another post about fstab & GRUB(still need to know how to manage(manipulate GRUB).

Get and use bootinfoscript to find out a lot about where your various bootloaders live and how they are configured.

Thanks, looks useful for future BIll-screwups, eh?

Glad you got it to work. FWIW, that “sr0” is your optical drive, DVD or similar.