[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: Strange module load behaviour

Buenas tardes, Carlos

A la hora de montar parciciones existe la opción de marcarlas con una etiqueta. Deberías mirar el comando 'e2label', pues creo que en fstab se puede indicar la partición según esta etiqueta en vez de /dev/sdb o /dev/sda

Un saludo.

Good Evening, Carlos

You can see 'e2label' command yo assign a label to your disk and mark this way, i think, in fstab.

Thanks and sorry for my English.

-----Mensaje original-----
De: Carlos Acedo [mailto:carlos@pangea.org] 
Enviado el: miércoles, 11 de abril de 2007 13:59
Para: debian-isp@lists.debian.org
Asunto: Strange module load behaviour

Hash: SHA1


I have installed Debian sarge (from a custom made CD with kernel 2.6.18) in a Sun Fire X4100 M2 server with a hardware RAID1.

When Debian boots, the disc name is either sda or sdb (in the installation is all ways sdb though), this obviously makes Debian unbootable when the fstab doesn't match the disc device name.

It seems that is related to the module load order, when it loads usb_storage before the disc module, the disc is sdb, but the other way around is sda. Adding usb_storage to blacklist partially solves the problem, it seems like in single user mode blacklist is not red

Any hint on this? can I decide de module load order?

Thank you.

Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: