VMware server 2.0, /usr/src/linux?

Sun Jan 25 22:28:45 UTC 2009

Found the problem ...

I built my system using HW RAID 1 and during a test I booted the system with
one of the drives unplugged.  The system booted just fine, that was the
extent of my testing though.

I have since booted my system with drive 2 unplugged, the system boots the
bad file ( /boot/System.map-2.6.27.9-159.fc10.x86_64) is not present,
rebooted with drive 1 missing only using drive 2, the system would not boot
at all.  Something about SELinux (which is disabled) could not apply a
police and stopped the boot sequence.

So, it boils down to bad HW implementation from my MB manufacture.

I will rebuild the system using SW RAID instead.

On Wed, Jan 21, 2009 at 11:37 PM, Jamie Bohr <jamiebohr at gmail.com> wrote:

> Same error: Stale NFS file handle
>
>
> On Wed, Jan 21, 2009 at 4:44 AM, iarly selbir <iarlyy at gmail.com> wrote:
>
>> try to set the permissions below
>>
>>
>> # chown root.root /boot/System.map-2.6.27.9-159.fc10.x86_64
>>
>> # chmod 644 /boot/System.map-2.6.27.9-159.fc10.x86_64
>>
>>
>> Regards,
>> - -
>> iarly selbir ( ski0s )
>>
>> :wq!
>>
>>
>> On Wed, Jan 21, 2009 at 12:15 AM, Jamie Bohr <jamiebohr at gmail.com> wrote:
>>
>>> No go,
>>>
>>> # package-cleanup --cleandupes
>>> Setting up yum
>>> Loaded plugins: kernel-module, refresh-packagekit
>>> No dupes to clean
>>>
>>> After doing so more digging I found
>>> /boot/System.map-2.6.27.9-159.fc10.x86_64 existed.  Very strange file
>>> permissions though,
>>>
>>> -????????? ? ?    ?          ?                ?
>>> System.map-2.6.27.9-159.fc10.x86_64
>>>
>>>
>>> # rm -rf System.map-2.6.27.9-159.fc10.x86_64
>>> rm: cannot remove `System.map-2.6.27.9-159.fc10.x86_64': Stale NFS file
>>> handle
>>>
>>>
>>> I never even had NFS running on this system, it is a new build.  The file
>>> permissions are the same in single user mode.  If I boot from a rescue disc
>>> the file is not listed.  I have been a UNIX Admin for many years and have
>>> never seen something like this.
>>>
>>> - Jamie
>>>
>>>
>>>
>>> On Tue, Jan 20, 2009 at 7:32 AM, Christopher A. Williams <
>>> chriswfedora at cawllc.com> wrote:
>>>
>>>> On Tue, 2009-01-20 at 07:15 -0700, Jamie Bohr wrote:
>>>> > I found a problem, don't know if it is related but
>>>> > kernel-2.6.27.9-159.fc10.x86_64.rpm fails to install with the
>>>> > following error below.
>>>> >
>>>> > # yum update
>>>> > .....
>>>> > Downloading Packages:
>>>> > kernel-2.6.27.9-159.fc10.x86_64.rpm
>>>> > |  20 MB     00:28
>>>> > ============================================================ Entering
>>>> > rpm code ============================================================
>>>> > Running rpm_check_debug
>>>> > Member: kernel.x86_64 0-2.6.27.9-159.fc10 - i
>>>> > Adding Package kernel-2.6.27.9-159.fc10.x86_64 in mode i
>>>> > rpm_check_debug time: 0.065
>>>> > Running Transaction Test
>>>> > Member: kernel.x86_64 0-2.6.27.9-159.fc10 - i
>>>> > Adding Package kernel-2.6.27.9-159.fc10.x86_64 in mode i
>>>> > Finished Transaction Test
>>>> > Transaction Test Succeeded
>>>> > Transaction Test time: 0.160
>>>> > Member: kernel.x86_64 0-2.6.27.9-159.fc10 - i
>>>> > Adding Package kernel-2.6.27.9-159.fc10.x86_64 in mode i
>>>> > Running Transaction
>>>> >   Installing     : kernel
>>>> > 1/1
>>>> > Error unpacking rpm package kernel-2.6.27.9-159.fc10.x86_64
>>>> > error: unpacking of archive failed on
>>>> > file /boot/System.map-2.6.27.9-159.fc10.x86_64: cpio: rename
>>>> > Warning: scriptlet or other non-fatal errors occurred during
>>>> > transaction.
>>>> > Running "posttrans" handler for "refresh-packagekit" plugin
>>>> > Transaction time: 0.373
>>>> > ============================================================ Leaving
>>>> > rpm code =============================================================
>>>> >
>>>> > Installed:
>>>> >   kernel.x86_64 0:2.6.27.9-159.fc10
>>>> > #
>>>> > # rpm -q -a kernel
>>>> > kernel-2.6.27.5-117.fc10.x86_64
>>>> >
>>>> > You can see that kernel-2.6.27.9 is NOT installed only kernel-2.6.27.5
>>>> > is.
>>>> >
>>>> > Any one know what the error above means?
>>>>
>>>> Looks like something didn't install cleanly a few updates ago.
>>>>
>>>> I would suggest using package-cleanup to fix it:
>>>>
>>>> # package-cleanup --cleandupes
>>>>
>>>> Once that's done, re-run yum update and see if that clears the problem.
>>>> If not, we may have to resort to more aggressive tactics. The good news
>>>> is this definitely can be fixed (voice of personal experience).
>>>>
>>>> Cheers,
>>>>
>>>> Chris
>>>>
>>>>
>>>>
>>>> --
>>>> ==================================
>>>> By all means marry;
>>>> If you get a good wife, you'll be happy.
>>>> If you get a bad one, you'll become a philosopher.
>>>>
>>>> --Socrates
>>>>
>>>> --
>>>> fedora-list mailing list
>>>> fedora-list at redhat.com
>>>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>>>> Guidelines:
>>>> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>>>>
>>>
>>>
>>>
>>> --
>>> Jamie Bohr
>>>
>>> --
>>> fedora-list mailing list
>>> fedora-list at redhat.com
>>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>>> Guidelines:
>>> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>>>
>>
>>
>> --
>> fedora-list mailing list
>> fedora-list at redhat.com
>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>> Guidelines:
>> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
>>
>
>
>
> --
> Jamie Bohr
>

-- 
Jamie Bohr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20090125/e69f29d9/attachment-0001.htm>