Kennedy, William J. wrote:
>
>> >
>> > Manually mounting the filesystem at /a without the '-t ext3' flags does
>> > not generate an error, only a warning about the lack of journal.
>
> /Well.... this is not a good behaviour.... if you want ext3, the journal/
> /must be used! :-) /
>
> --
> I know - I attempted to mount it manually after the autoinstall failed -
> just to isolate the problem. The mount point exists, the device exists,
> but mounting the device with the journal flag fails. When the script
> does it, as well as mounting it within BOEL by hand.
What happens if you run "mke2fs -j /dev/sda2" and then try again to
mount with -t ext3 (on the busybox prompt)?
And what about /dev/sda3? in the autoinstall script it seems that you're
using ext3 also for this partition... so if it works for sda3 it must
work also for sda2... what are the differences between the 2 partitions?
size, boot flag, ...
>
>> >
>> > I'm using 3.6.3 on the server and client.
>
> /I would suggest to use a more recent release, typically 3.7.5. Anyway,/
> /we're going to release 3.7.6 soon (maybe this weekend), so you can wait/
> /for it, if you've not urgent issues.../
> --
> I am required to use a stable release for this project. I have built an
> imageserver with 3.7.5 in anticipation, but I still having problems.
> Client-side version conflict maybe?
If you don't use a very old release you shouldn't find version
conflicts.. all the recent releases are backward compatible. What kind
of problems did you find? the ext3 problem above or also something else?
>
> Whatever version goes stable next is what I'll be using for the next
> year or so. Unless the upgrade process proves painless and reliable, I
> will not be upgrading the client software once it is deployed.
>
sounds reasonable. ;-)
>> >
>> > Here is my autoinstall.conf:
>> >
> ...
> /it seems ok./
>
> Will this need to change with different images? This image is a
> development image, and it seems to have replaced the information for my
> reiserfs-based "stable" image.
>
Every autoinstallscript.conf will be used to generate a master script
image in /var/lib/systemimager/scripts. If you don't explicitly use
--script SCRIPTNAME option with si_mkautoinstallscript it will be used
the name of the image as the basename of the master script.
>> > The image I am trying to restore is a rebuilt version of an existing
>> > image. The partitions and filesystems are different (ext3 vs.
>> > reiserfs), and I have regenerated an autoinstall.master script for the
>> > new image, both manually and by hand.
>
> /why didn't you use si_mkautoinstallscript? maybe manually you missed/
> /something in the fs creation.... did you add the -j option to mke2fs?/
>
> When I say "manually", I mean by manually running the si_mkautoinstall
> script utility in addition to the script automatically created during
> the 'si_getimage' process.
OK.
>
>> >
>> > 3.6.X is supposed to have the ''--my-modules" option for UYOK, correct?
>> > It's failing for me.
>
> /If I remember well the option --my-modules has been added in 3.7.4./
>
> That's what's confusing. The documentation suggests that it's in the
> 3.6 tree..
what do you mean with documentation? wiki, man pages? I'll check when
the option has been added exactly...
>
> I upgraded the server and client to 3.7.6r3835_arighi-1. I'm running
> into different issues (not able to create initrd - "file exists at
> UseYourOwnKernel.pm @ line 124"), but once I get those worked out, I'll
> test an image.
??? never seen that...
In fact at line 124 of UseYourOwnKrnel.pm:
mkdir("$staging_dir/lib/modules", 0755) or die "$!";
If you get a "file exists" errors it means that you have it in your
initrd template. But in the standard RPM the file doesn't exist:
$ rpm -qpl
systemimager-i386initrd_template-3.7.6r3835_arighi-1.noarch.rpm | grep
modules
/usr/share/systemimager/boot/i386/standard/initrd_template/lib/udev/pnp_modules
/usr/share/systemimager/boot/i386/standard/initrd_template/my_modules
/usr/share/systemimager/boot/i386/standard/initrd_template/my_modules/INSMOD_COMMANDS
Are you using 3.7.6r3835_arighi-1 in your golden client? Did you add
manually
/usr/share/systemimager/boot/i386/standard/initrd_template/lib/modules?
Anyway, maybe we should relax the constraint and remove the "or die $!"
part...
Regards,
-Andrea
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
