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


ADVERTISEMENT

Ubuntu Multimedia :: Unable To Open Device /dev/dsp - Device Or Resource Busy

Apr 13, 2010

All my music editing software programs say, "unable to open device /dev/dsp.Device or resource busy." How can I fix this?

View 3 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

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

General :: Can't Find Boot Device - Error "Unable To Determine Major/minor Number Of Root Device"

Mar 17, 2011

I just compiled my first own kernel (I'm using Arch Linux), following the tutorial on the german site. Now I tried to boot it, I ended up failing with this message: Code: Waiting 10 seconds for device /dev/sda1 ... Root device '/dev/sda1' doesn't exist, Attempting to create it. ERROR: Unable to determine major/minor number of root device '/dev/sda1' Here is the important part of my menu.lst:

[Code]....

I simply copy&pasted the Arch-entry, i.e. I also had the disk by uuid there. The failure message was the same, just the root device name was the different name Also, at first I did not have the initrd line in my menu.lst (as written in my tutorial that I may not need it). In this case I had this error message:

[Code]....

View 10 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

Ubuntu :: Moto4Lin - Unable To Open Device

Mar 6, 2010

I have installed moto4lin, as I want to be able to get pictures off my razr v3mM, which I could easily do in Windows. I found a guide for connecting a v3m, but for some reason moto4lin is screwing around with me. Here is my log:

[info] Phone is unplugged. Please connect it
[info] Phone plugged as AT
[info] Switching device /dev/ttyACM0 to P2K mode...
[error] Unable to open device
[error] Please check preferences
[info] Switching device /dev/ttyACM0 to P2K mode .....

View 5 Replies View Related

Fedora :: Cannot Open PCM Device Alsa_pcm For Playback / Start Jack Successfully?

Mar 18, 2009

attempting to start Jack using the qjackctl frontend...code...

then Jack stops... how do i start Jack successfully?

View 3 Replies View Related

Fedora :: Unable To Find Root Device In 14?

Jan 17, 2011

out in finding root device of fedora 14. I've windows XP and fedora 14 installed on. this is the output for blkid

/dev/sda1: UUID="962C8EA82C8E834B" TYPE="ntfs"
/dev/sda5: UUID="262C06BF2C068A4F" TYPE="ntfs"
/dev/sda6: UUID="cbcf539a-dee1-4f2f-b68c-ce315ae76e0f" TYPE="ext4"

[code]...

View 2 Replies View Related

Fedora :: Unable To Find Root Device Booting 14?

Mar 19, 2011

I've installed Fedora 15 with Fedora 14 already installed in other partitions, but now I can't boot Fedora 14 as it prompts "no root device found", these are both grub.confQuote:

#boot=/dev/sda
default=0
timeout=120

[code]...

View 2 Replies View Related

Ubuntu :: Virtual Network Device - Unable To Start Services

Jun 15, 2010

Just upgraded fro 9.10 to 10.04, and went to start VMware player. It needed to load and compile some modules.

All of them got a nice green tick except the Virtual Network Device

Unable to start services. See log file /tmp/vmware-root/setup-2986.log for details.

I cant access that log file. Set the folder to read only, and any contents, but theres no file in there.

How do I solve this so I can run WMware?

View 3 Replies View Related

Ubuntu Servers :: Unable To Open Device /dev/megadev0: No Such File Or Directory

Jun 19, 2011

I have an Ubuntu server x64 (10.04) that is running FOG for imaging Its installed on an Intel server board (1 RU rackmount) I configured the RAID in an Intekl based BIOS utility which Looks similar to This Ubuntu installed and runs perfectly. however im unable to monitor the status of the drives from the OS, so Im unaware of any drive failures that may occur I manged to install megacli but it returns blank data (along with exit code: 0x00) Iv also tryed megactl wich says

Code:

unable to open device /dev/megadev0: No such file or directory

one of my colleagues who had used the server previously was certain that the raid was on board the intel site also makes mention of intel using LSI products in their RAID controllers Relevant section of dmidecode:

Code:

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Intel

[code]....

View 5 Replies View Related

OpenSUSE Hardware :: Unable To Open A Device (hard Disc)

Dec 19, 2010

I have installed it (11.3) with KDE desktop.I have a problem with openening a device (harddisc) directly from sysinfo:/It is a ext4 partition, but also with my others (ntfs), this error occurs...

View 9 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

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 View Related

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

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

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

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

Hardware :: "Unable To Open The Initial Device Quitting"

Aug 12, 2010

if I want to print a regular document from the main tray, no problem. If I want to print an 8x11 photo from the main tray. slight problem (might be ink related, still researching that side). But if I want to print a 4x6 or a 5x7 from Linux massive problem Printer: HP Photosmart D5460. Will not print from the Gimp at all, I get the following when I try to print a photo using the Gimp: A page from the main tray with text similar to this:

"****Unable to open the initial device, quitting"

Actually for the last several years under OpenSuSE I have never been able to print a photo from the Gimp. It always prints some text error then quits OR will print the error at the top of every sheet in the tray until the printer either is manually unplugged / turned off OR it runs out of paper. The printer I have is listed as working perfectly according to Open Printing dot org. But none of my applications seem to be able to get the printer tray to operate for the smaller photos. Currently I have to copy the images to a card in the printer then print from the card. Unacceptable if you ask me.[URL]... what photo capable printer out there actually works 100% with OpenSuSE? And I mean I can access all the trays from all the applications I could possibly use, as well as monitor ink levels, perform maintenance and so forth.

View 1 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

Ubuntu :: Mdadm: Cannot Open Device /dev/sdb1: Device Or Resource Busy

Jun 11, 2011

I rebooted my server and out of nowhere the RAID5 array won't assemble. I've tried everything I could think of to reassemble the thing. I fear that the array is ruined, but I can't imagine how. Here are various bits of information: The simplest failure (with and without partition numbers, which have not been needed in the past):

Code:

richard@nas:~$ sudo mdadm --assemble --verbose /dev/md0 /dev/sd[bcd]
mdadm: looking for devices for /dev/md0
mdadm: cannot open device /dev/sdb: Device or resource busy

[code]...

View 5 Replies View Related

General :: Ubuntu 6.06: Mounting /root/sda1 /root Failed: No Such Device

Jan 22, 2010

An old machine in our office, running Ubuntu 6.06 all of a sudden will not boot up. I get the following info during boot:

Uncompressing Linux... Ok Booting the kernel
mount: Mounting /root/sda1 /root failed: No such device
mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory

[code]....

I haven't changed anything on the system as far as I'm aware, and I ran some HD diagnostics and everything seems fine. however when I try to mount the drive with the following command:

sudo mount -t ext3 -o rw /dev/hda1 /mnt

I get the following error:

mount: wrong fs type, bad option, bad
superblock on /dev/sda1, missing code
page or helper program, or other error
In some cases useful info is found in
syslog - try dmesg | tail or so

I ran fdisk -l and it says the partition type is Linux. The output after running dmesg | tail :

[12207.483801] init_special_inode: bogus i_mode (101)
[12207.483809] EXT2-fs: corrupt root inode, run e2fsck
[12260.427078] init_special_inode: bogus i_mode (101)

[code]...

Update: After running e2fsck -p /dev/sda1, I get the following info:

/dev/sda1: clean, 142449 / 9584640 files, 5402711 / 19161520 blocks

View 1 Replies View Related

Debian :: Root Access And Desktop Disabled \ Couldn't Open The Root Terminal?

Feb 19, 2011

I was using the latest stable release of Debian, dual-booted alongside Windows Vista, with the GNOME desktop, installed via netinst, trying to build and install a library that I knew and trusted, when suddenly I couldn't open the Root Terminal. I clicked the link (in Applications->Accessories (I think, whatever the top one is)->Root Terminal), and in the taskbar I saw an item that said "Starting Root Terminal". A few seconds later, that went away, but the terminal still wasn't open. I tried the regular user terminal, to see the same thing happen. Unsure of what was happening, I tried restarting my computer, since that's always the first step you should take in computer problems.

When I restarted, GNOME wouldn't start. The screen would flash a bit for a few seconds, then a dialog box would appear over a background of static that said "The greeter application is crashing. Attempting another one...".t would then go back to the DOS-style kernel, wait a second, and then the same thing would happen. After several of that, I would get a blue screen which said something to the effect of "It has been detected that the desktop environment has crashed six times in the past 30 seconds.

Waiting two minutes before trying again." When it did that, I tried logging in as root to assess the problem. I gave it the correct password, but it said that it was an incorrect login. After several tries (to ensure I didn't mistype the password), I logged in as myself. Same problem. I tried the su command, with the correct password, and it said it couldn't authorise it.

After a lengthy conversation with a friend of mine who was very good with computers, he basically summarised that he had no clue, but that his best guess would be a virus. Upon running the Linux installer, I found the Repair option. Not being particularly familiar with Linux, I used it simply to backup my important files onto a flash drive. I then tried running the Install option, in an attempt to simply write over my existing Linux and make it new again. The installer, however, consistently froze up when trying to start the partitioner, on the "Checking disks..." stage. I figured it was a problem with my partition. In my naivete, I simply used the Windows tools to clear that partition... It destroyed GRUB too, so I couldn't run any OS. I figured my computer was pretty well screwed, and at that point just decided to bring it into the shop and have them completely wipe it.

my computer was backed up onto an external hard driven I brought it back, I reinstalled Windows. Upon restart, it said that it was still looking for GRUB, which made no sense to me. After messing around with it a bit, I decided to just reinstall Linux too. To my lack of surprise, that fixed the problem. Both OS' now ran just fine. The first thing I did on Debian was to install the Clam Anti-Virus, which I understood to be one of the best Linux anti-viruses. However, within about 10 hours, got the same problem as originally. I wasn't doing any of the same things, and between the lack of consistency in activities and the fact that I had an anti-virus running,figured it wasn't a virus. Not knowing what to do, I just left it and have been using Windows since.

View 8 Replies View Related

OpenSUSE :: Root Trying To Open Flashplayer In KDE Getting Cannot Open Display

Feb 18, 2011

We have a digital signage appliance built on SUSE 11.3 with a LAMP server that uses the flashplayer application to play a .swf file from localhost. It is a AOpen GP7A mini pc that has the nVidia drivers loaded. We have lots of customers that have been running the exact same system for over 6 months (we image the drive for each sale).

For some reason, my last customer is seeing the following problem shown below, and this linux configuration is way over my head. Everything else is working (local LAMP server is working, communicating with our production servers to get information works, etc). I have verified that it is screen 0 that is running (at least it shows with Ctrl-Alt-F7). I thought that it may have occurred because of updating the software with zypper up. I had the customer rebuild from the image being careful not to upgrade the software. The result was the same. The pc is a newer version compared to my bench pc, but there are multiple other customers running that same version just fine. So I am not sure if it is

The command is issued by a php script that is run in a root cron job. As I said, it works great on all other customer pc's including my bench system. I also tried to execute the command on a ssh terminal as the root user with the same result. I also upgraded my bench pc and it still worked properly.

The command being executed is sudo env DISPLAY=:0 XAUTHORITY=/home/svision/.Xauthority flashplayer http://localhost/flash/sign.swf &

the result (when run in terminal) is: No protocol specified (flashplayer:15077): Gtk-WARNING **: cannot open display: :0

View 2 Replies View Related

Red Hat / Fedora :: Root Line Passwd File Now Unable To Login As Root?

Jan 26, 2010

I edited the passwd file to modify the default shell for root from bash to tcshnow when I try to login to root it gives me the following error:"su: /bin/tcsh : No such file or directory"

View 3 Replies View Related

Fedora :: Cannot Open PDF's In Firefox - Unable To Open Document

Aug 9, 2010

As of this morning I cannot open pdf's by clicking on them in firefox. I can download them and open them from the download window or even from the folder they are saved to, but not from the browser. Evince opens and says: Unable to open document Error opening file: No such file or directory.

View 1 Replies View Related

Ubuntu :: Mount Loopback Device As Root

Jun 23, 2011

I am trying to expand my Ubuntu partition into my Windows 7 C: drive, but the win7 partioner will not let me shrink it because of immovable files. Is there anyway for me to but an loopback device in the windows partion, and have Ubuntu boot with that as the root device?

View 1 Replies View Related







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