Fedora :: Trying To Build A Root Filesystem?
Aug 13, 2009I am trying to build a root file system for using it with the user mode linux on a fc 11 system.
View 5 RepliesI am trying to build a root file system for using it with the user mode linux on a fc 11 system.
View 5 RepliesWhen 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.
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.
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 Replies View RelatedRunning 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.
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 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.
I messed up the first installation of Fedora on my server. My setup is as follows: Fedora and Gnome - NFS system, No dual boot (Windows or anything) Fedora ISO DVD downloaded No kickstart or other tools. how to set this up, from the time I insert the disk and have it boot up (configged already to boot from it). I know how to wipe it clean at intall time. Is that the root directory? And, is /boot the actual boot directory? I'm just having a hard time uderstanding that. As I said, I just want a quick itemized list, step 1, step 2, etc, from partitioning, creating file system, mounting, etc. in the right order.
View 4 Replies View RelatedMy 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 am very new to linux, and I have a question regarding the filesystem check (fsck). The power recently went out and when I tried to restart linux the following error appears:
*/dev/sda1 contains file system w/errors, check forced it then goes on to say..
*An error occured during the file system check. Dropping you to a shell; the system will reboot when you leave the shell. Give root password for maintenance (or type Control-D to continue) I wasn't sure what to do, but checked some other online forums and they suggested running fsck manually - so I typed in the root password - and used the command, "fsck -A -V ; echo == $? ==" it then gave the following message
*WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage
*Would you like to continue (y/n)
Again, I wasn't sure what to do so i just checked no. I then manually turned off the computer and was prompted at the beginning to press Alt-3. I was brought to another screen and it informed me one of the drives was degraded and suggested rebuilding the array. I tried doing this, but it still brings me back to the original error of, "/dev/sda1 contains file system w/errors, check forced," and the process continues.
Also, when I tried to rebuild the array, I didn't backup any of the data on our home directory before doing this (which was probably a big mistake). After being prompted to type the root password, I was able to give the ls command and look at all the directories...the home directory where our data was stored was empty and I am afraid I may have lost some information. Is there a possibility that data was lost when I was trying to rebuild using the old drives?
mc (Midnight Commander) in Kubuntu 9.10 (Karmic Koala) has a problem accessing .zip and other archives as a virtual file system. It has to do with a changed format of the output from unzip. Discussions offer a workaround, but that requires system (i.e. root) file access; my work box is locked down.
I have Ubuntu (without the K) 9.10 at home, and I downloaded the source package and made a code change that's a horrible hack (I would not dream of publishing) that would allow me to run my own correctly working copy of mc in a subdirectory of my $HOME. Alas, my "at home" box is configured differently, both in terms of processor(s) and KDE vs. Gnome; a transferred-over mc executable fails immediately with bus error.
[Code]...
I have a custom Ubuntu distro that run both from a CD and PXE boot. The problem I have is that I need to boot in an environment that has to be routed through a router that can't forward NFS (the protocol doesn't use a standard port) I found that the Ubuntu based Clonezilla Live CD has a option like "fetch tftp://server/folder/filesystem.squashfs" I can borrow the kernel and initrd and it works, but how do I add this feature myself? Is there a package I need to install or a initrd option I need to add?
View 1 Replies View RelatedLately however my root filesystem is getting filled up every night-- I come in in the morning and have notices that I have 0 bytes remaining. There's tons of room on the disk, but the root is full. Here's what it looks like with a df -h:
[Code]....
ive been recently experiencing some problems with my ubuntu studio 9.10 setup, with the filesystem failing to mount. after deciding to try a new hard drive and cable, as well as clean install ubuntu, fedora and now mint, im still finding no filesystem.im using a live cd created for mint (like it ). having clicked install to hard drive, all is well until the partition manager, where all the boxes are greyed out. clicking forward produces a box saying "no root filesystem defined". i see there are a few on here from a few years back and having read through them, cannot find a fix for myself.
View 9 Replies View RelatedUsing Ubuntu 10.10, 64-bit, installing after LiveCD testing.sda3 can't really be erased due to its contents, something I can't exactly get back or transfer.
View 2 Replies View RelatedI'm trying to use buildroot to cross compile some libraries for me. To do so I've set up build root to point to my working tool chain in the menuconfig.All seems fine however when I try to make (buildroot) I get the following error
rm -rf /root/buildroot-2010.05/output/build/buildroot-config
mkdir -p /root/buildroot-2010.05/output/build
cp -dpRf package/config/buildroot-config /root/buildroot-2010.05/output/build/buildroot-config
Checking external toolchain settings
Incorrect selection of the C library
make: *** [/root/buildroot-2010.05/output/stamps/ext-toolchain-installed] Error 255
I know it's pointing to the correct files and gcc as any wrong paths are reported in make menuconfig.
I have switched recently from Ubuntu to Debian and overall I am enjoying it. However I was just wondering, does Debian, like Ubuntu check the filesystem at boot periodically or if damaged, because it is doing neither in my case? How do I get it to do this
View 6 Replies View RelatedI am running 11.2, kde4. The day before yesterday, the system updated and I think there was kernal update within that. I had no problems immediately afterward. Then I did a total shutdown for the night, and turned it back on yesterday only to find this:
Mount: wrong fs, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error
In some cases useful info is found in syslog--try dmesg | tail or so
Could not mount root filesystem--exiting to /bin/sh
sh: cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell
$
Besides the last updates from the other day, I did nothing out of the ordinary, no downloads or any system/configuration tweeks. Will I have to reinstall opensuse? or is there a way to reclaim my previous setup--or at least reclaim my files and documents? I'm running off of the 11.2 livecd.
I have a dual booting newly installed 64 bit Ubuntu 9.10 on my machine. It was all fine until today. Now when I boot into Ubuntu, I see the error Failed to mount root filesystem. I cant remember any significant changes during the last session. One thing I remember is I upgraded the system using the update manager which asked me to choose an option for grub boot loader. I opted for its upgradation. After the upgrade, I was able to work with Ubuntu for a few more sessions. Windows XP works very fine.I checked other threads which suggested running fsck, but it did not help. fsck does not report any errors.
View 1 Replies View RelatedAnybody know if its possible to add the root filesystem to the favorites in files and folder in ubuntu 10.04 nbr?
View 1 Replies View RelatedI am using GRUB bootloader. I can boot into windows fine. But booting into linux gives me the error "kernel panic: unable to mount root fs on unknown block(0,0)I got LILO to load linux fine but GRUB always gives me this error regardless of the linux OS for this particular computer.
View 11 Replies View RelatedI boot up a Linux appliance entirely in RAM, ie. the image has a Linux kernel and an attached ext2 root filesystem.
Now that it's working, I would like to copy the root filesystem from RAM to a NAND flash memory.
Can I just mount the NAND, run "cp -a /* /mnt/nand", reboot with the kernel command line "root=/dev/mtdblock2 rw", and expect Linux to be happy... or is it more involved than this?
Suppose I have a good backup of the / root filesystem. How do I recover the / root area? Suppose I have modified the root filesystem, perhaps I do an update some of the packages and regret it, and I want to get back to the system at the time of the backup. How do most linux people recover the root area of a system from a backup?
1) I wondered if I might put a System Rescue CD in and boot off it?
2) And then NFS mount the directory containing the backup? -In my case, I have made a good backup using rsync, to a directory elsewhere on the network.
3) And then, still booted off the System Rescue CD, mount the partition that contains the / root area in question?
4) Would I then clear or empty or delete the contents from the / root partition?
5) And then copy across all the files from the backup into the / root partition?
I ask these questions because of the (very nice) way linux OS is built entirely from packages... Am I being too complicated? (By comparison, I can see it is easy to recover user data.)If, instead, I simply recovered the backup straight onto the updated root filesystem, I wonder what it would look like if I then tried to verify it with "rpm -Va", for example? Surely, all the packages would fail the verification, because it would think it has a later version of each package from the update, but the actual files would have been overwritten by the earlier version from the backup?
When i installed ubuntu. I made a seperate partition so that i could copy an ISO image onto it of an up-to-date version of ubuntu. I wanted to then boot the ISO up so i could install the new version that way. I've already tried doing it through the update manager but it'll download, almost be done with installing and it freezes on me. so i figured this would be easier. However i do not know how to gain access to the other partition to copy the ISO image. Please help.
View 1 Replies View RelatedI'm running CentOS 4.3 on a VM which is an application server for Quinstreet. trouble is when i keep coming in during the mornings it seems to keep making this root filesystem read only. There is no pattern for this and neither is it clear in the messages log why this keeps happening.
View 5 Replies View RelatedI've setup a filesystem on a RAID 0+1 and am looking at moving root filesystem from a single disk to the new one. I could not install CentOS on mirrored filesystem as the RAID card did not have a pre-built driver for CentOS 5.3, so I had to compile the driver after installing the system.What I'm going to do now is:
1. Mount the new mirrored filesystem under /root1
2. use find | cpio to copy everything from the existing / to /root1
3. use grub to create a boot record on /root1
4. edit /root1/etc/fstab to point / to the new disk
5. reboot the system and keep my fingers crossed
Is this the way to go? Am I missing anything?
today I upgraded (yum update) one of my Dell Poweredge Server from 5.2 to 5.3. After rebooting the system first seems to start normal but then the following Error Messages appear:
Apr 5 14:28:26 srv_1 kernel: I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x668000008 ("xfs_trans_read_buf") error 5 buf count 4096
Apr 5 14:28:26 srv_1 kernel: attempt to access beyond end of device
Apr 5 14:28:26 srv_1 kernel: dm-0: rw=0, want=27514634256, limitfs]
[code]....
Booting with a rescue disk and doing a xfs_repair solves the file system Problems but moved a lot of files ( at least /usr/bin and /usr/lib completly) to "lost+found"... I tried the update with a spare 5.2 Server (different Hardware), and ended up with exactly the
same effect and error message. Both systems are running XFS as root File system on an LVM Disk.