Displaying 11 results from an estimated 11 matches for "1325056".
Did you mean:
1325055
2014 Sep 21
1
Re: Possible bug in mkfs.ext3
...ck could
not be read|Bad magic number'`
[ "x$possibleSB" = "x" ] && echo $sb - "$possibleSB"
sb=`expr $sb + 512`
done > possibleSB
I found these blocks, the value of which might hint that the current
start block of the partition may have been altered:
1325056
2373632
3815424
6553600
13376000
13391872
13407744
13423616
13439488
Running fsck /dev/sdc7:
for sb in 1325056 2373632 3815424 6553600 13376000 13391872 13407744
13423616 13439488 ; do
echo fsck -b $sb /dev/sdc7
fsck -b $sb /dev/sdc7
echo =================
done
=================================...
2017 Mar 22
3
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...ndles
the two conversion factors which it correctly got from BIOS call
INT 13H AH 8.
> Boot System ID : First : Last : Relative : Number of:
> Flag :Cyl Head Sec:Cyl Head Sec: Sector : Sectors :
> 80h 00h : 0 0 1 : 646 63 32 : 0: 1325056:
> 00h EFh ?? :1023 254 63 :1023 254 63 : 8524: 608:
The last sector 1325055 and its C/H/S (646, 63, 32) address tell that the
partition table was made under the assumption H/C= 64 and S/H= 32.
That's what hpa prescribed to me for smaller sized isohybrids.
The EFI partit...
2014 Sep 20
0
Re: Possible bug in mkfs.ext3
On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008 at gmail.com> wrote:
> I am reporting this on the advice of the Fedora Users Mailing List Member.
>
> This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run.
>
> I am reporting this per suggestions made to me on the Fedora Users Mailing List.
I would
2017 Mar 22
4
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
Hi,
funny or enlightening observation:
With my qemu-system-i386 it would work if the detected Heads/Cylinder and
Sectors/Head factors would change positions !
The effective read operation seems to use H/C = 32 , S/H = 63.
The correct LBA would be addressed by H/C = 63 , S/H = 32.
--------------------------------------------------------------------------
Reasoning:
I have transplanted the
2014 Sep 20
4
Possible bug in mkfs.ext3
I am reporting this on the advice of the Fedora Users Mailing List Member.
This the mailing list exchange outlining the problem with specifying -S
to mkfs,
and it's subsequent consequences when fsck is run.
I am reporting this per suggestions made to me on the Fedora Users
Mailing List.
The following is the mailing list exchange:
On 09/18/2014 07:01 PM, Robert Nichols wrote:
> On
2017 Mar 22
0
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...in debian-8.7.1-i386-xfce-CD-1.iso was
delivered with the following values (use a monospace font):
Boot System ID : First : Last : Relative : Number of:
Flag :Cyl Head Sec:Cyl Head Sec: Sector : Sectors :
80h 00h : 0 0 1 : 646 63 32 : 0: 1325056:
00h EFh ?? :1023 254 63 :1023 254 63 : 8524: 608:
00h 00h : 0 0 0 : 0 0 0 : 0: 0:
00h 00h : 0 0 0 : 0 0 0 : 0: 0:
If a specific BIOS' CHS/LBA translations cannot cope with the above, it
is no surpris...
2017 Mar 22
0
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...rs which it correctly got from BIOS call
> INT 13H AH 8.
>
>
> > Boot System ID : First : Last : Relative : Number of:
> > Flag :Cyl Head Sec:Cyl Head Sec: Sector : Sectors :
> > 80h 00h : 0 0 1 : 646 63 32 : 0: 1325056:
> > 00h EFh ?? :1023 254 63 :1023 254 63 : 8524: 608:
>
> The last sector 1325055 and its C/H/S (646, 63, 32) address tell that the
> partition table was made under the assumption H/C= 64 and S/H= 32.
> That's what hpa prescribed to me for smaller sized is...
2017 Mar 20
0
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...---------------------------------------------------------------
(It could be shorter if i did not insist in big endian words.)
To be compiled by
cc -o block_seq block_seq.c
and used like
./block_seq | dd bs=512 skip=1 count=1325055 seek=1 of=/dev/sdc
to overwrite the ISO except the MBR.
(1325056 blocks is the size of the Debian ISO in question. One could
of course fill the whole stick until it throws an i/o error.)
The block at LBA 1 bears as content
00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 01
...
The last block at LBA 1325055:
00 14 37 ff 00 14 37 ff 00...
2017 Mar 20
2
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
Thomas Schmitt wrote:
> So if we had a MBR which prints the content of the first 512 read bytes
> we could tell whether they are block aligned and from which block they
> come.
Ok. I'll try. Is it the isohdppx or isohdpfx (or both) that is
relevant?
Meanwhile I have a hacked isohdppx.bin that prints:
G if GPT
M if MBR
<nothing> if no partition info
E if EBIOS
C if not EBIOS
2017 Mar 21
0
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...520 bytes, 7592960 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x59f54072
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 1325055 1325056 647M 0 Empty
/dev/sdb2 8524 9131 608 304K ef EFI (FAT-12/16/32)
Boot the USB flash drive in computer with Intel D865GBFLK motherboard
and Intel Pentium 4 3.4E GHz processor:
C
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
000...
2017 Mar 21
2
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
Hi,
i have uploaded a little gz compressed tarball
http://scdbackup.webframe.org/block_seq.tgz
containing
-rwxr-xr-x thomas/thomas 4552 2017-03-21 09:23 block_seq
-rw-r--r-- thomas/thomas 315 2017-03-21 09:22 block_seq.c
To be unpacked in a suitable directory by
tar xvzf block_seq.tgz
The binary "block_seq" was compiled on Debian Jessie.
If it does not run, do
cc -o