Hi,
I am creating CentOS install usb keys and, apart from a few problems, it mostly works... 1. OT: My server HP does not seem to want to boot on it if I set the write protection on. 2. Anaconda tries to fetch the ks.cfg too early... It detects sda, then detects the RAID adapter, then re-detects sda with a "waiting for device to settle before scanning". Anaconda tries to access the ks.cfg file in the middle of this waiting. If, once the detection is over (just 2-3 seconds later), I retry, it works. 3. Error message "cannot mount read/write, will mount read-only" (I like to write protect) 4. OT: fs corruption ont he USB keys... I copy the iso file on the key (no error message), then compare it to the original and some random differences appear. I noticed in the logs: "ext2_new_block: Allocating block in system zone - block = 65536" "ext2_free_blocks: bit already cleared for block 88678" "ext2_free_blocks: Freeing blocks not in datazone - block = 3003818537, count = 1" Any idea how to fix 2. and 3. ?
Thx, JD
John Doe wrote:
Hi,
I am creating CentOS install usb keys and, apart from a few problems, it mostly works...
- OT: My server HP does not seem to want to boot on it if I set the write protection on.
- Anaconda tries to fetch the ks.cfg too early... It detects sda, then detects the RAID adapter, then re-detects sda with a "waiting for device to settle before scanning". Anaconda tries to access the ks.cfg file in the middle of this waiting. If, once the detection is over (just 2-3 seconds later), I retry, it works.
- Error message "cannot mount read/write, will mount read-only" (I like to write protect)
- OT: fs corruption ont he USB keys... I copy the iso file on the key (no error message), then compare it to the original and some random differences appear. I noticed in the logs: "ext2_new_block: Allocating block in system zone - block = 65536" "ext2_free_blocks: bit already cleared for block 88678" "ext2_free_blocks: Freeing blocks not in datazone - block = 3003818537, count = 1"
Any idea how to fix 2. and 3. ?
Is there a particular reason why you don't/can't use pxe boot and fetching the ks files over the network ?
From: Fabian Arrotin fabian.arrotin@arrfab.net
John Doe wrote:
I am creating CentOS install usb keys and, apart from a few problems, it
mostly works...
- OT: My server HP does not seem to want to boot on it if I set the write
protection on.
- Anaconda tries to fetch the ks.cfg too early... It detects sda, then
detects the
RAID adapter, then re-detects sda with a "waiting for device to settle
before scanning".
Anaconda tries to access the ks.cfg file in the middle of this waiting. If, once the detection is over (just 2-3 seconds later), I retry, it works. 3. Error message "cannot mount read/write, will mount read-only" (I like to
write protect)
- OT: fs corruption ont he USB keys... I copy the iso file on the key (no error message), then compare it to the
original and
some random differences appear. I noticed in the logs: "ext2_new_block: Allocating block in system zone - block = 65536" "ext2_free_blocks: bit already cleared for block 88678" "ext2_free_blocks: Freeing blocks not in datazone - block = 3003818537,
count = 1"
Any idea how to fix 2. and 3. ?
Is there a particular reason why you don't/can't use pxe boot and fetching the ks files over the network ?
I like to have everything on the key and not have to deal with network at setup time. Do you imply that fetching the ks.cfg from usb is not supposed to work?
JD
From: John Doe jdmls@yahoo.com
- OT: fs corruption ont he USB keys... I copy the iso file on the key (no error message), then compare it to the
original and some random differences appear. I noticed in the logs: "ext2_new_block: Allocating block in system zone - block = 65536" "ext2_free_blocks: bit already cleared for block 88678" "ext2_free_blocks: Freeing blocks not in datazone - block = 3003818537, count = 1"
About the corruption problems, I noticed: kernel: attempt to access beyond end of device kernel: sdg2: rw=0, want=27039680368, limit=15746760 kernel: attempt to access beyond end of device kernel: sdg2: rw=0, want=7948148456, limit=15746760 kernel: attempt to access beyond end of device kernel: sdg2: rw=0, want=7948148456, limit=15746760 kernel: attempt to access beyond end of device kernel: sdg2: rw=0, want=10942330464, limit=15746760 kernel: attempt to access beyond end of device kernel: sdg2: rw=0, want=10942330464, limit=15746760 etc...
The limit would look correct: 15746760*512=8062341120=8GB The usb-storage seems to have a little problem with the keys geometry... I am not even entirely filling the key; I fill it up to 60% It happens with 2 different (but same model) keys.
# fdisk -l /dev/sdg
Disk /dev/sdg: 8086 MB, 8086618112 bytes 249 heads, 62 sectors/track, 1023 cylinders Units = cylinders of 15438 * 512 = 7904256 bytes
Device Boot Start End Blocks Id System /dev/sdg1 * 1 3 23126 6 FAT16 /dev/sdg2 4 1023 7873380 83 Linux
Do USB keys need special geometries (not a boot problem)? Or could it be the corruption problem that was reported on the list with the new kernel...?
Thx, JD
From: John Doe jdmls@yahoo.com
- OT: fs corruption ont he USB keys... I copy the iso file on the key (no error message), then compare it to the
original and some random differences appear.
I have corruption problems with both the i386 (3.7GB) and x86_64 (4.2GB) DVD iso files. But I tried the CDROM iso files instead and I don't have any corruption (even though they use almost the same disk space)... Looks like there is a "big files" problem.
JD
-
Fabian Arrotin -
John Doe