[Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
Thanks for the report, since you're reinstalling the system, I'm going to mark this bug as Invalid since we won't be able to debug your previous system further. If you have problems after the reinstall, please do file a new bug ** Changed in: mountall (Ubuntu) Status: New = Invalid -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
definitely not the same as bug #439604; unduping. ** This bug is no longer a duplicate of bug 439604 boot process isn't paused while fsck runs on partition: boot process is completed with fsck running in the background preventing partition from mounting -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
My fstab looks like this(even though I changed it the last time): aufs / aufs rw 0 0 Is this the fstab on your hard drive, or the /etc/fstab as seen from a live CD when booting for recovery? I can't think of any reason you would have this fstab on an installed system. The /dev/disk/by-uuid/ output shows that both the uuids from the original error message is available, so it's not clear why mountall says it's still waiting for them. -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
I see. Should have known the fstab was from the usb startup disk. As I said, I am no GNU/Linux expert :). Anyway, I am going to reinstall my system now. Untill now I waited to see if a possible sollution came up. Thanks for the help -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
*** This bug is a duplicate of bug 439604 *** https://bugs.launchpad.net/bugs/439604 @Narchya, 1. copying myfstab letter for letter probably isn't going to work unless your disk is partitioned exactly as mine. Instead you need to get the earlier fstab and wherever it had some UUID= thing, stick in the disk instead you can work this out from -if the system boots- a call to : ls -l /dev/disk/by-uuid/ this lists the mapping from uuid to /dev entry 2. having lots of block errors is bad news, sign of disk problems. I would recommend replacing the HDD sooner rather than later, so you can get all the stuff you value off it. 3. When ubuntu 9.10 installs as an upgrade, I don't think it replaces the existing bootloader. Those listed kernels may be stuff left in the /boot/grub/menu.list file -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
*** This bug is a duplicate of bug 439604 *** https://bugs.launchpad.net/bugs/439604 On Sat, 2009-11-14 at 02:14 +, Narchya wrote: While I was logged in I did get a warning that my hard drive has many bad sectors. Could that influence the matter? If I were you I would back up any data you would like to keep on that hard drive as soon as possible. You could try getting the SMART-info of the HDD, to get an idea of how long it has to live. You can do so by installing the package 'smartmontools' and running the following command: sudo smartctl --health device-name Where device-name refers to the device name of the HDD in question (/dev/sda or /dev/sdb, for example). I once, by pure coincidence, did a SMART health status check on a HDD and was told it would probably stop functioning within 24 hours. So I backed up all the data on it, and sure enough, when I tried accessing it the day after it was completely dead. I just thought you would appreciate knowing this if you have any valuable data on that hard drive :). -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
*** This bug is a duplicate of bug 439604 *** https://bugs.launchpad.net/bugs/439604 @Steve ls -l /dev/disk/by-uuid/ gives the following feedback: total 0 lrwxrwxrwx 1 root root 10 2009-11-14 12:35 1DA0-42C2 - ../../sdb1 lrwxrwxrwx 1 root root 10 2009-11-14 12:35 33093bc1-3021-40ec-a231-d156b4224ef9 - ../../sda1 lrwxrwxrwx 1 root root 10 2009-11-14 12:35 46a4feb3-1702-4dbf-b077-6fdf5482f894 - ../../sda5 lrwxrwxrwx 1 root root 11 2009-11-14 12:35 a80ddaae-cd02-4f73-a7dc-bc58a41f6760 - ../../loop1 My fstab looks like this(even though I changed it the last time): aufs / aufs rw 0 0 tmpfs /tmp tmpfs nosuid,nodev 0 0 /dev/sda5 swap swap defaults 0 0 What exactly should I change? @Rune There isn't much data I need to recover. I am really only doing this out of curiosity and to try and work out this problem, not because I need to recover a lot of important stuff. The drive will be replaced soon. I want to look in to using a standard hard drive coupled with usb to use for the system, instead of opening up the notebook. Thanks for the advice on the tool you explained, I will try it out. -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
*** This bug is a duplicate of bug 439604 *** https://bugs.launchpad.net/bugs/439604 Narchya, thank you for taking the time to report this bug. This is a known issue in Karmic due to the new approach to startup: http://www.ubuntu.com/getubuntu/releasenotes/910#Login%20screen%20presented%20before%20optional%20filesystems%20are%20mounted If you edit your fstab file so that it has the bootwait option (although I am not quite to sure how well that would work for '/'...), this should stop the error message. Let me know if you have trouble editing your fstab file. ** This bug has been marked a duplicate of bug 439604 boot process isn't paused while fsck runs on partition: boot process is completed with fsck running in the background preventing partition from mounting -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
*** This bug is a duplicate of bug 439604 *** https://bugs.launchpad.net/bugs/439604 Well, the problem is I can't get it to boot at all. Is there any way to edit the file from the recovery shell or to do an alternative bootsequence so I can get in and edit it? Thanks for the reply. -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
*** This bug is a duplicate of bug 439604 *** https://bugs.launchpad.net/bugs/439604 And another question I have. Is this preventable before I update from 9.04 to 9.10? As I am about to do the same with my other PC as well.. -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
*** This bug is a duplicate of bug 439604 *** https://bugs.launchpad.net/bugs/439604 I am not convinced it is a duplicate, as I saw this problem on a separate machine -the OS was not booting when referencing disks by UUID, but only by /dev/sdXX entries: http://www.1060.org/blogxter/entry?publicid=E9A13D9C371E4C17503E0762175B8F7D Narchya, boot from the CD in the try out ubuntu mode, then mount the hard disk in that, you can edit fstab there. The fix was to edit fstab so that instead of asking for things by UUID, going back to asking for them by disk ID. This was the only way to get an older laptop to boot Here is the fstab I ended up with proc /proc proc defaults 0 0 # Entry for /dev/sda1 : /dev/sda1 / ext3 norelatime,noatime,nodiratime,errors=remount-ro 0 1 # Entry for /dev/sda5 : /dev/sda5 /home ext3 norelatime,noatime,nodiratime 0 2 # Entry for /dev/sda6 : /dev/sda6 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 This is not a bootwait problem 1. adding bootwait doesnt help 2. This is / we are talking about here, not any other file system; it is meant to be always mounted instead it is that UUID - device mapping seems not to be working -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 482228] Re: mount at startup problem jaunty upgrade - karmic
*** This bug is a duplicate of bug 439604 *** https://bugs.launchpad.net/bugs/439604 Ok here is what I did. I made a 9.10 USB startup disk. Ran it without installing it. Then I opened the fstab file with the root and changed it to: proc /proc proc defaults 0 0 # Entry for /dev/sda1 : /dev/sda1 / ext3 norelatime,noatime,nodiratime,errors=remount-ro 0 1 # Entry for /dev/sda5 : /dev/sda5 /home ext3 norelatime,noatime,nodiratime 0 2 # Entry for /dev/sda6 : /dev/sda6 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 As in exactly what Steve proposed. Then I rebooted and no juice. While I was logged in I did get a warning that my hard drive has many bad sectors. Could that influence the matter? Also previously before I tried all this, I tried to run a different kernel before the boot, and I could choose from 3 different 9.04 kernels, .11 .15 and .16 if I am not mistaken. Isn't that weird when I just upgraded to 9.10? I think I am just going for a reinstall with 9.04, but I wanted to post this for clarification. Hard disk needs replacing any way. -- mount at startup problem jaunty upgrade - karmic https://bugs.launchpad.net/bugs/482228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
