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
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
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.
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.
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:
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
I was looking at the root filesystem folder for mounting a device when I noticed extra folders. I'm using an encrypted filesystem so I'm not sure if it's that, a break in or the default Red Hat layout. I searched these forums and Google to no avail on extra folders. The root system contains the following:
bin {fda00e13-8c62-4f63-9d19-d168115b11ca} media opt selinux usr boot home misc proc srv var dev lib mnt root sys etc lost+found net sbin tmp
Trying to complete a RAID 1 mirror on a running system and have run into a wall at the last part. I can't add the active physical disk to the mirror. This is on a Centos 5.6 x86_64 system. Anybody know where to go from here? I've tried adding the nodmraid line to the kernel boot line with no luck. Tried removing the logical volumes from LVM, but it won't let me. Not a Linux newbie, but haven't set up a RAID in a long time.
[root@blackbox-0-2-e3-23-72-c5 ~]# mdadm /dev/md1 --add /dev/sda2 mdadm: Cannot open /dev/sda2: Device or resource busy
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.
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
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?
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:
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.
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).
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
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 :
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.
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:
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
I have installed live cd on usb pendrive. Everything works great. How can I find out which device driver it is using? Where are the device driver files stored? How do you specify the device driver when mounting a device?
I was trying to edit a file requiring root permissions, so I used sudo. I typed the root password and it failed. This happened three times, and the process was ended. I then logged in as root (su) and was able to navigate to the file and make changes as root. Am I missing something? How would I edit the sudoers file such that this password would work? Or is there another way to log in to the sudo group to make these changes? How do I set sudo passwords?
Ok For some reason I open my ports in security and firewall. I open ssh and other ports and port 7001 for example but when I go to check to see if they are open or try to connect to them. It shows that they are still closed. I am using - [URL] Also yes my ports are open on my router. I know my router works fine with opening ports because I have shoutcast setup on another computer with xp that is currently running. I am willing to pay for who can ever get this fixed for me...
I have had a Supermicro X7DCL-3 motherboard based machine, running CentOS 5.2 x86_64, recently upgraded to 5.3.Strangely enough, although I must have installed the 5.2 using DVD disk, the running system does not show the DVD drive. The machine was not used very much so I noticed that only today, after the update. There is no trace of it in 'dmesg', thera are no /dev/cd* and/or /dev/dvd* devices. The IDE controller is IT8213 (as shown by 'lspci'). In 5.2 kernel (2.6.18-92.el5-x86_64) lspci says "unknown device". I have checked the /usr/src/kernels/*/.config files and both kernels (5.2 and 2.6.18-128.el5-x86_64 of 5.3) seam to have the support for that controller added into the kernel:CONFIG_BLK_DEV_IT821X=yAny idea why it is not working? The Supermicro has apparently noticed this also as their OS compatibility chart lists the IDE interface for that motherboard as supported up to RHEL 5.1 but not for 5.2.
I'm experimenting with a K8055 board, connected through USB to our Asterisk server,running on CentOS. If I connect the device I can see it being connected by watching /var/log/messages. Also the device is mentionned in /proc/bus/usb/devices. But when I do lsusb the device isn't showing up and it should be showing up! If it is not listed with lsusb, I can't connect to it through the k8055 executable...
I want to be able to change the root device, say from sda to sdb, so that I am able to remove sda. I don't believe this is possible with chroot, as I am changing the root folder to a mount point that exists on sda (sdb is not on fstab), so removing it would lock up the system.
I have been using SLES 10 SP1 so far with about 6TB Raid system without problems.I have upgraded the OS to CentOS 5.3 i386 and I have noticed the kernel can not recognize raid system larger than 2TB.Is there any parameters that I have to set ? or the i386 distribution simply does not support larger raid, so I have to use x86_64 version, instead?
