Fixed what? You need to at least explain the problem.
You apparently had previous install in LVM (but you did not say anything so this is wild guess), so to preserve “home” installer had to preserve existing LVM configuration. This sounds to me exactly what you asked for. If my guess is wrong, then start with providing at least some information about what you had on this disk (you must have had previous Linux, otherwise there were no “home” to preserve).
Previous OS was openSUSE LEAP 42.3 on an 80-gig WD SATA drive with LVM. Three other drives were not part of the LVM.
I’m a bit surprised about the “reading minds” comment. I guess maybe there actually are setups with two or more "/"s and two or more swap files – I was not aware of that.
What I want: 1 80-gig drive with LVM and with only one “/” and only one SWAP, and “/home” preserved as it was before.
linux-qonm:~ # parted -l
Model: ATA WDC WD800JD-75MS (scsi)
Disk /dev/sda: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 80.0GB 80.0GB primary boot, lvm, type=8e
Model: ATA WDC WD5000AAKX-2 (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 500GB 500GB primary ext4 type=83
Model: ATA WDC WD5003AZEX-0 (scsi)
Disk /dev/sdc: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 500GB 500GB primary ext4 type=83
Model: ATA Hitachi HUA72202 (scsi)
Disk /dev/sdd: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 2000GB 2000GB primary ext4 type=83
linux-qonm:~ #
I’ve been up for too many hours for the last week with 42.3; couldn’t get it to connect to LAN. I gave up and installed “15”, now with screwed-up OS drive – but at least it connects with internet.
I sincerely hope for a repair solution but if I have to, I’ll install again. Thanks for your attention and advice…
Well, you did not even mention that your setup is using LVM. Something that is not done by many. And when you do not mention things, but nevertheless assume others know it, that assumes mind reading IMO.
It seems that only /dev/sda is involved in this mess. It is most probably used for LVM
When using LVM, it might be interesting to show some data about your LVM setup
vgdisplay
pvdisplay
lvdisplay
But it looks that:
/dev/mapper/system-root0 is used as your root file system /.
and
/dev/mapper/system-home is used on /home.
For swap you can see what the system uses with
swapon
but I guess that it is /dev/mapper/swap0.
It seems that you have originaly installed 42.3 telling the installer to use LVM. For some reason (because the deafults the installer uses or because you said the installer to do so), there was unused space left in the Volume Group.
Then you installed 15.0, but somehow you missed to tell the installer to do that on the existing Logical Volumes, thus the installer created new Logical Volumes for / and Swap. And the old ones are still there.
Now what do you want?
Re-install on the “old” LVs" (be carefull not to repeat the error), so that you then can remove the root0 and swap0 LVs, this will give you the same situation as with 42.3.
Or just remove the “old” LVs root and swap, which will leave you with some holes on your VG.
You can think this over but in the mean time give us please the LVM information asked for above, so we can have an idea about what is where and how large everything is.
Or just remove the “old” LVs root and swap,
yes, names of volumes do not really matter, “root0” is no worse than “root”
which will leave you with some holes on your VG.
existing volumes can be enlarged to utilize all available space.
Yes, all and much more is possible, but I do not have the impression that the OP knows much about LVM (I still wonder why he started using it). I only wanted to get him starting to think about what he wanted at 42.3 installation and what he wants now. I (like you I have no doubt) want him to understand a bit more about what he has else it will be problematic to help him on his path to what he wants.
E.g., I am not sure he wants “enlarging”. Why weren’t the42.3 one the size they are with space left?
My suggestion was in fact not the ultimate solution, but an image on what reuslt he wants. When he says, yes I want the 15.0 system on LV of the size they are now on root0 and swap0 and the others removed, we still can offer him commands to remove and move, etc.etc. BUT IMHO he needs a simple view to understand.
Wow, it is always difficult to help people who painted themselves into a corner.
Could you all please stop hammering me about “not providing information about LVM”?
O.K.
linux-qonm:/home/chuck/Downloads # vgdisplay
File descriptor 93 (socket:[1466199]) leaked on vgdisplay invocation. Parent PID 16244: -bash
File descriptor 96 (socket:[1466200]) leaked on vgdisplay invocation. Parent PID 16244: -bash
File descriptor 106 (socket:[1463943]) leaked on vgdisplay invocation. Parent PID 16244: -bash
File descriptor 107 (socket:[1463944]) leaked on vgdisplay invocation. Parent PID 16244: -bash
--- Volume group ---
VG Name system
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 9
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 5
Open LV 4
Max PV 0
Cur PV 1
Act PV 1
VG Size 74.50 GiB
PE Size 4.00 MiB
Total PE 19072
Alloc PE / Size 19072 / 74.50 GiB
Free PE / Size 0 / 0
VG UUID QmHk8O-uMBV-dzV8-FZqO-XkF3-rI5T-PnlPmB
linux-qonm:/home/chuck/Downloads #
linux-qonm:/home/chuck/Downloads # pvdisplay
File descriptor 93 (socket:[1466199]) leaked on pvdisplay invocation. Parent PID 16244: -bash
File descriptor 96 (socket:[1466200]) leaked on pvdisplay invocation. Parent PID 16244: -bash
File descriptor 106 (socket:[1463943]) leaked on pvdisplay invocation. Parent PID 16244: -bash
File descriptor 107 (socket:[1463944]) leaked on pvdisplay invocation. Parent PID 16244: -bash
--- Physical volume ---
PV Name /dev/sda1
VG Name system
PV Size 74.50 GiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 19072
Free PE 0
Allocated PE 19072
PV UUID 8aoZDF-hdyk-1Ng3-LWXN-o6Z6-j4ah-eDGf28
linux-qonm:/home/chuck/Downloads #
linux-qonm:/home/chuck/Downloads # lvdisplay
File descriptor 93 (socket:[1466199]) leaked on lvdisplay invocation. Parent PID 16244: -bash
File descriptor 96 (socket:[1466200]) leaked on lvdisplay invocation. Parent PID 16244: -bash
File descriptor 106 (socket:[1463943]) leaked on lvdisplay invocation. Parent PID 16244: -bash
File descriptor 107 (socket:[1463944]) leaked on lvdisplay invocation. Parent PID 16244: -bash
--- Logical volume ---
LV Path /dev/system/root
LV Name root
VG Name system
LV UUID ABXm1N-QlRz-Syln-wWVB-fO4y-hgLg-7EAA61
LV Write Access read/write
LV Creation host, time install, 2017-09-20 00:14:06 -0700
LV Status available
# open 1
LV Size 20.00 GiB
Current LE 5120
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 1024
Block device 254:2
--- Logical volume ---
LV Path /dev/system/swap
LV Name swap
VG Name system
LV UUID yMpdh0-ePxc-ErFW-AyaO-EjkJ-UPpT-z0ehpz
LV Write Access read/write
LV Creation host, time install, 2017-09-20 00:14:07 -0700
LV Status available
# open 0
LV Size 7.00 GiB
Current LE 1792
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 1024
Block device 254:3
--- Logical volume ---
LV Path /dev/system/swap0
LV Name swap0
VG Name system
LV UUID e32cmQ-vjf0-pTFn-12EV-fc4n-yRRy-i3yIzi
LV Write Access read/write
LV Creation host, time install, 2018-08-02 22:53:07 -0700
LV Status available
# open 2
LV Size 6.81 GiB
Current LE 1743
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 1024
Block device 254:0
--- Logical volume ---
LV Path /dev/system/home
LV Name home
VG Name system
LV UUID 01jyLP-fc5r-f6yy-jVi3-ckDf-cbLP-u2STDL
LV Write Access read/write
LV Creation host, time install, 2018-08-02 22:53:08 -0700
LV Status available
# open 1
LV Size 20.69 GiB
Current LE 5297
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 1024
Block device 254:4
--- Logical volume ---
LV Path /dev/system/root0
LV Name root0
VG Name system
LV UUID gHzWfT-sDOu-NKnk-c1Vv-SAQ0-H6Qi-Q2C3AV
LV Write Access read/write
LV Creation host, time install, 2018-08-02 22:53:11 -0700
LV Status available
# open 1
LV Size 20.00 GiB
Current LE 5120
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 1024
Block device 254:1
linux-qonm:/home/chuck/Downloads #
linux-qonm:/home/chuck/Downloads # swapon
NAME TYPE SIZE USED PRIO
/dev/dm-0 partition 6.8G 0B -1
linux-qonm:/home/chuck/Downloads #
Indeed, I took the “default” settings. I didn’t see any way to specify which Logical Volumes the installer would use. I presumed it would use what it would already “saw”.
Silly me.
The only setting I could see was the one to avoid formatting the “/home” partition.
What I want (again): 1 80-gig drive with LVM and with only one “/” and only one SWAP, and “/home” preserved as it was before.
Looks like I’m going to be starting over with another install.
Is anyone here familiar enough with the installer to tell me how to avoid the extra partitions during installation? (Yes, I’m still going to use LVM.)
Thanks, guys. I’m signing off for now … it’s almost 5 AM here, I’ve lost too much sleep over this thing, am about to do a faceplant on my keyboard…
I’ll check in tomorrow.
We looked at it. Your first post did not say that it came from Yast partitioner. You left us to guess that.
One of your file systems is mounted under “/run/media”. That one was probably mounted by your desktop environment and not part of the normal system mounting. Some desktop environments mount everything that they can find as you login.
I would go with the suggestion of arvidjaar in post #6 in this thread – remove the LVM volumes that you don’t currently need, and possibly use the freed space to expand the volumes that you do need.
The last thing the partitioning in the installer does is provide you with a list of what it plans to do. Pay attention to this screen and change anything that does not look right. My guess is that you selected a new install rather than an upgrade. This would produce what we see since the installer assumes you want a second OS installed an upgrade would have used existing partitions. Again the partition scheme screen would tell you that. DON"T just click passed it.
Then you will have ~27 GB unused at the beginning of the VG.
When having 42.3, you had ~27 GB unused at the end of the VG. Thus the new situation will not really differ much from what you had. And like before you will be able to use that unused space at your will later.
BTW, you seem to be a bit irritated by our questioning. Please take into account that, as said earlier, you provided some quoted information without any reference to it’s source. And add to that that when advising about partitions, LVs and the like and file systems, one has to be very careful. Thus please understand that people will very much like to have a good insight in what your situation is. Just posting some careless advice upon which you brake your system is most probably not what you want.
Hi Gogalthorp:
Thank you! This is exactly the advice I need.
The Installer at that point in the install is not clear about what to choose unless you already know the end result of each choice.
Please take into account that I’m sitting in front of my Linux machine which is the only one I’ll go online with.
My XP box contains only bookkeeping, etc. information, some other programs I need that only run in Windows, and never goes online.
Where did you think I got the information if not from the Yast Partitioner in my own machine?
Would I find “LVM” in the partitioner in a “normal”/“usual”/“conventional” install? I don’t know. I don’t remember seeing it before using LVM.
I had thought that the use of LVM was pretty clear in the original post, unless you may have thought I copied it from the internet. If I had done that, I certainly would have described it as such.
Check the “Volume Management” page in the Partitioner.
So yes, I am a bit irritated about the continual ragging about not telling you I’m using LVM. I had thought that to be fairly obvious since it was right there in the “code” on this page.
I’m going to venture a guess as to how we get into these situations;
When you guys check out the conditions in an OS, the first place you go to is the cli.
When I have to do the same, I go to the gui, and if beyond my understanding, I have to ask someone, and I give thanks for you guys who take the time to help us with these things.
But I think maybe because of that point-of-view your first thought is not of something I may have found in the gui - in this case the YaST Partitioner.
I hope we can get past this issue and focus on openSUSE LEAP15.0
I think we walk very different paths here. You seem to think that the majority of others use YaST > System > Partitioner all the time. This is not the case. Thus all we saw (in the first post) was a list that could be of your own design, typed down in a neat way, but nevertheless it could be just your own interpretation of things we did not see. And nobody of those that answered first recognized it as a sort of copy from the YaST partitioner.
And, I repeat, we are all very suspicious about the data shown to use (as somebody once on the forums formulated it: we are unbelievers, we want to see computer text) because we do not want to give bad advice that brakes your system. Thus better asked thrice then misunderstanding.
And please, when you more or less ask for it, You asked for help with a repair, but people could not see anything broken. And I repeat, in that famous list of you in post #1, I can not see any problem.
So, be glad that people try, in different ways, by asking different questions to you, to find out what this is all about and what you think is the problem.
Now, from me, enough if this.
I am much more interested if you now, using the rather common adivise above, have removed those two LVs and are satisfied with the result. Becaus that is what all here tried to achieve.
Yes, this is likely true. So we are more familiar with the output from “fdisk -l” and “parted -l” than with Yast partitioner.
I have often used Yast partition, and so have other folk who responded to this post. However, Yast partitioner was recently redesigned, so we are less familiar with the new design.
Hi, Mr. Rickert (and everyone else in this conversation):
Re: a quote from a previous post;
Thus all we saw (in the first post) was a list that could be of your own design, typed down in a neat way
Just hopefully to “clear the air”, the information in the first post was indeed “typed down” in as close an approximation as I could of what I saw in the YaST Partitioner, since the Partitioner does not allow “select” and “copy”. Re-creating it as text was my only option, since I haven’t the facility with the cli that I would like to have.
In short, we use the methods available to us within the limits of our knowledge and ability.
I also was not aware that having more than one root and more than one swap partition was “normal”. Now I have learned.
Thanks, everyone, for looking at this. I have, since my last post, re-installed LEAP 15.0 from scratch and am working out the subsequent details…
It is not normal. It all depends on what you tell the installer to do. Installers do not read your mind and only make best guess on how to install it is up to the user to determine that is what they want and change it if it is not.
