[Bug 219393] Re: ich9R raid array not detected
Ok, it works now!! i just had to read more carefully :) Thanks all! But I 've another question, what happens if I upgrade to new kernel version? Because I think this dmraid 45 patch is only available kor kernel 2.6.24.16? -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
i´ve got th same problem with my Abit ip35 pro, ICH9R I want to make a Raid 5 array, and after hours i managed, with the mdraid45 module (that appears only to be working in kernel 2.6.24.16) to build the array and format in ntfs. So basically i want it to be accessible in linux and windows, but it doesn´t have to be bootable. So i tried some of these things above, but i guess libata ignore_hpa=0 will not change anything because i´m not booting from it, am I right? But the problems seems the same, i tried it formatting in windows with partition magic and in ubuntu, but as sooon as I shut down and power up again those drives are offline. So how to fix this?? I can boot to windows and ubuntu without problems, sometimes i´ve got to manually edit grub because hd numbers are changed or something... But I really want this to be working so i can share media-files between windows and linux my dmraid-ay: ERROR: isw device for volume Data broken on /dev/sdb in RAID set isw_ddfgjgjdhh_Data ERROR: isw: wrong # of devices in RAID set isw_ddfgjgjdhh_Data [1/3] on /dev/sdb ERROR: isw device for volume Data broken on /dev/sda in RAID set isw_cdjicdbgha_Data ERROR: isw: wrong # of devices in RAID set isw_cdjicdbgha_Data [2/3] on /dev/sda ERROR: isw device for volume Data broken on /dev/sdc in RAID set isw_cdjicdbgha_Data ERROR: isw: wrong # of devices in RAID set isw_cdjicdbgha_Data [2/3] on /dev/sdc -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Thanks Phillip! That worked for me as well! I can now sudo mount /dev/dm-1 /media/RAID and read and write to it without breaking the array. The issue where the RAID is shown as broken after a soft reboot is resolved as well. Some of the research that I did on this issue since my last post indicates that this HPA could have been created by the Xpress recovery feature of this motherboard. This is supposed to create a system restore partition at the end of a hard disk, much like is found on some laptops, and some sources on forums indicate that these partitions are commonly hidden by the BIOS using HPA. I was trying to find a way to use the feature to change which drive it uses to apply HPA. The funny thing is that this board does not support the feature at all when the RAID controller is turned on, so I could not even load the configuration utility to see if it had such an option. Other people with similar features on their motherboards might need to use this same workaround. Thanks again, Phillip, for your excellent detective work and problem solution. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
And the winner is : Philip Susi :) Thanks, it works for me ! I have other problems with installer : Installer displays bizarre patition table, but nothing alarming. It can't format the ext3 partition. I did it manually, without a problem, and asked installer not ot format ... But now, it complains about system files that can not be removed, even when starting with an empty, freshly formated, partition. But this is another ... story. Because the trick makes dmraid works properly. One more time : Thanks Philip ! -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Ok, because libata is loaded as a module rather than built into the kernel, you have to add the line: options libata ignore_hpa=0 to /etc/modprobe.d/libata-options. After adding the line, you will need to run sudo update-initramfs -u. If you are booting from the livecd, then you need to add break=top to the kernel command line and when you get to the prompt, type: echo options libata ignore_hpa=0 /etc/modprobe.d/libata-options exit -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
hello, me again whit the bad english :-) jbfoley i tried to add this to the boot line in /boot/grub/menu.lst but after cold reboot its gone, /boot/grub/menu.lst was rewritten by ? ok looking in the dmesg it appears there [0.00] Command line: root=UUID=c62d8a18-ea63-45d2-83c7-44a6d197f299 ro quiet splash ata_ignore_hpa=0 here is a cut of the dmesg http://ubuntuusers.de/paste/225160/ have a look at the line 32 = Faking ... ? tried to add this line to /etc/modules no changes :-( libata ignore_hpa=0 how can change this para. before libata got loaded??? reg. masa ** Attachment added: dmraid http://launchpadlibrarian.net/14686483/dm1 -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
The kernel parameter does not appear to have had the intended effect. I added this entry to menu.lst in /boot/grub and cold-booted to it: title Ubuntu 8.04, kernel 2.6.24-16-generic (RAID fix) root(hd0,4) kernel /boot/vmlinuz-2.6.24-16-generic root=UUID=ec648d6c-188d-4513-b3d5-0a534bd5e377 ro splash ata_ignore_hpa=0 initrd /boot/initrd.img-2.6.24-16-generic Just appended ata_ignore_hpa=0 to then end of the kernel line. It looks like the command was taken. From dmesg: [0.00] Kernel command line: root=UUID=ec648d6c- 188d-4513-b3d5-0a534bd5e377 ro splash ata_ignore_hpa=0 but when it got to my second disk (which is the only one it was doing hpa unlocking on before): [ 47.817330] ata3.00: HPA unlocked: 976771055 - 976773168, native 976773168 I have included a partial dmesg from this attempt. Only one of the drives seems to get the hpa on it. I also tried several other ways to add the parameter, but none have prevented the line above from appearing. Also, Sebounet, I'd like to try your method. I'm not booting to a live cd, but I'm a bit new to ubuntu, so from a hard disk install, how and where would one add the modprobe libata ignore_hpa=0 line? /etc/modprobe.d has many files in it, and I don't just want to throw it in anywhere. ** Attachment added: dmesg.txt http://launchpadlibrarian.net/14651729/dmesg.txt -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Have you tried updating your bios yet? I also notice that the version recorded in the signature is rather old. According to Intel, the metadata is supposed to reside in the last two sectors of the disk. Based on the incorrect position and the incorrect disk size I noted that was recorded before, it appears that your bios has a bug where it sometimes can not correctly determine the size of that disk. I have a suspicion that the bios may be issuing commands to hide the tail end of the one disk, which the Linux kernel resets, causing the metadata to appear in the wrong position and the bios and windows don't recognize the disk after a warm boot because it does not reapply the hide command. Another strange thing is that originally the signature was in the correct place and dmraid found it, but the disks did not agree on the size. What changed between the time you originally created the array, and when you recreated it with the signature now in the wrong place? Odd. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I'll have to inform Gigabyte of the problem, then. The BIOS I have is F4, which is the release version, but also the most recent version available for this board. With such a new product, I guess that's the danger. In the meantime, I'd like to see this work at least once, just so we can confirm that this is the only issue. I seem to recall that there was a procedure for specifying the position of the signature to dmraid. Is that true, and if so, how would one do it? -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Thanks, I didn't see your last message before I posted, there. I'll give that kernel parameter a try this evening. I still think Gigabyte needs to act on this, especially if they've got an old version of the RAID BIOS. I think I will send them to this thread directly. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I have done some more reading of that thread on the ataraid list you linked before, and the bug reports they reference, and it seems my initial suspicions were correct. Your bios is using the Host Protected Area feature to reduce the size of the disk, and the kernel is resetting that. Could you try adding ata_ignore_hpa=0 to your kernel command line at boot? If you check your dmesg, you should see something like this now: [ 60.453908] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 60.456006] ata1.00: Host Protected Area detected: [ 60.456007] current size: 293044655 sectors [ 60.456008] native size: 293046768 sectors [ 60.457150] ata1.00: native size increased to 293046768 sectors I think that adding that parameter should get rid of the last line and the metadata will appear at the correct location. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Currently running on kubuntu live CD 8.04. Mobo : P35C-DS3R (rev2.0) with latest BIOS (F11e) ( First version of bios are AWFULL , nothing worked correctly... ) I added ata_ignore_hpa=0 at boot ... But it did not help :( still have : [EMAIL PROTECTED]:~# dmraid -ay ERROR: isw device for volume RAID0 broken on /dev/sdb in RAID set isw_cdgibffddf_RAID0 ERROR: isw: wrong # of devices in RAID set isw_cdgibffddf_RAID0 [1/2] on /dev/sdb ERROR: isw device for volume Volume0 broken on /dev/sda in RAID set isw_echgefjfjf_Volume0 ERROR: isw: wrong # of devices in RAID set isw_echgefjfjf_Volume0 [1/2] on /dev/sda dmesg gives : [ 365.835593] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed [ 365.835599] device-mapper: ioctl: error adding target to table [ 365.836529] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed [ 365.836533] device-mapper: ioctl: error adding target to table [ 381.580072] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed [ 381.580076] device-mapper: ioctl: error adding target to table [ 381.580964] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed [ 381.580967] device-mapper: ioctl: error adding target to table grepping in dmesg with ata , I noticed : [0.00] Kernel command line: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed boot=casper initrd=/casper/initrd.gz quiet splash -- ata_ignore_hpa=0 locale=fr_FR console-setup/layoutcode=fr console-setup/variantcode=oss [ 86.016927] Memory: 3621848k/4194304k available (2164k kernel code, 45784k reserved, 1007k data, 364k init, 2751360k highmem) [ 86.016935] .data : 0xc031d1bd - 0xc0418dc4 (1007 kB) [ 89.211303] libata version 3.00 loaded. [ 90.988408] ata1: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xfa102100 irq 219 [ 90.988411] ata2: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xfa102180 irq 219 [ 90.988412] ata3: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xfa102200 irq 219 [ 90.988414] ata4: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xfa102280 irq 219 [ 90.988416] ata5: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xfa102300 irq 219 [ 90.988418] ata6: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0xfa102380 irq 219 [ 91.307190] ata1: SATA link down (SStatus 0 SControl 300) [ 91.945515] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 91.958141] ata2.00: HPA unlocked: 1250261615 - 1250263728, native 1250263728 [ 91.958145] ata2.00: ATA-7: SAMSUNG HD642JJ, 1AA01109, max UDMA7 [ 91.958147] ata2.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 91.964528] ata2.00: configured for UDMA/133 [ 92.280638] ata3: SATA link down (SStatus 0 SControl 300) [ 92.599800] ata4: SATA link down (SStatus 0 SControl 300) [ 93.238126] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 93.250737] ata5.00: HPA unlocked: 1250261615 - 1250263728, native 1250263728 [ 93.250740] ata5.00: ATA-7: SAMSUNG HD642JJ, 1AA01109, max UDMA7 [ 93.250743] ata5.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 93.257139] ata5.00: configured for UDMA/133 I have numerous dmesg like this one : [ 195.966487] sda: rw=0, want=2500509696, limit=1250263728 [ 195.966491] attempt to access beyond end of device I put the full dmesg log in attachment. Thanks for help. All ideas are welcome :) ** Attachment added: log_dmesg.txt http://launchpadlibrarian.net/14646926/log_dmesg.txt -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I read here : http://ubuntuforums.org/showthread.php?p=4859992 that loading libata module this way : modprobe libata ignore_hpa=0 ..may help. But how to add this option while booting on liveCD ? -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
No other solution than extracting the Filesystem.squashfs - modifying - recreate an ISO ? ( long way to go for just a try ... ) -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
That's what I was just trying to figure out Sebounet... but in your case, your actual array is also broken since both disks were given different signatures when created. You might try recreating the array and see if they get the same signature this time. To work properly they need the same signature, AND you will need the HPA fix. I would suggest that you contact your motherboard manufacturer and open a trouble ticket with them and see if you can figure out why the bios is even protecting part of the disk in the first place, and if there is a way you can tell it not to. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
jbfoley, its a bug in ubuntu dmraid modules or somting else buts its in ubuntu! how Sebounet says if you are booting COLD in to a gentoo live cd it works fine, fdisk shows after spliting the disk the created devices unter /dev/maper ... but ubuntu-dmraid counts the devices up an reads the parti-tables from other device? scenario if you are booting in to ubunto the raid shows as brocken.ok, reboot(Warm) recreate the raid (BIOS,INTEL RAID MANAGER ) boot in to ubuntu and the raid seems to working, ok, second reboot(WARM) into the gentoo live CD, gentoo dmraid shows the saim raid, ok it works ??? NO now turn the pc OFF, not only reboot. gentoo Live cd shows the old raid ... there are somwhere cout-vars, which counting wrong by ubuntu-dmraid, or other stuff, the count variables for the raids are in the itel driver? am today in the evenings back at home , and i can post loadet modules, dmraid version (gentoo) where it works fine. however gentoo rocks :-) sorry for my ugly english :-( -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I tried breaking the array, reformatting both drives with mkfs (ext2) and then rebuilding the array. This time dmraid would only see one drive of the mirror, and not the other one. I'm including my info dump in a text file. Perhaps this version of the Intel driver only needs to mark one drive? Seems like it wouldn't work if one drive failed in that case. Other possibility is that it's putting the mark in a different spot on the second drive, but that also seems unlikely. It really looks to me like there is a bug preventing dmraid from finding the correct marker on the second drive. I should mention that I booted ubuntu immediately after the array build in this case, but after I did all of the stuff you seen in the text dump, I cold booted to windows and the array came up as healthy and happy. I then initialized it for windows and formatted it ntfs, then rebooted and tried ubuntu again, but there was no change, except that the ext2 filesystem that had been visible on each individual drive is now inaccessible, and only one 500 gig device shows, instead of both, but it is also unmountable. Also, watchwolf, I am using the rc14 version of dmraid, so it looks like that is not the fix for my problem: [EMAIL PROTECTED]:~$ dmraid -V dmraid version: 1.0.0.rc14 (2006.11.08) dmraid library version: 1.0.0.rc14 (2006.11.08) device-mapper version: unknown ** Attachment added: DMRAID.txt http://launchpadlibrarian.net/14626442/DMRAID.txt -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I have a gentoo live CD lying around somewhere, so I'll give that a try tonight. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Hrm it sounds like the bios may be writing the signature to a different location on the disk each time, and dmraid becomes messed up when it finds the wrong one. jfboley, would you wipe the disk clean, recreate the raid array, and then dump the last 2 megs of each disk and post them here? Zero the last 2 megs of each disk, repeat for each disk in the array: dd if=/dev/zero of=/dev/sda seek=976769072 Boot into the bios and verify that it no longer thinks the drives are part of an array ( since we just wiped out the signature ), and if not, create a new array, then dump the last 2 megs and attach here: dd if=/dev/sda skip=976769072 | bzip2 -c sda.bz2 Replace sda and repeat for each drive in the array. You did say that if you cold boot into ubuntu, dmraid works correctly right, but not if you warm boot? After zeroing the disk, be sure to cold boot into the bios, and cold boot again back to Ubuntu after creating the array. Once you have dumped the last two megs of the disks, see if dmraid -ay correct activates them, then warm boot and try again. Note the output of fdisk -l after a cold boot, and again after a warm, and see if they differ. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I will try this procedure this evening and post the results. Do you want me to run this procedure on sda as well? In my current configuration, sda is not a RAID member, and it serves as my boot disk. sdb and sdc are the members of the RAID. One correction, dmraid does not work correctly after a cold boot. Unfortunately, I've never been able to get dmraid to work on this machine. The cold boot has to do with getting the bios and the windows drivers to work correctly. If I boot Ubuntu, whether I try to use dmraid or not, then restart from Ubuntu (warm boot,) the bios shows both disks of the array as offline members and windows does not see them properly either. It is only when I cold boot and go directly to windows that the RAID works. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Phillip, I have attached the results of your suggested procedure. I took the chance to look at them, and found that while the sig data does exist on both drives, it is also located in very different spots on each. This seems very strange to me, but also suggests an easy workaround and fix. For now, I'm going to try moving both signatures to the same place. Hopefully, there is a way to make dmraid search for this data on both drives so that future users don't have to deal with this. I hope that the position is not supposed to be determined by the disk serial or something equally cryptic. I will post the results. ** Attachment added: Files generated http://launchpadlibrarian.net/14631998/RAID_info.tar.bz2 -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I moved the signature data on sdb to the same offset as that on sdc (and zeroed out its old position.) (I moved the data from sdb to sdb, even though it looked like the sigs on the two drives were identical.) This resulted in the BIOS seeing the RAID as degraded, with one member disk, and one non-member, but healthy disk. I booted without letting the BIOS make any changes, and dmraid also did not like the new set. I have attached that info in a text file. I did not boot windows at any time during all of this, and all boots were cold ones. From the results of dmraid -n it looks like there is some data for the RAID stored in other parts of the disk. I don't know enough to mess with it further, so I'll put it back the way it was and wait to hear back. p.s. thanks for all your help, Phillip. ** Attachment added: DMRAID-3.txt http://launchpadlibrarian.net/14632757/DMRAID-3.txt -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Masa, what you are seeing seems to agree with my most recent test. I once again deleted the array in BIOS and re-created it, only this time, I named it NewRAID1 When I ran dmraid -n it showed the first disk as being a part of NewRAID1 and the second as being a part of RAID1, which was the name of the old array. When I get home, I will try breaking the array, completely reformatting both, and then rebuilding it to see what happens. Sorry for the slow response, I have been on the road for the last couple of weeks. Intel's bug report process is a joke, for those of you who are interested. As far as I can tell, there is no way to report a driver or BIOS bug aside from going through the motherboard manufacturer. Glad I didn't get an Intel-made board. My guess is that this is really a bug in the driver/BIOS, as others have suggested. I will take it up with Gigabyte when time permits and post the results here (if any.) -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
When posting to a bug someone else filed to say me too you really need to try to provide the same detailed information that others have in the bug report to be useful. In this case, that would mean the output of dmraid -n and dmraid -ay - -. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Same problem here with a P35C-DS3R (rev2.0). dmraid works fine with gentoo liveCD , with exactly same version of dmraid and mapper. So in my mind, the raid array is badly initialized by something else... Maybe it comes from another module (not loaded in gentoo case) ? -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
same here! MOBO: Gigabyte GA-EP35-DS4 (Bios F2) ( http://www.gigabyte.de/Support/Motherboard/Driver_Model.aspx?ProductID=2678 ) CHIPSET: ICH9R Chipset RAID: RAID0 (SATA) + RAID1(SATA) - I have 2 raid arrays, RAID1 and RAID0. Seems that RAID1 works and after reboot it dosen't goes offline! but the RAID0 do this :-( And is there already an workaround to fix this problem? -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
[EMAIL PROTECTED]:~$ sudo dmraid -ay -vvv -d WARN: locking /var/lock/dmraid/.lock NOTICE: skipping removable device /dev/sdf NOTICE: skipping removable device /dev/sdg NOTICE: skipping removable device /dev/sdh NOTICE: skipping removable device /dev/sdi NOTICE: skipping removable device /dev/sdj NOTICE: /dev/sde: asr discovering NOTICE: /dev/sde: ddf1discovering NOTICE: /dev/sde: hpt37x discovering NOTICE: /dev/sde: hpt45x discovering NOTICE: /dev/sde: isw discovering NOTICE: /dev/sde: jmicron discovering NOTICE: /dev/sde: lsi discovering NOTICE: /dev/sde: nvidia discovering NOTICE: /dev/sde: pdc discovering NOTICE: /dev/sde: sil discovering NOTICE: /dev/sde: via discovering NOTICE: /dev/sdd: asr discovering NOTICE: /dev/sdd: ddf1discovering NOTICE: /dev/sdd: hpt37x discovering NOTICE: /dev/sdd: hpt45x discovering NOTICE: /dev/sdd: isw discovering NOTICE: /dev/sdd: isw metadata discovered NOTICE: /dev/sdd: jmicron discovering NOTICE: /dev/sdd: lsi discovering NOTICE: /dev/sdd: nvidia discovering NOTICE: /dev/sdd: pdc discovering NOTICE: /dev/sdd: sil discovering NOTICE: sil: areas 1,2,3,4[4] are valid NOTICE: /dev/sdd: sil metadata discovered /dev/sdd: sil and isw formats discovered (using isw)! NOTICE: /dev/sdd: via discovering NOTICE: /dev/sdc: asr discovering NOTICE: /dev/sdc: ddf1discovering NOTICE: /dev/sdc: hpt37x discovering NOTICE: /dev/sdc: hpt45x discovering NOTICE: /dev/sdc: isw discovering NOTICE: /dev/sdc: isw metadata discovered NOTICE: /dev/sdc: jmicron discovering NOTICE: /dev/sdc: lsi discovering NOTICE: /dev/sdc: nvidia discovering NOTICE: /dev/sdc: pdc discovering NOTICE: /dev/sdc: sil discovering NOTICE: sil: areas 1,2,3,4[4] are valid NOTICE: /dev/sdc: sil metadata discovered /dev/sdc: sil and isw formats discovered (using isw)! NOTICE: /dev/sdc: via discovering NOTICE: /dev/sdb: asr discovering NOTICE: /dev/sdb: ddf1discovering NOTICE: /dev/sdb: hpt37x discovering NOTICE: /dev/sdb: hpt45x discovering NOTICE: /dev/sdb: isw discovering NOTICE: /dev/sdb: isw metadata discovered NOTICE: /dev/sdb: jmicron discovering NOTICE: /dev/sdb: lsi discovering NOTICE: /dev/sdb: nvidia discovering NOTICE: /dev/sdb: pdc discovering NOTICE: /dev/sdb: sil discovering NOTICE: /dev/sdb: via discovering NOTICE: /dev/sda: asr discovering NOTICE: /dev/sda: ddf1discovering NOTICE: /dev/sda: hpt37x discovering NOTICE: /dev/sda: hpt45x discovering NOTICE: /dev/sda: isw discovering NOTICE: /dev/sda: isw metadata discovered NOTICE: /dev/sda: jmicron discovering NOTICE: /dev/sda: lsi discovering NOTICE: /dev/sda: nvidia discovering NOTICE: /dev/sda: pdc discovering NOTICE: /dev/sda: sil discovering NOTICE: /dev/sda: via discovering DEBUG: _find_set: searching isw_jejghfiaa DEBUG: _find_set: not found isw_jejghfiaa DEBUG: _find_set: searching isw_jejghfiaa_RAID1 DEBUG: _find_set: searching isw_jejghfiaa_RAID1 DEBUG: _find_set: not found isw_jejghfiaa_RAID1 DEBUG: _find_set: not found isw_jejghfiaa_RAID1 NOTICE: added /dev/sdd to RAID set isw_jejghfiaa DEBUG: _find_set: searching isw_jejghfiaa DEBUG: _find_set: found isw_jejghfiaa DEBUG: _find_set: searching isw_jejghfiaa_RAID1 DEBUG: _find_set: searching isw_jejghfiaa_RAID1 DEBUG: _find_set: found isw_jejghfiaa_RAID1 DEBUG: _find_set: found isw_jejghfiaa_RAID1 NOTICE: added /dev/sdc to RAID set isw_jejghfiaa DEBUG: _find_set: searching isw_djbfhchggj DEBUG: _find_set: not found isw_djbfhchggj DEBUG: _find_set: searching isw_djbfhchggj_MAIN_RAID01_1T DEBUG: _find_set: searching isw_djbfhchggj_MAIN_RAID01_1T DEBUG: _find_set: searching isw_djbfhchggj_MAIN_RAID01_1T DEBUG: _find_set: not found isw_djbfhchggj_MAIN_RAID01_1T DEBUG: _find_set: not found isw_djbfhchggj_MAIN_RAID01_1T DEBUG: _find_set: searching isw_djbfhchggj_MAIN_RAID01_1T DEBUG: _find_set: not found isw_djbfhchggj_MAIN_RAID01_1T DEBUG: _find_set: not found isw_djbfhchggj_MAIN_RAID01_1T NOTICE: added /dev/sdb to RAID set isw_djbfhchggj DEBUG: _find_set: searching isw_hbfdgdiai DEBUG: _find_set: not found isw_hbfdgdiai DEBUG: _find_set: searching isw_hbfdgdiai_RAID_0 DEBUG: _find_set: searching isw_hbfdgdiai_RAID_0 DEBUG: _find_set: searching isw_hbfdgdiai_RAID_0 DEBUG: _find_set: not found isw_hbfdgdiai_RAID_0 DEBUG: _find_set: not found isw_hbfdgdiai_RAID_0 DEBUG: _find_set: searching isw_hbfdgdiai_RAID_0 DEBUG: _find_set: searching isw_hbfdgdiai_RAID_0 DEBUG: _find_set: not found isw_hbfdgdiai_RAID_0 DEBUG: _find_set: not found isw_hbfdgdiai_RAID_0 DEBUG: _find_set: searching isw_hbfdgdiai_RAID_0 DEBUG: _find_set: not found isw_hbfdgdiai_RAID_0 DEBUG: _find_set: not found isw_hbfdgdiai_RAID_0 NOTICE: added /dev/sda to RAID set isw_hbfdgdiai DEBUG: checking isw device /dev/sdc DEBUG: checking isw device /dev/sdd DEBUG: set status of set isw_jejghfiaa_RAID1 to 16 DEBUG: set status of set isw_jejghfiaa to 16 DEBUG: checking isw device /dev/sdb ERROR:
[Bug 219393] Re: ich9R raid array not detected
You re not alone, I have the same problem. The raid was correctly detected with dmraid R13 but not usable (there was no device for the partition). The R14 fixed this problem but now, only 1 disk is detected by the raid and dmraid seems broken the raid. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I tried that the first time I saw this happen, because the offline member message when I rebooted made me think the raid had been broken by dmraid. On a later attempt, (when I actually had some data on that array to test) I tried a cold boot, and both Windows and the bios recognized the array as being healthy, with all data intact. (This array is on a new build, and it had always been built from scratch using this same board/bios) I'm willing to rebuild again to help figure this out, but only if there's a different method to try, as right now it would involve moving around a lot of data. For some reason, what dmraid sees as broken, Intel's windows driver thinks is just fine, with both disks participating in the mirror and healthy. This is what makes me think that either Intel has changed the way it marks these RAIDs, or perhaps the chipset driver is slightly off, so that it reads these incorrectly. I *have* rebuilt this array more than once, so it *could* be reading one of those sets of info from an earlier attempt, but it threw up the same error after the very first build, and these were brand new drives at that point. There was another bug with the ethernet controller on this board that caused Windows to turn the controller off on shutdown, and the ubuntu driver did not know how to turn it back on, so you needed to enable wake on lan in Windows or do a cold boot to turn ethernet back on. The first part of this bug seems almost like that in reverse, with the disks being offline after a warm boot from ubuntu. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
It looks like Intel has some bugs. Looking closely at the data, both disks disagree on the size of the primary disk. It looks like the bios may have a bug when creating the array which causes it to record the size incorrectly in one of the disks, which results in the family signature being different on both disks, and the windows driver apparently doesn't bother to verify that they match as they should. Try updating your bios and recreating the array. If that doesn't help, you may need to file a bug report with Intel. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I have the same problem, won't recognize he RAID 1 array on my ICH9R, (Intel X48, Gigabyte X48T-DQ6) warm reboot gives member offline for both member disks, but a cold reboot restores them to normal operational status. Using 8.04 Live CD. This RAID works fine under Windows. A similar problem is discussed in this thread: http://osdir.com/ml/linux.ataraid/2007-09/msg00019.html Here's my info, let me know if anything else would be useful: [EMAIL PROTECTED]:~$ sudo dmraid -ay ERROR: isw device for volume RAID broken on /dev/sdc in RAID set isw_bfhebdcdbd_RAID ERROR: isw: wrong # of devices in RAID set isw_bfhebdcdbd_RAID [1/2] on /dev/sdc ERROR: isw device for volume RAID broken on /dev/sdb in RAID set isw_cajggdbbad_RAID ERROR: isw: wrong # of devices in RAID set isw_cajggdbbad_RAID [1/2] on /dev/sdb ERROR: no mapping possible for RAID set isw_bfhebdcdbd_RAID ERROR: no mapping possible for RAID set isw_cajggdbbad_RAID [EMAIL PROTECTED]:~$ sudo dmraid -b /dev/sdc:976773168 total, 9QM0KAPS /dev/sdb:976773168 total, 9QM0K9QQ /dev/sda:488397168 total, 9SF03FRH # sda is my boot disk, and is not a member of the RAID [EMAIL PROTECTED]:~$ sudo dmraid -n /dev/sdc (isw): 0x000 sig: Intel Raid ISM Cfg Sig. 1.1.00 0x020 check_sum: 1693590363 0x024 mpb_size: 480 0x028 family_num: 1574132313 0x02c generation_num: 4466 0x030 reserved[0]: 4080 0x034 reserved[1]: 2147483648 0x038 num_disks: 2 0x039 num_raid_devs: 1 0x03a fill[0]: 2 0x03b fill[1]: 0 0x040 filler[1]: 1574132313 0x0d8 disk[0].serial: 9QM0K9QQ 0x0e8 disk[0].totalBlocks: 976771055 0x0ec disk[0].scsiId: 0x2 0x0f0 disk[0].status: 0x53a 0x108 disk[1].serial: 9QM0KAPS 0x118 disk[1].totalBlocks: 976773168 0x11c disk[1].scsiId: 0x3 0x120 disk[1].status: 0x53a 0x138 isw_dev[0].volume: RAID 0x14c isw_dev[0].SizeHigh: 0 0x148 isw_dev[0].SizeLow: 976764928 0x150 isw_dev[0].status: 0xc 0x154 isw_dev[0].reserved_blocks: 0 0x158 isw_dev[0].filler[0]: 1900544 0x190 isw_dev[0].vol.migr_state: 0 0x191 isw_dev[0].vol.migr_type: 0 0x192 isw_dev[0].vol.dirty: 0 0x193 isw_dev[0].vol.fill[0]: 255 0x1a8 isw_dev[0].vol.map.pba_of_lba0: 0 0x1ac isw_dev[0].vol.map.blocks_per_member: 976765192 0x1b0 isw_dev[0].vol.map.num_data_stripes: 3815488 0x1b4 isw_dev[0].vol.map.blocks_per_strip: 128 0x1b6 isw_dev[0].vol.map.map_state: 0 0x1b7 isw_dev[0].vol.map.raid_level: 1 0x1b8 isw_dev[0].vol.map.num_members: 2 0x1b9 isw_dev[0].vol.map.reserved[0]: 2 0x1ba isw_dev[0].vol.map.reserved[1]: 255 0x1bb isw_dev[0].vol.map.reserved[2]: 1 0x1d8 isw_dev[0].vol.map.disk_ord_tbl[0]: 0x0 0x1dc isw_dev[0].vol.map.disk_ord_tbl[1]: 0x1 /dev/sdb (isw): 0x000 sig: Intel Raid ISM Cfg Sig. 1.1.00 0x020 check_sum: 2738587652 0x024 mpb_size: 480 0x028 family_num: 2096631103 0x02c generation_num: 6 0x030 reserved[0]: 4080 0x034 reserved[1]: 2147483648 0x038 num_disks: 2 0x039 num_raid_devs: 1 0x03a fill[0]: 2 0x03b fill[1]: 0 0x040 filler[1]: 2096631103 0x0d8 disk[0].serial: 9QM0K9QQ 0x0e8 disk[0].totalBlocks: 976773168 0x0ec disk[0].scsiId: 0x2 0x0f0 disk[0].status: 0x13a 0x108 disk[1].serial: 9QM0KAPS 0x118 disk[1].totalBlocks: 976773168 0x11c disk[1].scsiId: 0x3 0x120 disk[1].status: 0x13a 0x138 isw_dev[0].volume: RAID 0x14c isw_dev[0].SizeHigh: 0 0x148 isw_dev[0].SizeLow: 976766976 0x150 isw_dev[0].status: 0xc 0x154 isw_dev[0].reserved_blocks: 0 0x158 isw_dev[0].filler[0]: 1900544 0x190 isw_dev[0].vol.migr_state: 0 0x191 isw_dev[0].vol.migr_type: 0 0x192 isw_dev[0].vol.dirty: 0 0x193 isw_dev[0].vol.fill[0]: 255 0x1a8 isw_dev[0].vol.map.pba_of_lba0: 0 0x1ac isw_dev[0].vol.map.blocks_per_member: 976767240 0x1b0 isw_dev[0].vol.map.num_data_stripes: 3815496 0x1b4 isw_dev[0].vol.map.blocks_per_strip: 128 0x1b6 isw_dev[0].vol.map.map_state: 0 0x1b7 isw_dev[0].vol.map.raid_level: 1 0x1b8 isw_dev[0].vol.map.num_members: 2 0x1b9 isw_dev[0].vol.map.reserved[0]: 2 0x1ba isw_dev[0].vol.map.reserved[1]: 255 0x1bb isw_dev[0].vol.map.reserved[2]: 1 0x1d8 isw_dev[0].vol.map.disk_ord_tbl[0]: 0x0 0x1dc isw_dev[0].vol.map.disk_ord_tbl[1]: 0x1 [EMAIL PROTECTED]:~$ -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
The two disks appear to not be part of the same raid set. Try deleting and recreating the raid set in the bios utility. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
** Changed in: dmraid (Ubuntu) Assignee: (unassigned) = Phillip Susi (psusi) Status: New = In Progress -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
In fact, it seems to be coming from somethingis else. If I simply boot from the live cd and reboot, my raid 0 disk is marked as failed and the raid 1 as degraded. After a cold reboot, the raid 0 is OK and the raid 1 marked as degraded. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
