similar to: Problem with memdisk and Free 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

Hello syslinuxers I'm stuck with a scientific problem which gives me headaches: I have a laptop (Gateway MX3410) which has a SD memory card reader. Recently an interesting thought crossed my mind: why don't I setup a 2GB SD card as a harddrive and put some rescue tools on it. So I dug on the net and I came across the idea of using memdisk to boot floppy images without the need of a

Dear Syslinux folks, For a firmware update I am following the Gentoo Wiki [1] to create a floppy image of 20 MB, so that the vendor update utility fits. Unfortunately, FreeDOS does not load, and it seems to hang loading the FreeDOS kernel. The original FreeDOS image boots. Do you know if that issue is memdisk related? It?s started from GRUB with the commands below. linux16 /boot/memdisk

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

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

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

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

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.

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

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

Hi list! I'm trying to make a hd image with can boot from memdisk over PXE. So this is what i did: - Created a new VM [VMware] -Installed DOS on a 100MB HD from a floppy -bootet Linux over PXE [DamnSmallLinux] -in terminal: dd if=/dev/hda of=dos.img This image [dos.img] isn't working! Memdisk loads the Image and boots the HD! The error message is something like this: I/O Device

I have been trying to track down information on building HD boot images for ISOLINUX and MEMDISK, and so far, haven't had a whole lot of luck. I've found a number of sources describing the process of setting up ISOLINUX and MEMDISK, and how to configure the boot CD to boot various OS's. I've also read through Bart Lagerweij's BootCD/ModBoot pages, and Mikhail

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

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

Hi, I'm trying to build a bootable MSDOS disk and put it on a ISO with floppy and hard disk emulation. I want to use commonly available Linux tools like dd, losetup, mkdosfs, memdisk etc. I have done the following: 1. dd if=/dev/zero of=myImage bs=1M count=50 [ Builds a 52MB image ] 2. losetup /dev/loop0 myImage [Links /dev/loop0 to myImage file ] 3. vi /grub/stage1; %!xxd; [ NULL the partion

Has anyone been able to boot a bartpe image successfully using pxelinux or does anyone know if this is impossible? For those who don't know, bartpe is a legitimate way to make a trimmed down installation of Windows XP or Server 2003 using your installation media. For more information on bartpe see: http://www.nu2.nu/pebuilder Basically the pebuilder gathers the minimum files needed to