i've enabled quotas for a user on my fedora 10 distro but whenever i reboot the machine the boot.log contains the following message :"Enabling local filesystem after every startup i have to login as root and issue the quotaon -auv command to reenable quotas.what causes this failure on startup ? is there a workaround to solve this problem ?there is plenty of free space on the root partition that quotas are enabled.
View 2 RepliesBack during the early days of live usb drives (F9) before persistent overlays were not ready for prime time, I created an approach to do persistence by injecting a special rc.local file into my custom live usb spin. This script mounts a file containing an encrypted ext3 filesystem using losetup which prompts for a password.
This scheme worked well for F9 and F10 but is now broken for F11 because the keyboard is not enabled at the time rc.local is executed. Obviously, all the work done to F11 for speeding up the boot time and moving the boot to the first console has broken my approach.
G'day. My distro is Fedora 13. I received the above subject error message at boot. My /etc/fstab is attached as follow:
#
# /etc/fstab
# Created by anaconda on Fri Mar 5 12:44:10 2010
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
[code].....
I had occasion to add a few lines to rc.sysinit. Turns out the lines syntax was wrong. Instead of the booting ignoring those lines and proceeding on, then giving me an error warning or perhaps dumping into the interactive mode it just hung up! After several tries at moving on I discovered ESC dropped me into some sort of unannounced shell I got the installation disk out and with the repair system option using VI I got the lines deleted and all went back to normal. Now my suggestion is that if something does not make sense in terms of syntax while booting then cover it by doing the above and ignoring it with a warning later.
View 14 Replies View RelatedI was having problems performing an update yesterday that failed on dovecot dependancies and after a few tries I removed dovecote (it wasn't being used) from the installation and tried again. Everything seemed to be going OK then the update (about 160MB) hung and the screen went black a few times and I think then shutdown automatically. The PC then fails to reboot and displayes the message "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" I have tried to get the PC to boot with the super grub disc but without success (probably my in experience) I have also tried a suggestion from one of the forums to start the PC with a live CD and typed su -c 'grub-install /dev/sda at the terminal again without sucess. I have looked at the files with the live CD there are grub, menu and kernel files there (some are in lost + found, b ut don't know wheer these should be so have not changed anything.
Is there an easy way for the in-experienced to repair the boot process ?
The PC is a pentium 4 running Fedora 13
There is a 200MB boot partition formated as Ext3
and a 19GB partition formated as a LVM with Ext4
There is a CD drive but no DVD
Everything has worked OK for the past year through two online upgrades.
I have just updated my kernel and immediately struck trouble. The kernel update is marked as security update.
When booting I get a multiple warnings " deprecated config file /etc/modprobe...", then "no root device found" followed by "boot has failed, sleeping forever"!Clearly something is amiss with this update, so figured the best thing might be to remove it and wait on a fix, but attempting to remove the kernel via the package manager would cause a whole lot of other packages to be removed as well.Instead, I edited grub.conf, commenting out all the kernel-2.6.34.7-63 lines, so that the default is now the previous kernel (2.6.34.7-61).
My laptop died while installing F12, without completing installation. Now I can not boot the computer from HD, CD, or USB. I have flashed the BIOS with the most recent ROM. I can access the BIOS setup and exhausted all my options there, which is mainly boot order. At the moment, the boot process goes to a blinking cursor and does not allow for input. The laptop in question is a lenovo Y510 that was previously running F10 with a single partition.
View 2 Replies View RelatedEvery time I boot up FC13 I get a boot message which is showing a failed task. The line is as follows:
Enabling the nvidia driver: /etc/rc.d/init.d/functions: line 530: 1174 Segmentation fault "$@"[FAILED]
Everything appears to be running fine on my system. This message is more nuisance that a functionality message. But I could be wrong.
I upgraded the kernel of my machine with a yum update, and now it will not boot. I am running Fedora 14 on a 64 bit machine. I really really need it to boot. Help!
I did Ctrl+Alt+F2 and managed to log in. I have kernel x86_64 2.6.35.12-90.fc14 installed. How do I log in as usual? I never get to a login screen.
I downloaded Fedora 15 Live and Fedora 14 Live to try to see where Linux is for music and broadcast audio on a laptop. It turns out I have to use 14. 14 and 15 both sort of work as live out of the box, although why they ship with the common Broadcom wifi driver missing and the touchpad tap disabled beats me. I also never found the magic button to close down 15. There must be one, but blow me I couldn't find it. Then I tried to follow the instructions at [URL] which mostly seemed to work. I need to keep Win 7 as this is the 32-bit test machine. I used EasyBCD v2.1 rather than the older version the guide is written for.
Booting into Win7 at first worked, then a boot into Linux stopped at a line that said something about a kernel thread helper Then Win 7 blue screened on boot, although it would boot to Safe Mode. Removed Veriface from the Lenovo laptop and it would boot Win 7. Tried setting Drive in EasyBCD to "Boot" rather than "C:" for Fedora. Now booting Fedora gave a Windows missing file message and croaked. Repairing startup with the Win 7 boot CD cured Win 7. Repeated the loop with the same failures. Re-partitioned and re-installed Fedora and just the same - a screen of text that stops. I can now boot to Windows and need help to sort out the Linux boot. How do I start to investigate the screen of text saying things like "__bad_area_nosemaphore" ?
Dual Boot: Fedora 12 and XP Dell 505I've had trouble with the latest kernel update.I updated a bunch of packages recently (including Xorg and kernel), and noticed a severe flickering after the update on my center monitor (Samsung T260 - the laptop display did not exhibit the flickering behavior). I backed out all the changes and started updating package by package. After I updated the kernel (again) I rebooted and here's where the fun part is -
I no longer get anything, except the cursor. No grub menu, no grub prompt. I rebooted and ran the rescue disk and followed the procedurery and point grub at the right boot partition - see here. However (obviously or I wouldn't be posting) that failed to work. I still get a blinking cursor and dead system on boot up.
So what happened is i had a small encrypted lvm volume that i no longer need because I have bought an external HDD and used truecrypt on in. So after I transfer all the files off of the encrypted partition, I restart and drop into single user mode and remove the unneeded volume. When i attempt to restart, instead of going to the login screen, when the boot progress bar is full, it says "welcome to emergency mode: enter rootssword for maintenance or press control D for normal mode" or something along those lines. I tired control+D, but that just brought me right back to the emerengy mode screen. I put in my root password and tried startx, but then x gave me this error: "can not start D-bus, can you call q-dbus?". After that i tried both "service dbus start" and "dbus-launch", both of which failed. Is there any quick remedy to this situation, or do i have to reinstall
View 4 Replies View RelatedI just upgraded via preupgrade-cli (from FC10), rebooted, the upgrade process completed, then the system rebooted and I just see a blinking white cursor now.I was able to boot up from a live cd of FC11, but I'm not sure how I can repair the system.
View 14 Replies View RelatedI was finally able to install Fedora 11 x64 after choosing to only install packages from the repository on the install DVD. Prior to that when I had chosen tio install from the default online repositories, the install itself failed with a Python exception ( see my other post ). Now, however, once I boot after the install I eventually receive a kernel panic message, and failure. The exact same thing happened with CentOS 5.3 x64 after a flawless install. So unless someone knows what might be going on I will assume that Fedore, Red hat, and offshoots for x64 bit systems are just not for me. I have been able to successfully install the latest Mandriva and SUSE x64 Linux distros so whatever Red Hat/Fedora has done just does not work on my system.
View 3 Replies View RelatedI'm getting a HDD Lock screen or Disk Controller Failure at boot up. (Compaq Armada) The HDD stops the system dead. The controller failure will allow me to boot Fedora or Puppy from the CD drive.
View 1 Replies View Relatedi have a netbook compaq mini with a sata toshiba hard drive.XP was installed on this machine until the hard drive started to have bad blocks.Then i bought a mypassport500go to install f14 on it.It worked but know the sata hard drive is more and more faulty.When i try to boot f14 it displays :acpi : package has zero elements. So i cannot boot.I tryed rescuecd, does not work either.i tryed many kernel params to disable sata at boot but it seems to be builtin.there is no option in the bios to disable the hard drive.
View 8 Replies View RelatedI am able to retrieve data off a RAID5 array. History: My system disk was partitioned to 10 gigs and over time was filled up to 100% locking me out of the GUI (I am a casual user). Now that I am relegated to the CLI, I need help to see if rebuilding the array and keeping the data intact is possible. I have three sata hard drives in the array and now it appears during the boot process, it fails and can't find the array.
I did the following:
mdadm -D /dev/md0
and here's some of the output:
State: active, FAILED, Not Started
And out of three drives, it states that two have failed. I find this hard to believe as I have had no issues until my system disk was full. A coworker today helped me find some files to delete and now have the system disk down to 97%/8.8 gigs yet I can still not enter the GUI due to the array issue.
Out of the three discs, here are the results (taken also from mdadm -D /dev/md0):
Number Major Minor RAID device STATE
0 8 1 0 active sync /dev/sda1
1 0 0 1 removed
2 0 0 2 removed
Sorry for providing so little, but I am in (Repair Filesystem) mode and only have local access to the machine meaning all outputs will need to be retyped.
I am able to do anything to the box as its only purpose was media storage and serving.
I've run the install to hard drive program three times over and each time I get "disk boot failure". I believe I've got Grub to install to the mbr but I am not sure.
System:
Barton 3200+ with 1GB of DDR1
Asus A7V333
High Point hard disk controller
other items
All the hard drives are hooked to the High Point controller. It recognizes all of them that have power hooked up and read/writes to them. Two have 98SE installs, the third is where I'm trying to install Fedora 12 to get away from some problems I'm having with 98SE.
The BIOS is set up to boot from the "SCSI device" which means it's booting from the High Point controller. The High Point lets me set a boot mark, which, when set to the Fedora drive, yields the disk boot failure no matter what I do to it.
I'm a long time Linux user. Finally got around to upgrading my Fedora 11 system to Fedora 12 by using the 'preupgrade' tool. The upgrade appeared to go well (downloaded packages, rebooted into installer, etc). However, now that the upgrade is complete, I'm unable to boot my system.
Here's my configuration:
/dev/sda (80Gb)
200Mb /boot partition (ext3)
52Gb / partition (ext4 - managed as logical volume)
2Gb swap partition (managed as logical volume)
20Gb /spare partition (ext3 - managed as logical volume) .....
All worked fine under Fedora 11 for the last few months. Grub now presents me with 'Fedora' and 'Windows XP' boot options. The /boot/grub/menu.lst file is essentially the same as it was for Fedora 11, except for the different kernel versions, etc. The boot sequence shows the Fedora bubble (??) and gets about 80% full when the screen goes black and the message displayed is:
No root device found
Boot has failed, sleeping forever
If I boot Windows, all works fine.
Am able to boot using a SystemRescueCD disk. The disks all look okay and I can mount/modify all partitions, etc. The grub menu.lst file read as follows (sorry, typed in, not copied):
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.32.11-99.fc12.i686.PAE)
root (hd0,0) .....
I have a fresh computer with specs as such:
Hard Drive: Western Digital Caviar Black 500Gb 6Gbs Sata
Asus Sata DVD/CD Burner
Core i3 3.3GHz Sandy Bridge chipset
MSI P67A-GD55 Motherboard
Zotac GTS 450
I have a problem where the live cd gives this error message:
Boot failure, sleeping forever.
Just got the latest kernel update 2.6.31.6-162 for fedora 12 64bit and it won't boot on my PC. I just get a black screen with some text that doesn't mean anything to me. Computer is a s775 E7200 with nvidia 730i/9300 integrated graphics. I am NOT using hardware graphics drivers at the moment, having decided to stick with Nouveau drivers for a time. What system log tools do I need to identify the problem?
View 2 Replies View RelatedVoice logger boot failure-reports 'error reading block 33051'
View 1 Replies View RelatedI tried to install fedora in my pc. First I insert fedora dvd and install as per procedure then finally system says like that your installation is completed please reboot ur system. So, before reboot I tried to eject my fedora dvd but it couldn't come out. So after click reboot I eject that dvd. And I got error msg like "media test failure exiting intel boot agent". How can I overcome this error.
View 3 Replies View Relatedi installed Samba on my Fedora, have created couple of Share directories and assigned users accordingly, that part is apsolutly fine and working without any problem, but now the next step is i want to assign the quota limits to users to save the disk space,
View 2 Replies View Relatedi am using linux redHat 5 and fedora9 How can assgin disk space quota to particular user suppose i have 4 users
user1
user2
user3
user4
All four users have a each folder
/data/folder1
/data/folder2
/data/folder3
/data/folder4
i want to assign space limit/restriction of 100MB on each on folder.
We are using Red Hat Enterprise AS 3.0. There are 100+ users connected to a single server. As the Inbox size of Mail Client (Thunderbird) for each user grows there are space constraint on the server. So I want to define a quota on mail folder for each user (say around 500 MB to 1 GB). How can I do this.
View 3 Replies View RelatedAfter my previous stint with 10.10 I've gone back to 10.04 because it boots in 20 seconds instead of 70+ and 10.10 didn't really seem to offer much new stuff that I need. Except one thing. When 10.10 boots, it automatically connects to whatever wireless network is set to Auto. 10.04 however, doesn't. I have to right click the tray applet and click on "Enable Wireless" and only then does it connect to the Auto networks. After a reboot, it's forgotten that I've clicked on "Enable Wireless" and I have to do it all over again.
I've found this thread that seems to describe the same problem and the only working suggesting is to use wicd instead of network-manager.
Does anybody know of a way to make it work using network manager? Do you know what command clicking on "Enable Wireless" runs - if I could just run that in an init script, problem solved. I thought it would be; ifconfig wlan0 up but that doesn't seem to do anything at all (wlan0 is definitely the right adapter)
After upgrading to natty alpha I enabled the nvida graphics drivers. Now I can't boot and get stuck on a purple screen, without grub.
Can I with a live cd revert the drivers back to normal?
Can someone help me with enabling the user login screen on boot up please
View 5 Replies View RelatedI just bought a new Club 3D (ATI) Radeon HD 3450 (8xAGP) graphics card, but received with it some problems.My Ubuntu 10.04 installation would not boot any more. It just gave a blank screen while caps- and scroll lock were flashing on the keyboard.
I then installed 11.04 which works fine except being unable to play even 720p video smoothly (the card should be able to play at least 1080p). When I enable the restricted driver ("ATI/AMD proprietary FLGRX graphics driver") and restart, the system will not boot. It gets to the point where it displays the "ubuntu" sign with the five dots below (where the dots normally change color one at a time), they all change color immediately and then the system freezes.
I realized when I received the card that it requires a power supply of 300 W, whereas the one in my PC is only 240 W. Could this cause the explained behaviour? I am not too happy about changing the power supply, unless there is real reason to think that this is the source of the problems, since I know myself well enough to know that I will probably break something in the process.