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
I have installed the ubuntu 9.10 and the pc already have 2 win 7 OS and 1 win xp I installed the ubuntu from win xp every thing go just fine but in win 7 boat loader it detects the 2 win 7 OS , previous windows ( the xp )and the ubuntu which fails to load from win7 boot loader ( the first problem ) but it is present also in win xp boat loader so when choosing older windows the win xp bootloader let me choose between windows xp and ubuntu which works fine when choosing it the ubuntu bootloader appears with ubuntuubuntu safe modewin7 bootloader
the second problems that choosing win 7 after restarting the pc from ubuntu fail to open it begin loading with the windows logo and then just shutdown the whole pc as if i have unplugged it! the only way to let it open is to choose older windows>>> ubuntu >>>> ubuntu bootloader >>> where there is win 7 bootloader option it returns me again to win 7 bootloader but this time the windows load complete ( mostly but may shut down also!)
I'm just curious - why do all linux distros (all I've seen) run their periodic disk checks during boot? I mean, I understand that a disk should be checked now and then, but why does the system do it during boot, when I'm waiting for it to load, instead of checking them during shutdown, when (most probably) user doesn't need the computer anymore.
I'm very new to Linux and recently setup a desktop PC with Puppy 5.2.5. only. I chose to have a permanent install on the hard drive and loaded additional PETS and utilities as I thought needed for my use. Last night after immediately booting up the PC I had a power cut lasting a few minutes. When power returned and I repowered the PC, I found during Puppy's boot sequence it reported an error and remained in what appeared to be a console mode - did not carry through and load my desktop. So I inserted the Puppy CD and booted from that but I'm afraid I'm not familiar enough with Linux to understand how I can get back my original desktop setup and run once again from my hard drive without having to go back to scratch.
when my pc boots and shuts down my monitor goes into 'input out of range' mode for a bit between the gui and the text only phases of boot/shutdown.is there a way to fix this? or where to start troubleshooting?also, when it shuts down it hangs after coming back to the text only part
I have minor problem with upgrading a hard drive. I am running an old pentium lll with two hard drives. On the first hard drive I have two partitions of around 90GB each. On the first partition is installed winXP and on the second partition I have Suse 10.3, both booted by grub and living happily side by side. My second hard drive (which is formatted for windows is only 4GB.
My problem arises when I try to replace the 4GB with a 80Gb hard drive. When I disconnect the 4GB drive the system fails to boot up and complains with error 21.
Did a clean minimal install of Testing in a Virtual Machine (VirtualBox).Login as root.Type "shutdown now".It starts shutting down, then says INIT: Sending processes the TERM signal Give root password for maintenance (or type Control-D to continue):If i press Control-D it goes back to a login prompt.Okay, i maybe missing a point since "shutdown -h now" gives the expected behaviour.Call me old fashioned but I think that a "shutdown now" should shutdown a system, and not effectively reboot the system. There is a reboot command for that.
this problem is a well known one as far as I have read, but the solution is yet to come.I formatted and installed OpenSuse 11.3 KDE as the only OS on a PC with 768 RAM, two Hard Disks (6+8 GB), mobo Abit BE6, processor Celeron Coppermine 1100Mhz (with slotket adapter), video card Matrox G400+, Sound Blaster Live! Value.HD 1 is set root and ext4 + 1 GB swap, HD2 is /home ext3.The live OpenSuse CD worked fine, shutdown turns off the power, while the installed one won't. I formatted twice, and the problem persist. Reboot works fine.At shutdown, the hard disks are turned off while the screen and power are still on, so I have to press the power button to turn off completely.
Yesterday I wasted all the day with this problem without solving it, I've read many threads but no solution worked. That PC obviously worked fine with both Windows 98 and XP.Those problems are in the "out of the box" installation, without any setting altered.I've tried disabling ACPI, PM control by APM, and power management features in the bios (latest 2001's Award bios for this old mobo).I've set alternatively pci=noacpi, nosmp, apm=power-off, acpi=force in GRUB options. I've updated the distro. I've set value poweroff for HALT in etc/sysconfig. Nothing changed.I've also tried macumba and ancient celtic cerimonies, yet they didn't work.Is it possible to solve this problem or it's a known unsolved bug? Loading OS screen:Those are the final screens after shutdown where it stops
I have a custom command I've made to quickly shut down all of my xen instances.
Code:
[root@LCENT02 ~]# virtdown -bash: syntax error near unexpected token `2'
As you can see it fails when I try to run it on the command line. It is stored in an ~/.env file in my home directory. What is odd to me is if I open the .env file and copy the command from there and paste it into the command line, it does actually work!
Code:
[root@LCENT02 ~]# for i in `virsh list | grep -v -e Id -e --- -e Domain-0 | awk '{print $1}'`; do virsh shutdown $i; done Domain 1 is being shutdown Domain 2 is being shutdown Domain 3 is being shutdown
And this is how I have the command entered into my .env file:
Code:
alias virtdown="for i in `virsh list | grep -v -e Id -e --- -e Domain-0 | awk '{print $1}'`; do virsh shutdown $i; done
Why would this command work if you paste it onto the command line but not use the custom command virtdown?
Basically, when I do a reboot or shutdown and then the system tries to start I get a blank screen thus I have to hit the reset button and then I'm showed a grub menu (not sure why I have it set to autoboot) and then I can boot properly.
Right Now I'm using hdparm command in unix to shut down the hard disk but there are few issues with it.
when it wakes back up it consumes lots power. Is there any other way to do it? Many times when I put my hard disk to sleep, I can see few bursts at the beginning and then after a while it goes to sleep. I think its because of the journaling system in ubuntu (which I use) Have anybody encountered that? What would be the best linux/unix operating system (eg: ubuntu/centos/redhat) to work on extensive hard disk operations?
When it first happened, I didnt know what to do so i accessed all my data, backed it up in a diff partition, reformated my drives and reinstalled a clean 9.10. But now, every now and then (i think its when i use frostwire and have other programs running) my ubuntu keeps freezing up, it becomes non-responsive to anything i do, so i have to do a hard shutdown, after which, when i reboot, it is not able to mount /home, so i run FSCK and it fixes it, but ive done this about 3 times now, its starting to get a bit annoying, i dont know if anyone else has this problem, or if its a known bug. Here are my specs:
Running: Ubuntu Karmic 9.10 64 bit 3 Sata HDD: 1 TB, 750 GB, 350 GB 4GB Ram 2 Nvidia 7900GS with a Pentium core 2 duo @ 3.0GHz
I've been running Debian Squeeze for the past couple of months. I decided to use a ReiserFS (not sure if it's relevant) and had a few problems where I had to hold the power button to shut down the computer. After that the system was not the same and froze from time to time (long periods of freezing) forcing me to hold the power button to shut down the computer, again.
Now, after /dev, /sbin...etc... not being found root not exiting, I have decided to do a new install, however, after several attempts at setting up new partition tables, deleting data on the HD and re-installing, I have failed. Maybe someone can give me some input... here are is my /var/log/syslog from when I ran the Debian install disk: pastebin - syslog - post number 1941832 (I think the end is most relevant).
In the mean time I am going to delete data on the current partitions (if I can) and try to re-install.
I have two internal harddisk. Harddisk 1 has ubuntu, fedora installed and harddisk 2 has ubuntu installed. I normally connect either one, and use it. How can i always keep connect both harddisks, and at the start, select from which harddisk to boot? Or it's not possible?
The Install program is failing to see the hard disk!
Now heres the really weird bit. The live cd can see the drive just fine.
I have created partitions using gparted and the disktool also sees the drive just fine but as soon as I go back to the installer it shows no hard disk!
It's a SATA drive which I suspect might be a part of the problem.
Is there a way I can install without the install program?
Is there a way to make the install program see the drive?
So when I booted my system up today my second internal hard drive which is formatted to ext4 failed to auto-mount for me(I have an fstab entry for it). When I I tried to manually mount it from terminal it failed and suggested I run dmesg | tail and here is the output from said command:
I have an Intel MB (855GME with 6300ESB) that I'm having trouble installing Ubuntu 9.0.4 on. It will install to a SATA drive but for various reasons I need to install on IDE (PATA on 6300ESB). The install fails to find any ide drive (I know the drive/interface works because I can install XP on this same ide drive). If I boot Ubuntu from the DVD (on USB) and open a terminal window and parse the dmesg output I see the message "pata_acpi :xxx device not available because of BAR 2 collisions". I'm trying to determine if there's some workaround for this. I've tried various kernel parameters and no joy.
I recently moved my ubuntu 9.10 server over to a new case with more memory, and when I did the webserver worked like a charm, but now apt-get is broken. Checked my 70-persistent-net.rules and saw the new NIC was there, so I edited my interfaces to use eth1 for the new NIC, but apt is still not working, failing to fetch everything. here is my 70-persistent-net.rules
As I have no blank cds handy right now, I had to go the way descirbed here:URL...But when I seect my partition and / (no sub dirs, an empty ext3 formated 6.8GB partition, exclusivly for that usage) it tells me there ws no installation media found and the search path got automagically adjusted to /imges/image.img.And ideas howto fix that? Or how to install fedora from harddisk (without big fuss)?
So when I booted my system up today my second internal hard drive which is formatted to ext4 failed to auto-mount for me(I have an fstab entry for it). When I I tried to manually mount it from terminal it failed and suggested I run dmesg | tail and here is the output from said command:
I've tried to be clever but as usual I didn't think before acting and missed a small detail.
I have recently installed karmic (dual booting with Vista) on my dell xps laptop. The install went fine, I'm very happy with my new OS.
I bought a new Seagate 500GB portable external HDD. I got a bit over-excited and installed karmic on the external drive. This worked fine and I got a lovely (but slow to appear) Grub2 menu showing my vista and both ubuntu options.
My problem is that now, when I unplug the external drive, Grub fails and I get a grub rescue> prompt. So I need the external drive to be plugged in if I want to boot.
It seems I have done something to the grub configuration. I have read around the subject but I am not confident about how best to proceed.
I understand there is an 'advanced' option in the installer which will allow me to choose where to install grub. Presumably I want it on the internal drive so that I can boot without the external one plugged in.
Am I right in thinking I can just pop in my install disk and redo the installation?
If I indicate I want to install Grub on the internal drive, which partition should I aim for?
Will I get a grub option for booting to the external drive?
Will I be able to plug the external drive into a different machine and boot from it?
I haven't done anything with the fresh install on the external drive so I don't mind losing that.
I'm new to the ubuntu forums as well as ubuntu. I'm excited to learn more about linux itself as well as ubuntu. I got ubuntu 10.04 running on my toshiba L505D laptop by disabling acpi in the boot commands. My first question is how do i do this permanently, is this bad, and would updating fix the issue? If so how would I go about updating.
Secondly, when the external hard drive I installed ubuntu on is not plugged in to the laptop, GRUB rescue comes up. I kind of like this because it provides a level of hardware security. I would however like to know how to load my windows partition encase the external hard drive fails.
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)
I have an Intel MB (855GME with 6300ESB) that I'm having trouble installing OpenSUSE 11.1 onto the IDE drive. It will install to a SATA drive but for various reasons I need to install on IDE (PATA on 6300ESB). The install fails to find any ide drive (I know the drive/interface works because I can install XP on this same ide drive and boot from it). If I parse the dmesg output I see the message "ata_piix 0000:1f.1 device not available because of BAR 2 (0x0-0x7) collisions". I'm trying to determine if there's some workaround for this. I've tried various kernel parameters and no joy.
I've tried Ubuntu with similar results. Older kernels WILL install onto this same MB/PATA controller (Ubuntu 6.06, 2.6.15 and RHEL4) so it seems that something changed in the ATA driver as the kernel has matured and my bios isn't up to snuff for these pickier drivers.
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.
Having trouble installing 'Squeeze' 6.0.1a-amd64-netinst on a new AMD64 system.The installer boots and runs fine until it gets to hard disk detection. Then it hangs for about 20 minutes showing a blue screen, during which time the HDD-activity light flickers every 5 seconds. Eventually it says it can't detect a hard disk, and displays a (longish) list of possible drivers; no idea which, if any, would suit.Anyone else installed (successfully or otherwise) on this combo?
I have a Onetouch 4 mini 160GB I bought a year ago. I t used to work fine but all of a sudden it started to become a problem device. My home pc has two operating systems on it: Windows 7 and ubuntu 10.04 lucid. the drive often fails to load on both systems. Sometimes it's recognized, but the reads are very slow and opening a folder on the drive takes around 120 seconds. Itried reformatting the whole drive, chicking it with chkdsk but it didn't help. Now I have around 70 GB of data on the drive. On my office pc I don't have such a problem and the drive works fine.
My home pc has an Asus P5B motherboard and intel core 2 duo cpu. I tried unplugging other usb devices, plugging in the extra power cord (data + data/power) and it didn't help. The drive also makes beeping sounds when I try to browes the files on it. I'm sure thid is not OS related as both Windows and Linux have the same issue. This is the output of dmesg | tail command on linux. You can see the os keeeps "resetting" the drive:
I just recently installed ubuntu 10.04 and it works great! I got it to work with both of my printers, scanner, and zune! The problem is occasionally when I boot up ubuntu it stops and displays "[drm:rs400_gart_adjust_size] *ERROR* Forcing to 32M GART size (because of ASIC bug ?)"
