i made a live usb stick with a original live iso image of f10 following carefully instructions of fedora support comunity once i finished i had tested it and i had the same problem (warning can not find root filesystem create symlink /dev/root and then exit this shell to continue the boot sequence, bash: no job control in this shell) of the following person:
View 2 RepliesI have a LiveCD (DVD with many linux versions on it) and no other software on my computer at the moment. The computer specs are as follow:
When I use the live cd I get the following message: Cannot find root file system
I have tried the suggestion along the lines of:
Then it either goes back to Bash or I get "Kernel panic - not syncing: Attempted to kill init"
Then my install just freezes there and I need to restart my computer.
I'm trying to install netbook remix on my out-of-the-box 1005PE with windows 7. I used LinuxLive USB Creator 2.4 to put the netbook remix file onto my usb device. I get to the part where I choose whether I want persistent mode, live mode, installation or a few other options. I chose installation. Here is what I see on my screen starting a little before where I think the error is:
Begin: Running /scripts/casper-premount ...
Done.
Done.
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built-in shell (ash) Enter 'help' for a list of built-in commands. Unable to find a medium containing a live file system I've tried the whole process several times. I've tried redownloading the netbook remix file, reusing LinuxLive and trying Unetbootin-windows-433.
I am trying to boot Debian Live, using Grub, from a folder on my hard drive which is basically the contents of the iso.
Here is my menu.lst:
However, on boot, after a while, it says boot failed. The error message it gives is: "Unable to find device with live filesystem" or something similar.
I have successful tar an existing CentOS 5.2 partition from Fefora10. The idea is to move a working CentOS 5.2 reside in an internal hard drive to a portable hard drive. I know how to edit a stencil in menu.lst to boot the clone CentOS5.2. During boot, I encountered
Red Hat nash version 5.1.19.6
mount: could not find filesystem /dev/root
setuproot: moving /dev failed No such file or directory
setuproot: mounting /proc: No such file or directory
setuproot: mounting /sys: No such file or directory
[Code]...
xubuntu iso was downloaded with wget on Kubuntu, I did a md5sum checksum in terminal which passed, also K3b's check passed. K3b burned iso with no errors, I set speed at 4x. I made two coasters before getting this far but it still won't get past the BusyBox built-in shell prompt after choosing my language and staring at the xfce mouse for a minute:
Code:
BusyBox v15.3 (Ubuntu 1:1.15.3-1ubuntu5) built-in shell (ash)
(initramfs) Can not mount /dev/loop0 (/cdrom/casper/filesystem.squashfs) on //filesystem.squashfs
is what I get when trying to boot live cd on both my Linux PC and Windows XP box.
When I try to boot to OpenSUSE I get the following error during boot-up: unknown filesystem type 'reiserfs' could not mount root filesystem - exiting to /bin/sh$
This only started happening quite recently - before this I could boot to Linux quite happily.
I am attempting to upgrade Fedora 12 to 13. I get an error screen that said root could not be found. Four options are given. Not sure exactly their wording, but two appear to allow you to cancel the other two warn that if you reinitialize you will wipe out all data.
I have a Vista partition and a Fedora partition. I've added the vista ntfs partition to fstab with no help. All of the partition use the long UUID form. I added the root location (root (hd0,5) to the upgrade menu item in grub.conf and that didn't work either.
I'm reluctant to proceed for fear of initializing the entire drive. I could live with installing Fedora 13 over the existing partitions.
I am trying to build a root file system for using it with the user mode linux on a fc 11 system.
View 5 Replies View RelatedOn Launchpad there is the following thread on ureadahead:
[URL]
Is it sensible to remove "ureadahead" until this is fixed or is there no harm done? As a normal user ... (yes still I have /var in a separate partition, because I want to be on the safe side with my databases located in /var when reinstalling or upgrading the system ... - by the way: does this make sense or is it better to just have /home separate and use a backup of /var folders?) ... as a normal user I feel a bit lost with bugs like this. It would be nice to get some information somewhere. Something like:
"Don't worry, just wait for an update with a bugfix!"
or
"To avoid further problems just remove 'ureadahead' until it's fixed!"
2 days ago I had installed Fedora 9 on an old machine. The installation was from a Flash USB, and was OK and the kernel on thar installation was 2.6.25-14.fc9.i686.
After the installation I updated the system, and all looks to be ok, and the system was set with the kernel 2.6.27.25-78.2.56.fc9.i686.
But when I start the system with the latest kernel itś get blockd on "remounting root filesystem in read-write mode" step, but not with the original kernel witch start correctly.
I'm new to fedora 13 and I have been through a few installs already with a 12TB raid. Fedora is installed on a separate 250GB drive. I've mounted the 12TB drive as a single share and I'm capturing large video files (12-90GB each) to the raid in a Samba Share across the network. The system runs great for about three days and then I start getting warning messages that "the volume filesystem root has only 1.9GB of disk space remaining" then another later 205MB etc until it eventually fills to 100% and then locks the machine. If I reboot I get a Gnome error and can't login. The only solution has been to reinstall fedora again from scratch.
Each time I allocate more space for root. My current partition is 65G in size. The raid shows only 5.1TB of space used and it shows 7.2TB of free space. The raid share shows as being mounted in /media. Root shows that it will be full at 5.2TB, and I'm almost there, so I'm probably looking at another install in just a short while when it freezes again. I've read reinstall and make a larger root partition, but I'm not sure how big that must be to avoid this problem in the future. Also, is there a limitation on the size that root can be? my question stems from the fact that I have over 7TB of free space but somehow the root is reporting as 100% full at only to 5.1TB.
Here is my problem. Grub2 outputs error: unknown filesystem. Then when i use "ls" command it outputs this:
(hd0), (hd0,4), (hd0,2), (hd1) and when i "ls (hd0,4)/ or any of them it says: error: no such disk
So, heres my story. I dual boot vista and ubuntu from my main 320GB hdd. Today i tried to fresh install 9.10 on a different external hdd. The 500GB hard drive already had two partitions, a 30GB Fat32 and the rest NTFS. both of these partitions had about 17GB used on them. I installed off a cd and i shrunk the NTFS to allow for more partitions. I made a 4gb swap as logical at the end then a primary ext4 / partition in front of it. The drives are Fat32 sdg0, ntfs sdg1, then an sdg3 (which im confused about and says is extension), and sdg4 (with linux) and sdg5 (swap). When finished with the partitions it asked me to select where to mount the ntfs and i said /windows. When i tried to boot up it did not recognize my external apparently because it was plugged in via firewire. I switched to usb and it booted but then i got the error message in grub. Also, when i switched from firewire to usb the drive changed from sdb to sdg. How do i fix this problem? Will reinstalling ubuntu fix this? Is there an easier way? I tried reinstalling grub but it did not work.
I've been playing around with an old laptop and a hand full of Linux distros. I found that each Linux has a kernel "vmlinuz" and a initrd "initrd.gz" no matter how you boot the distro it uses these to files. I have CrunchBang Installed on my laptop I put a copy of the ubuntu live disk in the location
/home/user-pc/ubuntu/
I added a new boot option for grub It looks like this
Title Ubuntu
kernel /home/user-pc/ubuntu/casper/vmlinuz
initrd /home/user-pc/ubuntu/casper/initrd.gz
This boots like a normal cd only problem is while its booting it tells me it cant find the file System. This happened for every single Linux distro I tried to boot. Is there something I am missing here is there a way to tell the boot peramiter where the file system is I think what it means by file system is the "filesystem.squashfs" file.
I have 2 questions
1. Is there anyway to tell the grub loader that this is the file system. To make the live CD boot properly.
2. How do CD's work is it not the same?
Have been running 11.1 on a generic notebook (eRacks) just fine until a few days ago when CUPS couldn't be reached. Rather than futz more with 11.1, I decided to install 11.2 (which has been on my desktop). Using the same CD, which continues to check ok, the install has failed many times at about the same point: 87% through "copying root filesystem" in yast2.
Specs: Intel P4 2.4 GHz, 1.5 GB RAM, ATI radeon PV250Lf
The HD was partitioned into /, swap, /home, and an extended partition of /opt, /var, /usr. Only / was ext4 and the rest were ext3. Tried various options:
* no apic
* no acpi
* "noapic acpi=off" entered manually
* Vesa instead of 1024x768
Each time had to edit partition table to mount the extended partitions. Always formatted /. At first didn't format the extended patitions, later formated all but /home. Then set yast2 to format / as ext3, to match the other partitions. In the sysinfo page the / partition is now shown as /mnt containing 723.6 MB out of 7 GB, still formatted as ext4. On rescan by yast2 partition manager, / shows as ext3. The install halts every time with an error while "copying root filesystem." Tried booting from the CD direct to install and to the Live OS followed by install--same result. So, hours later, went back to 11.1--which installed in minutes.
Running F12 on my compaq evo N410c. Did a system restart 4rm gnome logged in as root & now grub cant mount my root filesystem, it boots vista though. How do i rectify dis.
View 2 Replies View RelatedI rsync-ed root fs as a whole to another hard drive. In grub.conf I changed kernel option
root=/dev/sda1 ---> root=/dev/sdb
After kernel mounted root filesystem on the new hdd and all services started I successfully got prompt to enter login and password. However after login I immediatelly logout automatically. Here is /var/log/secure output:
Quote:
May 20 23:53:18 localhost login: pam_unix(login:session): session opened for user alex by alex(uid=0)
May 20 23:53:18 localhost login: LOGIN ON tty2 BY alex
May 20 23:53:18 localhost login: pam_unix(login:session): session closed for user alex
What is printed before this:
Quote:
May 20 23:50:47 localhost pam: gdm-password[1469]: gkr-pam: couldn't run gnome-keyring-daemon: Access denied
May 20 23:50:47 localhost pam: gdm-password[1455]: gkr-pam: gnome-keyring-daemon didn't start properly properly
Neither of these quotes appears if the initial file system (not rsync-ed) is used as root fs. I guess that pam might use information of hard drive, for example, its serial number, and login is tied to a disk. Please, give me a suggestion how to get rid of automatic logout.
i want to know that if i install linux on to my pc with SWAP/ boot as partition and after that i want to convert them to LVM2 type configuration .how can i do that.i want to create a system having logical volumes from that system without reinstalling these partitions should convert into two LV's
LV 0 for root
LV 1 for swap
both in one volume group.
I'm having trouble installing it on a "new" computer that I found at Goodwill for $60 with no operating system on it. When I go to edit the partitions, it won't let me do anything due to an apparent lack of a root filesystem. (I know this issue has been brought up and resolved in the past, but the usual solution (going into the validation.py file) isn't working for me, as there is no line in this one that says "if not root".)
View 9 Replies View RelatedI decided to try to do the 3 distro upgrade stretch from 8.04 to 10.04 this weekend and now I am hung on 9.04 to 9.10.. The upgrade went swimmingly, but I hit a wall upon boot. When I try to load kernel 2.6.31-22 I am greeted with the following error:
Code:
[ 20.879845] ACPI: I/O resource vt596_smbus [0x400-0$407] conflicts with ACPI region SMOV [0x400-0x406]
Mount of root filesystem failed.
A maintenance shell will now be started ... After doing some digging I found this thread which appears to be similar in the inability to mount the filesystem. However, it does not mention the ACPI error. I tried everything in that thread; verifying device ID's, editing fstab options; running a filesystem check, and flipping the UTC option in the rcS file but nothing worked. The OP of that thread eventually did a fresh install of Karmic; but I would rather not have to go that far.
I am facing a strange problem in my server, One of my filesystem shows as 3.1G when I execute df -h command and the utilization shows as 83%, but when I cd to the directory /usr/local I could not find any huge files in that filesystem and I have searched for hidden files as well,
groupserver:~ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda9 3.1G 2.5G 532M 83% /usr/local
groupserver:/usr/local # du -sh *
0 bin
93M abinav
[Code]...
My Fedora 12 System was failed when booting.The message like that : mount: wrong fs type, bad option, bad superblock on /dev/mapper/my_vol missing codepage or helper program, or other error. In some case, useful info is found in syslog - try dmesg | tail or so Can't mount at root filesystem. [drm: drm_mode_rmfb ] *ERROR* tried to remove a fb that we didn't own. Boot has failed, sleep forever. I guess something wrong with my hard disk, so the bootloader can't recognize the filesystem type.
View 2 Replies View RelatedI've upgraded my squeeze box to linux kernel 2.6.32-5. But it shows mounting "here is the uuid of / " on /root failed: Device or resource busy while booting.Here is the menuentry of linux kernel 2.6.32-5.
[code]....
I've downloaded Fedora 12 and decided to try and install it on my old laptop which is currently running Ubuntu 9.10 with no problems.
When I boot from the live cd, it starts to load with the 3 bars on the bottom, one on top of the other, one is white, one is dark blue, the other is in between those colours in the spectrum somewhere....
Anyway, the load bars complete and "Fedora 12" turns white, then the following output populates:
mount: unknown filesystem type 'DM_Snapshot_Cow' (<----- repeated a bunch of times) can't mount root filesystem Boot has failed, sleeping forever.
the message on the title only happens with Ubuntu. In Fedora, it just stops booting from LiveCD with "WARNING: Cannot find root file system!". The rest of the symptoms are the same.I'm trying to install Fedora LiveCD on an IBM i Series notebook (model 1161-21X). It's a Celeron powered unit with RAM expanded to 512MB. It has a 10GB HDD, and an internal CD-ROM drive. Although it has two USB ports (1.1), it cannot boot from a USB drive, so no pendrive nor external CD unit solution possible.When I boot from LiveCD, it stops booting with the message above. Looking atsg, there's no CD-ROM driver loaded. Also, there's a char device for sg0, but no block device for it, so no way to mount it. It seems that the driver module has been removed from the kernel. I'm currently running Fedora Core 5 in it. This very same problem happens with any Ubuntu newer that 6 or any Fedora post 7.
View 2 Replies View RelatedI've decided to give ubuntu another test drive now that I got a bigger and better desktop. I downloaded the latest version of ubuntu, loaded it into my usb stick and booted from it. I then clicked on the install icon on the desktop to start the installation. Everything was going ok, until I came to the partitioning part. I had already (on windows 7) created a separate partition for ubuntu which is 56GB. So I chose "manual partitioning" and selected the ubuntu partition as /home and began the installation.
Everything seemed to have went well, the window suddenly closed and then nothing happened. I waited for 15mins and still nothing happened. I decided to restart and see what happened, but I discovered that I couldn't boot into windows anymore. It said something about intel boot manager cannot find filesystem. So I decided to boot back from the usb and see if I can reinstall ubuntu, I came to the partitioning part and all the drives were gone, I couldn't see anything, it was blank.
My linux distro is CentOS 5.3. Today I edited /etc/sysconfig/readonly-root and set "READONLY" to yes, now my /etc/sysconfig/readonly-root file is like this:
# Set to 'yes' to mount the system filesystems read-only.
READONLY=yes
# Set to 'yes' to mount various temporary state as either tmpfs
[code]...
I have a couple of hard drives on my computer that I need to access with the live cd before I install Ubuntu. When I try to access them I get a message that says I don't have permission. How do I use root with the live cd, or how can I get access to these drives?
View 4 Replies View RelatedHow can root be used in Fedora 14 live?
View 7 Replies View RelatedI am trying to install Fedora on my computer and it boots fine but then comes up with an error it says"Warning : cannot find root file system"Create symlink /dev/root and then exit shell to continue the boot sequencebash:no job control in this shell bash-3.2# I am a completly new to all this so
View 3 Replies View Related