Fedora :: Cannot Open Root Device "<NULL>" Or Unkown-block(202,17)

Jun 21, 2009

VFS: Cannot open root device "<NULL>" or unkown-block(202,17)
append a correct "root=" boot option
Kernel panic not syncing
VFS: unable to mount root FS on unkown-block(202,17)

I have a Dell xps with a dual core, 8 gigs ram, a primary hard drive with vista on it, and a secondary with linux in its future. It starts loading vmlinuz but ends up with the kernel panic before anything else. I am able to install earlier cores (5-8) and vista recognizes the ram just fine.

View 1 Replies


ADVERTISEMENT

General :: VFS: Cannot Open Root Device "(null)" Or Unknown-block(8,1)

Apr 16, 2011

I got a problem with my kernel. The initramfs source is busybox, python and gcc from ubuntu. The busybox have i compiled it self. Python and gcc is from /usr/bin. I gonna install my kernel on a i586 machine. Old yes. On the xTerm (termial) it stand "root device 8,1).

Quote:

VFS: Cannot open root device "sda1" or unknow-block(0,0) append a correct "root=" boot option; here are the available partions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)Pid: 1, comm: swapper Not tainted 2.6.38.3 #1

Call trace: This is my syslinux.cfg

default menu.c32
prompt 0
menu title BOOTLOADER

[code]....

View 2 Replies View Related

OpenSUSE Install :: VFS - Cannot Open Root Device "NULL" Or Unknown-block - 3,1

Nov 14, 2009

Currently running rc2. Downloaded 11.2 final DVD, md5sum is good, burned DVD, YaST says media check is good. (And for completeness burned a second DVD and get the same problem.)

On booting from the DVD I select "Installation" - a kernel loads and starts checking available h/w devices then crashes with the above message.

Followed by Please append a correct "root=" boot option.

Tried with root=sda1 (partition that is /) and only change is unknown-block (0,0)

My best guess is that I have EXT4 (did a clean install of RC2)? And/or I dont have a swap partition?

View 1 Replies View Related

Ubuntu :: VFS: Cannot Open Root Device "mapper/mylaptop-root" Or Unknown-block(0,0)

Nov 5, 2010

Installed Maverick last night... the system has been working fine all day... then on a reboot tonight got the following.

RAMDISK: gzip image found at block 0
usb 1-2: new high speed usb device using ehci_hcd and address 2
uncompression error
VFS: Cannot open root device "mapper/mylaptop-root" or unknown-block(0,0)

[code]....

Then it gives the Kernel Panic

Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper not tainted 2.6.35-22-generic #35-Ubuntu

Then a call trace...This is a brand new install of Maverick I copied my files onto a USB and did a fresh install on the whole drive using the alternate CD (the desktop and netbook editions both failed to read on my system) was previously using Karmic with no issues. I tried to e2fsck the dev/sda1 from the CD in "repair broken system" mode but the return was "clean" I read that as the file system being intact but this is an area that I have no real knowledge in.

View 1 Replies View Related

General :: VFS:Cannot Open Root Device "hdxy" Or Unknow-block(0,0)

Nov 29, 2010

I got a HP LH 3000.Current OS release is RH9 2.4.20,and I wanna update it to RH9 2.6.5 While updating,I met the problem followed:

VFS:Cannot open root device "hdxy" or unknow-block(0,0)

Followed are packages I used:

device-mapper-1.00.19-2.i386.rpm
linux-2.6.5.tar.bz2
mkinitrd-4.1.18-2.i386.rpm
lvm2-2.00.25-1.01.i386.rpm
module-init-tools-3.2.tar.bz2

First I installed the mkinitrd-4.1.18-2.i386.rpm, then compiled the kernel and installed it.

View 5 Replies View Related

Ubuntu Installation :: From A USB Flash Memory Stick - Warning "VFS: Cannot Open Root Device "sda6" Or Unknown-block(0,0)" And Kernel Panic On First Boot

Apr 24, 2011

I am trying to install Ubuntu 10.10 from a USB flash memory stick. It works fine until around 95%, where I get the following warning/error:

