Tag Info

Hot answers tagged

9

LVM is not overkill if you have 17 partitions. (IMHO) As for the partition limit, it just happens to be the default. Probably no one expected that many partitions on a device that used to have only a few megs. /usr/src/linux/Documentation/devices.txt: 179 block MMC block devices 0 = /dev/mmcblk0 First SD/MMC card ...


4

After you dd an image to a flash drive, the drive will be divided in 2 parts: the image partition with the image's size and a blank part. That's normal. To get your drive go like before, just format it: mkfs.vfat -I /dev/sdb (as root).


4

A BIOS boot partition doesn't contain a filesystem; it's just a place to put some GRUB code that on an MBR disk would've been located immediately after the boot sector, before the start of the first partition. On a GPT disk, that area is used by the (larger) partition table and isn't available for bootloader code, so the bootloader code goes in a small ...


2

You have to unmount the drive before you can resize the partition. You will need to use a live CD/usb. Once you boot using the live CD you can repartition the drive. If one of the OS that you are installing is windows you probably want to start with that and then add linux. While you can certainly do it in either order it tends to be easier to do windows ...


2

It is not something I would do online but I think it is possible. I guess you are using ext4. umount /home $ umount /home shrink the /home filesystem $ fsck -f /dev/mapper/VolGroup-lv_home $ resize2fs /dev/mapper/VolGroup-lv_home 80G shrink the /home logical volume $ lvreduce -L -40G /dev/mapper/VolGroup-lv_home resize the /home partition to the size of ...


2

You disk size is 14.538 GiB (30489408 sectors * 512 bytes /1024/1024/1024). Its partition table is seriously broken as sdb4 is overlapping sdb1. You should remove sdb4 as soon as possible and in any case, you shouldn't use that fourth partition without a very strong risk of corrupting sdb1 content.


2

Assuming your volume group is already full, and you cannot extend it further, you will need to: Shrink the filesystem in lv_home using the specific tools for your filesystem, e.g. resize2fs if you use ext3/4. Resize lv_home accordingly with lvreduce. Increase lv_root with lvresize. Increase the filesystem in lv_root so that it uses all the additional ...


2

First off, you want to unmount the partitions in question. Boot an usb stick or similar. Backing up important data is always recommended before fiddling with filesystems. Reduce the filesystem first in /dev/mapper/vg_dckapstaging-lv_home. Otherwise, resizing the lv will drop the data. The way to do it depends naturally from filesystem. resize2fs works for ...


2

If you are using mkfs.ext4, you have to pass -E root_owner=your_uid:your_gid, this is usually passed in an 'extra options' textbox in gui partition tools. If you dont do this (< mkfs 1.42) then the person running the gui tool will get the permissions. Nowdays, for security, it assigns them to root:root (0:0). If you ever go back to fat32 or ntfs, you ...


2

You might be able to re-detect it without reboot, by unloading / re-loading the correct module (or just un-binding and re-binding the driver). For example: [ 978.527221] sd 11:0:0:1: [sdk] Attached SCSI removable disk #~> echo 11:0:0:1 > /sys/bus/scsi/drivers/sd/unbind #~> echo 11:0:0:1 > /sys/bus/scsi/drivers/sd/bind [ 5572.027119] sd ...


2

Here comes a memo to resize an NTFS partition using commandline with ntfsresize (from the ntfs-3g / ntfsprogs package) and fdisk, that should work for Windows XP-to-8 versions. Note that GParted does all the following for MBR/DOS as well as for EFI/GPT drives if ntfs-3g / ntfsprogs is installed. My references are at the end. OK in this scenario I have a ...


1

The file listing of /etc/mtab appears to belong to /etc/alternatives! Is there any way you could have accidentally renamed /etc/alternatives to /etc/mtab? Is /etc/alternatives missing? If so, then the fix is just to rename /etc/mtab back to /etc/alternatives. If not, then you are stuck with the problem of merging the contents of the real /etc/alternatives ...


1

You have overwritten the partition table with an ISO file system. The general expectation is that if a device contains an ISO file system, then that describes the entire contents of the media, and no further partitions are present, because that is how normal data CDs work. The system expects the rest of the media to be inaccessible, again because that is ...


1

This is a risky operation you should try to clean / (have a look at /var/log /var/spool and delete old and big file) theorical way to proceed include fsck -F /dev/mapper/vg_dckapstaging-lv_home lvresize --size -15G /dev/mapper/vg_dckapstaging-lv_home resize2fs /home lvresize --size +15G /dev/mapper/vg_dckapstaging-lv_root resize2fs / Disclaimer 3.1. be ...


1

Well, if you want them to be /dev/sdb you'll need to remove the partition table entirely. Maybe the most simple way to do that is just to backup the fs and create it anew. sudo mount /dev/sdb1 /mnt tar -C/mnt -cf /tmp/sdb . sudo umount /mnt sudo dd if=/dev/zero of=/dev/sdb bs=1kx1k count=4 sudo mkfs.vfat /dev/sdb sudo mount /dev/sdb /mnt tar -C/mnt -xf ...


1

You need to delete both partition sdb1 and sdb4. So that, it will become single storage device, which you can use it by creating one single partition. WARNING: DOING THIS WILL ERASE ALL THE CONTENT OF SDB1 AND SDB4. TAKE A BACKUP IN CASE, THOSE DATA IS VITAL FOR YOU.


1

You cannot resize or change at all any partition on a storage device that is currently mounted. That means that your system needs to be shutdown if you intend to modify the root partition (since you cannot unmount it) You will need to boot in an external OS (e.g. using a live-CD) to perform these tasks. I would recommend you to backup any sensible data ...


1

Had the same problem: Disk that is about to die, with NTFS partition that I wanted to rescue first and fix after (before the disk is totally gone). Was able to resolve it with ntfsclone: Connect the two disks - old and new Boot with Live-Linux from USB (can use Parted Magic for that as well) Create a big-enough partition on the new disk (use gparted for ...



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