HELP HELP HELP

Hi again:  Just tested my first test and proceeded to test
and install a second time.  This time I let the server run
the update after registering with Novell.  However, upon
reboot the server was dorked as it could not read my /usr
and /var partitions (fstab was bad).

Now here is what changed between my first the second build:

I added a separate partition for /usr, that is all.

I could really use a hand here.  If I can't trust the update
mechanism ......

Chris.

Chris wrote:

> Hi again:  Just tested my first test and proceeded to test
> and install a second time.  This time I let the server run
> the update after registering with Novell.  However, upon
> reboot the server was dorked as it could not read my /usr
> and /var partitions (fstab was bad).
> 
> Now here is what changed between my first the second build:
> 
> I added a separate partition for /usr, that is all.
> 
> I could really use a hand here.  If I can't trust the update
> mechanism ......

I never update during the install. Always after. Are you using OES 2
Sp2 ?


-- 
Cheers,
Edward

Yes oes 2a.  I think the issue is a failed kernel update,
possibly a grub error.  I did notice the kernel version sis
not change after the reboot - error.  On my first test
install the install and update resulted in a change in the
kernel version in grub.



>>> On 12/30/2009 at 7:44 PM, in message
, Edward van
der Maas wrote:
> Chris wrote:
> 
>> Hi again:  Just tested my first test and proceeded to 
> test
>> and install a second time.  This time I let the server 
> run
>> the update after registering with Novell.  However, upon
>> reboot the server was dorked as it could not read my 
> /usr
>> and /var partitions (fstab was bad).
>> 
>> Now here is what changed between my first the second 
> build:
>> 
>> I added a separate partition for /usr, that is all.
>> 
>> I could really use a hand here.  If I can't trust the 
> update
>> mechanism ......
> 
> I never update during the install. Always after. Are you 
> using OES 2
> Sp2 ?
>