search for: lbas

Hello! I need to write a user space tool that can dump logical block addresses used by every file in a ext3 file system. For example, if file foo uses LBAs 2,3 and file bar uses LBAs 100,102,156, then the ouptut should read: FILENAME LBAs foo 2, 3 bar 100,102,156 Is there a tool that exists that can do this? If not, what would be a good strategy to write this tool. I am learning filesystem programming and would really appreciate...

...redhat.com > Date: Mon, 16 Apr 2007 11:17:12 -0700 (PDT) > Subject: User space tool to extract ext3 inode information > Hello! > > I need to write a user space tool that can dump > logical block addresses used by every file in a ext3 > file system. For example, if file foo uses LBAs 2,3 > and file bar uses LBAs 100,102,156, then the ouptut > should read: > > FILENAME LBAs > foo 2, 3 > bar 100,102,156 > > Is there a tool that exists that can do this? If not, > what would be a good strategy to write this tool. I am > learning file...

...merged image of a rescue CD with further DVD content (the issue: I prepared a rescue CD that worked fine everywhere, when merging this CD with a few thousand files and re-named boot files to a DVD, it stopped booting on some machines). On all of my test systems everything worked even with high LBAs while the troubles my colleages had were as described: ETCD disk error plus halt, reboot or just hanging systems. After comparing the images of the rescue system alone with the merged DVD we noticed the different LBAs of isolinux.bin. When everything booted fine on every machine after moving is...

Hi, hpa wrote: > - mov dx,cx > + movzx edx,cx Gerardo Exequiel Pozzi: > Yes! Fixed :) > (maybe garbage in high word of "edx"?) I am now pondering too, why my machine booted from high LBAs. I understand that the new code zeros the upper 16 bit of EDX. Was there remaining garbage from early BIOS activity before isolinux.bin got started ? Does my BIOS perhaps clean registers before handing over control ? Have a nice day :) Thomas

Hi Feng, I'm currently hitting the overflow in core/diskstart.inc on the elfink branch where I see you changed the overflow check, commit 2e91ec5f155f04aee878ed70a04fb5b15e40da3b Author: Feng Tang <feng.tang at intel.com> Date: Wed Jul 14 15:55:25 2010 +0800 elflink: a lot of core/fs merge @@ -691,16 +798,22 @@ rl_checkpt equ $ ; Must be

...t file length in bytes 20 bi_csum 4 bytes 32-bit checksum 24 bi_reserved 40 bytes Reserved The 32-bit checksum is the sum of all the 32-bit words in the boot file starting at byte offset 64. All linear block addresses (LBAs) are given in CD sectors (normally 2048 bytes). ----------------------------------------------------------------------------- The "primary volume descriptor" of a first session on medium is always at Logical Block Address 16 = 0x10 0x00 0x00 0x00. "Boot file length" and "3...

> As stated earlier, the next version of xorriso will have > sort weight 2 for El Torito boot images by default. > But it will not harm to explicitely use --sort-weight > options with old and new versions of xorriso. FWIW, mkisofs is supposed to assign a +2 sort weight by default to the eltorito boot image and +1 to the boot catalog, at least when no sort file is provided. I

On 11/24/2013 09:23 PM, Gerardo Exequiel Pozzi wrote: > On 11/23/2013 09:35 AM, Carl Duff wrote: >> -- Re-sent as original may be stuck at awaiting "authorisation" (originally >> sent before I joined the mailing list) >> >> Hi All, >> >> It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or >> DVD on older - non-UEFI -

...r versions of mkisofs and genisoimage >do not force the boot images to low addresses. >I am curious what a mass test with the users will bring. >From experience of making Debian CDs, we've had bug reports years ago about buggy BIOS implementations that won't boot images using high LBAs. For ages, we've been simply using two file trees when creating CDs, putting boot files into the first one mentioned on the mkisofs/genisoimage command line. Since we started doing that workaround, things worked much better. -- Steve McIntyre, Cambridge, UK. ste...

...easy way probably is to take Win32DiskImager and one of the official Ubuntu ISO images. The official ISOs are hybrid images. They also contain a partition table and a bootloader. With Win32DiskImager you can create a bootable thumb drive. Since the hybrid images usually have a bootloader at low LBAs and use a drive geometry that works nearly everywhere, this Ubuntu stick should boot on your board. When it boots, you can take the Ubuntu live system to analyze the drives that do not boot. You also can install software in memory in the the Ubuntu system running from USB if you have sufficien...

