similar to: After install centos does not find hardrives (SATA)

What's the easiest way to transition to a larger HD when using LVM2? I'm running Centos 4.4. I'm going from a 20gb HD to a 40gb HD. I've already DD'd it to the 40gb HD. So now I have 20gb of unused space. Ideally, I'd like to make it one big physical space for the logical space instead of making another physical partition to expand the logical. Here is what I have now

This is my first post to this mailing list, although I have been reading it for a while. Please forgive the length of my message. Also, great work! I'm trying to get Centos-3 running on an ASUS SK8V Opteron motherboard in a way that is useful for me. I've had some success, but now I'm stuck on a problem with the SATA driver. Okay, so I got it up on the network by replacing sk98lin

Hello, sorry for the long email, it's a little hard to explain this issue. The gist of it is that the Ubuntu version of parted allowed me to do something which perhaps should not be allowed i.e. creating partitions on a 2.7TB drive when the partition table is not *gpt* but *msdos*. I am trying to configure 2 identical servers, both are Dell Poweredge 2970 machines with 6 disks in them

I have just finished creating an array on our new enclosure and our CentOS 5 server has recognized it. It shows as the full 6tb in the LSI configuration utility as well as when I ran fdisk: [root at HOST sbin]# fdisk /dev/sdb Note: sector size is 2048 (not 512) The number of cylinders for this disk is set to 182292. There is nothing wrong with that, but this is larger than 1024, and could in

Hello all, I have 2 x 250GB sata disks (sda and sdb). # fdisk -l /dev/sda Disk /dev/sda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 14939 119997486 fd Linux raid autodetect /dev/sda2 14940 29878

I am getting the following error, however as you can see below this is a SMI label... cannot set property for ''rpool'': property ''bootfs'' not supported on EFI labeled devices # zpool get bootfs rpool NAME PROPERTY VALUE SOURCE rpool bootfs - default # zpool set bootfs=rpool/ROOT/s10s_u8wos_08a rpool cannot set property for ''rpool'': property

Hi, I am installing Centos ServerCD 4.4 64-bit on a new Supermicro board, the RAID BIOS looks fine, RAID 5, all 4 Seagate ES 250 GB drives show up as a single array in the RAID BIOS tool, and the OS install phase completes without a hitch. One thing I noticed was that the OS was loading the sata_nv driver and picking up the 4 Sata drives instead of the large RAID5 volume, it should just

I am trying to mount a FAT32 partition in CentOS. I'm following the instructions on this page: http://www.linuxforum.com/linux_tutorials/14/1.php This is the line I put into /etc/fstab /dev/hda /mnt/windows vfat users,owner,rw,umask=000 0 0 And this is the error I get: [root at localhost mnt]# mount -a mount: wrong fs type, bad option, bad superblock on

On 04/22/16 08:19, Leon Fauster wrote: <<>> > check it with: > > blockdev --getalignoff /dev/sd > > (if a '0' is returned, the partition is aligned) > ===> Leon, thank you for reply. ]$ sudo blockdev --getalignoff /dev/sdc1 0 ]$ sudo blockdev --getalignoff /dev/sdc2 0 ]$ sudo blockdev --getalignoff /dev/sdc5 2560 ]$ sudo blockdev --report /dev/sdc1 RO

The `lofiadm'' man page describes how to export a file as a block device and then use `mkfs -F pcfs'' to create a FAT filesystem on it. Can''t I do the same thing by first creating a zvol and then creating a FAT filesystem on it? Nothing I''ve tried seems to work. Isn''t the zvol just another block device? -- -Gary Mills- -Unix Group-

greetings. centos 6.7 [current] 'disk utility' has started showing message; WARNING: The partition is misaligned by 2560 bytes. This may result in very poor performance. Repartitioning is suggested. for sdc5 - /home partition. /dev/sdc5 302243312 156348604 130534968 55% /home /dev/sdc7 80854912 57088 76683952 1% /hdd/c/07 other than time involved to backup

Semi-OT? I just got a new SanDisk 8GB flash drive, and, as usual, it came with the U3 software (for Windoze) on a "CD" partition and considerably less than 8GB on the disk partition. I put it into my WinXP portable and told U3 to delete itself, but I still can't get at the old U3 part of the drive. I've tried WinXP's format command, disk management and CentOS's fdisk,

I have a USB flash drive that I'd like to image, and then load that image via pxelinux and memdisk. The flash drive was formatted under Windows 98 SE as FAT, and boots just fine on its own. The PXE boot process gets as far as loading the image via memdisk, but then when the boot process switches over to the RAM disk, it fails: [...PXE diagnostic information...] Loading boot

Hi I had installed Xen-3.0.4 in Scientific linux 4 (kernel version 2.6.16.33) by following the instructions given in following link project-xen.web.cern.ch/project-xen/xen/howto_slcXen.html I ve created the guest Domain with fedora image of size 2.2GB , disk space as 10GB and the domain started successfully . when i logged into the xm console and checked the disk space its showing only 2.2GB ..

Hi, Ronald F. Guilmette wrote: > what exactly did we determine that GA-M55Plus-S3G is failing > to support? It appears to be related to the choice of CHS addressing with the FAT filesystem. This opens the door for misperceived factors of heads per cylinder and sectors per heads. My current suspicion is that the partition end did not expose the effective factors in its end CHS address, so

I have a 1.5TB internal disk on my server. I partitioned this with fdisk, and CentOS-5.6 runs perfectly on it. But fdisk gives a very strange report. Here is the perfectly normal response to mount: ----------------------------- /dev/sdb10 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sdb2 on /boot type ext3

I have my 640GB USB drive connected to a CentOS 5 server and using fdisk, it seems to show a partition of the correct size, /dev/sdd1, but after mounting, the drive shows only 244M size. Does the message received when running fdisk below mean I should reformat this drive, I can't seemed to figure out how to do that with fdisk. Can someone tell me how to reformat, if needed? The drive is empty,

I'm trying to extend a logical volume and I'm doing as follow: 1- Run `fdisk -l` command and this is the output: Disk /dev/sda: 85.9 GB, 85899345920 bytes 255 heads, 63 sectors/track, 10443 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier:

We have a server with about 6x750Gb SATA drives setup on a hardware RAID controller. We created hardware RAID 5 on these 6x750GB HDDs. The effective size after RAID 5 implementation is 3.4TB. This server we want to use it as a data backup server. Here is the problem we are stuck with, when we use fdisk -l, we can see the drive specs and its size as 3.4TB. But when we want to create two different

I've tried several times to resize one of my ocfs volumes[see emcpowere1 below] I'm on the latest [prod] version of ocfs/ocfs-tools as of 3pm EST on 18JUL04. Per instructions... Take down db, unmount all ocfs drives, use ' tuneocfs -F -S 100G /dev/emcpowere1 ' Supposedly this should work, but I get get.... The size specified, 100G, is larger than the device size, 59G. Aborting.