Bug 4442

More info will be required to figure out what is going on.
Please create a text file, and attach it to this bug report
with the output from the following commands.

sfdisk -l -x /dev/sda>bug.txt
pvs >>bug.txt
lvs >>bug.txt
blkid >>bug.txt

You'll probably have to install sfdisk first.  The
commands should all be run as root.

CC: (none) => davidwhodgins

OK, will do later.
However i have now run gparted from a live USB to clean up strange partitions, and possibly that made the trick, see

https://bugs.mageia.org/show_bug.cgi?id=4449#c2

System is now bootable but need a bit of work

Created attachment 1513 [details]
As per request in #2

However, as said in previous post, this is now after i have fixed it using gparted.
Sorry i was in an hurry to get it working, should have made a disk image or this dump earlier...

Screenshots of gparted @ #2 uploaded at https://bugs.mageia.org/show_bug.cgi?id=4449#c8 and 9

I'm going to close this bug as old, since the problem was
fixed by repartitioning, before the info was provided.

Feel free to reopen, if you think this bug can be recreated
so more info can be gathered.

I will add that it if you're using lvm, it is usual to use
one single partition, for all of the filesystems, which makes
shrinking one filesystem so you can grow another, easier.

If all of the partitions are being assigned to the same volume
group, the only waste is partitioning overhead.  If they are in
different volumegroups, the changing filesystem sizes will
require repartitioning.

I do have three separate lvm partitions, but each one is used
by a different linux installation, with 7 filesystems in each
physical volume.

Status: NEW => RESOLVED
Resolution: (none) => OLD

HM, OK
See if i have time to stress test some time

Yes LVM is used so it is easy to change size of partitions inside.
I even have both cauldron and mga 1 in same LVM on my main machine, and separate real /boot partitions outside LVM.

But when running OSes which can not share LVM, one cannot transfer space between systems easily, and sometimes it is needed, especially when using expensive pe rmegabyte SSD and need several systems.

LVM volume groups can be assembled of several real partiions on same or different drives.

So therefore it is a good idea to divide the disk in several partitions that can be used when needed in the differens OS:es LVM:s or used directly by i.e stupid Microsoft OS:es.

- REOPENING -
Same machine, same drive, same installation, after some use;

Using MCC -> diskdrake i have successfully done online extending of both /home and / in that LVM when needed. :)

But now it ran out of space in that LVM and it was not possible to schrink swap, so i removed it, recreated a smaller swap, and extended other.

But after reboot, it failed.

I attach a screenshot below.  You can see it is writing about both swap and swap1. The name i gave the swap partition is is swap.  When i created the swap it suggested "1" as name (within the vg), but i changed it to swap.  Possibly some part of diskdrake appended the "1".


I have almost never handled LVM manually so i have no idea what file may be wrong.
Maybe some partition setup file is in /boot ?


__Another possible problem:
I also changed the small NTFS partition i had to share with win XP, into a part of LVM vg. (i forgot the term)  When i look at the disk in gparted I (booted on a live USB) it identifies the other physical parts of the LVM, but not the last one added, it is just "unknown" type.

I can keep the drive untouched for a while now.
Tell me what i can do.

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

Created attachment 2213 [details]
Fail finding volumes in LVM - wrong naming

Did you use swapoff before trying to resize the swap?

Anyway, the problem is that the swap partition has a different uuid.

You'll have to edit the kernel parameters at startup, and remove the
resume= parm, so that it won't look for the swap.

After you reboot, as root run "dracut -f", to update the initrd file
with the new uuid for the swap.

If that works, please reclose the bug.

I pressed button to unmount swap, still no button to resize appeared.
Therefor i deleted it and made a new smaller one.
I thinnk it is a bug in itself that that did not work.

I can try to get some info, and also be happy if it came back to life, but need help.

Removing the resume parameter made it not complain on Resume operation.

However the rest is the same, it seem not to find home, and drops to debug shell.

I can easily access /boot by plugging the drive into another system, but do not know what to fix.

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

2x no reply, closing as old.

This report confuses me, btw, to me it looks like two seperate issues, the one in the description and the one in comment 7

Feel free to reopen if needed, but please be very explicit about:

* was the installer issue still valid for Mageia 2 final? If so please attach:
/root/drakx/report.bug.gz

* is the issue using diskdrake in an *installed* system still valid? If so:
* for which version(s) of Mageia (as far as you can check or know)?

Status: REOPENED => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD

The common thing in #0 and #7 is that i set diskdrake to do something, and after reboot it shows the result was something else.

I guess it get confused by something. Probably pretty uniqe, and i think developers time is better spent somewhere else, at least until the problem shows up again.