Tag Info

New answers tagged

0

Try this: #dmraid -r -E /dev/sda If that doesn't work, try #mdadm --zero-superblock /dev/sda It is also possible to do this automatically by editing the Kickstart file to use clearpart option, see: http://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-kickstart2-options.html


1

1: it doesn't have to do anything with primary/extended/logical partitions. 2: I think you wanted to say "logical" partition instead of "extended". 3: mkfs thinks your partition size if 0 bytes. It was very surely, because the kernel wasn't able to update the partition table after a repartitioning. After you edited the partition table, didn't you get some ...


4

I figured it out. My bootloader wasn't configured properly. Sounds obvious, right? Modifying fstab doesn't quite qualify as configuring the bootloader. I had to change a line in /boot/syslinux/syslinux.cgf to refer to correct boot partition. That said, there was no need to boot off of the second disk in the first place. I could have avoided this problem by ...


0

sysctl kern.geom.debugflags=16 This solve it for me. If some one can explain for future reader how and why this work I delete my answer and accept your answer.


0

ef00 appears to be the correct hex code.


0

you need to move/recreate the linux swap partition and ensure that it begins/ends on a cylinder boundary


0

You must run the command partprobe -s before doing any operation on /dev/sda6 If you don't have that command then simply reboot the machine


2

I ran across the same issue just now, and found another workaround. Basically, it involves making the hosts /run directory available to the guest. First, we mount /run where it can be accessed by the guest. I will assume that your install partition is mounted at /mnt mkdir /mnt/hostrun mount --bind /run /mnt/hostrun Then, we chroot into the guest, and ...


0

Have you tried "grub-install" from a terminal? You will need to be root or use sudo. grub-install or sudo grub-install To see which version you have you can run: grub-install --version GRUB1 is versions <= 0.98. Also on the boot loader screen, it should say if it is "GRUB" or "GRUB2".


1

You can try recover some files with the program testdisk. They have a good tutorial and in some Linux distros it's already included. If yours has it not, download from here.


3

You may want to try booting into a recovery disk. System Rescue CD MAY be able to recover the data. It is better to do this from a live disk because then you are less likely to overwrite the information that is there. When you delete a file it is not wiped, but instead the computer sees it as space that it can write over. As long as it has not been ...


1

See here mount info for current directory This question answers how to find mount info for file-system for current working directory. So if you can cd to somewhere in the mount, then you can find out with (cd $somewhereInTheMount; until findmnt . ; do cd .. ; done)


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 ...


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 ...



Top 50 recent answers are included