search for: fdisking

Sorry for the cross-post, but I do not know whether this is a bug in Free FDISK, memdisk, or neither. This problem is with Free FDISK 1.2.1 and memdisk 2.04. I am using PXELINUX+memdisk to boot to a virtual hard drive containing MS-DOS 6.22. This works fine; DOS boots and the virtual drive appears as C:. Now I want to use Free FDISK to partition the *physical* drive. But when I run any of the

Hi, 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". There are valid /dev/sdd and /dev/sde devices which are mounted and they are accessible but, somehow /dev/sdc is having a problem and

Hi, I'm currently teaching Linux system administration to a class at the local "chambre de commerce". The course is based mainly on a minimal CentOS 7 installation. Usually my preferred tool for handling manual GPT partitioning is gdisk, which is not installed on a minimal install. I just gave the good old fdisk a spin, which enables GPT partition table creation with the

Hi, Is it possible to create one raid volume of 3.3 TB (9550SX-8lp X WD5000YS - 8nos) and create a file system with ext3? (CentOs4.3 64bit) The maximum I am getting is 1.24tb and fdisk returns no more space available. But when I say fdisk /dev/sda it list full size of 3.3 TB. But I can not create partitions more than 1.24TB. Any idea? Thanks Rajeev -------------- next part

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

Hello, How to explain to fdisk that /dev/sda size changed? I increased LUN on storage, reloaded iscsi, did echo 1 > /sys/<something>/rescan. And I see in "dmesg" that kernel found new size of the LUN. But when I type "fdisk /dev/sda" it still shows old size. On /dev/sda1 sits LVM PV and I'd like to resize it instead of adding one more PV to volume group.

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

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

Hello list, Currently, i use a partition image to run my XenU (/dev/hda2) and "fdisk -l" return nothing and can''t open /dev/hda . I want to use a full hard drive image (not partition image) from my Xen0 as hda in my XenU. I want to be able to run fdisk on hda in my XenU to list and regenerate partitions. I tried with this (/img is my hard drive image): disk =

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

> Both sticks show very unusual factors for heads and sectors > which are hardly intentional. If BIOS gets confused like fdisk, > then the failure to find files is quite plausible. > > ------------------------------------------------------------- > > Could you please exercise what is described for Linux in > http://www.syslinux.org/doc/usbkey.txt > and check whether

Hi all What is the best practice to remove all data in the disk? ls fdisk ok or use dd Can data be recovered? and what is the dd command? Thank you __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/

There were no live connections. The problem what we had was more related to OS requirement for some software. This drive was not in a bad shape. On 12 July 2016 at 23:03, Gordon Messmer <gordon.messmer at gmail.com> wrote: > 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

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

I downloaded DOS6.22 image from putergeek.com. Used fdisk from that floppy and format from that floppy. Still no luck. If I execute fdisk under leaf (monkeynoodle.org) as fdisk/dev/hdc, and give p for print partition table, I get the following: Disk /dev/hdc: 16 heads, 32 sectors, 123 cylinders. Units = cylinders of 512 * 512 bytes Device Boot Start End Blocks Id System /dev/hdc1

hail, I partitioned the disk this way: fdisk da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=12161 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=12161 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size