Nieuws:

Welkom, Gast. Alsjeblieft inloggen of registreren.
Heb je de activerings-mail niet ontvangen?

Auteur Topic: [OPGELOST] Ubuntu Karmic opstartprobleem (mounts, swap, cannot display)  (gelezen 1574 keer)

Offline barilie

  • Lid
  • Steunpunt: Nee
Ubuntu 9.10 (installatie november 2009)
dual boot (Windows XP)
2 harde schijven
Pentium 4 werkgeheugen 1 Gb

Ik installeerde niets nieuws maar sinds twee dagen krijg ik bij het opstartscherm (Ubuntu studio) volgende boodschap:

One ore more of the mounts listed in /etc/fstab cannot yet be mounted:
/media/HHD: waiting for UUID= 26C8183AC8180AA7
/home: waiting for UUID=bbcaab0c-f1ca-446c-ae30-57556405246e
Press esc to enter a recovery shell

Als ik dan enter, krijg ik het volgende:

General error mounting filesystems
A maintenance shell will now be started
CONTROL-D will terminate this shell and re-try
root@lieven-desktop:~#

Naar mijn mening gebeurt er dan niets...
CONTROL-D geeft het volgende resultaat:

mountall start/starting
swapon: /dev/disk/by- uuid/3410dde9-be53-414e-ae02-7c1cbe097022: swapon failed: Device or resource busy
mountall: swapon: /dev/disk/by- uuid/3410dde9-be53-414e-ae02-7c1cbe097022 [902] terminated with status 255
mountall: Problem activating swap: /dev/disk/by- uuid/3410dde9-be53-414e-ae02-7c1cbe097022
init: ureadahead -other main process (904) terminated with status 4
One ore more of the mounts listed in /etc/fstab cannot yet be mounted: (ESC for recovery shell)
/media/HHD: waiting for UUID= 26C8183AC8180AA7
/home: waiting for UUID=bbcaab0c-f1ca-446c-ae30-57556405246e
mountall cancelled

Wat ik al heb geprobeerd:

gksudo gedit /etc/fstab
resultaat:
(gksudo:939): GTK-warning xx: cannot open display
Kan iemand hulp bieden?

« Laatst bewerkt op: 2010/03/11, 09:41:51 door barilie »

Offline Lexaldo

  • Lid
  • Steunpunt: Nee
Re: Ubuntu Karmic opstartprobleem (mounts, swap, cannot display)
« Reactie #1 Gepost op: 2010/03/08, 11:37:57 »
Alhoewel ik het niet zo 1-2-3 kan oplossen weet ik wel dat het volgende belangrijk is:

cat /etc/fstab

sudo blkid

sudo fdisk -l


Gaarne de uitkomst van deze drie opdrachten hier plaatsen.
« Laatst bewerkt op: 2010/03/08, 11:41:07 door Lexaldo »

Offline barilie

  • Lid
  • Steunpunt: Nee
Re: Ubuntu Karmic opstartprobleem (mounts, swap, cannot display)
« Reactie #2 Gepost op: 2010/03/09, 12:18:20 »
Lexaldom dit is het resultaat:

ubuntu@ubuntu:~$ cat /etc/fstab
aufs / aufs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
/dev/sdb2 swap swap defaults 0 0
ubuntu@ubuntu:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: UUID="CE74611774610395" TYPE="ntfs"
/dev/sda5: LABEL="" UUID="48E6-0C33" TYPE="vfat"
/dev/sdb1: UUID="4dd7ef23-04b0-47de-85d0-521715af2f7c" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: UUID="3410dde9-be53-414e-ae02-7c1cbe097022" TYPE="swap"
/dev/sdb4: LABEL="" UUID="48E6-0535" TYPE="vfat"
ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe02ae02a

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        5099    40957686    7  HPFS/NTFS
/dev/sda2            5100       14592    76252522+   f  W95 Ext'd (LBA)
/dev/sda5            5100       14592    76252491    c  W95 FAT32 (LBA)

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000616e9

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        3647    29294496   83  Linux
/dev/sdb2            3648        3890     1951897+  82  Linux swap / Solaris
/dev/sdb3            3891       13616    78124095   83  Linux
/dev/sdb4           13617       30401   134825512+   b  W95 FAT32
« Laatst bewerkt op: 2010/03/09, 15:38:22 door barilie »

