[Buildroot] Creating a bootable filesystem image?

[Arun Reddy]

One more message before I await some more feedback. Following Sebastian's
advice, I am trying to play around with buildroot's menuconfig to try to
make the FS image larger. I have gone into:

Target filesystem options -> ext2 root filesystem.

There are three selections: size in blocks, inodes, reserved blocks
percentage. They are all set to 0 right now for auto calculation. Clearly
autocalculation is only making the FS "big enough" and adding the extra
features from GRUB simply won't fit.

Rather than ask what you guys selected, can anyone direct me on where I can
find out more information about these buildroot options, or a buildroot
guide on how to properly select the FS size? Or do you guys think I should
just experiment and make them a large size to see if this works? I think the
former is better since I would actually know what these options do. Thanks!

Arun

On Mon, Apr 14, 2008 at 9:57 AM, Arun Reddy <reddyac at gmail.com> wrote:

> Hi Sam,
>
> Just to be clear are you referring to the same script "build-ext3-img"
> script? If so can I get some more information on what exactly it is you are
> trying to fix with it?
>
> I would like to point out that I was also able to bypass the error Sam and
> I mentioned by simply moving my .iso image from the .../binaries/uclibc
> folder and placing it somewhere else. Using the script, it then made use of
> the actual rootfs.i386.ext2 image. Unfortunately I am still getting the
> error that there is no space.
>
> arun
>
>
> On Fri, Apr 11, 2008 at 12:11 PM, Sam Liddicott <sam at liddicott.com> wrote:
>
> > I've managed to understand lba and chs freakery.
> >
> > The disk image chs mapping that gub ses is not the one used bye the
> > mount the copied the files.
> >
> > I've spent the best part of a day this week playing with lba and chs
> > mappings and think that on Monday I can fix the script.
> >
> > Sam
> >
> >
> > ------------------------------
> > From: Arun Reddy <reddyac at gmail.com>
> > Sent: 11 April 2008 19:51
> > To: Sebastian <bastisoft at arcorde>
> > Cc: Buildroot List <buildroot at uclibc.org>
> > Subject: Re: [Buildroot] Creating a bootable filesystem image?
> >
> > Sebastian and Buildroot members
> >
> > I will try this as soon as I can. Right now I am not near my machine
> > with my build system. If anyone can please try this out for themselves to
> > give further feedback I would greatly appreciate it. This might be something
> > I can submit as a bug if everyone is experiencing it. Thank you and I will
> > let you know about my results as soon as I can
> >
> > Arun
> >
> > On Wed, Apr 9, 2008 at 10:44 AM, Sebastian <bastisoft at arcor.de> wrote:
> >
> > > Hello Arun,
> > >
> > > I tried to create an ext2 file system myself (i486 architecture
> > > without any applications enabled).
> > >
> > > The first two questions I answered with return, the last one with
> > > /home/basti/linux/buildroot/binaries/uclibc/ and then I noticed that the
> > > fdisk command gave the same error message as you wrote.
> > >
> > > But it doesn't create a partition, so I create one myself: (n)ew,
> > > (p)rimary, (1), return, return, (w)rite. Then it tries to install grub which
> > > fails for me, as it can't find /boot/grub/stage1 on the image. If I could
> > > provide these files, it should work, as grub recognizes the partition.
> > >
> > > Maybe you could try to build no ISO image at all, just the ext2 (ext3)
> > > root file system. I have really no idea why it tries to copy your iso file
> > > onto the image, as it is not to be placed there.
> > >
> > > Best regards,
> > > Sebastian
> > >
> > >
> > >        Sebastian,
> > > >
> > > >        Thanks for the information, I do understand it much clearer
> > > >        now. I am attempting to run the script and find out whether
> > > > my
> > > >        input will result in the bootable filesystem I want. When
> > > >        running build-ext-img, I input
> > > >
> > > >        Enter the path to the image:
> > > >
> > > >        I input "/root/buildroot/scripts/" since that is where the
> > > >        filesystem image is located.
> > > >
> > > >        Enter the name of the image file:
> > > >
> > > >        I input "buildroot.img"
> > > >
> > > >        Enter the path to the root filesystem that you want to
> > > > install
> > > >        the image
> > > >
> > > >        I input "/root/buildroot/binaries/uclibc/" since this is
> > > > where
> > > >        my filesystem image (rootfs.i386.ext2) is located.
> > > >
> > > >        When the script runs, it looks like everything is ok at
> > > > first,
> > > >        but eventually I get the warning stating Device contains
> > > >        neither a valid DOS partition table, nor Sun, SGI... etc. It
> > > >        builds a new DOS disklabel for me, so I go ahead and
> > > > continue.
> > > >        I also get a warning that there is an invalid flag 0x0000 of
> > > >        partition table 4 that will be corrected by w(rite) which I
> > > > go
> > > >        ahead an accept. I then type q to quit and continue building
> > > >        the bootable FS.
> > > >
> > > >        I am finally left with
> > > >
> > > >        cp: writing /root/buildroot/scripts/temp/rootfs.i386.iso: No
> > > >        space left on device.
> > > >
> > > >        I examined the script and noticed when installing software to
> > > >        the image, ${IMAGE} is mounted to ${IMAGE_PATH}/temp, then
> > > >        ${ROOT_PATH}/* is copied to that location, and then the temp
> > > >        folder is unmounted and removed. Am I getting that there is
> > > > no
> > > >        space on the device because it is trying to copy to a folder
> > > >        where the image is mounted? Or did I not correctly interpret
> > > >        the inputs correctly above? Thanks for answering these. I
> > > >        should point out I am using Snapshot from 4-1-2008.
> > > >
> > > >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildroot.org/pipermail/buildroot/attachments/20080414/0254e4a6/attachment-0001.html>