[Code]....

I click OK and the installer seems to finish nicely, except the terminal throws several errors along these lines (see photo):

[Code]....

I tried also with 10.04 LTS, the difference being that the install warning appears two or three times instead of once. Some results from googling (Ubuntu Forums, Ubiquity bug) suggest unchecking the initial update options. I am going to try this but I'm not sure if I'll be able to get the boot loader right (there seemed to be problems with this).

View 7 Replies View Related

OpenSUSE Hardware :: No Application That Can Open Type Block Device (inode/blockdevice)?

Jul 21, 2010

I'm having trouble mounting hard drives and partitions - and am rather nervous about using Yast partitioner to do this. Is there something that would tell me about mount points in Yast partitioner? So far I haven't been able to find that information anywhere. I don't want to lose information on existing drives and partitions but do want to be able to access them.Some of them appear under disk information in "My Computer" but if I try to mount them I get this error message.There is no application installed that can open files of the type block device (inode/blockdevice).I was trying to edit fstab,his didn't seem straightforward either. I've been hacking this about in other Linux distros - so not entirely clueless

View 6 Replies View Related

Fedora :: Coin Error In Glxglue_init(): Couldn't Open NULL Display

Jan 23, 2010

I wrote a simple code using Open Inventor(OpenGL) classes to print a Sphere in a .png file.I tested it on Windows and it worked well.But when I run it on Fedora 10, I got the following error with no output .png file:

Coin error in glxglue_init(): Couldn't open NULL display. Coin warning in SoOffscreenRenderer::renderFromBase(): Could not set up an offscreen OpenGL context.
Segmentation fault

View 2 Replies View Related

Red Hat :: Cannot Open Root Device?

Oct 25, 2010

I have a redhat ES3 I want virtualized.the virtual machine encounters a problem starting when it is virtualized

There are this message :
RAMDISK : couldn't find valid RAM Disk image Starting at 0.
VFS: Cannot open root device "LABEL=/" or 00:00
please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00

View 2 Replies View Related

CentOS 5 :: VFS - Cannot Open Root Device

Mar 22, 2011

I have added CentOS5.5 x86-64 to a linux box that already contains installations of Ubuntu 9 and SL 5.2. Grub2 was installed with Ubuntu and is on the MBR of the disk. I did not install grub with anaconda/Cent. Grub update in ubuntu finds the Cent install and addes it to the grub.conf, and Cent appears in the grub menu at boot. If I select Cent, I get the following error.
VFS: Cannot open root device "sda7" or unknown-block(0,0)
Please append a correct "root=" boot option

Below is the output of boot_info_script, which gives the relevant boot file data. There are still grub conf files on the SL install, but grub is not installed there anymore.
Boot Info Script 0.55 dated February 15th, 2010
=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in partition #6 for /boot/grub .....
sda3/boot/grub/grub.conf:
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that all kernel and initrd paths are relative to /, eg.
# root (hd1,2)
# kernel /boot/vmlinuz-version ro root=/dev/sdb3
# initrd /boot/initrd-version.img

View 1 Replies View Related

Ubuntu :: Unable To Start - Cannot Open Root Device

Apr 23, 2010

When booting up my IBM Thinkpad Ubuntu stalls giving the following messages:

Cannot open root device "uuid=58a5831c-5757-49f8.....

Kernal Panic - not syncing: Unable to mount root fs on unknown-block

Spurious ACK on isa0060/serio0. Some program might be trying to access hardware directly.

I am or was using Hardy.

It seems to me that the program is telling me it can't find the hard drive or the partition where the OS resides. I have my drive partitioned with into sections for booting, the OS and my Home directory.

View 7 Replies View Related

Slackware :: Won't Boot After Update - VFS Cannot Open Root Device

Oct 21, 2010

I have been trialling Slack 13.1 on a spare 32b system for a couple of weeks, and today I took the plunge and put it on my main machine. I completely re-partitioned the drive (using the Slack disk) and installed Windows7 on one partition and Slack 13.1 on another. The install worked fine and I tested that it boots from LILO into both Windows and Slack perfectly. I then ran:

