OpenSuse won't boot after installing gparted

Hello,

I tried to install gparted on OpenSuse, which worked. The tool starts without problems. But then I rebooted the system and it is corrupt.
It seems that gparted has replaced fstab with mtab, which causes several problems because it is a cloned OpenSuse-installation where I replaced disk-ids in fstab with the UUIDs. Now something must be completely misconfigured, because OpenSuse tries to boot from disks that don’t exist anymore and keeps hanging.

I tried to edit mtab, but it was not possible to open the file. So I deleted it, because the system is already broken and in hope it will use the fstab instead. It didn’t work and so I tried to figure out where the fstab/mtab is loaded, but I didn’t suceed. I re-installed grub2 via rescue system but this didn’t help.

Does anybody have experience with this problem or tried the same?

Additional information:
OpenSuse 13.1 64 Bit on HP ProLian ML350p Gen8

best regards,
tolan

No, I doubt that.

Normally you should have both fstab and mtab.
fstab lists what devices are to be mounted and where/how, mtab lists the devices that are mounted.
So do I understand you correctly that you do not have an fstab any more?

Now something must be completely misconfigured, because OpenSuse tries to boot from disks that don’t exist anymore and keeps hanging.

Please, more details.
What tries to boot from disks that don’t exist anymore?
The bootloader?
The kernel?

Where does it hang?
Are there any messages on the screen?

I tried to edit mtab, but it was not possible to open the file.

You cannot edit mtab, that’s controlled automatically by mount.
You have to edit fstab.

So I deleted it, because the system is already broken and in hope it will use the fstab instead.

The system does only use fstab, even if mtab exists.

So, do you have an fstab now or not?
Can you post the content?
And the output of:

fdisk -l

On 2014-11-06 08:46, tolan wrote:
>
> Hello,
>
> I tried to install gparted on OpenSuse, which worked. The tool starts
> without problems. But then I rebooted the system and it is corrupt.

Surely you did something more.

> It seems that gparted has replaced fstab with mtab,

No.

> which causes several
> problems because it is a cloned OpenSuse-installation where I replaced
> disk-ids in fstab with the UUIDs. Now something must be completely
> misconfigured, because OpenSuse tries to boot from disks that don’t
> exist anymore and keeps hanging.

Only fstab is used, if it is missing, you are f-worded. Create it again
from scratch or backup.

(Sorry for language, my health is bad today so I’ll pay it with you :-p )

The mtab file appears to be a copy of what is actually mounted /now/. I
don’t know/remember what keeps it, but it is automatic. No fstab, no
boot, plain simple. Unless the systemd boys decide otherwise :stuck_out_tongue:

> I tried to edit mtab, but it was not possible to open the file.

Don’t even try.

And everything you try is spoiling it further. Just create a new fstab,
from scratch of from backup.

Are you using btrfs? You may have an snapshot.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Ah ok. I thought mtab and fstab are both for the configuration of the mount points and only one of them is used (two concepts for the same thing). The fstab-file does exist with the right entries (UUIDs of the partitions) which did work correctly before the installation of gparted.
I deleted mtab, because i couldn’t edit it and thought the system would stick to fstab, which was not a good idea after your explanation.

Please, more details.
What tries to boot from disks that don’t exist anymore?
The bootloader?
The kernel?

Where does it hang?
Are there any messages on the screen?

It hangs when the green screen of kde appears, after the dialog which says ‘Loading linux-desktop’. If I press END it shows messages:

trying normal resume from /dev/disk/by-id/scsi3600...-part1
resume device from /dev/disk/by-id/scsi3600...-part1 (ignoring)
waiting for device /dev/root to appear: could not find dev/root
want me to fall back to from /dev/disk/by-id/scsi3600...-part2 (Y/n)

I can’t say yes or no, if I press the Y- or N-key or enter there is no repsone.

So, do you have an fstab now or not?
Can you post the content?

As written before the fstab still exists:


UUID=8d50...   swap swap defaults 0 0 
UUID=b3f5e...  / ext4 acl,user_xattr 1 1
UUID=67ff...    /home ext4 acl,user_xattr 1 2
UUID=0ae6... /var ext4 acl,user_xattr 1 2

The output of fdisk:


Disk /dev/sda:300.0GB ...
...
Disk label type: dos
Disk identifier: 0x00030a74

Device       Boot Start End Id System
/dev/sda1                     82 Linux swap/Solaris
/dev/sda2    *               83 Linux
/dev/sda3                     83 Linux
/dev/sda4                     83 Linux

Partition 4 does not start on physical sector boundary

I left out the sector numbers. The last sentence does not sound good or can this be ignored? I googled and it should only affect the perfomance of the hdd.

fstab still exists, but I think I’m f-worded also xD

Don’t even try.

And everything you try is spoiling it further. Just create a new fstab,
from scratch of from backup.

Are you using btrfs? You may have an snapshot.

I don’t use btrfs, but I think building the machine from scratch will be better and faster now…

So far, thanks for your reply and your help.

best regards,
tolan

On 2014-11-06 11:46, tolan wrote:

> I deleted mtab, because i couldn’t edit it and thought the system would
> stick to fstab, which was not a good idea after your explanation.

Deleting mtab should have no effects at all.

> Code:
> --------------------
> trying normal resume from /dev/disk/by-id/scsi3600…-part1
> resume device from /dev/disk/by-id/scsi3600…-part1 (ignoring)
> waiting for device /dev/root to appear: could not find dev/root
> want me to fall back to from /dev/disk/by-id/scsi3600…-part2 (Y/n)
> --------------------

Does “/dev/disk/by-id/scsi3600…-part2” exist? As you fiddled with gparted, maybe it doesn’t, because that is one of the jobs of gparted: create and delete partitions. Maybe it is “/dev/disk/by-id/scsi3600…-part3” or “/dev/disk/by-id/scsi3600…-part1” now. Or some other device altogether.

Which is why 'uuid’s are advantageous…

>> So, do you have an fstab now or not?
>> Can you post the content?
>
> As written before the fstab still exists:
>
> Code:
> --------------------
>
> UUID=8d50… swap swap defaults 0 0
> UUID=b3f5e… / ext4 acl,user_xattr 1 1
> UUID=67ff… /home ext4 acl,user_xattr 1 2
> UUID=0ae6… /var ext4 acl,user_xattr 1 2
>
> --------------------

Please, complete. Do not edit it. There is no privacy breach by posting that.

> The output of fdisk:

I prefer at this time:


lsblk --output NAME,KNAME,RA,RM,RO,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT

And post it complete, please.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

I will check this. It is curious for me that the identifiers sda1 to sda3 are still ok.

the complete output of fstab:


UUID=8d50e417-7f36-4b13-8b75-3dc7fd2e6300   swap swap defaults 0 0
  UUID=b3f5e860-a5cf-4d5a-8ac6-80a9a8409b36  / ext4 acl,user_xattr 1 1
UUID=67ff4e5e-4c0a-4f91-824d-e9af71ca7674   /home ext4 acl,user_xattr 1 2
UUID=0ae6db42-7773-427f-8822-b93fc4b22b9f /var ext4 acl,user_xattr 1 2

I prefer at this time:

lsblk --output NAME,KNAME,RA,RM,RO,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT

This command does not work on my machine, I also tried with less arguments. NAME, KNAME, etc. can not be found? Is there any trick?

Thanks for your help, but I will reinstall our server now. It seems that this is a very strange failure.

You said you installed gparted but never mentioned how and where you got it… If you installed a version ment for another distro you certainly could run into problems.

Last I looked I think gparted is installed by default anyway?? I got it here and don’t remember installing it from the repos.

No, it’s not. I had to install it here. Maybe that depends on the desktop.

However, it is on the live KDE media. So if you installed from live media, it may well be there by default.

Yes I installed by live media

In any case installing via the repos should not damage anything. Installing any other way may

On 2014-11-06 12:56, tolan wrote:

> I will check this. It is curious for me that the identifiers sda1 to
> sda3 are still ok.

Depends on the hardware. They can change, even from session to session.

> the complete output of fstab:

Yep, but without the output of lsblk it can not be verified.

> This command does not work on my machine, I also tried with less
> arguments. NAME, KNAME, etc. can not be found? Is there any trick?

Did you install a minimal server pattern? I never do that, as it
installs close to nothing. You may have to install lsblk separately.

With the minimal pattern you have to add anything else you want manually.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Hello, I installed it via yast out of the standard repositories.

Meanwhile I installed another OpenSuse wit gparted out of the standard repos in a virtual machine without problems. So I think it wasn’t the gparted installation which damaged the operating system.

It was a normal OpenSuse-installation, no minimal configuration.

I reinstalled the server, because doing this was faster than fixing it ^^
I’ll try to reproduce this error in a virtual machine, so I won’t have pressure to get the server ready for work. If I get to know something more I’ll come back here.

Thank you all for your help anyway.

best regards from Germany
tolan