[Bug 406460] New: Can setup RAID5 with 2.7TB in yast, but system crashed during creation
https://bugzilla.novell.com/show_bug.cgi?id=406460 Summary: Can setup RAID5 with 2.7TB in yast, but system crashed during creation Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Joachim.Reichelt@helmholtz-hzi.de QAContact: jsrain@novell.com Found By: --- I can create in yast2 a raid5 from 5 750GB HDs. But when I start creation thge system immideately crashes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 User Joachim.Reichelt@helmholtz-hzi.de added comment https://bugzilla.novell.com/show_bug.cgi?id=406460#c1 --- Comment #1 from Joachim Reichelt <Joachim.Reichelt@helmholtz-hzi.de> 2008-07-04 04:46:50 MDT --- test: /dev/i2o/hd[abcde] Partitions created. # fdisk -l /dev/i2o/hda Platte /dev/i2o/hda: 750.1 GByte, 750156341760 Byte 255 Köpfe, 63 Sektoren/Spuren, 91201 Zylinder Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes Disk identifier: 0x0000f897 Gerät boot. Anfang Ende Blöcke Id System /dev/i2o/hda1 1 26109 209720511 fd Linux raid autodetect remote login: # mdadm --create /dev/md1 /dev/i2o/hd*1 mdadm: /dev/md1 has been started with 4 drives (out of 5) and 1 spare. -> kernel panic interrupt: i2o_pci_interrupt i2o_core ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 User martin.lasarsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406460#c2 --- Comment #2 from Martin Lasarsch <martin.lasarsch@novell.com> 2008-07-04 18:27:01 MDT --- got 4x 1TB drives and tried raid5 with 11.0 32 bit in YaST during installation, works for me (it started to format the raid). So it seems that the size is not the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 User rvojcik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406460#c3 Robert Vojcik <rvojcik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Joachim.Reichelt@helmholtz-hzi.de --- Comment #3 from Robert Vojcik <rvojcik@novell.com> 2008-07-15 09:44:05 MDT --- Hello, could you provide yast2 logs after yast crash ? If you are unsure how to obtain it follow: http://en.opensuse.org/Bugs/YaST Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406460#c5 Michal Zugec <mzugec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Joachim.Reichelt@helmholtz-hzi.de --- Comment #5 from Michal Zugec <mzugec@novell.com> 2008-07-16 08:23:22 MDT --- set back NEEDINFO (YaST logs) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 User Joachim.Reichelt@helmholtz-hzi.de added comment https://bugzilla.novell.com/show_bug.cgi?id=406460#c6 Joachim Reichelt <Joachim.Reichelt@helmholtz-hzi.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Component|YaST2 |X11 3rd Party Driver Info Provider|Joachim.Reichelt@helmholtz-hzi.de | --- Comment #6 from Joachim Reichelt <Joachim.Reichelt@helmholtz-hzi.de> 2008-07-25 13:47:49 MDT --- I cannot get the logs, as the system frezes immideately. This seems to be a controller related problem. It is a Promise SX6000. There were some mails on it on the kernel mailing list. I can use mdadm to crash the system. So it is NOT A YAST problem! It took some days to find it. It is a kernel/hardware problem. So change the component to kernel? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 Arvin Schnell <aschnell@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@novell.com AssignedTo|yast2-maintainers@suse.de |bnc-team-screening@forge.provo.novell.com Component|X11 3rd Party Driver |Kernel QAContact|jsrain@novell.com |qa@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 Robert Vojcik <rvojcik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 User lmb@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406460#c7 Lars Marowsky-Bree <lmb@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Joachim.Reichelt@helmholtz-hzi.de --- Comment #7 from Lars Marowsky-Bree <lmb@novell.com> 2008-07-30 07:32:27 MDT --- We cannot debug this without the kernel panic logs. You can use a serial console to capture it, or take a screenshot if need be, but we really need it to be able to debug this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406460#c8 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com --- Comment #8 from Jeff Mahoney <jeffm@novell.com> 2008-08-08 11:19:44 MDT --- Prior to running the mdadm command to cause the panic, please run "klogconsole -r0 -l8" so that kernel messages will be output to the current console. As Lars said, a serial console capture would be ideal, but a photo will do in a pinch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 User Joachim.Reichelt@helmholtz-hzi.de added comment https://bugzilla.novell.com/show_bug.cgi?id=406460#c9 Joachim Reichelt <Joachim.Reichelt@helmholtz-hzi.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|Joachim.Reichelt@helmholtz-hzi.de | --- Comment #9 from Joachim Reichelt <Joachim.Reichelt@helmholtz-hzi.de> 2008-08-22 00:12:46 MDT --- Created an attachment (id=234847) --> (https://bugzilla.novell.com/attachment.cgi?id=234847) Hyperterm LOG from serial Console I booted the system, created the RAID with mdadm --create and than crashed the system with mdadm --assamble This is strongly related to the SX6000 controller. Same disks but two dumb PCI/ATA controller and the one on the MB and all is fine! I got the 2.7TB up and running using YAST. So we should change the subject reflecting this. I had to remove the controller as we need this system urgent. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 Joachim Reichelt <Joachim.Reichelt@helmholtz-hzi.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Can setup RAID5 with 2.7TB in yast, but system |Can setup RAID5 with 2.7TB on Promise SX6000 |crashed during creation | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406460#c10 --- Comment #10 from Jeff Mahoney <jeffm@novell.com> 2008-08-25 13:31:06 MDT --- Thanks. Here's the important bit: Oops: 0002 [#1] SMP last sysfs file: /sys/devices/virtual/block/md0/md/array_state Modules linked in: raid456 async_xor async_memcpy async_tx xor iptable_filter ip_tables ip6_tables x_tables microcode firmware_class snd_pcm_oss snd_mixer_oss snd_seq_midi snd_seq_midi_event snd_opl3_synth snd_seq_midi_emul snd_seq fuse loop dm_mod ppdev parport_pc parport rtc_cmos rtc_core rtc_lib snd_cmipci gameport snd_pcm snd_page_alloc snd_opl3_lib snd_timer snd_hwdep ohci1394 snd_mpu401_uart via_rhine e100 ieee1394 mii snd_rawmidi snd_seq_device snd soundcore iTCO_wdt iTCO_vendor_support button i2c_i801 intel_agp shpchp sr_mod i2c_core cdrom pci_hotplug agpgart sg sd_mod ehci_hcd uhci_hcd usbcore i2o_block i2o_core edd ext3 mbcache jbd fan ide_generic ata_piix libata scsi_mod dock pdc202xx_new ide_core thermal processor Pid: 0, comm: swapper Tainted: G N (2.6.25.5-1.1-pae #1) EIP: 0060:[<f905bdb0>] EFLAGS: 00010016 CPU: 0 EIP is at i2o_block_reply+0xd2/0x11a [i2o_block] EAX: 00200200 EBX: 00000246 ECX: f605b580 EDX: 00100100 ESI: f7cb6e00 EDI: 00000000 EBP: c048deec ESP: c048ded4 DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Process swapper (pid: 0, ti=c048c000 task=c044f3a0 task.ti=c048c000) Stack: f770ece0 f7c10200 f605b580 f7cb6e00 f905bcde 00000000 c048df10 f910b538 37cb6e00 f7738400 f905dd9c 003d0900 37cb6e00 f7738400 00000000 c048df20 f910c796 f7c10800 00000000 c048df38 c0154fd8 00000017 c0481a00 00000017 Call Trace: [<f910b538>] i2o_driver_dispatch+0x199/0x1a8 [i2o_core] [<f910c796>] i2o_pci_interrupt+0x25/0x43 [i2o_core] [<c0154fd8>] handle_IRQ_event+0x2a/0x5a [<c0155e58>] handle_fasteoi_irq+0x7b/0xaf [<c010830c>] do_IRQ+0x71/0x89 [<c0106a33>] common_interrupt+0x23/0x30 [<c0116b0b>] native_safe_halt+0x5/0x7 [<c0104a99>] default_idle+0x46/0x7d [<c0104a33>] cpu_idle+0xa0/0xc0 [<c02d7301>] rest_init+0x49/0x4b [<c04938a0>] start_kernel+0x32a/0x332 ======================= Code: e8 b9 9a 17 c7 8b 55 e8 8b 82 3c 01 00 00 e8 5f 8a 28 c7 83 7d ec 00 89 c3 74 22 8b 4d ec ff 49 14 8b 45 f0 8b 10 89 c1 8b 40 04 <89> 42 04 89 10 c7 41 04 00 02 20 00 c7 01 00 01 10 00 8b 45 e8 EIP: [<f905bdb0>] i2o_block_reply+0xd2/0x11a [i2o_block] SS:ESP 0068:c048ded4 Kernel panic - not syncing: Fatal exception in interrupt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |hare@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=406460 User hare@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406460#c11 Hannes Reinecke <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #11 from Hannes Reinecke <hare@novell.com> 2008-08-26 03:19:53 MDT --- The I2O protocol itself is only specified for 32 bit. So I'd be surprised if this would work. And consequently I doubt we can ever support more than 2T on this adapter. We have a hard enough time converting the driver to 64 bits ... Sorry, but there is not much we can do here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com