slackpkg update
slackpkg install-new
slackpkg upgrade-all

And since then it fails to boot with the following:

Code:
VFS: Cannot open root device "802" or unknown block(8,2)
Please append a correct "root=" boot option; here are the available partitions:
0840 488386584 sde driver: sd
0841 97659103 sde1
0842 19535040 sde2
0843 498015 sde3

[Code]....

I have seen many, many similar problems when searching Google but they all seem to be caused by different things.

View 8 Replies View Related

Debian Configuration :: Kernel Panic: Cannot Open Root Device

Jun 7, 2010

I am using a kernel with no initrd. I have had this kind of panic before. Usually it means that the kernel can access the hard drive because the driver for the controller or filesystem isn't built into the kernel.

The kernel is 2.6.34 vanilla.

My IDE controller is a Silicon Integrated Systems SiS 5513, and I built the driver for it into the kernel BLK_DEV_SIS5513=y

My /boot (hda1) is ext2, and everything else is ext3

EXT2_FS=y
EXT3_FS=y

My grub entry (hda2 is my root partition) kernel (hd0,0)/vmlinuz root=/dev/hda2

View 5 Replies View Related

Debian Programming :: R Graphics Can't Be Viewed On Null Device

Jul 19, 2015

So I wanted to use R's graphics to visualize information, but when I typed

Code: Select alldemo (graphics::graphics), R's built-in introduction to its graphics, the separate window opened up with no graphics, and the terminal returns

Code: Select allError in plot.new() : attempt to plot on null device.

I have the core Jessie packages for R, so I don't think that is the issue.

View 0 Replies View Related

Software :: Failed To Open /dev/null?

Sep 24, 2010

Having an odd boot message with Ubuntu 10.04. I've had it since I first installed Ubuntu a few months back and I am getting tired of it slowing down my boot up time.No luck on the Ubuntu forums or bug reports; no one seems to know what to do.uote:udevd-work [332] open /dev/null failed no such file or directory

View 6 Replies View Related

Fedora :: Can A Removable Block Device Be Always Recognized With Same Name

Apr 7, 2010

I have an external hard disk drive and I would like it to be recognized with the same name (e.g. /dev/sbd) after each boot.
Is there any way to make that?

View 7 Replies View Related

Server :: Kernel Panic - WARNING: Can't Access (null) Exec Of Init ((null)) Failed

Aug 5, 2010

I have a server running Red Hat Enterprise Linux ES (2.6.9.55.ELsmp). When it starts up I get the following error: Uncompressing Linux... Ok, booting the kernel. Red Hat nash version 4.2.1.10 starting WARNING: can't access (null) exec of init ((null)) failed!!!: 14 unmount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init!

After that I got no response from the OS. I have the installation CD, so I tried to start the rescue mode, while going through the steps I received an error stating that mounting to /mnt/sysimage failed and that if I want to I can access a shell. I really don't know what to do from here

View 6 Replies View Related

General :: Use Gedit To Open File With Null Characters?

Feb 15, 2011

I know GEdit has a bug which prevents it from opening a file with null () characters in it. This is a huge inconvenience for me because I frequently have to open big log files with only a couple rogue 's in them.

Sometimes I just run a quick tr -d '' < file.log > file.log.correct and open the correct file. This is a big nuisance. I would like to have maybe an external tool in GEdit that would execute the above command. I tried writing an external tool action (GEdit plugin) using just:

#!/bin/bash
tr -d ''

Input is "current document", output action is "replace current document". But this isn't working. When I open the file, GEdit shows the familiar red warning; activating the external tool with the warning showing apparently has no effect (I think the script is being called but its input/output are not set).

View 1 Replies View Related

Fedora :: Kernel: Buffer I/O Error On Device Dm-0, Logical Block 124

Nov 28, 2009

I have 2 hdds, with encrypted / and /home. Besides there are four other (encrypted ext4) partitions I use rarely. In Fedora 11 at boottime I gave the luks passphrase for / and home and the system booted as intended.

