Ubuntu Installation :: Random Naming Of Disks At Each Boot After Upgrade To 10.04 / Fix It?
May 4, 2010
After upgrade to 10.04, my disks are randomly named (sda, sdb, sdc) at each boot. My drive labeled "XP" is sometimes named "sdb" and sometimes "sdc", while my other drive "DATA" is respectively "sdc" or "sdb". This wasn't the case before upgrade with KUbuntu 9.10.
Due to this random naming, my auto-mount in fstab often fail at boot time !
Any solution for this (not found here by myself) ?
Is this linked to Grub troubles reported many times here ?
During installation when i set the partitions i have to provide a Name and a Label. What is the difference of these? It looks like only one should be needed. Any problems of using the same name for both?
I have/had a PC with several hard drives, and a mix of ubuntu and windows on multi boot.The old boot drive died screaming, and I need to start again. (But my data is safe! yay!)
Is there anything special about which drive can be the main drive to start booting from? Or to put it another way, can I install to any of the other 3 and expect it to work, or do I need to switch them around so a different drive is on the connections for the recently dead one?
Just upgraded from Karmic to Lucid using auto upgrade on Thinkpad T42. Since doing this, I am experiencing random logging off. Suddenly, I get dumped to the log in screen and need to log back in. A search in the forum suggests this was a problem that some people had with Karmic, but is now fixed (I never experienced it with Karmic)
It seems to be associated with Firefox, with it not happened since switching to Chrome, but switching back to Firefox has just resulted in me being logged off. This could be a coincidence of course. This is rather serious problem as I use the Thinkpad to give presentations
As per the title, really. I've upgraded to 11.04, ran updates, but I can't stop LottaNZB randomly crashing out. It will be running fine one moment, then 'zap' it disappears. I've tried going through the apps running at the same time, and there doesn't appear to be any pattern. In fact, I've left it running with nothing else open and have returned to a computer with no running apps. Sometimes, however, it will run fine for several hours, completing all of it's downloads, although this is pretty rare. LottaNZB's logs appear to wipe after a crash (unless I'm missing something) so I'm none the wiser why it happens. Has anyone got any ideas what to try next? It ran faultlessly on Ubuntu 10.x
I've installed Windows 7 onto one hard drive, and then installed Ubuntu 9.10 onto a second hard drive. The installations seemed to go fine, and I can boot into Ubuntu from the GRUB menu. However when I try to boot into Windows from the GRUB menu, I get a message saying "error: no such device: 446e94786e946488".
I recently tried installing Lucid x86 on my system beside Windows 7 and managed to screw it up.
My disk setup is this;
Disk A = 3 partitions (1st partition=Windows 2&3 partitions=Data) Disk B = 1 partition Disk C = 3 partitions (1st partition=Data 2&3 partitions=Ubuntu & Swap)
Disk A = SATA and internal Disk B = SATA to USB external Disk C = SATA to USB external
I want to install Lucid on the 2nd partition on Disk C. And dual boot it with Windows on Disk A.
During Lucid setup i specified the partition for installation (C2) and asked for GRUB to install on Disk A (no partition specified) so GRUB is always used as the dual-boot manager even if the Lucid disk (Disk C) is ejected. Once installed and rebooted i was taken to the GRUB rescue prompt as no installation drive could be found (a long string of numbers (looked like a Disk ID number???) was also shown). Obvviiusly, i could not access either OS on my system at this point. I had my W7 DVD handy so it was just a case of recovering the windows boot manager and i could use my PC but how do i go about installing Lucid with this setup? Should i specify a partition for GRUB to install to? I have a hunch this is where i am going wrong but am too scared to try again and potentially balls things up.
I have a fully operational PXE boot server, the client boots up and begins the setup process however, fails to detect the hard disk, I have tried with ubuntu 8.10, 9.10 and 10.10 and none of them will see my hard disk, I boot to the cd and it sees the hard disks with no problem, so apparently the pxe boot server isnt serving up the neccesary drivers or something to detect my hard disks properly. They are just IDE drives and like I said, regular cd install detects my drives just fine.So if anyone here has any information that may help shed some light on this issue I would be so grateful
I have no hard drives in my computer, so I have been trying to boot Ubuntu 11.04 from an 8GB usb flash drive. Is this possible? So far the best result i have gotten is it will sit on the loading screen for a while then dump. I was only able to get the last little bit which reads mount. mounting /dev on /root/dev failed: no such file or directory. mounting /sys on /root/sys filed: no such file or directory. mounting /proc on /root/proc failed: no such file or dirctory. target file system doesn't have requested /sbin/init
I am using Ubuntu Lucid Lynx 10.04 (64 bits) in my Asus U30JC laptop (Core i3 M350, intel 4500MHD + nvidia 310M with nvidia Optimus, 4GB RAM). I am content with Lucid and I don't want to upgrade to 10.10 for now. However I read that the new 2.6.36 kernel has some good improvements, such as improving system interactivity while intensive I/O (such as copying large files), and improved energy management for i3/i5 processors (which I hope translates into more battery time, which is a problem of Ubuntu vs Win7 in my laptop).
I discovered I had 2 options: compile the kernel myself, or use the Ubuntu Kernel PPA (maintained by the Ubuntu Kernel Team). I decided to use the PPA, so I added it to my software sources and installed the generic"linux-lts-backport-natty" kernel (2.6.36-1).
Package installation went fine, and after reboot, I could log in to the desktop no problem. Everything seemed fine, but after a few minutes, the system freezes completely: mouse did not move, none of the indicators moved, even Ctrl + Alt + F1 did not work.Where is the log file where there might be a message related to the freeze? Do you think that the kernel developers would try to fix a bug that probably only affects people running the 2.6.36-1 kernel on a distribution that was not built around it?
Dell 600SC running an Adaptec 39160 dual channel SCSI controller which has 2 disks connected to it. The machine also has 2 IDE drives connected to it. The boot order of the disks is set to the SCSI disks as the first in boot order (after CD).
I am trying to set it to maximize performance from the SCSI config so I have XP on the first SCSI and I set up Ub 9.1 on the second SCSI in a dual-boot configuration.
In this set up the machine when rebooting goes straight to XP (on the first SCSI) and does not even see the Ub installation. The installation went fine and no complaints. On the same machine if I just had Ub on the first SCSI - machine boots fine (albeit after a long pause looking for the bootloader).
So with XP on the first disk (which I need to - to have XP) the Ub bootloader does not seem to set the right params to be able to boot.
Again this is with 9.1. Not trying 10.04 as with 10.04 I don't even get to boot even with standalone Ub (with no XP). However it installs fine but does not find bootloader in 10.4, so we will keep to the 9.1 for now. I am however open to working with 10.04 if there is a solution in dual-boot with XP in my config.
So again 9.1 installs fine with XP on 1st SCSI disk, an ub 9.1 on 2nd SCSI disk, but then bootloader does not get activated and machine goes straight to XP.
I have triple boot pc (xp, ubuntu, and fedora), installed in that order. xp and ubuntu seem to be stable. i have had to pull the power cord 3 or 4 times while booted in fedora. i noticed the last 2 times i can still move the mouse around, but can't get it to open anything. the keyboard is locked up, can't alt-f1 or f2 or anything to get console. can't get it to do anything, other than watch the mouse tail move around (weird).
i installed a new power supply (and at least i now have a power switch - the old one never had one), but that didn't fix the lock up problem. i haven't ran yum update since the fc10 live cd gnome install. was planning on doing that later.. not sure how long it will stay up to download all the 300 or so updates. right now the only thing open is a terminal (can't type in it).. what should i look at to fix this lock up problem?
Why is it that about 98 to 99% of the time my computer will boot to Ubuntu/Lucid just fine but on rare / random occasions after seeing the initial BIOS boot screen and initial cursor just after initial BIOS boot screens, the video will just go BLANK, i.e. does not boot to Ubuntu desktop ?
If I then do ALT,CRL,DEL sequence the SPLASH screen is displayed on the monitor and the system then reboots and then goes thru the complete boot process all the way to the desktop just fine.Why this occasional failure to boot completely to the desktop ?
One of my disks in my computer crashed, it was the one containing /boot and some data partitions. The other system and /home partitions were on a second disk, which is ok.
I was wondering, can I create a new /boot partition, and keep on using the rest of the system? Can I somehow do it with a chroot from a live/installer disk, run grub, and use my system again? I have another disk which I can put in the system, but there is even an unused partition on the disk which is ok (but it is rather big for /boot).
I just installed Fedora 12 and grub is not working for me. I have 2 physical drives, and installed Fedora on sdb (win xp is on sda). I picked the option that the computer booted from sdb when I installed. I then went and switched the boot order in the bios so that the computer would boot from sdb. Now Fedora boots fine, but when I try to boot into windows I just get a blinking cursor. I tried booting to windows manually (via picking that drive from the bios options) and that works fine.
I tried to edit grub.conf, but wasn't sure how to address the appropriate hard drive. How do I know what to fill in? The linux drive is (hd0,0), and grub tried to make windows (hd1,0). How do I know what to put in (hdx,y) for the windows partition? Grub tells me I have a /boot partition so everything is relative to that.If I'm way off base, please let me know. Is there a way I can just re-run grub so that it looks for everything anew? I also looked at device.map and sda is hd0.---------- Post added at 02:42 PM CDT ---------- Previous post was at 02:37 PM CDT ----------If it helps, this is my grub.conf:
Having installed 9,10 onto a laptop my cherubic daughter swicthed off the power (no battery) and upon restarting i am faced with "Starting Init crypto disks... OK) and there it stops!! I had hoped that I could go to recovery mode and fix it but am faced with the same stalling point. I see others are unresolved in this.
1st post @ LQ. Ubuntu user since 2007ish. Lots of PC experience... now vexed by upgrade from 9.10 Karmic to 10.04LTS Lucid.
The problem: random freezes whenever I boot into Lucid as user through usual Grub menu. The freeze sequence is: 1- screen stops, 2- mouse pointer freeze w/ no effect on click but moves freely and keyboard is useless, 3- screen blacks out for about 30 seconds and then returns but is unusable and 4- constant HDD activity for about 5-10 seconds. I have waited several minutes for a recovery of some sort but no dice. I reboot via on/off or reset button. Ubu deletes 2 inodes and then I'm off and running again.
If I boot through the recovery console there are no problems at all. The recovery console sequence: 1- select recovery from Grub menu, 2- at recovery menu select drop to root command prompt, 3- give root password, 4- enter 'gdm' at console prompt, finish boot up in my only user desktop (not root.)
I have not been able to find any log files that show an error message, but I'm not so tech oriented that I would necessarily know one if I saw one. Through many hours of browsing posts describing Lucid problems @ UbuntuForums (one of which has over 1,000 responses) I have found my '.xsession-errors' file (attached) is full of data.code...
Disk 0 (500GB): Windows Vista Disk 1 (1TB): Windows 7 Disk 2 (160GB): Ubuntu
My boot disk is Disk 0. Currently when I turn on the PC, GRUB loads from Disk 0. I can then choose either Ubuntu or Windows Loader. If I choose Windows Loader (also located on Disk 0), I can choose to load Windows Vista or Windows 7. I like this setup, but I would like to move the loaders (exactly as they are) to Disk 1 so that I can format Disk 0.
I've a question in regards to RAID, im new to the whole RAID thing. Okay, my question. I have a machine with RAID 1, and I'd like to upgrade the two disks on this machine, BUT in case my backup image does not work, is it possible to power the machine off and re-insert the original disks back in and be rocking and rolling without a prob?
I've just recently upgraded to lenny using aptitude (following the instructions on debian.org. All went smoothly, and almost everything is working fine.I have had my X server crash twice since then, both times when I simply doubleclicked a running application. There is some indication of problems in the Xorg.log file, but it's not helpful to me -- can you help me understand?
Ever since my upgrade from 9.10 to 10.4, every time I reboot the system it does a full disk check. /var/log/boot.log tells me that fsck thinks that the file systems contain errors or that it wasn't cleanly unmounted. And yet, it doesn't seem to actually find errors, and a clean reboot starts another check (again with it thinking something is dirty). I dual-boot with Windows, and reboot from there with the same problem.Again, all of this is new with 10.4 and was not happening with 9.10.Is there a way to find out when/how/why the disks are not being unmounted cleanly?
I seem to be having a problem booting into ubuntu 10.04 (and 9.10 before I upgraded a while back). It's been ongoing for a while now, but I can't seem to actually even get to the login screen. Some kernels just give me a blank screen, and others hang at the ubuntu logo (http://i.cbsi.com.au/story_media/339...ic-koala_1.jpg). It seems to be totally random, and I can't seem to even narrow down which kernels do what. It seems to be a game every time I reboot. Perhaps it has something to do with the beta 2.6.32-rc6 kernel I installed (by clicking on the .deb) a while back? I'm not too sure how to uninstall it, but I first installed it I think back at 9.04, and it always seems to be the first option in grub. Can I clean out my old kernels somehow? Or is that dangerous?
Maybe it's caused by graphics drivers? "Safe mode" doesn't seem to work any better though. And I can't get to the TTY terminals by <ctrl><alt><1-6> either, which would suggest to me that it isn't a graphics issue? I don't see the login screen, nor do I always see the splash screen.
I'm looking for a script that copies a random .jpg from a random folder in my ~/Pictures folder to my ~/temp folder with a standard filename. This file will then be displayed in Conky. I can fix the last part, but I cannot find a way to do the first part.
I get the pinkish Ubuntu screen and a message such as "checking disk 1 of 4". I assume that it is doing an fsck. However, the time it takes does not seem to relate to the time it takes if I do a manual fsck (almost instantaneous) or fsck -c (several minutes to half an hour depending on the drive). I also wonder what is counts as a "disk". I have in the system:
I'm having trouble with Ubuntu 11.04. Every now and then when my laptop boots into the OS (It's a Toshiba Satellite L10) I get a weird desktop layout, that I have never used before (it has happened a few times though).
I was happy with my Jaunty on my Asus X53 with ati radeon hd2600 and restricted driver, until two hours ago. I've started (after a long wait) to upgrade my Jaunty, everything was fine after upgrade, but I've noticed video was running with "ubuntu driver" and 3d wasn't available, so I started to install a fresh release of ati driver. But before I've saw in /usr/share/ati the previous copy of my restricted driver so before install the fresh copy I've run "sh ./fglrx-uninstall.sh" it had remove all telling me there wasn't any istance of fglrx (of course I thought...) ...and so before start with new installation I've thought about a reboot for first, but after it I'm unable to boot...
from normal boot it simply hang after a while, I think when it try to initialize video card. but more worse, also after choice recovery option at grub loader it hang after a bit, without give me any prompt.
I made a mistake while upgrading the GRUB options - when choosing "install the maintainer's version vs. keep the local version"...in the drop down menu, I chose the local version option. On reboot, GRUB works, but I can't boot into 10.04. My old entries (kernels) are still there, but when I choose them, there's an error that says something like "disk not found". However, I am able to boot into Vista.
So do I solve this problem by fixing GRUB? If so, how? I have a Live CD of 9.10, would that be necessary to use it to solve this problem?
refer to [URL], under GRUB.menulst: maintainer's version vs. keep the local version. I read it afterwards (I should've read it before)
After going through the upgrade (alternate cd) I now can't boot into XP, even though it's in the GRUB2 menu. I have fixed up the boot sector as described at this site Attached are my results from the boot info script
SDA1 is XP SDA3 is 10.04
sda3 has this strange error: Quote: Grub 2 is installed in the boot sector of sda3 and looks at sector 66800445 of the same hard drive for core.img, but core.img can not be found at this location.
