You should better not expect anything in term on device names (sda, sdb, etc). They are given in the order the modules are loaded and the disks appear and they might change if you connect an external hdd or even randomly. It’s OK as long as you don’t pay attention to them. None of the essential system files (like /etc/fstab or the boot menu) use device names nowadays in modern Linux distributions.
If the disk appears as sdb when you install and as sda when you reboot … don’t worry (it’s not you).
You’ll find many posts on that topic if you search the forum.
On 11/30/2011 03:06 PM, stdufour wrote:
> I am trying to install Opensuse
suggest you declare the exact version of openSUSE you installed…maybe
tell us the name of the .iso you (i guess) downloaded and burned to an
install disk…
and, tell us if you ran into any problems during the install? did you,
for example accept the default partitioning scheme, or did you go the
custom route?
oh, and i checked the specs on that server and see it has several
operating systems listed for use and none of them are openSUSE and so i
wonder why you picked it?
did you intend to pick a system which is certified for the hardware?
–
DD
openSUSE®, the “German Engineered Automobiles” of operating systems!
I’m guessing you have your device names specified with their ‘real’ names and not their UUID’s or something within /etc/fstab and/or in your grub configuration file.
This is a problem across all distros where the device names may change due to the order in which modules are loaded (a major major sore spot with me honestly, as I shouldn’t expect things to change from reboot to reboot). UUIDs and device labels were ‘invented’ to work around this ‘problem’.
Actually, my blind guess was: it has too much memory to handle for a default kernel, so I removed swap partition. It worked…
As said, it’s a PXE boot, I followed those steps SDB:PXE boot installation - openSUSE
Everything comes from Index of /factory/repo/oss and its a 12.2-1.2. I may rerun the install in 12.1…
It’s for a VOIP Call generator in test lab, software provider requiers it to run on OpenSuse, we have no blade available except this one. If it doesn’t work we’ll have to do without it.
On 12/01/2011 10:56 AM, stdufour wrote:
>
> Problem solved
no, the problem is not solved…the problem is that something is wrong
in the two non-pae kernels named?
what you did was avoid the symptom of the problem through the work
around of switching kernels…sure hope one of you two can find time to
visit bugzilla with your experience with this quirky thorn, go: http://tinyurl.com/nzhq7j
logging discovered bugs is a really good way to give back…