<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>'/Dev/Root' on rtnpro</title><link>https://rtnpro.com/categories//dev/root/</link><description>Recent content in '/Dev/Root' on rtnpro</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 11 Mar 2009 07:36:45 +0000</lastBuildDate><atom:link href="https://rtnpro.com/categories//dev/root/index.xml" rel="self" type="application/rss+xml"/><item><title>Resolved Kernel boot problem :D</title><link>https://rtnpro.com/post/resolved-kernel-boot-problem-d/</link><pubDate>Wed, 11 Mar 2009 07:36:45 +0000</pubDate><guid>https://rtnpro.com/post/resolved-kernel-boot-problem-d/</guid><description>&lt;p&gt;I am using Fedora 10 and I was running the kernel 2.6.27.15-170.2.24.fc10.i686 and I was happy until I did a ‘yum update’. My kernel got updated to kernel 2.6.27.19-170.2.35.fc10.i686, and then the system won’t boot the latest kernel. While booting it gave a mesage :&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Unable to access resume device (/dev/dm-1)&lt;/p&gt;
&lt;p&gt;mount : could not find filesystem ‘/dev/root’&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I wondered what had happened? But, the old kernel 2.6.27.15-170.2.24.fc10.i686 seemed to work perfectly. I became fanatic to resolve this issue. I did some googling, and finally came to know that the issue was with /etc/fstab and my Fedora 10 being installed on LVM. Here is my previous fstab details :&lt;/p&gt;</description></item></channel></rss>