similar to: How to make a bootable USB flash drive manually?

I would like to boot FreeDOS ISO image from USB memory stick using syslinux. I have done following: 1) I created a partition to my 2GB memory stick: root at debian64:~# fdisk -lu /dev/sdb Disk /dev/sdb: 2013 MB, 2013265920 bytes 62 heads, 62 sectors/track, 1022 cylinders, total 3932160 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size

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

Greetings - Ok, I have my CentOS 7 KVM host system installed and I want to be able to boot the system from either installed drive if one of them fails. My objective is to have the following layout for the two 3 TB disks. sda1 /boot/efi sda2 /boot sda3 RAID1 with sdb3 sdb1 /boot/efi sdb2 /boot sdb3 RAID1 with sda3 The system is installed and boots from sda[1,2] and md127 (sda3 and

On 6/19/20 9:48 AM, Nicolas Kovacs wrote: > Hi, > > In my daily work I'm mainly using USB keys for work : one with CentOS 7, one > with OpenSUSE Leap 15.1, one with Slax Live for data recovery purposes, one > with Ghost4Linux and one with FreeDOS which I use for flashing the odd BIOS. > > Last week I bought a set of three flashy colored USB keys in a local shop. To >

1. ext4 mke2fs -b 4096 -m 5 -t ext4 -O^uninit_bg -r 1 -v /dev/sdb1 sdparm --command=sync /dev/sdb 2. 150G 3. gdisk /dev/sdb x a 2 w y sdparm --command=sync /dev/sdb 4. mount /dev/sdb1 /mnt/sdb1 cd /mnt/sdb1 extlinux -i /mnt/sdb1/boot umount /mnt/sdb1 sync;sync;sync sdparm --command=sync /dev/sdb cat gptmbr.bin >/dev/sdb1 sync;sync;sync sdparm --command=sync /dev/sdb

I installed a fresh copy of Debian 4.0 and Xen 3.1.0 SMP PAE from the binaries. I had a few issues getting fully virtualized guests up and running, but finally managed to figure everything out. Now I''m having a problem with paravirtualized guests and hoping that someone can help. My domU config: # # Configuration file for the Xen instance dev.umucaoki.org, created # by xen-tools

Hi all. I am new to the list. I am trying to make a SD flash bootable. I have a MSI Wind netbook running Fedora 9 with a built-in card reader that detects the SD flash properly. However, when I run syslinux, it does not update the boot block. I also tried using a SD -> USB adapter, but I get the same behavior. Fedora 9 uses an older syslinux 3.61, but I also tried the latest 3.72 with

Hi. I added a disk to a hardware raid 5 array and now i want to expand the LVM physical volume. There are now 4 sas 146GB disks in the server. The virtual disk /dev/sdb from the raid controller has been resized successfully with the server management software osma. [root at srv1 ~]# fdisk -l /dev/sdb Disk /dev/sdb: 438.4 GB, 438489317376 bytes 255 heads, 63 sectors/track, 53309 cylinders

Ok, I give up... I have to ask. This is CentOS 5. I switched one of my raid1 disks, and I already thought I had succeeded. But now it seems that something is very wrong with the first partition on the new disk. Luckily my system is fully bootable with the other disk. Here's some info. The new disk is sdb. // I removed all partitions with parted, and created the first one again. // parted

I try two ways to use syslinux for USB key (2GB USB key), and one approach can boot from machine, another approach can not. Could you review the following steps and tell me why #2 can not boot? Thanks very much! approach #1 steps: mkfs.vfat -F 16 -n USB /dev/sdb -I (pay attention, it uses "-I" here) syslinux /dev/sdb (pay attention, it is "sdb", not "sdb1" here)

On 05/12/2018 05:37, Nicolas Kovacs wrote: > Le 04/12/2018 ? 23:50, Stephen John Smoogen a ?crit?: >> In the rescue mode, recreate the partition table which was on the sdb >> by copying over what is on sda >> >> >> sfdisk ?d /dev/sda | sfdisk /dev/sdb >> >> This will give the kernel enough to know it has things to do on >> rebuilding parts. >

On 12/10/2014 10:13 AM, Jeff Boyce wrote: > The short story is that got my new install completed with the > partitioning I wanted and using software raid, but after a reboot I > ended up with a grub prompt, and do not appear to have a grub.cfg file. ... > I initially created the sda[1,2] and sdb[1,2] partitions via GParted > leaving the remaining space unpartitioned. I'm

I got the following error, but there''s no "cycle" I commented out File["/dev/sdb3"] and it works, but of course would choke if I ran it and the requirement were not met err: Could not apply complete catalog: Found cycles in the following relationships: File[/dev/sdb1] => Exec[echo -e "0,290\n,290\n," | sfdisk /dev/sdb] Here''s the node: node

Hello, I have a weird problem after adding new PV do LMV volume group. It seems the error comes out only during boot time. Please read the story. I have couple of 1U machines. They all have two, four or more Fujitsu-Siemens SAS 2,5" disks, which are bounded in Raid1 pairs with Linux mdadm. First pair of disks has always two arrays (md0, md1). Small md0 is used for booting and the rest - md1

Hi, I see some strange and dangerous things happening on a HPE server with HPE Smart Array controller where EL9 ends up with wrong device nodes/symlinks to the attached disks/raid volumes: (I didn't touch anything here but at 08:09 some symlinks were changed) /dev/disk/by-id/: lrwxrwxrwx 1 root root 9 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_00000000 -> ../../sdc lrwxrwxrwx 1 root root 10

On 03/19/2017 01:01 AM, Thomas Schmitt via Syslinux wrote: > David Christensen wrote: >> Is there a way I can build live 32-bit Debian GNU/Linux USB images without >> isohdpfx.S and syslinux.bin? > > You could try > https://www.debian.org/releases/jessie/i386/ch04s03.html.en#usb-copy-flexible This is how I prepared an ADATA USB Flash Drive 4 GB: # cat

The most recent message is: [3108269.919256] sd 2:0:1:0: timing out command, waited 1080s [3108269.919528] sd 2:0:1:0: [sdb] Unhandled error code [3108269.919535] sd 2:0:1:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_OK [3108269.919540] sd 2:0:1:0: [sdb] CDB: Read(10): 28 00 00 01 21 47 00 00 08 00 [3108269.919586] EXT4-fs error (device sdb1): ext4_find_entry: reading directory #2 offset 0

I have 2 SCSI disks each w/a RH 7.3 ext3 root filesystem: /dev/sdb1, and /dev/sdc1. /dev/sda1 is an old RH4.2 root filesystem. (sdb1 was created as an image of sdc1 using dd.) I have no problem booting from a SYSLINUX 1.52 floppy with SYSLINUX.CFG containing "append initrd=initrd.img root=/dev/sdb1". When I alter SYSLINUX.CFG with: "append initrd=initrd.img root=/dev/sdc1".

Hi! I have problem making ext3 FS on new disk. When I run mke2fs, it stops and gives me: "File size limit exceeded". Is this known issue? I'm running linux-2.4.10 with ext3 patch, e2fsprogs-1.25 freshly compiled. Cheers, Vita Appended are outputs of following programs: bash /usr/src/linux/scripts/ver_linux /sbin/mke2fs -m0 -v -j /dev/sdb1 fdisk -l /dev/sdb strace

On 12/05/2014 01:50 PM, Jeff Boyce wrote: > > ----- Original Message ----- From: "Mark Milhollan" <mlm at pixelgate.net> > To: "Jeff Boyce" <jboyce at meridianenv.com> > Sent: Thursday, December 04, 2014 7:18 AM > Subject: Re: [CentOS] CentOS 7 install software Raid on large drives error > > >> On Wed, 3 Dec 2014, Jeff Boyce wrote: