Ubuntu :: NFS Mounts Failing At Boot With DNS Errors
Jul 14, 2010
I have several NFS entries in my /etc/fstab file. Each entry generates an error during boot (from /var/log/boot.log):mount.nfs: DNS resolution failed for macpro.dpc: Name or service not known mountall: mount /mnt/BaseLines [656] terminated with status 32
This occurs even if I specify an IP address in fstab rather than a host name. I was really surprised by that. The odd thing is that by the time the system is up, not only is DNS working as expected, but the NFS shares are mounted as expected. I'd just ignore it for now, accept that it prevents Apache from starting since some of the server's files live on the NFS shares (this is a development system). It appears that the DNS resolver isn't running when the mounts are attempted and that they are attempted again later, after the resolver is running.
I did an
$ sudo apt-get update
$ sudo apt-get upgrade....
I'm building a lab of fedora 14 machines that are supported by an RHEL/CentOS 5.6 server. Everything was working fine yesterday, but today ypbind can't connect to the server and nfs mounts fail with this message:
mount.nfs: mount(2): Operation not permitted mount.nfs: trying text-based options 'addr=10.9.1.6' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query failed: RPC: Remote system error - No route to host
I can ping the server from the client using FQDN and ip address.
I have multiple ubuntu machines and I connect to one through an NFS share. I have done this for a few years without issue. However, since re-installing ubuntu and upgrading to 10.4 I have a problem with my system hanging when the remote shares are lost.
Basically, I can power down the machine downstairs, and my main machine then has a fit. I can not open any folders in ubuntu, nor can I shut down. If I try and shut down the system hangs, last time it hung for 8 hours before I had to kill the power.
These are the lines in my fstab
I don't know what I've done wrong, or how I can prevent this from hanging. I have googled the heck out of this as well and can't seem to find an answer either.
Upon reboot, sometimes it would mount automatically and sometimes it would not. I have not discovered any specific pattern. It is very random. Sometimes it would go many reboots without mounting and on the next it would mount it. I tried putting timeo paramter, played with the parameters, but still have the same issue. My laptop is connected to a wireless network. When I do mount -a or if I go to Places everything mounts great. It just simply will not mount all the time automatically upon boot, and after wireless connection is established.
About a month and a half ago I purchased two new 500GB serial ATA hard drives from Best Buy to replace my other, very old 186GB SATA hard drive. Since then I've had issues with Linux. Sometimes when it's booting it gives a bunch of error messages, such as "failed to set xfermode," and then it boots. Other times, after INIT has started, I get ext3 errors about failing to read an inode block, then "cannot start /sbin/agetty" and "ID c5 respawning too fast," and at this point booting fails altogether. These errors seem to happen randomly. However, once the system has booted, everything seems to work fine, and there are no further issues.
I know it's not a faulty hard drive or filesystem because I've tried Linux on both hard drives numerous times, and I've reformatted many times, one time I even tried erasing one of the hard drives byte for byte and then formatting it, and still had issues.
I've tried Arch Linux, Gentoo, VectorLinux, and openSUSE, and all of them have given me these problems. The live CD's for Ubuntu 10.04, Clonezilla, and GParted all have trouble partitioning/cloning/installing to these hard drives. At this point, it's obvious to me that there is a universal problem with this particular model.
GRUB and Syslinux both work fine, and Windows XP works fine too. It's only Linux that's giving me issues.
I would rather not buy a new hard drive if I can help it, seeing as these two are almost brand new. Is there some BIOS setting that could be causing these problems? Is it some unsupported feature in the hard drives? Is it a bug in the Linux kernel?
The hard drive model is WD5000AADS. Both hard drives are this same model. My motherboard is an NForce 680i SLI.
EDIT: I've tried ext2/3, ReiserFS, and XFS, and all of them do this, so I don't think it's a filesystem issue.
I "upgraded" to Karmic and now my computer won't start. It shows the grub menu, I select the first Ubuntu option, and it shows the white logo. Underneath the logo these words appear, and it does nothing:Quote:One or more of the mounts listed in /etc/fstab cannot yet be mounted: /boot: waiting for UUID=338c820e..Press ESC to enter a recovery shell
ubuntu 9.10. Won't boot. Not a new installation, no new hardware. When I boot it up into 2.5.31-22-generic safemode it says: One or more of the mounts listed in etc/fstab cannot yet be mounted: /home: wating for UUID...
Booted up w/ live CD, fsck says that /dev/sda3 is clean I have a 320 GB hard drive, 20 GB is the linux boot, 2 GB is swap, and the rest is /home. Palimpset Disk Utility can recognize the 20 & swap, but says the rest is unrecognized.
I need to mount tmpfs partitions to /etc & /var and unpack archieves of this folders there. This task is complete working on Gentoo with monolite kernel & handmade initramfs script. But on fedora this method is like hacking. And not pretty for later upgrades, etc... I think, may be it is need to create script in /etc/init.d/ with high run priority. But this method takes many errors on boot. It is need to mount two tmpfs partitions to /etc/ & /var & unpack archieves. All this processes are to be executet after switching init from initramfs to realinit. But before first system processes try to start. How to complete this task with fedora way?
My Debian Lenny server crashed today for some inexplicable reason, and now one of my machines refuses to mount NFS shares on bootup. Manual mounting works fine. It's just one machine; the others are still mounting normally.
had a really good reliable machine going with 10.10, but for some reason upon powering up this morning is failing to boot. Any ideas on how to fix this problem greatly appreciated, i have already tried dropping to root shell un-installing reinstalling the gnome desktop but that doesn't appear to be the problem.
I have an external 500gb usb drive with a bootable full install of slackware 12.2, and it also contains all the sets, patches, and extras for 12.2 in /usr/src, along with some other non slackware packages, like gparted, and I use it for rescue, backup, installation, etc.I used this disk with no errors, setting up 12.2 on my mother's dell, a pentium 4.However, my mom has an older gateway as well (a pentium 2) that she keeps around because it has M$ Publisher on it, and sometimes a student emails her a Publisher document, and she has to use her old sluggish beast to open it up.
I have not found an open source solution to open Publisher docs in Linux, so I have been trying to follow http://www.virtualbox.org/wiki/Migrate_Windows to migrate the her xp installation on her old box to a vdi to use with virtualbox.My first obstacle is that the cd drive in the old machine is non-functioning. My second obstacle is that her machine dates back to the days before the bios supported booting from usb.
I have never had the time to mess with network booting, and don't know how to set up a bootp server, so sticking with what I know, I thought I could install lilo on a floppy, and have it configured to boot my external usb. Originally, lilo was installed on the mbr of the usb, but for this project, I went ahead, using the pentium 4, and reinstalled the lilo boot loader on a floppy. I did this by mounting my external usb drive (which shows up as /dev/sda) and then binding /sys, /proc, and /dev to it, and chrooting into the external usb install. Then I modified lilo.conf and reran lilo. It worked, and now the external hard drive only boots on the pentium 4 when I have the floppy inserted into /dev/fd0. However, when I plug the external drive into the pentium 2's usb, and insert the floppy and try to boot, it never makes it to the lilo prompt, and just displays 10 lines of L 07 07 07 07 07 07 07 07 07..The boot order is correctly set in bios to try the floppy first. I thought I might have problems with the smp kernel on such an old system, and thought I might have to go back to huge.s, but I'm not even making it to the prompt...
I just reinstalled my windows partition from a backup image. Following that the Grub2 needed repair. That was accomplished and the grub2 menu along with the changes I made (to the grub screen) come up just fine. I can select my Windows 2K installation and it boots okay.when I select the "Linux 2.6.31-17-generic" the boot process appears to begin normally with the Ubuntu symbol shown, but at some point the screen goes blank and the boot process stalls. recovery mode gives me a jumbled up recovery menu. Alt-Ctrl-Delete gets me out of either.If I boot from the previous "Linux 2.6.31-14-generic", I�m receiving this error during boot-Quote:"One or more of the mounts listed in etc/fstab cannot be mounted"
There are subsequent screens that warn I'm running in "low graphics mode", but I can boot to a somewhat functional system. I was able to boot it once, but get the same results with either kernelThere is a difficult to read message in the jumble of the recovery menu.Quote:"One or more of the mounts listed in etc/fstab cannot be mounted. Swap: waiting for UUID=35b77xxxxxx"Any ideas? I'm not sure how to troubleshoot the problem, or what steps to take to resolve it.
Having a problem, have built some VM's and importet some from JumpBox, but they will not boot from the HD. I am using files for the HDs mixture of ".img" and ".vmdk". I can boot and build from the network and CD/ISO, but after the installation completes it reboots attempts to boot from the HD and nothing happends. No error message is displayed.
I used gparted in PartedMagic to resize my /home partition from 360GB to 160GB, and create a new FAT32 partition out of the remaining 200GB.My /home directory only had about 9GB worth of files in it and as far as I can tell there was no reason for any of them to be anywhere near the portion which was deleted. So the resizing and creating the new partition seemed to go fine. Then I rebooted and it got stuck while booting into Debian.
I tried checking my BIOS for an IOMMU option but there doesn't seem to be one at all. I also only have 4GB of RAM so I don't know why it thinks I have 4.75GB.
I've done the ordinary sources.list update (lenny to squeeze) and Code: sudo apt-get update sudo apt-get install dpkg apt aptitude.sudo aptitude full-upgrade However, udev failed to install, and I used..Code: touch /etc/udev/kernel-upgrade and did full-upgrade again. Everything was going fine, I went through several package configurations and suddenly, after 30-40 minutes of "Unpacking Setting up." I just heard two system beeps and got an error similar to a kernel panic. The SYSRQs did nothing. Did a hard reboot.I got two kernels in GRUB now. + the GRUB2 chainloading option. Used this one and got Code: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block It's all the same with the 2.6.32-5-686 kernel kernel panic. Using the older kernel didn't fail on the boot up, but showed many UDEV related errors and logging in was impossible - all I get were segmentation faults. Forgot to mention it - my FS is Reiserfs
Have just installed 5.4 64 bit on an AMD64 x2 system with 4 GB ram running ESXi4.Text based install went fine, but on reboot starting up it gets as far as 'Starting udev' and just hangs. Checking the performance in ESXi it appears to be using 100% cpu.I have left it for half an hour and it does not progress and the only thing to do is to power cycle the VM.I have searched and found a few suggestions for kernel parameters but they did not make any difference. I can't even get in to a command line as it doesn't boot up far enough.I have reinstalled it several times and also checked the MD5 of the downloaded file and all appears Ok.
Somehow Bind dns, Postfix, Cron all fail to start automatically at boot time? All of them need to be started manually after the system is up in order to function.
I have a 10-year-old desktop computer with Windows XP on one drive and Ubuntu 10.4 on the second drive. The first is an old IDE disk, the second a more modern SATA drive. Tried to boot Ubuntu, and got a lot of arcane i/o errors that I am sorry I can't repeat verbatim but there was something about unable to read sector this or sector that, among other things. I thought maybe the drive was hosed. Tried booting into recovery mode to see if I could figure anything out but it was too geeky for me. Then I tried rebooting Ubuntu to see if I could look at the errors again but now the system insists on going into recovery mode.
Then I tried booting windows, which as I mentioned is on a different physical drive. The MS logo comes up and then it reboots spontaneously and we're back where we started. Any ideas? Should I suspect the second drive is seriously damaged, or could there be some problem with the motherboard?
I'm having two distinct Grub boot errors with Ubuntu 9.10, stemming from two different setups. Anticipating that I'll be asked I ran BootInfoScript on both setups. This is the first setup, where I put a Flash ROM card in the Flash ROM port in front of the computer. This setup will not boot at all, and I get a message something like "Insert appropriate media and try again."
I have a relatively new computer that won't boot Win 7. After going through a lot of tries, I got a suggestion that I try to boot using Ubuntu from a USB flash drive ( since I can't burn a CD).
I followed the procedure to put the necessary files (Version 10.04 64 bit if I recall correctly) on the drive and tried to boot using it.
I got this message:
When I tried to boot again (from the above) I just got the second message (No DEFAULT etc.)
i just built a new ubuntu 10.04 system for my mother because her windows machine died. I was wondering is there anyway i can get here email address and stuff from outlook onto Evolution. i have the old harddrive in a external box via usb, so i can get to the files. i can not boot from that drive because windows has seriouse errors in it.
What would prompt this? i shut off teh computer and turned it back on , didnt press any buttons and it started checking my drives, so i pressed C and cancelled it.
I have partitioned my HDD to three parts and installed Windows 7 and then Ubuntu 11.04. After a while I installed Hackinosh Snow Leopard grub was not there and whenever I tried to boot to ubuntu from Chameleon bootloader it showed an error and told to press Ctrl+Alt+Delete to restart! I have already tried to restore grub from a Live CD but nothing!
I've had a lot of success over the past year with Ubuntu 10.4; however, recently I've been experiencing nothing but problems. It all started with an upgrade a month ago that caused me to experience a boot error. Now every time I re-install the system, I will have a random boot error. I have been trying to install the system on a friend's computer and getting the same thing. I've tried a different download and burned different discs, but I am still experiencing problems with the system having a boot error. Sometimes it is immediate after installation and other times it might boot fine for a day or two and then suddenly it will no longer boot. Is there some kind of bug with 10.4 now? I never, never had this hard of a time with Ubuntu. I've installed it on several computers for myself and other people.
This is what my computer looks like while it's booting. Gdm pops up shortly, and I can use my computer with no problems. More recently, I screwed up something in gdm, so I can't do anything with my ubuntu computer.
Since installing debian 8.2 I have had a list of errors appear during the boot, I get the usual Loading, please wait message then a series of random errors.I think I am stuck in initramfs, then typing exit resumes boot. Should I be concerned and can I jump straight into the login screen without typing exit each time?
Do you know a way to know what's up at boot time?? Before that the sistem is ready to "be used" there are some "errors" I would like to solve. Besaides, the "/var/log/boot" file is empty.
