I recently created a bootable pen drive using unetbootin of Ubuntu 10-10 release. It was failing with error message similar to 'specify the init' then formatted the pendrive/usb and now it was giving, SYSLINUX 3.63 Debian 2008-07-15 EBIOS CopyRight ..... Could not find kernal image. boot: when you press enter it again goes to Could not find kernal image. boot: linux
I believe this is due to USB creator. Let me try with creating bootable USB from some windows machine.
I am building a 10.04.1LTS server. I am putting the /root filesystem into a Software RAID1 partition. I want to keeo my /boot partition outside of RAID.Is there a way to have a boot partition on both sda and sdb so if one drive fails the second boot partition will work away - or should this be kept in with RAID also.
I was upgrading our lab's dhcp server to Lucid and it totally died. I have it running on a Debian recovery cd right now. I ran into a bug in gtk which I seem to have fixed, but now I have more serious errors. If I boot without a CD, I get dumped into a busybox shell after the machine fails to boot. From the live CD, I tried dist-upgrading again and it dies trying to build and install rsyslog with a broken pipe error. I am at a loss as to what to do from here short of reinstalling (which is the last option as this server has a lot of custom configs on it)
My Internet connection works fine when I boot Ubuntu with the CD and it does not work when I boot from the Hard Drive. It was working then it stopped. I tried to diagnose the problem but I am not familiar with Linux.
I opened a Terminal window and entered ipconfig (don't laugh ... sadly, i've been in Windows for too long) ipconfig was something that could not be found in my terminal window so i exited.
Next it was System->Administration->Network Tools. I ping'd www.yahoo.com and it said it could not find it. hmmmm. Let's see if restarting the system will fix it.
I did a shutdown and when it came back up; same problem. Ok, i really didn't think it would magically correct itself; this is Linux after all. Windows? Well sometimes you can fix things by turning them off and on. Next, another shutdown and I rebooted with the CD instead of the Hard drive and here I sit entering this help question in.
I am guessing that a file or setting got changed in /etc/someplace and I am not even sure of that. Can anyone point me in the correct direction? I am assuming that there is a setting which is correct in the CD version that is not not correct in the HD version and somehow i need to find what it is and synchronize it with the CD version.
I downloaded ubuntu 10.10 iso, made CD, installed as dual-boot with win Vista home premium and used it for a week to access the 'net and email. Yesterday, while deleting an email, the "d" key stuck down while I was issuing <CTRL>D and the cursor froze. I then rebooted by using the reset button and saw many lines of text including "kernel panic". so I reset and booted into 'repair boot'. Again, many lines of text which stop at the same place if I try this twice.
I assume I've fried my ubuntu install and would like to fix or re-install it. When I installed it, I let the [wubi?] installer make decisions except choice of drive because it picked the external, USB drive. It appears to've used about 80 G on internal drive D: I could boot from the distro CD and see if it will re-install but I'm concerned that I may not fix my problem or that it may mess up my windows installation.
My old computer started randomly rebooting so I went out yesterday and bought a new one. It's a standard Intel 64 architecture with 2gb ram etc.The old computer was running Lenny however I'm happy to upgrade, so I just went to the main Debian download site and downloaded:debian-6.0.1a-ia64.netinst.iso (this didn't work, apparently ia64 is for itanium and my machine is definitely not that), so I downloaded: debian-6.0.1a-amd64-netinst.iso, burnt the CD and ran the install. First time through I had a power failure.
Second time through (a complete fresh start - new partition and everything) it went all the way through to completion and reboot.Clicked 'Continue' to reboot and the machine reset as it would normally and the Grub loader started okay, prompted for the "Debian amd64" standard boot image, selected that and the first 6 lines appeared normal, then the messages wizzed by so fast that only superman could read them. Then they stop - here is some of the content...
[3.816673] Kernel panic - not syncing: Attempted to killl init! Call trace: get_empty_filp panic
[code].....
Running it again I get similar stack stuff but it's a different place: [3.541816], [3.427502] And sometimes if I wait for a minute or two it will continue on further but appear to crash again. Hardware details (everything is onboard - no added cards):
i am very frustrated with my ubuntu system which is meant as a workstation-server. It seems to loose track of its drives every time I add diskspace.Now every other boot (it seems) it says (among other things: VFS: can't find ext3 filesystem on dev sdd5) drops me to a maintenance-shell and asks for the root password (whats that in ubuntu, the user password does not word) - so I can't log in. Ctrl-D sometimes works and it boots through or boots after warmstart by Ctrl-Alt-Del.
[edit: found out that with alt-f3 i can access a normal shell - good - but how do I start up the GUI in ubuntu? - startx does not work] I have manually fsck'd all ext2/3 partitions form a ubuntu booted from CD - still it says something about not being able to mount /dev/sdd5.Since every now and then I have so much trouble bringing up the machine I am quite unhappy. I suspect the constant updates are prone to break things - is that so?And how do I resolve this issue. Unfortunately there is nothing about the errors in /var/log/messages or dmesg so it is no use posting it here. Where are such errors recorded? [edit: I changed the mappings in fstab to resolve the issue - still it is awkward that drives get messed up so easily. Are UUIDs in fstab less error prone when moving drives around, or do they have other issues?]
I have a laptop with Windows 7 and Ubuntu installed in seperate partitions. When I boot up the computer I get options to boot either in windows 7 or Ubuntu. Yesterday I updated Ubuntu to 10.4 version. I have been having issues with grub rescue, which was rectified an hour ago. Now I can boot up into windows 7, but when I try to boot into Ubuntu, I get a GRUB screen as below code...
I installed Ubuntu netbook version on my HP netbook Mini 110 with Windows 7. After installing Ubuntu the first boot up failed. It hangs with a black screen with a flashing text-mode cursor. After several attempts (just rebooting) it worked. However, about 95% of the time the machine fails to boot - after 3-4 seconds, and without showing anything on the screen (text or graphical), it hangs with a black screen with a flashing text-mode cursor. Pressing Ctrl-Alt-F7 (or any other keys) has no effect.
I also tried booting in recovery mode from the Grub menu I get at start-up. It failed too. The last few lines I get in recovery mode looks like : ata1: SATA max UDMA/133 abar m1024@0xfe(some numbers)
ata2: DUMMY ata3: SATA max UDMA/133 abar m1024@0xfe(some numbers) ata4: DUMMY
After this it get stuck there forever. Can someone help me out on this ? I'm a novice in this area.
I've installed burg with no major hassle. Started up the computer to see a pretty new boot menu, but Ubuntu fails to boot. The screen immediately turns black and the computer reboots. Fortunately, I have grub backed up on a usb flash drive so I can boot.
This morning my system has a problem which is beyond my ability to understand: Firstly, the system does not boot automatically, after a fixed delay, from the grub menu. I have to press 'enter' against a chosen boot option. Secondly boot then fails. A lot of messages flash past the screen (which appear to be a trace) and end showing the following (partial example):
Code: Killed mount: mounting /dev on /root/dev failed: No such file or directory mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg.
at this stage I can move around the directory structure using 'cd', but no other commands seem to work.I tried the recovery boot option - same result. Is this a symptom that my boot drive has failed? No, that can't be true, or I would not be able to see the grub menu, would I? I can't find a similar situation after a Google search; what recovery procedure I should use? Correction: I must have had brain fade: I see there is quite a long thread on this very topic on the forum. I'm going to examine that first before I ask for more help.
this problem began some time ago and I can't quite remember how or why. This computer is somewhat new as my former HDD died and I bought some other stuff along the new HDD and it wasn't until some time later that I noticed the problems which never happened before, I had been using Ubuntu 10.10 both before and after I got the new HDD.For some reason, Ubuntu began giving error messages when I tried to run it, most often it would give them over and over unless I decided to give up and try again several minutes later. The error message was always a lot of weird things from which the only thing I could make out was
"Kernel panich - Not Synching: VF:S unable to mount root fs on unknown-block 0,0" (or something like that)I tried using other kernels but it'd give the same error message, I sometimes even used WinXP, sometimes it'd boot correctly, others it'd reboot.This became really annoying and tried with a clean install, the first few times I logged in seemed to be working fine but this morning I'm having a problem that seems even worse.When I try the now only kernel I have available it just remains unmoving from a blinking cursor screen. If I try the recovery mode I get the "Kernel panic..." errror message and when I try with Memory Test
Installed v9 a couple of weeks back and have been causally mucking about with it since. I managed to get XP and ubuntu running as a dual boot system (which was an achievement ).
Anyway, i've upgraded to 10.04 - and already loving it. However... my XP o/s no longer boots. It use to prior to the upgrade. Now, when the XP o/s is selected from GRUB2, I just get a series of bleeps and a flashing _.
Now, I am a complete novice. I actually have no idea where to even begin trouble shooting GRUB2 (and i'm assuming its a problem with GRUB).
I created a Ubuntu live usb，it works fine on my notebook, but boots fail on my desktop pc. I found that /dev/sdb1 is always mounted to /cdrom when booting, but usb key is /dev/sdc on my desktop pc, it causes sequence booting process which depend upon files under /cdrom fails.
I have Vista on my Samsung R60 + and have installed Ubuntu. On start up I get the dual boot option, select Ubuntu which then goes to completeing install etc, get some HD activity then nothing.
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?
Dual boot Windows XP SP3 & Ubuntu 9.10 on a single hdd, w/2 partitions. Booted to Ubuntu and upgraded online. XP boots fine, but Ubuntu, not so much; a msg about /dev not found, followed by a shell login prompt. I suspect a grub problem, but haven't been able to find a definitive answer. Since I can at least boot XP, I do not want to do anything that would screw that up and leave me with no bootable OS. I did the "upgrade" shortly after 10.04 was released. Is there a way to reliably fix this w/o possibly screwing up my ability to boot XP, the only OS I can boot? I have no Ubuntu 10.04 disk, as I used their upgrade online option.
I'm having a lot of trouble with a PC that has been running Ubuntu for ages, since about 8.04 I think. I've run the distro upgrade a few times and it was running 10.04, but for some reason won't boot anymore. So I'm trying to do a fresh reinstall but I can't get the LiveCD to boot. I'm trying to install 10.04 AMD64 desktop.If I leave the CD to boot, I get to a Busybox screen showing the error "No init found. Try passing init= bootarg." and an (initramfs) prompt. This is all displayed at 1280x1024 res - the native image of the screen I'm using.It's an NVidia chipset - an older one. So I tried hitting a key during boot and putting the nomodeset option on. I get the same error, but at a lower resolution
Now this no longer works with whatever grub 10.04 uses, I suspect it is grub2? How do I restore grub to the specific partition I need and NOT to MBR? I have a different boot loader and this boot loader is directed to Ubuntu's boot partition.... Since I cannot boot directly to Ubuntu's boot partition I am perhaps left with only LiveCD to do the recovery, right?
So I just finished doing a Hardy based LiveCD. I made an installation in VirtualBox, installed some packages, and then compiled a totally new kernel, 2.6.35, actually this one: [URL] I compiled squashfs support in the kernel naturally Everything seems to be fine, the system boots up normally etc. But here comes the trouble: I make the iso file with remasterys (2.0.12-latest for Hardy) but this iso isn't able to boot.
It drops to busybox shell, casper.log says: /init: 1 /dev/sr0: no such file or directory Unable to find medium with the livesystem. My /dev folder is totally empty, it contains only the shells (8 pieces of tty). I don't know what's wrong...my rootfs is surely mounted, mount shows rootfs rw /
I have win 7 installed on my main first hdd and would like to install ubuntu 10.10 on my newly installed second hdd. Problem is that during install when i choose manual partitioning my second hdd is not visible. So it is impossible to choose the disk for installation. Tried to disable first hdd in bios but pc than fails to boot from dvd. Tried the alternate ubuntu cd and second drive even then is invisible. Second hdd is visible in win 7 and fully can be manipulated in 7. Tried to format the drive as fat32, ntfs, linux ext 2 and 3, but same problem. Drives are mounted as 1st hdd is primary master and 2nd hdd is secondary master.
I am trying to get Ubuntu to boot from a usb, and failing.
I have a two year old Acaer Aspire 5735Z with Windows Vista as the OS. This has USB as a possible boot source, now of course at the top of the list.
I downloaded 10.10 and installed on an empty 8 GB Kingston drive as guided. There is just under 4 GB on the drive. The drive had been used before and all deleted.
So at start up the first thing that happens is the led on the USB drive flickers for less than one second, and then the Windows boots.
I was stupidly compiling code on my netbook with 10% battery left. The CPU ate up my battery reeaally quickly and it did a hard shutdown while still compiling.When I boot up, the Ubuntu loading screen shows up for about two seconds and then it goes to a completely black unresponsive screen. I have a live install on my thumb drive, but I don't actually know what I need to do to fix whatever broke.Edit:Oo, something happened. When I pressed a key the screen filled up with a bunch of stuff I don't understand. But the last two messages are: [ 450.807328] Fixing recursive fault but reboot is needed!mountall: Disconnected from Plymouth
Recently I installed Ubuntu 10.10 on a desktop I use on occasion. It is a Dell Dimension E510. It was running on Windows XP(?) and I think ours dates back to around 2005 or 2007, but I can't say so with certainty.
Anyway, let's say it was about ten days ago when I installed. Everything worked fine and was great. But now the computer won't boot and I'm at a total loss of where I should go from here.
To summarize what happens: Basically I hit the power button and can hear the machine turn on (the monitor's power button is stuck on, so it's already powered), but the screen just stays dark.
I've done a slight amount of research and tested to see if it was the CPU behind it, and if removing any external devices would help (which I'm still not sure if it isn't the culprit) to no avail. My younger sister uses the computer almost exclusively for charging her iPod - which in that case may be related. I'm curious if anyone knows other methods to get around the possibility of it being a CPU problem just in case.
I was using Maverick, I performed upgrade to Natty today morning and rebooted and it was working fine. Then I turned off my PC and left home.
Now in the evening when I'm trying to boot nothing happens, just black screen. Nothing happens after that.
Though I can boot by selecting "Previous Version" but can't boot normally. Though I was surprised that even after selecting "previous version" I was booted in to Natty(I guess so, as the UI is Unity not GNOME).
But can't boot using the Kernel that's listed first in my Menu.
I just upgraded to ubuntu 11.04 but now all the kernels fail to boot. The resolution of grub changed and the older kernels are put into a 'previous kernels' folder. The most recent kernel halts at the message '* Stopping userspace bootsplash [ OK ]' and the previous kernels fail with the message 'Unlink after no-irq. Controller is probably using the wrong IRQ',
or show the background of the login screen with just a white box.
I think the cause is that I have an ATI graphics card (HD Radeon 3650), because on my 2 other computers ubuntu upgrades fine and they have NVIDEA graphics cards.
As a last resort I tried installing different distro's like Linux Mint but it also gived me the 'unlink after no-irq' message.
I downloaded Ubuntu desktop 10.10 on to my Acer 5741 laptop (which I checked online for comptability), following the site's instructions to the letter. I used the USB installer to create a live USB which seemed to go fine. I then restarted as instructed and changed the USB to be selected to boot. However, from that point, the OS fails to load. I get several pages of code loading, then a screen with a logo at the bottom, then my screen just goes dark.
