![]() ![]() We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Therefore, we occasionally resort to using automated bots to request further testing. However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. ![]() Thank you for taking the time to file a bug report on this issue. UpgradeStatus: No upgrade log present (probably fresh install)ĭmi.bios.vendor: Phoenix Technologies LTDĭmi.modalias: dmi:bvnPhoenixT echnologiesLTD: bvr2.1: bd06/23/ 2008:svnSupermi cro:pnX7DVL: pvr0123456789: rvnSupermicro: rnX7DVL: rvrPCBVersion: cvnSupermicro: ct1:cvr01234567 89: Linux- backports- modules- 3.2.0-12- generic N/A Linux- restricted- modules- 3.2.0-12- generic N/A InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1) ProcVersionSign ature: Ubuntu 3.2.0-12.21-generic 3.2.2Ĭrw-rw-T 1 root audio 116, 1 Feb 1 23:35 seqĬrw-rw-T 1 root audio 116, 33 Feb 1 23:35 timerĪplayDevices: Error: No such file or directoryĪrecordDevices: Error: No such file or directoryĪudioDevicesInUse: Error: command failed with exit code 1:ĬRDA: Error: No such file or directory So according to the test instructions, this test is a failure because I can't rebuild the array (nor is it automatically rebuilt). I also tried using sudo mdadm -re-add /dev/md0 /dev/sdb1 Mdadm: To make this a spare, use "mdadm -zero-superblock /dev/sdb1" first. Mdadm: not performing -add as that would convert /dev/sdb1 in to a spare. Mdadm: /dev/sdb1 reports being an active member for /dev/md0, but a -re-add fails. The instructions indicated that I may have to re-add the drives that are missing manually, so I attemted sudo mdadm -add /dev/md0 /dev/sdb1 Instead, I found that the second drive was missing from md0 and md2 while md1 (the swap LUN) was cat /proc/mdstat ![]() After logging in, I rechecked /dev/mdstat, expecting to see both drives for each md device and a resync in progress. I re-inserted drive2 (sdb) and powered the system up again. On reboot, I verified that the array was active and degraded and powered the system back down, again per the test instructions. I then powered the machine down per the test case instructions, removed disk 2 (sdb) and powered back up. On the initial boot, I verified that all three RAID devices were present and cat /proc/mdstat Md2: 180GB RAID1 using sda3 and sdb3 for /home Md1: 20GB RAID1 using sda2 and sdb2 for swap Md0: 50GB RAID1 using sda1 and sdb1 for / I then created three RAID deviecs, md0 - md2 as follows: I created the three partitions for each physical disk. Using the instructions found here: testcases. ![]() Hardware config is a 1U server with 2 SATA drives wth the following partitions: Attempting the RAID install test with Precise server AMD64. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |