Tag Info

Hot answers tagged

11

You're not going to be able to use GParted because the filesystem is on LVM and GParted does not support that. First, TAKE A BACKUP OF THE VM. Then perform the following as "root" from a command line. It looks like you've already rebooted but just in case, ensure the kernel recognizes the larger disk echo 1 > /sys/class/scsi_disk/0:0:0:0/device/rescan ...


6

There is a possibility to recover the partition table, but it requires 2 conditions be met: You have not rebooted your machine. The drive was in use at the time the table was changed. How this works is that the kernel keeps the partition layout in memory. If a partition is in use, it needs to know where the partition starts, so it will refuse to reload ...


6

Short answer: You can use the same swap partition as the data in swap is not preserved from one boot to the next. It is totally normal to have multiple linux installations on a disk with a single swap. There is one exception/caveat I know of, however: if you use hibernate (aka, 'suspend to disk'), hibernate uses your swap space for storage. If you then ...


4

It's perfectly safe to convert your unallocated space to a partition while your system is running. The only practical danger is in human error (i.e., yours) or a power loss while the partition table is being written. These just as likely to happen while booted normally as they are booted from a Live CD.


4

You might try using testdisk to recover the partition table. Testdisk will read the surface of the disk and attempt to determine where partitions start and end.


4

Your drive is a LVM physical volume. Your free space is being managed by lvm. Look at vgdisplay to find free space in your volume group and lvcreate to create a new partition from that space. To grow a partition you will first lvextend the logical volume then (if ext2/3/4) resize2fs to size the filesystem to the new volume size.


4

It appears that the device file does not exist. You can verify this by doing ls /dev/sdb6. Try running the command partprobe, or sudo partprobe as user. This should detect the devices and create the according device files. This may return the error Error informing the kernel about modifications to partition /dev/sdb5 -- Device or resource busy If it ...


3

You need to associate a loopback device with the file: sudo losetup /dev/loop0 /home/user/harddriveimg Then run gparted on that.


3

do I need to have a swap partition for each distro or can LFS use the swap partition I already have? As goldilock says, unless you are hibernating (suspend to disk), yes. Otherwise no, because you could overwrite swap of a hibernated system - either it's saved state or the part that was used as regular swap at suspend time. If so, would the swap ...


3

The process appears to be: create a new partition in your newly available free space; your choice of filesystem doesn't much matter, as we will change it later reboot into the system use cfdisk to flag the new partition as Linux LVM instead of whatever you chose above use pvcreate to flag your new partition as a physical volume for LVM use vgextend to add ...


3

The filesystem is 20G on a partition that has 40G. You need to resize the filesystem! growfs is the correct tool.


3

Assuming you're talking about merging 3 partitions into 1 with all the original data intact I do not believe you'll be able to merge these partitions, as they are. There is not enough unused space on any of the partitions that can contain the other partitions' used space. You could shuffle them around and maximize the free space so that it's on 1 of the 3 ...


3

You split your disk into (at least) two partitions - one for your home directories (/home) and another for everything else (/). It looks like you only allocated about 10GB for /, which is now full. The partition mounted as your /home directory is ~621GB, with plenty of free space, but that's not where most system files go. That's the danger of allocating ...


3

It defines the partition id as linux swap. The entry of the partition in the master boot record of the device contains the hex value of that partition type. In that case it would be 0x82. The problem is every operating system interprets them different. It is theoretically possible that if you use two operating systems with the same harddisk, the same code ...


2

Since "when booted" means that the OS that needs to make changes and write to the disk, is also running from the same disk, has a higher potential for problems/disaster if something goes wrong. Following Murphy's Law, "Anything that can go wrong, will", you are safest to run the operation isolated from the operating system. My suggestion would be to use ...


2

You have copy & pasted a lot of unnecessary transcripts but your first paragraph pretty much says it all: When I run sudo gparted on a live ubuntu USB, I get Input/output error during read on /dev/sdc. So you have a defective disk. The error comes directly on /dev/sdc (not /dev/sdc1 or /dev/sda2, etc...) so it applies to the whole disk. Therefore ...


2

You can't enlarge it with GParted because it currently does not support HFS+ partition "grow". It only supports HFS+ "shrink". See Gparted features or, on your machine: GParted >> View >> File System Support


2

Easy. Go into your VM as root. Type "fdisk -l" - if you already see the new disk size - good. If not - try partprobe - if you still do not see the new disk size - reboot. Now fdisk /dev/sda Write down you starting cylinder for the second partition. "Delete" the second partiton Recreate the second partiton, same starting cylinder, last cylinder for end ...


2

You might want to check out CrunchBang. Like Ubuntu, it is based on Debian, however, it uses the Openbox window manager and in turn is significantly lighter on resources. I can't tell you specifically how well it will work on an Inspiron 630m, but it is definitely a solid distro. The project lead, Philip Newborough, has done an incredible job of blending ...


2

From what I found, this laptop is powerful enough to run a lightweight GUI (like XFCE, Openbox etc...). You could start using Debian (which isn't much more complicated than Ubuntu) or Arch Linux (which is more difficult, but will be a good experience).


2

First, to avoid messing up, you should backup an entire image of the disk (provided you have a bigger disk to store it). For this, several solutions are proposed on this question, last time i did it, I used dd. Once you are sure you can restore the image in case of problem, you can use testdisk to redetect the partition table and fix it. This question for ...


2

To have more space for your Linux installation you need to expand sda6. Having freed up 10GB by shrinking sda3 you would then expand sda4 by 10GB and expand sda6 to fill up all of sda4. However, resizing existing partions, especially NTFS ones, always bares the risk of loosing all data on that partition! I don't know anybody who ever experienced loss of ...


2

You appear to have both a dos and mac partition table on the disk, and parted is recognizing the mac one. You should be able to zap the mac partition table with: sudo dd if=/dev/zero count=1 bs=2 of=/dev/sda


2

No it will not move the entire extended partition nor make the space contigious. Although in theory the extended partition could just be recreated with the same logical partitions, that would mean that the entries stay in place (with some zero size first, logical partition), or you would have to rearange the Extended partition information. Both that would ...


2

I suggest you read this guide on Ask Ubuntu. As for the difference, gparted and similar tools help you partition your hard drive. The Ubuntu installer can also do this automatically which is, presumably, the way suggested by the sites you read. I would not do that though and especially not with a system that has windowd8 installed since there are other ...


2

This is a critical moment of the installation, the guide doesn't want to interfere too much because: you have chosen expert you could erase data involuntarily Exposing all possible options to a GUI installer is difficult (GUI is always limiting choices). Finally some recommendations: Bootable flag for boot partion: on Other partitions, bootable flag: ...


1

Keep only /boot in the first partition First, 243MB is enough for /boot. If it's the root partition that you have on /dev/sda1, then there isn't enough room even for a basic installation. If you've separated /usr, don't: this was useful in the days of read-only or shared /usr but isn't nowadays. To move the root partition: Move all the files to the ...


1

The card does not have a Master Boot Record (MBR). If it had your hexdump would have given you at least one partition entry at offset 0x1C0 and 55aa at the end. Not all partition tables lay out data in the first 512 bytes. The spurious data you see is SID and CSD register of (a / the) SD card. But from the looks of it it is not the correct data for the card ...


1

I would try using the sfdisk command as opposed to dd. For example: $ sudo sfdisk -d /dev/sda > /tmp/mbr_using_sfdisk.bin Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. Now looking at mbr_using_sfdisk.bin reveals what you're looking for: $ more /tmp/mbr_using_sfdisk.bin # ...


1

you can use the following commands: cat /proc/partitions cfdisk YOUR_DEVICE ===> such as cfdisk /dev/sdb



Only top voted, non community-wiki answers of a minimum length are eligible