Whenever I needed those extra encrypted partitions I mounted them in Nautilus. Now, in Fedora 12 at boottime dracut tries to open all the encrypted partitions, / and /home are mounted fine, but opening all the other partitions gave the following messages in messages.log:

Quote:

dracut: luksOpen /dev/sdb6 luks-02a0e706-a26f-4019-a2a0-88a0366a994d
kernel: Buffer I/O error on device dm-0, logical block 124
kernel: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-304
kernel: Buffer I/O error on device dm-0, logical block 124
kernel: Buffer I/O error on device dm-0, logical block 124

[code]....

...and these messages are repeated with the other partiitions, and the boot time takes very, very long. How can I tell dracut to ignore those extra encrypted partitions at boottime?

View 8 Replies View Related

Fedora Installation :: F10 Live CD Buffer I/O Error On Device Sr0 Logical Block?

Jan 29, 2009

Create symlink /dev/root and then exit this to continue the boot sequence.

Buffer I/O error on device sr0, logical block *******
sr 4:0:0:0 [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sr 4:0:0:0 [sr0] Sense Key : Medium Error [current]
sr 4:0:0:0 [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1395920
Clocksource tsc unstable (delta = -499902943 ns)

loops that during install. new hard drive fresh out of box. WD 320GB 7200 Toshiba Qosmio intell core duo i've installed with this same disk before previous hard drive died. installed over windows vista. this time im trying to install solo no windows disk to reinstall with, F10 only. I've tried other distros as well, Mandriva one 2009, Dreamlinux, and this one. i've suspected hard drive controller went out but i can format and partition the drive. also the cd/dvd drive is bad but im booting from cd fine. tried removing the cd drive and booting from an external usb cd rom, same errors.

im about to deploy and need my computer up and running ASAP. 7 months no entertainment is not good. when i use a linux boot disk from Ultimate Boot Disk (UBD) i get an error of - hda status no response and something about invalid heads dreamlinux pushes past the error till i get the error about cant start x server. about my graphics

View 1 Replies View Related

Red Hat / Fedora :: Unable To Mount Root Fs On Unknown Block?

Nov 23, 2010

i bought following server about some days ago :Supermicro X8DTi1u Super micro
2x 1TB Sata 2 i want install centos 5.5 64bit on it, i download centos 5.5 64bit from centos.org torrent link but when i want setup centos it says :kernel panic : not syncing : VFS: unable to mount root fs on unknown block(253,3)and also i set adptec raid in my bios and set raid 0 in adptec raid controller (my mainboard has onboard raid) i run any command you think like linux dd, linux all-generic-ide, linux noprobe, linux nostorage and etc but none of them does not work for ,e

View 6 Replies View Related

Fedora Installation :: Livecd Cant Burn Correctly / Buffer I/O Error On Device Sr0 Logical Block 352328?

Oct 3, 2009

i've just burned a livecd (fedora 11), but it doesn't work correctly.it says after i hit boot:

BUFFER I/O error on device sr0 logical block 352328

and then something else, which is similar so i didn't write it down.i read on bugzilla, that is should try to append the boot command with pci=nomsi, but it doesn't work for me

View 3 Replies View Related

Fedora :: Kernel Panic - Not Syncing: VFS Unable To Mount Root Fs On Unknown-block (0,0)

Jul 23, 2010

I just installed the DVD iso of Fedora 13...and did a "sudo yum update" after the installation got finished. After 3 hours of waiting, I restarted. I was greeted by Fedora with a kernel panic, right after it boots up.

Here's the message:

Code:

Kernel Panic - not syncing: VFS unable to mount root fs on unknown-block (0,0)

EDIT: Here's the content of grub.conf

Code:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that

[code]....

What is peculiar on this grub.conf, is that the 2.6.33.6-147 boot conf is missing an initrd line...I looked in the /boot directory...and I found out that the initramfs file that matches the 2.6.33.3-147 kernel is also missing (i.e initramfs-2.6.33.3-147.fc13.i686.PAE.img).

View 1 Replies View Related

Fedora :: Kernel Panic - Not Syncing - VFS - Unable To Mount Root Fs On Unknown-block - 0,0

May 10, 2011

My Fedora 14 box is no longer starting. I am getting a message at startup - "Kernel panic - not syncing:

VFS: Unable to mount root fs on unknown-block(0,0)".

Unfortunately, I don't know what I did before I got the message. I mean, I have made various installations, including some kernel drivers (such as a wifi card and a sound card). Also I did need to update the kernel-devel package as a requirement for some install or other. I know that is not very helpful, but let's get to the important bit...

What does the message "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" mean? What has broken?

And how does on recover from it? I have been reading around, and of course I am able to boot the machine from a live CD, but I am not sure what I should do with grub.conf, what I should rebuild, how to do it and so on.

View 3 Replies View Related

Ubuntu Installation :: "Cannot Open Root Device" While Booting Install Iso On Flash Drive?

Sep 26, 2010

Ubuntu 10.04.1 to prepare a USB flash drive for use as installation media for a new computer that's on the way. When the Linux kernel tries booting up on the flash drive, I get an error saying VFS: Cannot open root device "<NULL>" or unknown-block(8,1).Here's how I got to this point...Created bootable partition on the thumb drive.Put the following files onto the flash drive: initrd.gz, vmlinuz, and ubuntu-10.04.1-server-amd64.iso fromhttp://archive.ubuntu.com/ubuntu/dis...ages/hd-media/Install Grub2 to the drive via grub-install.Put the following into boot/grub/grub.cfg:

Code:
set timeout=120
set default=0

[code]....

View 9 Replies View Related

General :: Error: VFS: Cannot Open Root Device "343" Or 03:43

Jul 16, 2010

I have been working with a project pc. I have a new HD loaded with Linspire. After loading the o/s I replaced the motherboard and cpu. I now have a Biostar A780L (Didn't see it listed on the HCL) and an AMD Athalon II Multi-Core Processor. Now when the pc boots I get an error:VFS: Cannot open root device "343" or 03:43 append a correct "root" boot option Kernel panic: VFS: Unable to mount the root fs on 03:43 I tried reloading the o/s but the disk won't read from the DVD ROM. Checked my BIOS and it appears to me that it should read from the DVD ROM first but it goes to the HD and tries to load the o/s there.

View 6 Replies View Related

Fedora Installation :: Kernal Panic - Not Synching - VFS - Unable To Mount Root Fs On Unknown Block - 0,0

Aug 14, 2009

I've got the following system:

Quote:

I've been having problems with the system ever since I replaced the motherboard. Moving slow and just generally acting 'wonky.' Well the other day I reached my frustration limit and wiped the HDD. Up to this point the HDD had been in 2 partitions, one for the DELL diagnostics and one for the OS, XP Pro.

I decided that I wanted to set up the system in a dual-boot during the rebuild so I created a two partitions using the Windows install. Partition one is the DELL Diagnostic partition, partition 2 is the XP Pro partition and partition 3 is to be the Linux partition. All seemed to go well with the Windows install. I got the OS up and running and got all the updates done and drivers installed.

I only have the one HDD in the system so I was going to have to make this dual-boot off of one HDD.

I had previously, within the past week or two, downloaded the .iso and created the disk for FC11.

I went through the install process and successfully installed Linux on the 3rd partition, or so I thought. When I attempted to boot into Linux I got the Kernal Panic error.

My grub file as it exists now is:

Code:

If I leave the file as is, I get the kernal panic error but the splash image works fine. If I try to change the 'splash image' and 'root' references from '(hd0,2),' then neither works.

I can boot into Windows XP from the setup as it is now.

I if I boot using my LoaS (FC 11 made at the same time as the images for the cds were downloaded) I can see the hdd and multiple partitions. There seems to be a 'boot' partion, the Linux OS partition, a swap partion, as well as the Dell and XP partions. Now I've tried changing the references in the grub file to reflect the different partitions, basically I've tried 2, 3, 4 and 5, everything but 0 (the dell diagnostics) and 1 (the XP Pro).

I've also re-wiped the HDD and started the whole process over from scratch, thinking maybe I'd hosed something up the first time, but being a firm believer in 'Always do what you've always done and you'll always get what you've always gotten,' and that one of the definitions of insanity it keep performing the same actions over and over and expect different results, I seem to be at impasse here.

Results from 'sfdisk -l'

Quote:

View 11 Replies View Related

Fedora :: Raid1 Kernel Panic - Not Syncing - VFS Unable To Mount Root Fs On Unknown-block - 0,0

Dec 13, 2010

I have trawled through an extensive number of post on quite a few forums without even a step forward with this.

I have a fedora 13_x64 system with software raid1 for /boot and / (md0 and md1 respectively) , swap is not raided.

I was doing an yum update through the software updater in gnome and the system froze.

I had to press reset to get any response from the machine.

Since then I have been getting the kernel panic above just after grub starts fedora.

I tried the previous kernel from the previous update and it has the same error.

At the worst I am prepared to load OS again but there is still some info and configs that I would like to access from the raid partitions before I go ahead. Is there any way to access these partitions through a live CD or rescue environment?

Is there a method to bring this install back to life? or am I looking at a reinstall?

View 1 Replies View Related

Fedora :: FC12 - Kernel Panic - Not Syncing: Vfs - Unable To Mount Root Fs On Unknown Block - 0,0

Feb 1, 2010

I just installed a fresh copy of Fedora Core 12 on a system. I have a 1 GB swap partition, a 20 GB root partition and a 50 GB /video partition (for a mythtv system I am building).

Installation went fine, but upon the initial boot, I get:

Kernel panic - not syncing: vfs: unable to mount root fs on unknown block (0,0)

I can boot off the FC12 cd and go to the rescue option and get to a shell, but not sure where to go from

View 9 Replies View Related

Fedora Installation :: FC13 - Kernel Panic - Not Syncing VFS Unable To Mount Root Fs On Unknown Block?

Oct 14, 2010

I am running FC13 on a fairly old PC (PIII 500MHz, 384MB RAM, 10GB SCSI disk). It works fine using kernel 2.6.33.5-112.fc13.i686.PAE. After a series of recent updates the system now also has a new kernel 2.6.34.7-56.fc13.i686.PAE.

/boot/conf/grub.conf contains:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
code....

When I try and boot to the newer kernel I get an error like:

Kernel panic - not syncing VFS Unable to mount root fs on unknown block(0,0)

I read on the forum about a similar problem where the fix was to insert the line

initrd /initramfs-2.6.34.7-56.fc13.i686.PAE.img

but this file doesn't exist and so the boot then hangs with no messages, so I took this line out again. Here is contents of /boot:

$ ls -l
total 21148
-rw-r--r--. 1 root root 111391 May 27 04:06 config-2.6.33.5-112.fc13.i686.PAE
-rw-r--r--. 1 root root 112291 Sep 15 04:32 config-2.6.34.7-56.fc13.i686.PAE
drwxr-xr-x. 3 root root 1024 Jan 23 2010 efi
code....

As you may deduce from the above I haven't used the system much so the auto-update hasn't run for several months.

Any help on running / installing the newer kernel appreciated. Note that I am trying to install a wireless LAN card and am following instructions here: url

I got as far as

cd /lib/modules/`uname -r`
ls -l

which gave:

[root@localhost 2.6.33.5-112.fc13.i686.PAE]# ls -l
total 3300
lrwxrwxrwx. 1 root root 51 Jun 3 00:52 build -> ../../../usr/src/kernels/2.6.33.5-112.fc13.i686.PAE
drwxr-xr-x. 2 root root 4096 May 27 04:08 extra
drwxr-xr-x. 11 root root 4096 Jun 3 00:52 kernel
code.....

so I have the src files for the newer kernel not the one I am running. I thought it best to stop and think (and ask for help!) rather than break a working machine (but with no wireless LAN!)

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved