sidux.com :: View topic - /etc/fstab problem after installing kernel 2.6.19-slh-up-1

sidux.com

Installation - /etc/fstab problem after installing kernel 2.6.19-slh-up-1

holzi - Jan 22, 2007 - 04:13 PM
Post subject: /etc/fstab problem after installing kernel 2.6.19-slh-up-1

Hallo!

I just installed the 2.6.19-slh-up-1 kernel and now I cannot use my swap anymore.

I guess it's related with my fstab, which looks like this:

[code]
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs devmode=0666 0 0
UUID=587f59c3-40c7-4c51-89c2-7955d92ce822 / reiserfs defaults 0 1
/dev/disk/by-uuid/3171-1DEA /media/hda1 vfat umask=000,shortname=mixed,quiet 0 0
UUID=69dbb2d8-c7b7-4cd2-88ca-65dbe0ba23a1 none swap sw 0 0
/dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0

none /sys sysfs [code]defaults 0 0
[/code]

before the kernel update it was like that:
[code]
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs devmode=0666 0 0
/dev/hda2 / reiserfs defaults 0 1
/dev/hda1 /media/hda1 vfat umask=000,shortname=mixed,quiet 0 0
/dev/hda3 none swap sw 0 0
/dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0

none /sys sysfs defaults 0 0
[/code]

Has anyone an idea what I have to change so that I can use my swap again ?

Many thanks,
LG
Georg

drb - Jan 22, 2007 - 04:40 PM
Post subject:

the 'before kernel update' is correct. I've no idea why there has been a change in partition identity though.

drb

Saltek - Jan 22, 2007 - 04:53 PM
Post subject: Re: /etc/fstab problem after installing kernel 2.6.19-slh-up

holzi wrote:

Just do an fdisk -l to see what /dev/? your swap partition is now called, and then put that entry into fstab. Alternatively, give your swap partition a label:

Quote:

mkswap -L <label> /dev/XXX

You can then add this to fstab, which will ensure a persistent entry even if the device node changes. See this link for a full description:

http://wiki.archlinux.org/index.php/Per ... ice_naming

slh - Jan 22, 2007 - 05:00 PM
Post subject:

The fstab looks fine, assuming your swap is really /dev/hda3 you can also use:

Code:

swapoff -a

mkswap /dev/hda3

swapon /dev/hda3

/lib/udev/vol_id -u /dev/hda3

afterwards you have to update the UUID= settings for swap with the new UUID.

devil - Jan 22, 2007 - 05:01 PM
Post subject: Re: /etc/fstab problem after installing kernel 2.6.19-slh-up

saltek,

Quote:

You can then add this to fstab, which will ensure a persistent entry even if the device node changes. See this link for a full description:

exactly that is, what uuid is for: Universally Unique Identifier

Code:

http://de.wikipedia.org/wiki/UUID

greetz
devil

Saltek - Jan 22, 2007 - 05:08 PM
Post subject: Re: /etc/fstab problem after installing kernel 2.6.19-slh-up

devil wrote:

saltek,

Quote:

You can then add this to fstab, which will ensure a persistent entry even if the device node changes. See this link for a full description:

exactly that is, what uuid is for: Universally Unique Identifier

Code:

http://de.wikipedia.org/wiki/UUID

greetz
devil

Hi devil, yep, UUID or label, as I understand the situation it doesn't much matter which you use Smile

Cheers
Saltek

holzi - Jan 22, 2007 - 05:42 PM
Post subject:

Thanks for all the explanations - now I understand the sense of UUID ...

The problem in my case was, that the swap is now /dev/sda3 instead of /dev/hda3.

(Everything changed to sda* instead of hda* ... strange)

Thanks,
LG
Georg

kstevek - Jan 22, 2007 - 05:44 PM
Post subject: RE: Re: /etc/fstab problem after installing kernel 2.6.19-sl

Is this something thats going to be introduced soon ie. in the iso when its out? should we alter our fstab beforehand or will kernel upgrade or upgrade install with iso take care of it? or am I just being silly/paranoid/overly cautious Smile

UUIDs sound like a good idea though, to keep everything in order through changes in future.

cheers kstevek

slh - Jan 22, 2007 - 06:13 PM
Post subject: RE: Re: /etc/fstab problem after installing kernel 2.6.19-sl

The install-kernel-sidux.sh script should take care of that (and it has for the mentioned fstab, why it fails to mount swap is another question I can't answer without more debugging), the ISO installer as well. Mounting by UUID is required now, because partitions can change between /dev/hdX and /dev/sdY with each upgrade now, depending on which libata/ PATA driver becomes stable and supercedes the classic IDE drivers. Right now this already happenend for Intel PIIX (ICH8+ is very slow with classic IDE support and libata seems to be stable, at least following my tests with ICH4m) and jmicron (IDE drivers seem to be rather immature, no complaints about libata/ PATA yet) controllers - on the other hand nvidia, via and promise pdc20265 libata drivers don't seem to be ready for prime time yet (only nvidia works at all, but is still very crashy).

drb - Jan 22, 2007 - 06:26 PM
Post subject:

I upgraded to 2.6.19-slh-up-1 a few weeks ago. Why has my fstab continued with the normal identifiers instead of UUID format?

drb