[URL] and instead of a fat32 I added a ntfs 2 tb hd to my computer. But it doesnt like it, so now when I boot I get
init: ureadahead-other main process (1234) terminated with status 4
I searched and people are mentioning logging into the terminal and what not, but I cant get to a terminal so that kind of silly. People also talking about updating their video cards for this issue, which also is not my problem.
I have made an entry in fstab that is keeping me from booting. I am able to get into recovery either from entering "M" as it is trying to mount my bad entry or from Grub.
However once in recovery I am unable to save my edits in vi. I have tried several attempts at saving my edits to no avail. What trick will I have to impose in order to clean up my fstab so I can boot successfully.
I am stuck in recovery shell because I mistyped one line in the fstab file. I know what I did wrong but now I cant edit my fstab anymore. I can only enter recovery shell and thats it.
sudo nano doesent work because it's a read only file / disk.
So any idea is worth trying
Because I forgot to bring a portable hard drive, I cannot boot to a linux OS.
The reason is that the /etc/fstab has a line that is
Quote:
And ext3-datadisk is on the portable hard drive.
The booting process stopped when it prompts for a root passwd or Ctl-D to reboot.
I keyed in the root passwd, and a (File Recovery) prompt appeared.
I tried to vi /etc/fstab but I cannot save the edited /etc/fstab.
How can I boot successfully in this case ?
We have a Wipro Net Power 8552 server on RAID 5 with Linux Advanced Server. The Databse is Oracle . Every time the reocovery is made the block corruption error gets changed. There are four hardisk in the Raid with 18 GB capacity of Quantum make. I want to make sure if any Utility is there in Linux to check the Harddisk if any Block corruption is there or Not.
View 1 Replies View RelatedForgive the terseness. I'm frazzled with this issue, perhaps I should have asked earlier. Every weekend for the past 2 months has been an endless cycle of 'repair broken system' off the install disk.
Installed from Ubuntu server 10.04LTS x86_64, + xfce-desktop Here is uname -a Linux ournas 2.6.32-25-server #45-Ubuntu SMP Sat Oct 16 20:06:58 UTC 2010 x86_64 GNU/Linux If I add my raid + lvm to the fstab file, the boot stalls, (no error it, just hangs waiting, forever). So that's a not very user friendly to start with.
I've tried the suggestions about UUID in fstab tried using LABEL instead, or even /dev/xxx. Every time it hangs. I've googled this endlessly and not found a solution. So don't ask why... since I seem to have tried every odd suggestion to fix this, I've lost track. There seems to be some consensus that whoever gave us plymouth laid an egg. Forgive me if I'm wrong, but did we need a better graphical boot if it breaks everything else?
[Code]...
I have a Computer, It came with Windows 7 64bit on it. I installed Ubuntu through WUBI. I used the Windows Disk Management program to resize my HDD. I shrunk the main drive and created a 20 gig free space. I installed WindowsXP on this 20g space. I had to change from AHCI to ATA. I started my new XP installation. As I should have expected my the screen that let me pick between Windows 7 and Ubuntu was gone, and it just said XP. Well thats cool. I get in XP use bcdeasy and use the install Win7 to mbr. So I restarted. Great I now I have Ubuntu and Win7... but no XP. So i think, okay, ill boot into Ubuntu, use the update grub command and XP will be there, so i do it and restart. No XP, So i try to boot into Win7 and see if i can do something in there.. No luck it says it can't boot and takes me to a startup recovery thing. Which, as Windows recovery things tend to do, doesn't find anything wrong. So I have Ubuntu now, which is great, but I do need Windows.
View 4 Replies View RelatedI have an external hdd that I have added to the fstab so it will mount when I boot. But every time I add the line to fstab and reboot, it hangs during the boot process and says something about ureadahead-other status 4. here is my line in fstab..
/dev/sdc1 /NAS ext3 defaults 0 0
Is there anything wrong with that? I couldn't remember what fs I chose when I formatted it so I did "sudo parted /dev/sdc print" and it said it was ext3.
I'm puzzled as to why this fstab isn't working:
Code:
# /etc/fstab: static file system information.
#
[code]...
I made a mistake in my fstab. I know what the problem is and how the fstab needs to be changed. However, since the system will not boot I'm having diffeculty getting in to edit it.The system is running Ubuntu 10.4 64 Bit with LVM2.I have both 10.4 64Bit Server and 10.4 32Bit Desktop cds currently and could burn others if needed. With 32Bit Desktop I'm able to get to a live cd prompt but my hard disks are not mounted.if I try mounting /dev/sda5 to a dummy directory I created it tells me it doesn't know the type of 'LVM2_member'.
View 5 Replies View RelatedWhat would be the best way list disk and partitions in the fstab file?
View 1 Replies View RelatedI've had two hd's in my box forever. for more space and backup reasons. Well I have started running the Debian Squeeze distro since December. I've had many issues, some are still unresolved. but now I'm running into major headaches with the fstab. Specifically dealing with/wondering why UUID's are used instead of the old /dev/hd? I was a little annoyed when I tried Kubuntu to find /dev/sd? used instead of /dev/hd? but that was workable. But the UUID's are a nightmare. Here's my problem.
My main box is finally giving up the ghost. The mobo is dying. So in order to do some tests I took my hd bundle (my two hard drives with their cables) physically out of the box and temp installed them in a test box. I wanted to do some benchmark and other tests. I got all kinds of errors. I found that the system wasn't recognizing the UUID's listed in fstab. My concern is when the new mobo gets here next week I won't simply be able to plug the hd's in like I always have been and just let Linux reconfigure itself (Debian used to be good about this). I really don't want to have to clean reinstall if it's not needed.
So for this I have two questions. WHY developers decided to drop using /dev/hd? or even /dev/sd? ?
And is it possible to revert fstab's listings back to the old /dev/hd? settings. In debian fstab had lines commented out showing how each partition was listed in it's /dev/hd? status during install.
I'm getting really sick of all these archane changes in ALL aspects of linux that don't seem to have any good explaination or need.
I was able to successfully create a small, fixed-size "ram disk" just for kicks, via:
Code:
sudo mkfs -t ext3 -q /dev/ram1 65536
sudo mkdir -p /media/ramdisk
sudo mount /dev/ram1 /media/ramdisk -o defaults,rw
However, I wanted it to auto-boot, so I added the line to fstab:
Code:
/dev/ram1 /media/ramdisk ext3 defaults 0 0
This, however, rendered Ubuntu unbootable and I had to repair the fstab by removing the line via a Live CD. I had enough patience to boot through the CD an extra time to see if just deleting "ext3" would work, but it did not. What would cause this to make the system unbootable and how I could make it work?
No Boot started w/auto check of drives and it failed on my Virtual C: drive. I know,... but I edited /etc/fstab and now I have nothing available to get a command line. I have grub2 and don't know how or can't get to a boot menu either. Is this a reinstall?
View 9 Replies View RelatedI "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
View 9 Replies View RelatedI recently formatted my HDD and installed Ubuntu Server 10.04 x64. This is actually the 4th install in the past week because I was testing some things. But I had this problem on at least the previous install which made me want to start fresh again. The problem I'm having is Ubuntu will not boot if I add any of my drives to fstab. If I leave it with the standard proc, /, and swap lines it works fine. As soon as I add a line for one of my RAID arrays or an NTFS formatted partition the system hangs on bootup. It doesn't matter if I have the extra drives operating or not.
The last thing I see before it hangs is:
Code:
/dev/sda1: clean, 69351/4358144 files, 583945/17401600 blocks
Here is what the fstab currently looks like:
Code:
proc /proc proc nodev,noexec,nosuid 0 0
UUID=c62ac627-46a6-4fd5-87e8-4ae0d9185d53 / ext4 errors=remount-ro 0 1
UUID=c1cee1e4-f8ac-4555-a88b-f237afdedd27 none swap sw 0 0
/dev/md0 /mnt/raid5 ext4 defaults 0 0
The other two lines which also made it hang included one which was almost exactly the same as the /dev/md0 line except it was md1 with a different mount point and another which used a UUID and was ntfs-3g. I know they work because all 3 of them were mounted by "mount -a" after putting them into fstab and they're pretty much the same as what I was using with 9.04 server.
I'm trying to add a line to fstab to mount a share on every boot. I can mount the share manually using
sudo mount -t nfs 192.168.2.1:/x_machine /mnt/test
I've added the line
192.168.2.1:/x_machine /mnt/test nfs rw,hard,intr 0 0
to my /etc/fstab file, but it doesn't seem to mount on boot. What am I missing. I tried looking in the log files for an error, but couldn't find anything. Ubuntu 10.04 x64 desktop edition.
I have ntfs partition installed bran new ubuntu system. I have some problem with unrar utf8 character zip files.Then i change my fstab file that uses files in D:ubuntudisks oot.disk and i added with out no fearless Code: ,utf8 and after all now i can't boot my linux system it does not allow me to change anything in fstab file. Although i use as a prefix sudo or as a root "sudo -i" commands I dont have any right to change it.
View 6 Replies View RelatedI really need some help here, this is driving me mad. I edited my fstab file to boot a partition on start up, only instead of typing sda7 I typed sda1 by mistake and now can't boot.
The problem that is driving me mad is I cannot save changes to fstab from a live cd because I do not have root permissions.
I am relatively new to Linux and have no idea how to use the fedora install disk or the commands to use or if it will let me save changes to the file.
I cannot believe something so easy to fix does not appear to be possible because i can't save changes to the fstab on my fedora install.
I've edited /etc/fstab to auto-mount two partitions on a new disk drive that have been formatted as ext3, by appending the following two lines:
/dev/sdb1 /bak1 ext3 defaults 1 1
/dev/sdb2 /bak2 ext3 defaults 1 1
On reboot, the system complains there is some problem (I can't advise what the problem is, because the display scrolls up too fast to read!), and I'm left with a root command prompt.
Its a /etc/fstab problem, presumably. I've used vi to edit /etc/fstab to remove the two lines mentioned above, but on quit and save, I'm told I have a read-only file system!
1. How can I mount a read-write file system so I can edit /etc/fstab?
2. What's wrong with my two new entries in /etc/fstab? After formatting /dev/sdb1 and /dev/sdb2, I checked the they were mountable with # mount /dev/sdbn /bakn (n = 1, 2) before editing fstab.
I have a removable SATA Mobilerack which i use to play with.It has redhat linux loaded on a 500GB disk and i made a new partition using fdisk and then made an ext3 filesystem with mkfs. I then tried to edit fstab to add the new partition but have obviously stuffed it up. When I tried to reboot I get the error fsck ext3: UNABLE TO RESOLVE `LABEL=/mnt'.
View 3 Replies View RelatedI'm having a huge problem right now and I could use some help deciphering what's wrong.I can't get my system to boot (see signature) and even the recovery mode is buggered. henever I try to boot, all I get is a flashing underscore. This is the same for both the normal and recovery modes Kernels. I've run the boot info script from a live cd and I've attached it to this post.
View 9 Replies View RelatedA friend's old Compaq Presario came with Windows XP. However, when it got buggy (without his knowledge or consent), his kids overwrote his OS by installing a warez edition of Windows 7 Ultimate. Unfortunately, that wiped out all his data, including photos of his late wife that he does not have backed up. I want to recover those if possible. I don't want to install anything because that may overwrite the photos if they're still there in some shape or form.
What I'm wondering is if there's a DVD-bootable distro of Linux specifically for data recovery. If I could boot to that, I could run its data recovery utilities without danger of putting anything on the hard drive. Once I've recovered the photos and backed them up to an external hard drive, I'm going to make his PC legal by installing Ubuntu. That's no problem. I'm very up to speed on that. What I need to learn is the best data recovery strategy via some type of bootable Linux. I suspect someone has written such a tool given how often people lose data due to viruses, accidental deletions, formats, etc.
I have a usb-hdd at one location that I use for backup purposes.It is listed (by its specific label, not uuid because I don't want to go through the hassle of changing this when changing backup drives or adding one at a different location.Now, since upgrading from 9.10 to 10.04, I get the following message during boot when the usb-hdd is not present and thus not attached:The disk drive for "/media/backup" is not ready yet or not presentI need to press S to skip mounting manually, whereas 9.10 just ignored that fstab entry and continued booting. How can I get the old behavior back? Is there an option I can give in fstab that mounts the drive at bootup when present and ignores it when not?
Perhaps an even better solution would be to let the drive be mounted according to the fstab entry whenever it is attached (be it at bootup or at any other moment): is this possible?elated to that: are drives unmounted/mounted in a suspend/resume cycle?
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.
Due to my script error my boot/grub/menu.lst and etc/fstab files are ruined without being backed up first.
Anyone, the boot/grub/menu.lst and etc/fstab file of Ubuntu 10 LTS installed by default on HD (or whatever).
Ubuntu 10.10 doesn't boot at all. The liveCD only boots once every like 30 attempts, installing from liveCD froze, but the Alternate CD worked and installed ubuntu. Now when I try to boot into it using GRUB, it freezes at the beginning of the boot process.With normal boot it freezes at line: Starting AppArmor profiles Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox.With recovery mode it freezes even before showing me anything
A little kinda like the liveCD, if I try like 30 times, it might manage to boot once in normal mode.That line keeps on repeating, the the xxx.xxx integer changes each time, and this goes on forever.I tried removing my floppy drive, but it didn't help.I tried to boot with fd0=noprobeThe one time it booted, when I restarted, it froze while trying to restart.
I've just started playing around with a Sheevaplug running a very light version of Ubuntu. I'm planning to run it with an SD card to store all my server data and a USB stick to regularly back up some of it.My problem is that the 2 partitions on my SD card mount fine at boot, but my USB stick's single partition does not. Could it be that the mounts specified in fstab are done before my USB device has finished getting alive? Mounting the USB stick manually works perfectly well.
fstab
Code:
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/sda1 /media/usb1 ext2 defaults 0 0
/dev/mmcblk0p1 /media/sd1 ext2 defaults 0 0
/dev/mmcblk0p2 /media/sd2 ext2 defaults 0 0
dmesg after boot
Code:
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver.....
In the dmesg
Code:
usb-storage: device scan complete
comes after
Code:
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
which makes me think the USB stick has missed the fstab train the 2 SD card partitions are on. And changing the order of the entries in fstab does not make any difference either.
I'm not planning to reboot my Sheevaplug every 5 minutes, but I like things to be nice and clean.
shut down my RHEL 4 system with an error still present in the /etc/fstab file. Current symptom: When I now try to boot, everything hangs when "Enabling swap space". Highly likely, the reason is the failure to "Mount local filesystems" in the previous step (i.e. "mount point 0 does not exist" = error due to my incorrect line in the /etc/fstab file).Question: Is there any way that I can still boot my system, such that I can remove the incorrect line in the /etc/fstab file?
View 6 Replies View RelatedThis is an urgent problem. I removed my propreitary ati display drivers because I had to update them but I don't know what happened. Now I can't boot. The screen shows the Ubuntu splash screen but then the login screen does not come on. I get a blank screen. Worst of all, I had removed Recovery entries from the grub so I can't boot into recovery mode so easily. It's urgent. I don't want to reinstall with my exams a week away.
View 2 Replies View Related