Andrey Borzenkov wrote:
- mount by LABEL/UUID/whatever, but not by /dev/sdX. Uncountable times I got support call after adding some additional storage after installation and staying before system that does not boot.
For "truth in advertising"... I do use device id's in one place -- lilo.conf. It didn't parse names there when I wrote it 5 years ago, dunno about now. however, if your addition of disks has changed the "sd" ordering, it won't boot from the correct disk and your initrd won't be loaded either. Of major note -- I had a suse install install it's boot kernel and init rd on a different partition than boot (this was some time ago, it may read the info from the BIOS now), but the result was that it updated an unused partition to boot from, and updated the boot sector on a disk that the machine didn't boot from. The result was it booted from my old kernel (which was newer than the one the distro was installing) from a different disk -- and then proceeded to mount the updated root. I.e. my 'boot' partition is separate from root. Nothing is on the boot partition except the kernel images (this is true when it used the suse initrd boot as well, as both lilo and grub support separate boot and root partitions. My boot system continued to work, as it was configured knowing the bios configuration, the suse method, at that time, didn't. and updated an unused parition for boot (thought it correctly updated my root partition). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org