...ard: -------------------------------------------------------------- 2 GB Intenso: Partition type 0x06 (Wikipedia: FAT 16, CHS or LBA) Start LBA 32 = CHS 0 1 1 End LBA 3915775 = CHS 956 128 32 The latter has no integer solution pairs for H/C and S/H. (Neither have neighboring LBAs.) Partition content according to command "file": x86 boot sector, Microsoft Windows 98 Bootloader IO.SYS+MSDOS.SYS, code offset 0x3c, OEM-ID "MSWIN4.1", sectors/cluster 64, root entries 512, Media descriptor 0xf8, sectors/FAT 239, heads 128, hidden sectors 32, sectors 39...

> Hi, > > Ronald F. Guilmette: > > > Doesn't the Syslinux project provide (hopefully strong) specific > > > reccomendations, [...] > > hpa: > > We try (see our wiki), > > The general wiki > http://www.syslinux.org/wiki/index.php/SYSLINUX#Creating_a_Bootable_Disk > says > "In order to create a bootable disk using SYSLINUX, prepare

...The downloaded packages are in ?/tmp/Rtmp7uCMsh/downloaded_packages? Mensajes de aviso perdidos In install.packages("lme4") : installation of package 'lme4' had non-zero exit status ----- Surfing on internet and R hel system it seems the problem is related to LAPACK, LBAS. ATLAS libraries. R tries to find unsuccessfully " -lRlapack " I have checked which libraries R is pointing to: --- busta at temisto:~$ ldd /usr/lib/R/bin/exec/R linux-vdso.so.1 => (0x00007fff1e100000) libR.so => /usr/lib/R/lib/libR.so (0x00007f9157c54000)...

In message <CAD0Rxe=p2gHHN9U3Zjn34Y71-KTxk5v+WzG7V3VH0ZNGCzqSvA at mail.gmail.com> Gene Cumm <gene.cumm at gmail.com> wrote: >On Fri, Jan 10, 2014 at 9:35 PM, Ronald F. Guilmette ><rfg at tristatelogic.com> wrote: >> In message <BLU0-SMTP145A44932CB6CC2DB4621568BB30 at phx.gbl>, >> Ady <ady-sf at hotmail.com> wrote: > >>>I don't know

...equivalent) when the original isohybrid image was created? Yes. C/H/S addresses are only recorded in the MBR partition table. (Anyways, only the heads/cylinder and sectors/head ideas of the BIOS matter. One should never believe the C/H/S addresses in the partition table, but rather convert the LBAs of the partition table to C/H/S by the numbers inquired from the BIOS.) > _ whichever combination of boot entries in the El Torito boot catalog? Yes. El Torito does not matter if the MBR gets started. (That's why i do not generally propose to patch in Martin's MBR by program isohybr...

On 11/26/2013 01:14 AM, H. Peter Anvin wrote: > On 11/25/2013 06:32 PM, H. Peter Anvin wrote: >> On 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote: >>> >>> I made some more and more experiments beyond LBA 65535 >>> >>> Works: * isolinux-4.07.bin (size 24574) * isolinux-5.00.bin (size >>> 34816) >>> >>> Does not work: *

Hi All, ZPOOL / ZFS commands writes EFI label on a device if we create ZPOOL/ZFS fs on it. Is it true ? I formatted a device with VTOC lable and I created a ZFS file system on it. Now which label the ZFS device has ? is it old VTOC or EFI ? After creating the ZFS file system on a VTOC labeled disk, I am seeing the following warning messages. Feb 3 07:47:00 scoobyb

> > It looks like Clonezilla and Ultimate Boot CD both prescribe > special installation procedures for USB stick. > isohybrids can be put onto stick just by e.g.: dd of=/dev/sdb > Make a backup of the stick if you later want to restore its > partitioning. > The (recent yet not latest) versions of Clonezilla that used Syslinux 5.xx will fail in some systems when writing

Hi, Ady wrote: > This is a quote from Wonko/Jaclaz, who has also been investigation this > issue and deserves credit for it: > Ok, not that I understand the code, but what *somehow* happens is that > the "embedded" checksum in Isolinux.bin (starting from 4.00) is the > checksum of the WHOLE file (i.e. starting from offset 0 instead of 64) > at a time when: > 1)

Hi, > # Most linux distros dont have `mkisofs' Or they have genisoimage under the name "mkisofs". (e.g. Debian, Archlinux) > mkisofs \ > -o output.iso \ > -no-emul-boot \ > -boot-info-table \ > -boot-load-size 4 \ > -c isolinux/boot.cat \ > -b isolinux/isolinux.bin \ > ISO_root I would add option -R or -r for Rock Ridge names and file