similar to: Curious fdisk report on large disk

Hello, I have two disks sda and sdb. One of the was broken so I have changed the broken disk with a working one. I started the server in rescue mode, and created the partional table, and added all the partitions to the software raid. *I have added the partitions to the RAID, and reboot.* # mdadm /dev/md0 --add /dev/sdb1 # mdadm /dev/md1 --add /dev/sdb2 # mdadm /dev/md2 --add /dev/sdb3 # mdadm

Hi All, After updating to the latest kernel, I get subject error at grub. I have no idea as to how to fix this. Booting of the previous kernel is fine. Could someone please help sort this out? Thank you in advance!! Phil Relative info: grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a

I got a I/O error on one of my disks that caused the journal to abort (error below) and be mounted in read only mode. I rebooted and the file system check ran automatically and resolved the error. I did some searching around and couldn't find a likely cause (the disk is a virtual disk, shared from a SAN for VMWare ESXi5.0). An hour after bringing the system back up, we got another one.

Add detection code for "FreeDOS (eXtended FDisk)" MBR to disklib. Signed-off-by: Gert Hulselmans <gerth at zytor.com> --- com32/gpllib/disk/mbrs.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/com32/gpllib/disk/mbrs.c b/com32/gpllib/disk/mbrs.c index 37309e1..6150fcf 100644 --- a/com32/gpllib/disk/mbrs.c +++ b/com32/gpllib/disk/mbrs.c @@ -27,7 +27,6

the other day i was trying to create a new freebsd slice on the same disk i booted from (on a freshly updated RELENG_6) and both fdisk and sysinstall failed with some error (i think they could not write on the disk, or something similar). boot -s did not seem to help, either. I remember vaguely some time ago a bit of discussion on this topic, but cannot recall the outcome nor any keyword to

6727404: intermittent fdisk errors while installing xVM Server guests http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6727404 Is that (at least case #1) the same as OpenSolaris 2008.05 bug 2133 (comment #22)? http://defect.opensolaris.org/bz/show_bug.cgi?id=2133 In some cases the Solaris ata driver is returning a slightly truncated capacity with the DIOCTL_GETGEOM /

Hi, I am using isolinux with memdisk to create a multi-bootable resource cd where I work. I have the Windows 98SE bootdisk created as an image and everything boots fine from the CD. However when I attempt to use fdisk, it asks about enabling large disk support and when I answer yes it dumps me back out to the prompt. Running fdisk /mbr reports 'no fixed disks present.' I made a

How can I use fdisk to partition when installing CentOS4 instead of using 'auto' or disk-druid I want to make RAID 'fd' type partitions for hda and hdc I tried every ctrl-alt Fx and can't get to a shell TIA Gerald

What does the plus sign after the blocks value exactly mean in the fdisk output? Some research reveals that it indicates that not all the blocks are included in the fdisk value. But what does this exactly mean? Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

Hi all, Does anyone know if it's possible to recover an LVM partition from a drive that was fdisked? I accidently fdisk'd the wrong drive (had to fdisk a lot of 160GB drivers from old servers and one still has important data on that client now wants) by running fdisk /dev/sdc & deleting the partitions. The drive is still in a another machine and hasn't been rebooted yet, but

On Sun, Mar 7, 2010 at 8:50 AM, nate <centos at linuxpowered.net> wrote: > > re-create the original partition table, which is just a map, as long > as you haven't formatted or overwritten data everything should still > be there > > Also suggest if your not already doing it set your LVm partitons to > type 8e so it's obvious they are LVM > > [root at

I am getting the WRONG values reported from fdisk on centos 6. This is listing an 8G CF card on /dev/sde Disk /dev/sde: 8019 MB, 8019099648 bytes 247 heads, 62 sectors/track, 1022 cylinders Units = cylinders of 15314 * 512 = 7840768 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xd1b46611 It should be 255 heads, 63

CentOS-6.2 I created a new VirtIO disk for one of my virtual machines. Previous experience has taught me that I need to partition it before attempting to add the new storage to the physical volume set of the intended guest. Up to now I have simply accepted the defaults given by fdisk after telling it that I want a new partition. The defaults always exclude the first 2048 sectors. Disk

On 07/12/2016 09:52 AM, Hersh wrote: > There was some problem with our system so I re-installed the server with > CentOS 7. Now, when I am trying to run 'fdisk -l' command, it is returning > a broken output. > > It throws this error- "fdisk: cannot open /dev/sdc: Input/output error". So, your server had an undiagnosed problem, and now it reports read errors on

I tried to run fsck on /dev/sdc drive and here what I got. [root at localhost ~]# fsck /dev/sdc fsck from util-linux 2.23.2 e2fsck 1.42.9 (28-Dec-2013) fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdc Could this be a zero-length partition? [root at localhost ~]# fsck /dev/sdc1 fsck from util-linux 2.23.2 e2fsck 1.42.9 (28-Dec-2013) fsck.ext2:

Le 07/10/2018 ? 12:09, Nicolas Kovacs a ?crit?: > Now my first reaction would be to install gdisk (yum install gdisk) and > use this to handle GTP partitioning. But I'm curious. How "experimental" > (e. g. prone to blow up in my face) is fdisk really? So far, I've only > used it for MBR-style partitioning. I have a follow-up remark. Before CentOS, I've been

I am trying to use CentOS 8 host to boot an image (OS X) that I created using dd. First I tried fdisk -l image_file.img - all looks good so I did fdisk image_file.img - this works - but seems in CentOS 8 fdisk there is no longer a toggle bootable flag option. How do I do that ? Thanks, Jerry

On Tue, Jun 30, 2020 at 12:12 PM Jerry Geis <jerry.geis at gmail.com> wrote: > I am trying to use CentOS 8 host to boot an image (OS X) that I created > using dd. > > First I tried fdisk -l image_file.img ... fdisk has been deprecated for quite a long time, I think parted is the preferred command line tool now. -- -john r pierce recycling used bits in santa cruz

On Jun 30, 2020, at 1:25 PM, John Pierce <jhn.pierce at gmail.com> wrote: > > On Tue, Jun 30, 2020 at 12:12 PM Jerry Geis <jerry.geis at gmail.com> wrote: > >> I am trying to use CentOS 8 host to boot an image (OS X) that I created >> using dd. >> >> First I tried fdisk -l image_file.img ... > > > fdisk has been deprecated for quite a

Hi folks, I'm moving a server over to amd64 in the next week or so and I'm preparing the RAID1 disk set with the 64 bit ports as we speak. I came across a nasty little bug whilst doing so. Motherboard is a Gigabyte GA-K8U with a ULi SATA controller and AR0 set up as a RAID1 array using FreeBSD pseudo-RAID (ULi's metadata isn't supported). So far, so good. Then into sysinstall