similar to: fdisk boot partition

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

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

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 all, I just did a fresh C7 install using kickstart. fdisk -l /dev/sda shows: # Start End Size Type Name 1 2048 2050047 1000M EFI System EFI System Partition 2 2050048 104450047 48.8G Microsoft basic 3 104450048 112642047 3.9G Linux swap 4 112642048 234440703 58.1G Microsoft basic What extra do I need to

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

Hi, I have a 24TB RAID6 disk with a GPT partition table on it. I need to partition it into 2 partitions one of 16TB and 1 of 8TB to put ext4 filesystems on both. But I really need to do this remotely. ( if I can get to the site I could use gparted ) Now fdisk doesn't understand GPT partition tables and pat

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, I have a 2GB USB disk on key on /dev/sdb1. I had created on it one partition (FAT16). This partition holds all cylinders of the USB disk. I want to create a bootable Linux USB disk. For this, I tried: syslinux -s /dev/sdb1 An than I ran: fdisk -l /dev/sdb Disk /dev/sdb: 2048 MB, 2048729600 bytes 64 heads, 62 sectors/track, 1008 cylinders Units = cylinders of 3968 * 512 = 2031616

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

I have a system running CentOS 6.3, with a SCSI attached RAID: http://www.raidweb.com/index.php/2012-10-24-12-40-09/janus-ii-scsi/2012-10-24-12-40-59.html For disaster recovery purposes, I want to build up a spare system which could take the place of the server hosting the RAID above. But here's what I see: # fdisk -l /dev/sdc WARNING: GPT (GUID Partition Table) detected on

Thank you all for the help. I'm writing this summary message because of people requests. I haven't tried all of this. I just collected it and organized it. You've got a big storage. Now what? The short answer is: "Just connect it. It should work." I'll play safe by saying that the following applies to <10TB storage. Some people reported file systems of 80TB.

we have DELL server with Centos 5.3 X86_64 bits version on it. This server also have couple MD1000 connect to it. We configured MD1000 as one hardware Volume size 2990GB. I tried to use "fdisk" to partition this 2990Gb volume and "fdisk" can only see 2000GB. does 64 bits O.S. still have 2TB limitation on File system? Does there has other tool can partition disk size large

On Thu, Sep 29, 2016 at 9:18 PM, John R Pierce <pierce at hogranch.com> wrote: > On 9/29/2016 5:55 PM, Michael B Allen wrote: >> >> It seems optical drives are gone. Do I boot the iso from USB or what's >> the procedure now? > > yup, put iso on USB, go to town. Mmn, that didn't work. I dd'd the latest Fedora Live iso onto a USB drive, put it into a

Hi, if I inspect an hybrid ISO with tools like fdisk and gdisk, then looks like hybrid ISO has both the MBR and GPT in order to support both the BIOS and UEFI: # gdisk -l /dev/sdb GPT fdisk (gdisk) version 0.8.10 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT

I believe I've posted before about one of the speed issues we were having, of backups taking many, many hours that should *not* take that long. My manager and I finally nailed it down to the h/d itself. Identical boxes, and he tried a backup of one system which took under two hours, while the same regular one rand nearly six. I'd been googling on and off for weeks, and this morning, ran

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

Hi: I have an NFS volume that I'm trying to resize a partition on. Something about the fdisk process is corrupting something on the drive Before running fdisk, I can mount the volume find: $ mount /dev/sdo1 /home ... and the volume is mounted fine. And, $ e2fsck -f /dev/sdo1 /dev/sdo1: clean, ... But then I run fdisk to rewrite the partition table of this drive, to expand the /dev/sdo1

Hi, i think i found the reason for the boot failure in the definition of Extended Boot Records. https://en.wikipedia.org/wiki/Extended_boot_record#Values "Starting sector = relative offset between this EBR sector and the first sector of the logical partition. Note: This is often the same value for each EBR on the same hard disk; usually 63 for Windows XP or older." So if

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