Re: creating a bootable iso for raid BIOS flash
On Sun, 8 Jan 2012, the wise Polytropon wrote: Does this image boot successfully? Unfortunately this is also a no go. I think Intel has done something special to their iso's, considering that I'm missing 7MB of data. Regards, Marco -- Men have as exaggerated an idea of their rights as women have of their wrongs. -- Edgar W. Howe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: creating a bootable iso for raid BIOS flash
On Sun, 8 Jan 2012, the wise Polytropon wrote: Does this image boot successfully? I don't know yet because I've used all my cd-r's :-(. Within a few days I'm expecting some new cd-rw's and I'll let you know how things went. If you compare your ISO with the original one, file sizes should be the same for all files; are they? A reason could be that the original one contains some "metadata" that the creating program (which will very probably _not_ be mkisofs as you're using) may have stored there. Things like for example an application ID, copyright information, media name. Maybe the original program did use a different "mechanism" to create the ISO? You can easily add the file sizes inside the original ISO and compare them to your sources (which should be equal) and see where the difference comes from. I think it will be some file system metadata (remember that the ISO-9660 file system occupies "invisible" space within the ISO file). I compared the original iso from Intel with the one generated by me and I really can't see any differences. My generated one is 9MB, and 8 MB of metadata seems a lot to me, or isn't it?. Don't know how Intel makes his iso's. Regards, Marco -- From the moment I picked your book up until I put it down I was convulsed with laughter. Some day I intend reading it. -- Groucho Marx, from "The Book of Insults" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: creating a bootable iso for raid BIOS flash
On Sun, 8 Jan 2012 01:11:30 +0100 (CET), Marco Beishuizen wrote: > On Sun, 8 Jan 2012, the wise Polytropon wrote: > > > If this is depending on the name "[BOOT]", there are > > two ways to deal with special characters in file names, > > if you need to specify them on the command line: > > > > a) use escape sequences: > > -b \[BOOT\]/Bootable_HardDisk.img > > > > b) use quoting: > > -b "[BOOT]/Bootable_HardDisk.img" > > I used escape sequences and that works. The "no match" error is gone. By using [ and ], the shell tries to expand a regular expression where [BOOT] means "one of the letters B, O, or T; neither B/Bootable_HardDisk.img, O/Bootable_HardDisk.img or T/Bootable_HardDisk.img is present, so the shell fully correctly replies with "no match". (In a similar fashion, * and ? are interpreted by the shell.) > > Also read "man mkisofs" about the boot-related > > options, especially -b, where > > > > If the boot image is not an image of a floppy, you need to add > > one of the options: -hard-disk-boot or -no-emul-boot. If the > > system should not boot off the emulated disk, use -no-boot. > > > > is mentioned. Maybe consider using -G instead of -b? > > I tried the -G option and removed the -hard-disk-boot option and now it > created an iso without errors. The size is still 9MB though. I looked > inside the original iso and the one generated by me but I really can't see > any differences. Does this image boot successfully? If you compare your ISO with the original one, file sizes should be the same for all files; are they? A reason could be that the original one contains some "metadata" that the creating program (which will very probably _not_ be mkisofs as you're using) may have stored there. Things like for example an application ID, copyright information, media name. Maybe the original program did use a different "mechanism" to create the ISO? You can easily add the file sizes inside the original ISO and compare them to your sources (which should be equal) and see where the difference comes from. I think it will be some file system metadata (remember that the ISO-9660 file system occupies "invisible" space within the ISO file). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: creating a bootable iso for raid BIOS flash
On Sun, 8 Jan 2012, the wise Polytropon wrote: If this is depending on the name "[BOOT]", there are two ways to deal with special characters in file names, if you need to specify them on the command line: a) use escape sequences: -b \[BOOT\]/Bootable_HardDisk.img b) use quoting: -b "[BOOT]/Bootable_HardDisk.img" I used escape sequences and that works. The "no match" error is gone. Also read "man mkisofs" about the boot-related options, especially -b, where If the boot image is not an image of a floppy, you need to add one of the options: -hard-disk-boot or -no-emul-boot. If the system should not boot off the emulated disk, use -no-boot. is mentioned. Maybe consider using -G instead of -b? I tried the -G option and removed the -hard-disk-boot option and now it created an iso without errors. The size is still 9MB though. I looked inside the original iso and the one generated by me but I really can't see any differences. -- The future is a race between education and catastrophe. -- H. G. Wells ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: creating a bootable iso for raid BIOS flash
On Fri, 6 Jan 2012 17:22:57 +0100 (CET), Marco Beishuizen wrote: > After that I tried to create the iso with: > root@yokozuna:/data2/tmp# mkisofs -r -J -b [BOOT]/Bootable_HardDisk.img > -hard-disk-boot -o raid.iso /data2/tmp > which gives an error: mkisofs: No match > > First I thought the directory name [BOOT] was weird so I changed this to > BOOT. Running mkisofs -r -J -b BOOT/Bootable_HardDisk.img -hard-disk-boot > -o raid.iso /data2/tmp creates an iso, but when I burn this to a cd it > doesn't boot. If this is depending on the name "[BOOT]", there are two ways to deal with special characters in file names, if you need to specify them on the command line: a) use escape sequences: -b \[BOOT\]/Bootable_HardDisk.img b) use quoting: -b "[BOOT]/Bootable_HardDisk.img" Also read "man mkisofs" about the boot-related options, especially -b, where If the boot image is not an image of a floppy, you need to add one of the options: -hard-disk-boot or -no-emul-boot. If the system should not boot off the emulated disk, use -no-boot. is mentioned. Maybe consider using -G instead of -b? > Strange thing also is the fact that the original iso has the size of > ~17MB, but the created iso by me is ~10MB. So it seems I'm missing some > files. You can mount the ISO you've generated and look inside to find out which files may be missing, or if there are differences in file sizes. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
creating a bootable iso for raid BIOS flash
Hi, I have an Intel SRCU42X raid controller that currently has firmware version 414D. The bios flash was done by a "system update package", from Intel which is an iso file that you can burn to a cd. The upgrade to 414D went fine. But the newest firmware version is 414I and is not available as a bootable iso, only as a 414I.rom file (windows only etc.). So I thought: lets alter the 414D iso to the newest 414I iso, and make a new bootable iso. But this was harder than I thought. I extracted the original iso file with file-roller and replaced the 414D.rom file with 414I.rom, and modified the .bat-files references from 414D to 414I. The files and directories in the original iso are: -rwxr-xr-x 1 marco wheel 7828 Feb 9 2006 LICENSE.TXT drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCS16 drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCS28X drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCU41L drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCU42E drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCU42L drwxr-xr-x 2 marco wheel 512 Jan 6 11:24 SRCU42X drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCZCRX drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SROMB42E -rwxr-xr-x 1 marco wheel 1207 Aug 23 2004 SUP.BAT -rwxr-xr-x 1 marco wheel 3732 Feb 11 2006 SUP.TXT -rwxr-xr-x 1 marco wheel 4350 Mar 10 2006 SUP_Release_note.txt -rwxr-xr-x 1 marco wheel 5479 Feb 10 2006 UPDATE.BAT -rwxr-xr-x 1 marco wheel 244 Jan 6 11:25 VER_LOAD.BAT drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 [BOOT] The SRCU42X directory contains the 414I.rom file, an irflash.exe update utility and a run.bat batch file (running irflash.exe with reference to the .rom file). The [BOOT] directory contains one file: Bootable_HardDisk.img. After that I tried to create the iso with: root@yokozuna:/data2/tmp# mkisofs -r -J -b [BOOT]/Bootable_HardDisk.img -hard-disk-boot -o raid.iso /data2/tmp which gives an error: mkisofs: No match First I thought the directory name [BOOT] was weird so I changed this to BOOT. Running mkisofs -r -J -b BOOT/Bootable_HardDisk.img -hard-disk-boot -o raid.iso /data2/tmp creates an iso, but when I burn this to a cd it doesn't boot. Strange thing also is the fact that the original iso has the size of ~17MB, but the created iso by me is ~10MB. So it seems I'm missing some files. So what am I doing wrong and what is the correct commandline to create a bootable iso for flashing a raid controller bios? Thanks, Marco -- If I promised you the moon and the stars, would you believe it? -- Alan Parsons Project ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
