So I'm trying to install the last version of Ubuntu Server 11.10 64bits on my server ( replacing Windows Server 2008 completely ). Since I need more Sata ports, I bought a PCI Sata RAID Controller based on the chipset SiI3114. The problem is that when I configure the array to RAID 1, when the installer gets to the point where I partition the disks, the RAID array simply doesn't appear on the list. The installer asks me if I want to 'activate the Serial Ata RAID devices', I choose yes, and nothing is listed. If I instead of creating an RAID 1 array, create an Raid 0 array, it appears on the list to partition the disk. This last part, is what I don't understand, it gets recognized when it is a RAID 0 array, but if it is a RAID 1 array it doesn't. I've read the FakeRaid wiki on, and also this post: Running in RAID 1, and executing the shell on the installer and running the command dmraid -r, I get: /dev/sdb: sil, 'sil_bhbgdfdcfdfc', mirror, ok, 976771072 sectors, data@ 0 /dev/sda: sil, 'sil_bhbgdfdcfdfc', mirror, ok, 976771072 sectors, data@ 0 Looks good I think. When in RAID 0, using the same commands, I get: /dev/sdb: sil, 'sil_bhbgdfdcfdfc', stripe, ok, 976771072 sectors, data@ 0 /dev/sda: sil, 'sil_bhbgdfdcfdfc', stripe, ok, 976771072 sectors, data@ 0 Everything looks OK, I guess, it's the first time I'm installing Ubuntu Server for real, I've installed 4 or 5 times on VMPlayer to see how everything works. If I don't configure an array, the disks are recognized with no problem whatsoever, if the PCI card, wasn't detected properly it wouldn't show any disks connected to the card in any instance I think. The card is also capable of RAID 5 and RAID 10, but I haven't tested that yet, later when I arrive home, I will see if the installer detects those RAID arrays. EDIT: So I arrived home, and started googling again, and i found, so I ran the command dmraid -ay: ERROR: device-mapper target type 'mirror' is not in the kernel. RAID set 'sil_bhbgdgaaaaba' was not activated. Then I googled for this error, and what I found kind of scared me,, basically all I have to do is recompile the Kernel with mirroring support, I can't recompile the kernel I simply don't have the knowledge to do it. Can anyone give me a solution that doesn't involve recompiling the kernel? Second edit: I just downloaded and burned an Ubuntu Live CD, and guess what? The RAID array is detected on the spot ( I'm currently installing Ubuntu in the RAID array ). Now I'm just plain confused, I tough the Ubuntu Server was a Ubuntu version but without an windows manager. Third edit: Just saved the syslog, to have more information to show: Oct 24 22:46:43 anna-install: Installing dmraid-udeb Oct 24 22:46:43 anna[10984]: DEBUG: retrieving dmraid-udeb 1.0.0.rc16-4.1ubuntu4 Oct 24 22:46:43 anna[10984]: DEBUG: retrieving libdmraid1.0.0.rc16-udeb 1.0.0.rc16-4.1ubuntu4 Oct 24 22:46:43 disk-detect: Serial ATA RAID disk(s) detected. Oct 24 22:46:44 disk-detect: Enabling dmraid support. Rant mode, if I'm allowed, this doesn't make any sense, at least for me, why doesn't Ubuntu Server come with the support for Raid 1 compiled into the kernel? And I'm almost sure that RAID 5 and RAID 10 aren't also ( I can't test it because the Sata cables are too short ), this way only complicates the life for people, when it can be a lot simpler, I understand that the Raid card I bought only supports FakeRaid, but I want to use no matter what, even if it's slower, and what if I had bought a $400 card that doesn't do fake raid and I want to use it? I'd have to recompile the kernel! – Oct 24 '11 at 19:49. 1.) sudo lsmod Check and see if the (dm_raid) module has loaded? 2.) sudo dmraid -tay either of these commands work ( sudo dmraid -ay) Test the raid array? 3.) gedit /boot/grub/device.map and add (hd0) /dev/sda (hd1) /dev/sdb 4.) gedit /etc/fstab comment out ( /dev/mapper/sil_biabadbhagdc1) and ( /dev/mapper/sil_biabadbhagdc5) place a # in front of those lines. Add your UUID's like so, you can use this command to get your UUID's ( sudo blkid) Mine looks like this: # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5). # # proc /proc proc nodev,noexec,nosuid 0 0 # /dev/mapper/sil_biabadbhagdc1 UUID='01331dc5-0c78-49ab-9cf5-655b645110d2 / ext4 errors=remount-ro 0 1 #/dev/mapper/sil_biabadbhagdc5 UUID='ea62296d-27ef-4b59-8206-e89d7a31a844 none swap sw 0 0 5.) sudo reboot and check your log files, keep in mind do not use the () in these commands. I am using raid0 with a SYBA PCI-X 4 port sata II Raid card. On a Tyan board with two Seagate 320 drives. This may or may not work for you. This topic describes the tasks that you must complete before you test a hardware-based RAID storage array by using the Windows Hardware Lab Kit (Windows HLK): •. • The storage tests that you must run, the testing prerequisites, and the test setup vary depending on whether the RAID system is Internet SCSI (iSCSI) based or whether it uses another connection type: Fibre Channel, Serial Attached SCSI (SAS), SCSI, or Serial Advanced Technology Attachment (SATA). Hardware Requirements To test a hardware-based RAID array, you need the following hardware. You might need additional hardware if the test device offers other features. To determine whether additional hardware requirements apply, see the description for each test that appears for the device in Windows HLK Studio. ASUS P5K DELUXE USER MANUAL Pdf Download. Jan 01, 2004Select your preferred way to display the comments and click Save settings to activate your changes. ASUS P5K DELUXE USER MANUAL Pdf Download. Activate serial ata raid devices. Learn the nuts and bolts of PCs, from the core components that provide. Download the latest Adaptec Serial ATA RAID 21610SA device drivers (Official and Certified). Adaptec Serial ATA RAID 21610SA drivers updated daily. Download Now. Preparing for Hardware-based RAID Systems Testing Preparing to Test Hardware-based Raid Systems. Check that all RAID devices. Or Serial ATA RAID. This page describes how to install Debian using the Serial ATA RAID (aka fake RAID, BIOS RAID) feature provided by your SATA disk controller. These are controllers that advertise RAID. Not to be confused with the Linux kernel's software RAID feature (Multidisk Device). This is the preferable and more. Note All hardware (except the test device, monitor, keyboard, mouse, and floppy disk drive) must be listed in the Windows Catalog. • 1 test computer that meets the Windows HLK requirements. For more information, see. In addition, this computer must include: • 1 logo-compliant Advanced Configuration and Power Interface (ACPI) BIOS, with ACPI enabled by default. • Dual-core or equivalent processor and a minimum of 2 gigabytes (GB) of memory for Windows client operating systems (for example, Windows 8, Windows 7, and Windows Vista). • Quad-core or equivalent processor and 6 GB of memory for Windows Server® operating systems. An equivalent processor is any processor that appears to Windows as if it contains the specified number of CPUs. You can achieve this status through 1 or more physical microprocessors. • 1 test-specific type of RAID storage system: Fibre Channel, SAS, SCSI, or SATA RAID (for example, a SAS RAID storage system for a SAS system test). This device is the test device. Warning The RAID system must be a single cabinet that consists of an array controller that's enclosed in an external subsystem with hard disk drives. Or it must be an external array controller that connects to a RAID JBOD. The RAID system can't consist of only a Peripheral Component Interconnect (PCI)–based controller and 1 RAID JBOD. • 1 PCI-based, test-specific type of host bus adapter (HBA). If the test system supports Microsoft® Multipath I/O (MPIO), 2 ports in the HBA or 2 identical HBAs (if each of them has only 1 port) must be connected to the same target device. Note The RAID system should support the PCI-based HBA that you select to test the RAID system. Any drivers that you use on the test system for this HBA must have a Windows logo, and the HBA model and firmware version must be included in the Windows Catalog. • 1 bootable ATA, SCSI, or SATA (only for testing SATA hardware-based RAID systems) hard disk drive, if the RAID system doesn't support boot. This drive must have a minimum capacity of 36 GB. To certify your product for use on servers, the test computer must support four processors and a minimum of 1 GB of RAM. These system capabilities are required to test the Rebalance, D3 State, and Multiple Processor Group functionality of the device and driver. You do not need a computer that actually has more than 64 processors to test your device. Additionally, the server system(s) being used for device or driver testing must have Server Core installed prior to testing. For more information see. If you use a pool of test computers to test your device, at least 1 computer in the pool must contain 4 processors and a minimum of 1 GB of RAM. Additionally, that computer must contain the device and the driver that you want to test. As long as the driver is the same on all the computers in the pool, the system creates a schedule to run against all test computers. For tests that don't include a driver to test, like tests for a hard disk drive, the Windows HLK scheduler constrains the tests that validate the device's and driver's Rebalance, D3 State, and Multiple Processor Groups functionality to run on the default test computer. You must manually configure this computer to have multiple processor groups. The default computer is the first test computer in the list. Make sure that the first test computer in the list meets the minimum hardware requirements. Note Multiple Processor Groups Setting You must set the value for the processor group size for Hardware Lab Kit testing of Windows Server 2008 R2 and later device drivers for certification. This is done by running bcdedit in an elevated command prompt window, using the /set option. The commands for adding the group settings and restarting are as follows: bcdedit.exe /set groupsize 2 bcdedit.exe /set groupaware on shutdown.exe -r -t 0 -f The commands for removing the group settings and rebooting are as follows: bcdedit.exe /deletevalue groupsize bcdedit.exe /deletevalue groupaware shutdown.exe -r -t 0 -f. Note Code Integrity Setting The Virtualization Based Security feature (VBS) of Windows Server 2016 must be enabled using Server Manager first. Once that has occurred, the following Registry key must be created and set: HKLM System CurrentControlSet Control DeviceGuard HypervisorEnforcedCodeIntegrity:REG_DWORD 0 or 1 (disabled, enabled) Software Requirements To test a hardware-based RAID array, you need this software: • Any drivers for the test hardware that aren't included with Windows. • The latest Windows HLK filters or updates. • Windows symbol files. These are available from the website. Configuring the Test Computer To configure the test computer to test your Fibre Channel, SAS, SCSI, or SATA RAID array, follow these steps: • Configure the RAID system by using the RAID system operator panel, by using the command-line tool, or by connecting another system to the RAID system and running the configuration tool. Specifically: • Check that all RAID devices support only 1 RAID level: either RAID 5, RAID 1, or RAID 0. If your RAID system supports more than 1 RAID level, you must test all RAID levels that the device supports. • Create three 40-GB RAID arrays on the RAID system. Configure the arrays according to this table: If the test device supports these RAID levels RAID level for RAID Array 1 RAID level for RAID Array 2 RAID level for RAID Array 3 0 only 0 0 0 1 only 1 1 1 5 only 5 5 5 0 and 1 only 1 0 1 or 0 0, 1, and 10 10 1 0 0 and 5 only 5 5 0 1 and 5 only 5 5 1 0, 1, and 5 5 1 0 0, 1, 5, and 10 5 10 1 or 0 • Turn off the test computer. • Install 1 test-specific type of HBA. For example, if you're testing for a Fibre Channel system, install the Fibre Channel HBA. • In the test system, connect the HBA to the RAID system by using the appropriate cables for the bus type (for example, SCSI, SATA, and so on). Note If the test RAID system supports more than 1 bus protocol, you must test and submit your device for Windows certification 1 time with each protocol that you want to have it qualified for. • If the device supports MPIO, make sure that the HBA has at least 2 ports. If the HBA has only 1 port, install another HBA of the same model, and then connect it to the RAID system by using the appropriate cables for the bus. • For a non-MPIO test environment, if both the HBA that you're using to test the RAID system and the RAID system itself support boot, follow these steps: • Install any HBA or RAID system drivers, including multipath drivers that are required to connect to or manage the test device. • Create a 36-GB NTFS file system partition on RAID Array 1, and then install the appropriate operating system on this partition. Note We recommend SAN-boot configuration, but it isn't required. For an MPIO test environment, we don't recommend that you set up MPIO logical unit number (LUN) bootable. Instead, follow these steps: 1. Install an alternate boot controller on the test system. Connect a hard disk drive to the alternate boot controller on the test system. Install any necessary drivers for the alternate boot controller. Install the appropriate operating system on a 36-GB NTFS partition on the hard disk drive. Install any HBA or RAID system drivers, including multipath drivers that are required to connect to or manage the peripheral devices. • Click Start, and then click Run. • Type diskmgmt.msc, and then press Enter. If the test operating system is Windows Vista or Windows Server 2008, and you're prompted to enter administrator credentials, enter the credentials. • If the disks appear to be inactive, activate them by right-clicking the disk and then clicking Initialize Disk. • Partition and format all disks: • Right-click each disk, and then click Convert to Basic Disk if it is not basic already. • Right-click each disk, and then click New Partition. Note Each partition should be a primary partition, should use all of the disk space, should use any drive letter, and should be formatted in NTFS. For a non-MPIO test environment, if the HBA that you're using to test the RAID system is bootable, and if the RAID system supports boot, RAID Array 1 should already have a 36-GB partition. Create a new NTFS partition by using the remaining space on this drive. • Restart the operating system to update the size of the page file. • Verify that the computer can read or write to the test RAID array. • Install the Windows symbol files to the C: Symbols directory. These are available from the webpage. • Install the Windows HLK client application on the test computer. • Use Windows HLK Studio to create a computer pool, and then move the test computer to that pool. For all types of RAID arrays that you're testing, make sure that the test computer is in the ready state before you begin your testing. If a test requires you to set parameters before you run it, a dialog box will appear for that test. For more information, review the specific test topic. Some Windows HLK tests require user intervention. When you're running tests for a submission, it's a best practice to run the automated tests in a block separately from manual tests. This prevents a manual test from interrupting the completion of an automated test. Warning When testing storage devices, we strongly recommend that you complete all Device Fundamentals tests before starting storage tests. Storage tests will reconfigure your test device, leaving the device in a state unsuitable to support Device Fundamentals tests. The following configurations provide steps to create volume on the storage test device. This is important to complete the Device Fundamental part of testing (DevFund). Feature-Based Configuration If your device supports any of the feature(s) in this section, please update the associated configurations steps in addition to the general interface-based configuration steps in the “Configuring the Test Computer” section. Minor modifications may be applicable depending on the specifics of your device form-factor. Device.Storage.Hd.Mpio • MPIO Test needs multiple ports connected to the same LUN. HBA needs to have multiple ports, or multiple one-port HBAs need to be set up. • For iSCSI test environment, it needs NIC card(s) or iSCSI HBA(s). • HBA firmware and drivers. • At least three LUNs. • Install MPIO feature by using Server Manager and install MS DSM or 3rd party DSM. • For iSCSI test environment, the users need to set up multiple iSCSI sessions for each pair of initiator IP address and target. • If device supports MPIO, then all of the three LUNs should be MPIO LUNs. • Configure the LUNs LBP policy to be Failover Only. • Configure the LUNs to be with partitions. • While creating submissions, select both DSM and the specific LUNs supporting specific features. You do not need to manually add the MPIO feature to the LUN. Device.Storage.Hd.OffloadedDataTransfer • Test system has minimum 2 adapters with Adapter1 having 2 LUNs and Adapter2 having 1 LUN. • LUNs configured should be a minimum of 21 GB in size. • Single HBA Push Scenario & Single HBA Pull Scenario: Runs Offload Scenario test between Lun0 and Lun1. • Multiple HBA Push Scenario & Multiple HBA Pull Scenario: Runs Offload Scenario test between Lun0 and Lun2. Device.Storage.Hd.RaidArray Upon completion of hardware setup, and manually select this feature when going through the Windows HLK’s target selection. Device.Storage.Hd.ThinProvisioning • If the device supports thin provisioning, at least include one thin provisioned LUN and one full provisioned LUN. Thinly provisioned LUN needs to have a size no larger than 25 GB. • If the device supports thin provisioning, thin provisioning feature, threshold notification and persistent resource exhaustion, features need to be configured on the storage device end. • Configure the threshold notification to be set at 70% for thinly-provisioned LUN. • Enable permanent resource exhaustion feature on storage array.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2018
Categories |