SUSE Linux Enterprise Server 11: Archived Driver, Partition and Boot Setup
This is an archived SUSE Linux Enterprise Server 11 workflow; the screenshots identify SLES 11 SP2. They include a VMware virtual machine and different example disk capacities, so they are not proof of successful RAID hardware detection on a physical server. Match the actual service pack, controller driver, boot mode and supported hardware.
1. Present the driver-update media
The source describes a driver ISO or supported floppy/virtual-floppy/USB/optical medium, sometimes prepared using UltraISO. The required media format depends on the actual driver update; do not treat every ISO as a floppy image. Use a matching vendor-provided package and verify its instructions.
At the installation boot screen, highlight Installation, press F6 and choose Yes for a driver update, then press Enter. The two source captures show the F6 menu and the resulting Yes setting:
Select the verified driver medium, confirm with OK and, after the required driver has been read, use Back to continue. The illustrated fd0/sr0/sda names belong to a virtual-machine example; their presence alone does not establish a compatible RAID driver loaded:
2. Language, installation mode, time and scenario
Select the installation language and keyboard layout and review the license. The source welcome capture has English(US) selected and the license-agreement checkbox still unchecked:
For the source’s fresh-install branch, choose New Installation rather than updating/repairing an existing system:
Set the actual time zone and hardware-clock convention. The source illustrates Asia/Beijing, Hardware Clock Set to UTC, and the displayed 2013 date/time; that is an example setting, not a timezone to assign to every installation:
The source selects Physical Machine. The actual UI label also says this choice applies to fully virtualized guests; it is consistent with the VMware example and differs from a paravirtualized Xen guest or a Xen virtualization-host choice:
3. Review the Expert installation settings
Open Expert in Installation Settings and inspect Partitioning, Booting and Software before committing changes:
3.1 Custom partitions
Open Partitioning → Custom Partitioning(for experts). In the Expert Partitioner, select the intended disk and add a partition. Device names and sizes are examples; confirm actual identity and data protection first:
The source chooses a Primary Partition, specifies the required size, selects Ext3 and mounts it at /. Create swap and any other required partitions using their appropriate type/filesystem:
The source’s final proposal separately shows 1.46GB swap and 13.54GB root. A 15 GB root consuming a 15 GB disk would not leave room for that swap; the mixed captures are not a consistent size-by-size partition recipe. Plan the actual layout and boot requirements before accepting any formatting. Root plus swap is only the source’s simple legacy example, not a universal partition requirement.
3.2 GRUB installation and disk order
Open Booting → Boot Loader Installation. The source uses GRUB and leaves its example boot-loader location selected. Its screenshot selects Boot from Boot Partition; that setting and any necessary boot chain depend on the actual BIOS/UEFI layout and are not safe defaults for all machines:
When installing from USB, the source opens Boot Loader Installation Details and moves the verified local OS disk ahead of the USB installer in the device order. Avoid putting the boot loader on removable installation media. The pictured device map has only /dev/sda; it illustrates the dialog rather than proving a two-disk reorder:
4. Select software and review before installation
Open Software and select the supported packages required by the workload. The source recommends C/C++ Compiler and Tools for later driver builds; install it when the actual supported driver workflow requires building, rather than assuming all installations need a compiler. The source checkbox remains unchecked in this localized illustration:
Review all selections, target disks and boot configuration, then use Install when the intended changes are approved. The last source image is still an Installation Settings page with an Install button, not a completion/reboot confirmation:
The source instructs waiting for installation to finish but provides no post-install verification capture. Verify the actual completed system, installed driver, local-disk boot without removable media and expected networking through the matching release’s procedure. No formatting, package install or reboot was performed here.