Offline barilie

  • Lid
  • Steunpunt: Nee
Re: Ubuntu Karmic opstartprobleem (mounts, swap, cannot display)
« Reactie #3 Gepost op: 2010/03/09, 13:39:35 »
Ik zag net dat de inhoud van fstab niet klopte (ivm live cd...)

In volgend rapport staat ook fstab (dit resultaat verkreeg ik door het uitvoeren van volgend script: http://sourceforge.net/projects/bootinfoscript/ )

Ik trachtte ook al enkele lijnen aan te passen maar kon dat ondanks gksudo nautilus niet realiseren. De aanpassing bleek wel opgeslagen maar bij de reboot was er niets opgeslagen. Dat is het gevolg van te werken via de live cd vermoed ik, maar hoe kan het dan wel?


             Boot Info Script 0.55    dated February 15th, 2010                    

============================= Boot Info Summary: ==============================

 => Grub 0.97 is installed in the MBR of /dev/sda and looks on boot drive #2
    in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst.
 => No boot loader is installed in the MBR of /dev/sdb

sda1: _________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows XP
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  Windows XP
    Boot files/dirs:   /boot.ini /ntldr /NTDETECT.COM

sda2: _________________________________________________________________________

    File system:       Extended Partition
    Boot sector type:  -
    Boot sector info:  

sda5: _________________________________________________________________________

    File system:       vfat
    Boot sector type:  Fat32
    Boot sector info:  According to the info in the boot sector, sda5 starts
                       at sector 0. But according to the info from fdisk,
                       sda5 starts at sector 81915498.
    Operating System:  
    Boot files/dirs:  

sdb1: _________________________________________________________________________

    File system:       ext3
    Boot sector type:  -
    Boot sector info:  
    Operating System:  Ubuntu 9.10
    Boot files/dirs:   /boot/grub/menu.lst /etc/fstab

sdb2: _________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info:  

sdb3: _________________________________________________________________________

    File system:      
    Boot sector type:  -
    Boot sector info:  
    Mounting failed:
mount: unknown filesystem type ''

sdb4: _________________________________________________________________________

    File system:       vfat
    Boot sector type:  Fat32
    Boot sector info:  According to the info in the boot sector, sdb4 starts
                       at sector 0. But according to the info from fdisk,
                       sdb4 starts at sector 218741040.
    Operating System:  
    Boot files/dirs:  

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ _____________________________________________________

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0xe02ae02a

Partition  Boot         Start           End          Size  Id System

/dev/sda1    *             63    81,915,434    81,915,372   7 HPFS/NTFS
/dev/sda2          81,915,435   234,420,479   152,505,045   f W95 Ext d (LBA)
/dev/sda5          81,915,498   234,420,479   152,504,982   c W95 FAT32 (LBA)


Drive: sdb ___________________ _____________________________________________________

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x000616e9

Partition  Boot         Start           End          Size  Id System

/dev/sdb1                  63    58,589,054    58,588,992  83 Linux
/dev/sdb2          58,589,055    62,492,849     3,903,795  82 Linux swap / Solaris
/dev/sdb3          62,492,850   218,741,039   156,248,190  83 Linux
/dev/sdb4         218,741,040   488,392,064   269,651,025   b W95 FAT32


blkid -c /dev/null: ____________________________________________________________

Device           UUID                                   TYPE       LABEL                        

/dev/loop0                                              squashfs                                
/dev/sda1        CE74611774610395                       ntfs                                    
/dev/sda5        48E6-0C33                              vfat                                    
/dev/sdb1        4dd7ef23-04b0-47de-85d0-521715af2f7c   ext3                                    
/dev/sdb2        3410dde9-be53-414e-ae02-7c1cbe097022   swap                                    
/dev/sdb3: ambivalent result (probably more filesystems on the device)
/dev/sdb4        48E6-0535                              vfat                                    

============================ "mount | grep ^/dev  output: ===========================

Device           Mount_Point              Type       Options

aufs             /                        aufs       (rw)
/dev/sr0         /cdrom                   iso9660    (rw)
/dev/loop0       /rofs                    squashfs   (rw)
/dev/sdb1        /media/4dd7ef23-04b0-47de-85d0-521715af2f7c ext3       (rw,nosuid,nodev,uhelper=devkit)


================================ sda1/boot.ini: ================================

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect


=========================== sdb1/boot/grub/menu.lst: ===========================

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd1,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
##      lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
##      indomU=true
##      indomU=false
# indomU=detect

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Ubuntu 9.10, kernel 2.6.31-19-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-19-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.31-19-generic
quiet

title Ubuntu 9.10, kernel 2.6.31-19-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-19-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.31-19-generic

title Ubuntu 9.10, kernel 2.6.31-17-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-17-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.31-17-generic
quiet

title Ubuntu 9.10, kernel 2.6.31-17-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-17-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.31-17-generic

title Ubuntu 9.10, kernel 2.6.31-16-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-16-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.31-16-generic
quiet

title Ubuntu 9.10, kernel 2.6.31-16-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-16-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.31-16-generic

title Ubuntu 9.10, kernel 2.6.31-15-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-15-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.31-15-generic
quiet

title Ubuntu 9.10, kernel 2.6.31-15-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-15-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.31-15-generic

title Ubuntu 9.10, kernel 2.6.31-14-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-14-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
quiet

title Ubuntu 9.10, kernel 2.6.31-14-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-14-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.31-14-generic

title Ubuntu 9.10, kernel 2.6.31-9-rt
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-9-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.31-9-rt
quiet

title Ubuntu 9.10, kernel 2.6.31-9-rt (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.31-9-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.31-9-rt

title Ubuntu 9.10, kernel 2.6.28-16-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.28-16-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.28-16-generic
quiet

title Ubuntu 9.10, kernel 2.6.28-16-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.28-16-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.28-16-generic

title Ubuntu 9.10, kernel 2.6.27-14-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.27-14-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.27-14-generic
quiet

title Ubuntu 9.10, kernel 2.6.27-14-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.27-14-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.27-14-generic

title Ubuntu 9.10, kernel 2.6.27-3-rt
root (hd1,0)
kernel /boot/vmlinuz-2.6.27-3-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.27-3-rt
quiet

title Ubuntu 9.10, kernel 2.6.27-3-rt (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.27-3-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.27-3-rt

title Ubuntu 9.10, kernel 2.6.24-24-rt
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-24-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.24-24-rt
quiet

title Ubuntu 9.10, kernel 2.6.24-24-rt (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-24-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.24-24-rt

title Ubuntu 9.10, kernel 2.6.24-24-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-24-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.24-24-generic
quiet

title Ubuntu 9.10, kernel 2.6.24-24-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-24-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.24-24-generic

title Ubuntu 9.10, kernel 2.6.24-23-rt
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-23-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.24-23-rt
quiet

title Ubuntu 9.10, kernel 2.6.24-23-rt (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-23-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.24-23-rt

title Ubuntu 9.10, kernel 2.6.24-23-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-23-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.24-23-generic
quiet

title Ubuntu 9.10, kernel 2.6.24-23-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-23-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.24-23-generic

title Ubuntu 9.10, kernel 2.6.24-22-rt
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-22-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.24-22-rt
quiet

title Ubuntu 9.10, kernel 2.6.24-22-rt (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-22-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.24-22-rt

title Ubuntu 9.10, kernel 2.6.24-22-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-22-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.24-22-generic
quiet

title Ubuntu 9.10, kernel 2.6.24-22-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-22-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.24-22-generic

title Ubuntu 9.10, kernel 2.6.24-21-rt
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-21-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.24-21-rt
quiet

title Ubuntu 9.10, kernel 2.6.24-21-rt (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-21-rt root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.24-21-rt

title Ubuntu 9.10, kernel 2.6.24-21-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-21-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.24-21-generic
quiet

title Ubuntu 9.10, kernel 2.6.24-21-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-21-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.24-21-generic

title Ubuntu 9.10, kernel 2.6.24-19-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro quiet splash
initrd /boot/initrd.img-2.6.24-19-generic
quiet

title Ubuntu 9.10, kernel 2.6.24-19-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c ro  single
initrd /boot/initrd.img-2.6.24-19-generic

title Ubuntu 9.10, memtest86+
root (hd1,0)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Microsoft Windows XP Home Edition
root (hd0,0)
savedefault
makeactive
chainloader +1


=============================== sdb1/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# /dev/sda1
UUID=26C8183AC8180AA7         /media/HDD     ntfs-3g    force          0       0
# /dev/sdb1
UUID=4dd7ef23-04b0-47de-85d0-521715af2f7c /               ext3    relatime,errors=remount-ro 0       1
# /dev/sdb3
UUID=bbcaab0c-f1ca-446c-ae30-57556405246e /home           ext3    relatime        0       2
/dev/sdb4       /media/data     vfat    utf8,umask=007,gid=46 0       1
# /dev/sdb2
UUID=3410dde9-be53-414e-ae02-7c1cbe097022 none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0

/dev/sdc2 /media/iPod vfat nosuid,noauto,nodev,rw,umask=077,gid=1000,uid=1000,user,defaults,noatime,iocharset=utf8 0 0
« Laatst bewerkt op: 2010/03/09, 15:31:15 door barilie »

Offline barilie

  • Lid
  • Steunpunt: Nee
Re: Ubuntu Karmic opstartprobleem (mounts, swap, cannot display)
« Reactie #4 Gepost op: 2010/03/09, 15:16:06 »
de rest van het rapport:

=================== sdb1: Location of files loaded by Grub: ===================


  27.6GB: boot/grub/menu.lst
  27.3GB: boot/grub/stage2
  27.3GB: boot/initrd.img-2.6.24-19-generic
  27.3GB: boot/initrd.img-2.6.24-19-generic.bak
  27.2GB: boot/initrd.img-2.6.24-21-generic
  27.4GB: boot/initrd.img-2.6.24-21-generic.bak
  27.2GB: boot/initrd.img-2.6.24-21-rt
  27.2GB: boot/initrd.img-2.6.24-21-rt.bak
  27.4GB: boot/initrd.img-2.6.24-22-generic
  27.4GB: boot/initrd.img-2.6.24-22-generic.bak
  27.4GB: boot/initrd.img-2.6.24-22-rt
  27.4GB: boot/initrd.img-2.6.24-22-rt.bak
  27.5GB: boot/initrd.img-2.6.24-23-generic
  27.4GB: boot/initrd.img-2.6.24-23-generic.bak
  27.2GB: boot/initrd.img-2.6.24-23-rt
  27.5GB: boot/initrd.img-2.6.24-23-rt.bak
  27.5GB: boot/initrd.img-2.6.24-24-generic
  27.5GB: boot/initrd.img-2.6.24-24-generic.bak
  27.5GB: boot/initrd.img-2.6.24-24-rt
  27.5GB: boot/initrd.img-2.6.24-24-rt.bak
  27.4GB: boot/initrd.img-2.6.27-14-generic
  27.5GB: boot/initrd.img-2.6.27-3-rt
  27.3GB: boot/initrd.img-2.6.28-16-generic
  27.6GB: boot/initrd.img-2.6.31-14-generic
  27.3GB: boot/initrd.img-2.6.31-15-generic
  27.5GB: boot/initrd.img-2.6.31-16-generic
  27.6GB: boot/initrd.img-2.6.31-17-generic
  27.6GB: boot/initrd.img-2.6.31-19-generic
  27.6GB: boot/initrd.img-2.6.31-9-rt
  27.3GB: boot/vmlinuz-2.6.24-19-generic
  27.4GB: boot/vmlinuz-2.6.24-21-generic
  27.4GB: boot/vmlinuz-2.6.24-21-rt
  27.4GB: boot/vmlinuz-2.6.24-22-generic
  27.4GB: boot/vmlinuz-2.6.24-22-rt
  27.4GB: boot/vmlinuz-2.6.24-23-generic
  27.4GB: boot/vmlinuz-2.6.24-23-rt
  27.2GB: boot/vmlinuz-2.6.24-24-generic
  27.2GB: boot/vmlinuz-2.6.24-24-rt
  27.4GB: boot/vmlinuz-2.6.27-14-generic
  27.5GB: boot/vmlinuz-2.6.27-3-rt
  27.3GB: boot/vmlinuz-2.6.28-16-generic
  27.4GB: boot/vmlinuz-2.6.31-14-generic
  27.3GB: boot/vmlinuz-2.6.31-15-generic
  27.3GB: boot/vmlinuz-2.6.31-16-generic
  27.6GB: boot/vmlinuz-2.6.31-17-generic
  27.3GB: boot/vmlinuz-2.6.31-19-generic
  27.6GB: boot/vmlinuz-2.6.31-9-rt
  27.6GB: initrd.img
  27.6GB: initrd.img.old
  27.3GB: vmlinuz
  27.6GB: vmlinuz.old
« Laatst bewerkt op: 2010/03/09, 15:31:54 door barilie »

Offline Lexaldo

  • Lid
  • Steunpunt: Nee
Re: Ubuntu Karmic opstartprobleem (mounts, swap, cannot display)
« Reactie #5 Gepost op: 2010/03/09, 15:22:08 »
Met deze info moeten de de deskundigen wel uit de voeten kunnen.

Ik zou die info als code# posten; misschien kun je dat nog aanpassen.
Dat gaat zo: die grote lappen gegevens markeren en dan klikken op (staat bovenin het opmaakschermpje naast ).

Offline barilie

  • Lid
  • Steunpunt: Nee
Re: Ubuntu Karmic opstartprobleem (mounts, swap, cannot display)
« Reactie #6 Gepost op: 2010/03/09, 15:35:59 »
merci voor de tip....ik dacht al dat er iets niet klopte... :rolleyes:

en jij kan me niet helpen? ook niet hoe je moet opslaan als je met de live cd werkt?

Offline barilie

  • Lid
  • Steunpunt: Nee
Re: Ubuntu Karmic opstartprobleem (mounts, swap, cannot display)
« Reactie #7 Gepost op: 2010/03/09, 17:08:07 »
ik kon de gewijzigde fstab opslaan en alles werkt als voorheen.  :)

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# /dev/sda1
/dev/sda1         /media/HDD     ntfs-3g    force          0       0
# /dev/sdb1
/dev/sdb1 /               ext3    relatime,errors=remount-ro 0       1
# /dev/sdb3
/dev/sdb3 /home           ext3    relatime        0       2
/dev/sdb4       /media/data     vfat    utf8,umask=007,gid=46 0       1
# /dev/sdb2
/dev/sdb2 none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0

/dev/sdc2 /media/iPod vfat nosuid,noauto,nodev,rw,umask=077,gid=1000,uid=1000,user,defaults,noatime,iocharset=utf8 0 0

ik heb in een ander topic wel gelezen dat het weglaten van UUID's niet zo'n goed idee is.
Enig advies?