Tag Info

New answers tagged

1

sda2 is kind of like a 'suitcase' holding all extended partitions. You can't delete it. sda5 is the only partition in the 'suitcase', and is your LVM physical volumes. You can't delete it. To actually see what you have spare space wise, use these commands: df -h : Shows the free space on all your volumes (you might be able to reclaim some space) vgs : ...


4

No! /dev/sda contains: a small /dev/sda1 which is needed to boot. a extended partition /dev/sda2 The extended partition contains a logical partition /dev/sda5. The logical partition contains a LVM setup, broken down into to two logical volumes: /dev/mapper/server--vg-swap_1 which is your swap space /dev/mapper/server--vg-root which is your root (/) ...


1

From man fstab: Instead of giving the device explicitly, one may indicate the (ext2 or xfs) filesystem that is to be mounted by its UUID or volume label (cf. e2label(8) or xfs_admin(8)), writing LABEL= or UUID=, e.g., 'LABEL=Boot' or 'UUID=3e6be9de-8139-11d1-9106- a43f08d823a6'. This will make the system more robust: adding or removing a ...


1

You can't do fdisk because you're already at twice MBR's maximum with a 4TB device at 512b sectors. You need to format it with GPT. From wikipedia: The organization of the partition table in the MBR limits the maximum addressable storage space of a disk to 2 TB (232 × 512 bytes). Get the gdisk package and reformat the disk (though it seems to me it ...


0

If the Ubuntu installation replaced or overwrote your windows partition (and data)...I'm afraid the only alternative left for you is to reinstall the Windows systems either from scratch or using your backups.


1

If you access the disk using a filemanager then the partition is mounted in: /run/media/<username>/<label or uuid> Only the user which used the filemanager has permissions to this partition. To make the partition visible to others, you'll need to add it to /etc/fstab. For example: /dev/sdb1 /media/mystuff ext4 defaults 1 2 ...


0

Had the same issue with a friend's USB stick right now. It would not mount at all. dmesg output: [248948.377351] usb 3-1: new high speed USB device number 95 using xhci_hcd [248948.744276] usb 3-1: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes [248948.744283] usb 3-1: ep 0x2 - rounding interval to 128 microframes, ep desc ...


2

The first step is to create a partition. There's no entry in /dev for the free space because it's free space, not a partition. You can use fdisk to create a partition. Run fdisk /dev/sda, then enter the n command and create a partition covering the free space. Once you're satisfied with the new partition table, enter the command w to write it to disk. You ...


0

Here's the solution I used to the problem, for future reference: I installed freebsd 10.0-RELEASE using the "stock" disc1 ISO, selected root-on-zfs and targeted the two SSDs I wanted to use. I completed the installation, then booted into the live-cd environment, inserted a small USB flash drive made a filesystem on it, made a zroot@fresh snapshot, and used ...


0

One of the possibilities could be to try to mount the backup image and just copy the files to your new drive having previously created a filesystem on the new drive. This post describes how you can prepare a clonezilla image for mounting. It looks like you are going to need a lot of space, though, to decompress the image.


1

If you have space, please back up the disk as a whole (e.g. dd if=/dev/sdb of=disk.img bs=1M), before running random programs like fsck on things that you don't think are valid partitions :p. I'm not saying you've damaged it, but there's a very good chance of doing so while experimenting. The partition table shown by parted & the kernel looks ...


2

The offset is specified in 512-byte sectors. Your alternative offset of 63 comes from the C/H/S geometry, which is obsolete and should be ignored. Offset 64 sounds better than 63. It's clearly more even - it provides alignment to 512*64 = 32KiB. You definitely want to aim for 4KiB alignment. (Even if you weren't using an SSD - hard drives are now based ...


2

Add the shared volume to your /etc/fstab file so it mounts automatically at boot. Then run the following commands: mount -a ln -s shared_volume_mount_point/path_to_My_Music /home/My_Music ln -s shared_volume_mount_point/path_to_My_Videos /home/My_Videos ln -s shared_volume_mount_point/path_to_My_Documents /home/My_Documents Navigating should be pretty ...


2

