Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm migrating from Fedora Core 1 virtual server to Centos 6 one but at this time I need to enlarge / file system and disk has several partitions so I don't know what steps follow:
/dev/sda1 on / type ext3 (rw)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
/dev/sda7 on /tmp type ext3 (rw)
/dev/sda6 on /usr type ext3 (rw)
/dev/sda2 on /usr/local type ext3 (rw)
/dev/sda5 on /var type ext3 (rw)
/dev/sda8 on /home/appliacation type ext3 (rw)
/dev/sdb1 on /area type ext3 (rw)
I just enlarged physical disk size by vmware but now I have to enlarge fs to /dev/sda1.
Geometry is very complex and Gparted is failed during resize process.
What can you suggest me?
This topic should be moved as it is a user issue software issue. => enlarged physical disk size by vmware
I'm not agree with you because now my environment is as if I disk was cloned to another bigger, infact now there is raw space to end of disk and OS detects real disk size.
Virtual environment or physical environment in this case doesn't affect about resizing. New disk is bigger and it's necessary to resize partitions.
Many years ago physical disk was cloned to new bigger one and afterwards replaced it, the process is the same.
Maybe you should read this somewhat related current thread. I can't believe there are people still running real work on FC1.
The simple answer for the partition question is to use a current gparted livecd to move the other partitions around to ensure sufficient free space immediately follows /dev/sda1, then resize it.
You give no indication of current phyiscal layout, or the errors gparted fails with, so any suggestions would be guess-work.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
Is there any particular reason you wouldn't install the latest centos? Is there anything on the drive you want to keep? If not, you can boot the Knoppix CD and partition the drive with parted.
Is there any particular reason you wouldn't install the latest centos? Is there anything on the drive you want to keep? If not, you can boot the Knoppix CD and partition the drive with parted.
it's application problem to pass latest Centos 7.x so It's necessary to migrate to 6.
I tried only with Gpart, but I Made all steps together and perhaps I should process in steps... (move partition, resize, ...) because disk geometry is very complex .
Maybe you should read this somewhat related current thread. I can't believe there are people still running real work on FC1.
The simple answer for the partition question is to use a current gparted livecd to move the other partitions around to ensure sufficient free space immediately follows /dev/sda1, then resize it.
You give no indication of current phyiscal layout, or the errors gparted fails with, so any suggestions would be guess-work.
Here is partitions layout:
GNU Parted 1.6.3
Copyright (C) 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
This program is free software, covered by the GNU General Public License.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU General Public License for more details.
Using /dev/sda
Warning: Unable to align partition properly. This probably means that another partitioning tool generated an incorrect partition table, because it didn't have the correct BIOS
geometry. It is safe to ignore,but ignoring may cause (fixable) problems with some boot loaders.
Ignore/Cancel? i
(parted) print
Disk geometry for /dev/sda: 0.000-61440.000 megabytes
Disk label type: msdos
Minor Start End Type Filesystem Flags
1 0.031 1027.595 primary ext3 boot
2 1027.595 9216.979 primary ext3
3 9216.980 13311.672 primary linux-swap
4 13311.672 46080.000 extended
5 17368.000 21462.661 logical ext3
6 23659.000 31946.000 logical ext3
7 31946.088 41983.000 logical ext3
8 41983.683 46080.000 logical ext3
it's enough?
As you can see disk size is larger used space so there is raw space which I can use.
See you on bottom side GUI Gpart layout
Last edited by zio_mangrovia; 06-04-2018 at 01:19 AM.
OK, this is like a "sliding block" game. You need to slide all the partitions (other than /dev/sda1) to the right so the unallocated 15 Gig relocates to be be immediately next to /dev/sda1.
First you need to grab the right edge of the extended partition /dev/sda4 and pull it all the way to the right - the unallocated will then be inside the extended partition, which is just a container.
Then slide - in this order - sda8, sda7, sda6 and sda5 as far right as they will go. That will effectively "move" the free space. Then drag the left edge of sda4 to the right so the free space is outside of sda4.
Then slide /dev/sda3 then sda2 to the right so the free space is next to /dev/sda1, then you can resize /dev/sda1.
This usually works fine, but backups should always be taken before moving partitions around - especially with a system so far out of support.
OK, this is like a "sliding block" game.
First you need to grab the right edge of the extended partition /dev/sda4 and pull it all the way to the right - the unallocated will then be inside the extended partition, which is just a container.
far out of support.
I select /dev/sda4, extended partition, I'm not able to move this partition to the right but only resize partition.
See image:
I select /dev/sda4, extended partition, I'm not able to move this partition to the right but only resize partition.
Exactly, that is what you need to do and for safety sake, after rezing the Extended partition so that includes the current logical partitions plus the free space at the end, move the logical partitions in the order suggested in post 12 above, sda8 first then moving down, sda7, sda6, etc.
Exactly, that is what you need to do and for safety sake, after rezing the Extended partition so that includes the current logical partitions plus the free space at the end, move the logical partitions in the order suggested in post 12 above, sda8 first then moving down, sda7, sda6, etc.
You didn't see what I wrote: Gparted cannot permit me to move this specific partition (sda4) but only to resize, while with other ones Gparted permit to move them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.