Found the problem ...<br><br>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.<br><br>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.<br>
<br>So, it boils down to bad HW implementation from my MB manufacture.<br><br>I will rebuild the system using SW RAID instead.<br><br><div class="gmail_quote">On Wed, Jan 21, 2009 at 11:37 PM, Jamie Bohr <span dir="ltr"><<a href="mailto:jamiebohr@gmail.com">jamiebohr@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Same error: Stale NFS file handle<div><div></div><div class="Wj3C7c"><br><br><div class="gmail_quote">
On Wed, Jan 21, 2009 at 4:44 AM, iarly selbir <span dir="ltr"><<a href="mailto:iarlyy@gmail.com" target="_blank">iarlyy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
try to set the permissions below<br><br><br># chown root.root /boot/System.map-2.6.27.9-159.fc10.x86_64<br><br># chmod 644 /boot/System.map-2.6.27.9-159.fc10.x86_64<div><br><br><br clear="all">Regards,<br>- -<br>
iarly selbir ( ski0s )<br>
<br>:wq!<br>
<br><br></div><div><div></div><div><div class="gmail_quote">On Wed, Jan 21, 2009 at 12:15 AM, Jamie Bohr <span dir="ltr"><<a href="mailto:jamiebohr@gmail.com" target="_blank">jamiebohr@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
No go, <br><br># package-cleanup --cleandupes<br>Setting up yum<br>Loaded plugins: kernel-module, refresh-packagekit<br>No dupes to clean<br><br>After doing so more digging I found /boot/System.map-2.6.27.9-159.fc10.x86_64 existed. Very strange file permissions though,<br>
<br>-????????? ? ? ? ? ? System.map-2.6.27.9-159.fc10.x86_64<br><br><br># rm -rf System.map-2.6.27.9-159.fc10.x86_64<br>rm: cannot remove `System.map-2.6.27.9-159.fc10.x86_64': Stale NFS file handle<br>
<br><br>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.<br>
<br>- Jamie<div><div></div><div><br><br><br><div class="gmail_quote">On Tue, Jan 20, 2009 at 7:32 AM, Christopher A. Williams <span dir="ltr"><<a href="mailto:chriswfedora@cawllc.com" target="_blank">chriswfedora@cawllc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div>On Tue, 2009-01-20 at 07:15 -0700, Jamie Bohr wrote:<br>
> I found a problem, don't know if it is related but<br>
> kernel-2.6.27.9-159.fc10.x86_64.rpm fails to install with the<br>
> following error below.<br>
><br>
> # yum update<br>
> .....<br>
> Downloading Packages:<br>
> kernel-2.6.27.9-159.fc10.x86_64.rpm<br>
> | 20 MB 00:28<br>
> ============================================================ Entering<br>
> rpm code ============================================================<br>
> Running rpm_check_debug<br>
> Member: kernel.x86_64 0-2.6.27.9-159.fc10 - i<br>
> Adding Package kernel-2.6.27.9-159.fc10.x86_64 in mode i<br>
> rpm_check_debug time: 0.065<br>
> Running Transaction Test<br>
> Member: kernel.x86_64 0-2.6.27.9-159.fc10 - i<br>
> Adding Package kernel-2.6.27.9-159.fc10.x86_64 in mode i<br>
> Finished Transaction Test<br>
> Transaction Test Succeeded<br>
> Transaction Test time: 0.160<br>
> Member: kernel.x86_64 0-2.6.27.9-159.fc10 - i<br>
> Adding Package kernel-2.6.27.9-159.fc10.x86_64 in mode i<br>
> Running Transaction<br>
> Installing : kernel<br>
> 1/1<br>
> Error unpacking rpm package kernel-2.6.27.9-159.fc10.x86_64<br>
> error: unpacking of archive failed on<br>
> file /boot/System.map-2.6.27.9-159.fc10.x86_64: cpio: rename<br>
> Warning: scriptlet or other non-fatal errors occurred during<br>
> transaction.<br>
> Running "posttrans" handler for "refresh-packagekit" plugin<br>
> Transaction time: 0.373<br>
> ============================================================ Leaving<br>
> rpm code =============================================================<br>
><br>
> Installed:<br>
> kernel.x86_64 0:2.6.27.9-159.fc10<br>
> #<br>
> # rpm -q -a kernel<br>
> kernel-2.6.27.5-117.fc10.x86_64<br>
><br>
> You can see that kernel-2.6.27.9 is NOT installed only kernel-2.6.27.5<br>
> is.<br>
><br>
> Any one know what the error above means?<br>
<br>
</div></div>Looks like something didn't install cleanly a few updates ago.<br>
<br>
I would suggest using package-cleanup to fix it:<br>
<br>
# package-cleanup --cleandupes<br>
<br>
Once that's done, re-run yum update and see if that clears the problem.<br>
If not, we may have to resort to more aggressive tactics. The good news<br>
is this definitely can be fixed (voice of personal experience).<br>
<br>
Cheers,<br>
<br>
Chris<br>
<br>
<br>
<br>
--<br>
==================================<br>
By all means marry;<br>
If you get a good wife, you'll be happy.<br>
If you get a bad one, you'll become a philosopher.<br>
<br>
--Socrates<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div>fedora-list mailing list<br>
<a href="mailto:fedora-list@redhat.com" target="_blank">fedora-list@redhat.com</a><br>
To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-list</a><br>
Guidelines: <a href="http://fedoraproject.org/wiki/Communicate/MailingListGuidelines" target="_blank">http://fedoraproject.org/wiki/Communicate/MailingListGuidelines</a><br>
</div></div></blockquote></div><br><br clear="all"><br></div></div>-- <br><font color="#888888">Jamie Bohr<br>
</font><br>--<br>
fedora-list mailing list<br>
<a href="mailto:fedora-list@redhat.com" target="_blank">fedora-list@redhat.com</a><br>
To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-list</a><br>
Guidelines: <a href="http://fedoraproject.org/wiki/Communicate/MailingListGuidelines" target="_blank">http://fedoraproject.org/wiki/Communicate/MailingListGuidelines</a><br></blockquote></div><br>
</div></div><br>--<br>
fedora-list mailing list<br>
<a href="mailto:fedora-list@redhat.com" target="_blank">fedora-list@redhat.com</a><br>
To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-list</a><br>
Guidelines: <a href="http://fedoraproject.org/wiki/Communicate/MailingListGuidelines" target="_blank">http://fedoraproject.org/wiki/Communicate/MailingListGuidelines</a><br></blockquote></div><br><br clear="all"><br>-- <br>
Jamie Bohr<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Jamie Bohr<br>