Like UVV wrote in a comment, this shouldn't present a problem. Do it from single user mode if you want to play it safe. Create a partition to hold the new /home, create a file system on it, and mount that file system. Move everything under /home into the root of the file system on the new partition. mv /home/* /mnt/ or something like that should do nicely. ...


0

As I couldn't restart the host I fixed the error: >pvs /dev/sdc1: read failed after 0 of 2048 at 0: Input/output error PV VG Fmt Attr PSize PFree /dev/sdb data lvm2 a-- 330.00g 0 by typing: echo 1 > /sys/block/sdc/device/delete


2

I don't think the installer can do what you want yet (although it's getting better over time), so you could try booting the installation image, and run a root shell from the initial menu. You can then use gpart, zpool and zfs to configure your disks by hand and install the system from the archives on the image. There are numerous guides around the Internet, ...


0

You need to give each an unique name, as follows: Assuming one of your external partitions is /dev/sdb1 - you'll need to alter it for your setup and carry this out on all offending partitions/filesystems. lsblk will show you all of them. Check whether Ubuntu is showing you the partition or filesystem label: blkid /dev/sdb1 /dev/block/253:1: ...


0

Though this might seem like necroposting it is still quite relevant and a problem I ran in to myself recently with the current stable release of Debian. My 1 terabyte drive took a day and a half to wipe. In Debian 7 (Wheezy) when setup says it is "erasing the disk" - the part that takes so long - you can safely hit cancel to proceed to the next step which ...


0

Windows needs to have a primary partition for some system files. It can use logical partitions, but only as a second partition for extra data. So you'll need to shrink the extended partition to make room. Fortunately, the partition you want to reuse is the last one in disk order. So Delete the last logical partition /dev/sda8. Shrink the extended ...


1

This is related to the file system you intend to use. Some of them, such as EXT4 or ReiserFS, allow to mark bad sectors: see the -c option of e2fsck or the -B option of reiserfsck. I think this works on other file systems as well. If you choose this way you should partition and format the hard disk with bad blocks control enabled, and proceed with the ...


2

Modern disks these days usually contain a number of spare sectors that are automatically put into service should a problem in one sector is found. If you run out of these spare sectors, then you are looking at a disk that is in pretty bad shape. Instead of attempting to zero out the bad blocks and continuing, I'd get a new disk and install it. It's far ...


6

You will first need to reconstruct the partition table the way it was. This will not affect the contents of any partition, just the system's idea of where each partition begins and ends. It sounds like you might have already done this because you seem to have a partition that exists that is "unknown", but exactly the same size as the partition was before. ...


1

I haven't used the new installer yet but I have used mfsbsd with 9.x, doing exactly what you describe. There is an option to the zfsinstall on mfsbsd: -z zfs_part_size : create zfs parition of this size (default: all space left) mfsbsd is really simple and fast to use.


1

The debconf question partman-partitioning/default_label should set the partition table type. You also need to set the boolean question partman-partitioning/confirm_write_new_label to true or partman will not overrite an existing partition table. So you should put in your pressed file : d-i partman-partitioning/default_label select msdos d-i ...


0

sudo fdisk /dev/sda Command (m for help): m Command action a toggle a bootable flag b edit bsd disklabel c toggle the DOS compatibility flag d delete a partition l list known partition types m print this menu n add a new partition o create a new empty DOS partition table p print the partition table q quit ...


0

is there a possibility that I can change it to sda2 fdisk utility itself has an option to toggle the boot partition. fdisk /dev/sda type 'a' to toggle the bootable flag


1

Linux shows you device files for partitions when the disk has partitions. If the disk has partitions, there's no point in telling Linux not to show them to you: whatever problem you're having, this could only hide the problem, not solve it. If you change the partition table while the disk is connected, the kernel might not notice and might keep acting on ...


0

I can confirm this on Debian 7. I have a 500GB HDD and it took 3 hours for just approx. 13% of the full capacity. When something like this happens my advice is to ask yourself "Do I really need an encrypted LVM?". If you have some important data that you want to preserve from unwanted access, you can encrypt the data separately.


0

e2label didn't work for me with UDF filesystem labels. blkid did; blkid -s LABEL -o value /dev/sdg1



Top 50 recent answers are included