https://bugzilla.novell.com/show_bug.cgi?id=775746 https://bugzilla.novell.com/show_bug.cgi?id=775746#c1 --- Comment #1 from John Langley 2012-08-13 22:35:49 UTC --- mdadm /dev/md1 --add /dev/sdb4 starts the array again and it works perfectly for hours until the next reboot. after reboot today i ended up in a shell: [ 11.263189] input: Venus USB2.0 Camera as /devices/pci0000:00/0000:00:0b.1/usb1/1-6/1-6:1.0/input/input13 [ 11.263360] usbcore: registered new interface driver uvcvideo [ 11.263363] USB Video Class driver (1.1.1) [ 11.343139] Adding 1051644k swap on /dev/sda1. Priority:0 extents:1 across:1051644k [ 11.354278] md: bind<sda4> [ 11.418756] Adding 1051644k swap on /dev/sdb1. Priority:0 extents:1 across:1051644k [ 11.515482] nvidia 0000:03:00.0: PCI INT A -> Link[APC5] -> GSI 16 (level, low) -> IRQ 16 [ 11.515492] nvidia 0000:03:00.0: setting latency timer to 64 [ 11.515498] vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [ 11.515806] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 295.59 Wed Jun 6 21:19:40 PDT 2012 [ 11.550355] md: could not open unknown-block(8,20). [ 11.550455] md: md_import_device returned -16 [ 11.550766] md: could not open unknown-block(8,20). [ 11.550857] md: md_import_device returned -16 [ 11.601393] boot.md[448]: Starting MD RAID mdadm: /dev/md/1 is already in use. [ 11.601940] boot.md[448]: ..failed [ 11.602543] systemd[1]: md.service: control process exited, code=exited status=1 [ 11.608358] systemd[1]: Unit md.service entered failed state. [ 97.101581] systemd[1]: Job dev-md1.device/start timed out. [ 97.101819] systemd[1]: Job remote-fs-pre.target/start failed with result 'dependency'. [ 97.101826] systemd[1]: Job local-fs.target/start failed with result 'dependency'. [ 97.101831] systemd[1]: Triggering OnFailure= dependencies of local-fs.target. [ 97.102766] systemd[1]: Job home.mount/start failed with result 'dependency'. [ 97.102774] systemd[1]: Job dev-md1.device/start failed with result 'timeout'. [ 97.390477] systemd[1]: Startup finished in 5s 50ms 326us (kernel) + 1min 32s 340ms 36us (userspace) = 1min 37s 390ms 362us. [ 351.569324] md/raid1:md1: active with 1 out of 2 mirrors [ 351.569509] created bitmap (4 pages) for device md1 [ 351.569729] md1: bitmap initialized from disk: read 1/1 pages, set 7 of 6701 bits [ 351.605682] md1: detected capacity change from 0 to 449637638144 [ 369.175955] md1: unknown partition table But the individual disks of the array actually were fine: /dev/sda4: Magic : a92b4efc Version : 1.0 Feature Map : 0x1 Array UUID : 909d58d0:3a4ee94e:8897cfe8:d7aefeea Name : linux-99ig:1 Creation Time : Fri Oct 21 21:36:33 2011 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 878198512 (418.76 GiB 449.64 GB) Array Size : 878198512 (418.76 GiB 449.64 GB) Super Offset : 878198768 sectors State : clean Device UUID : 82cdb9ef:19aaa29b:1d7b1d7c:ea687817 Internal Bitmap : -8 sectors from superblock Update Time : Mon Aug 13 22:46:08 2012 Checksum : d62737a5 - correct Events : 93354 Device Role : Active device 0 Array State : AA ('A' == active, '.' == missing) /dev/sdb4: Magic : a92b4efc Version : 1.0 Feature Map : 0x1 Array UUID : 909d58d0:3a4ee94e:8897cfe8:d7aefeea Name : linux-99ig:1 Creation Time : Fri Oct 21 21:36:33 2011 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 878198512 (418.76 GiB 449.64 GB) Array Size : 878198512 (418.76 GiB 449.64 GB) Super Offset : 878198768 sectors State : clean Device UUID : 46360291:b7806b6c:ce1f892e:fa56fc78 Internal Bitmap : -8 sectors from superblock Update Time : Mon Aug 13 22:46:08 2012 Checksum : 5c2809c9 - correct Events : 93354 Device Role : Active device 1 Array State : AA ('A' == active, '.' == missing) "mdadm --run /dev/md1" started the array "mdadm /dev/md1 --add /dev/sdb4" fixed the array and it works well again That the array is degraded happens only on reboot. Mostly sdb4 is missing but i also had sda4 (md1) or sda2 or sdb2 (md0) Always just one partition! -- 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=775746 https://bugzilla.novell.com/show_bug.cgi?id=775746#c2 --- Comment #2 from John Langley 2012-08-19 23:32:07 UTC --- Since my previous comment everthing works well. No problems on boot. But today my dmesg log showed this: [43299.808066] ata2: EH in SWNCQ mode,QC:qc_active 0x1 sactive 0x1 [43299.808076] ata2: SWNCQ:qc_active 0x1 defer_bits 0x0 last_issue_tag 0x0 [43299.808086] ata2: ATA_REG 0x40 ERR_REG 0x0 [43299.808090] ata2: tag : dhfis dmafis sdbfis sactive [43299.808096] ata2: tag 0x0: 1 1 0 1 [43299.808114] ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen [43299.808123] ata2.00: failed command: WRITE FPDMA QUEUED [43299.808137] ata2.00: cmd 61/01:00:e8:2f:20/00:00:05:00:00/40 tag 0 ncq 512 out [43299.808146] ata2.00: status: { DRDY } [43299.808156] ata2: hard resetting link [43299.808160] ata2: nv: skipping hardreset on occupied port [43300.262069] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [43300.265222] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [43300.265232] ata2.00: revalidation failed (errno=-5) [43305.262059] ata2: hard resetting link [43305.262068] ata2: nv: skipping hardreset on occupied port [43305.716090] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [43305.723383] ata2.00: configured for UDMA/133 [43305.723395] ata2.00: device reported invalid CHS sector 0 [43305.723409] ata2: EH complete [50448.736069] ata1: EH in SWNCQ mode,QC:qc_active 0x1 sactive 0x1 [50448.736079] ata1: SWNCQ:qc_active 0x1 defer_bits 0x0 last_issue_tag 0x0 [50448.736090] ata1: ATA_REG 0x40 ERR_REG 0x0 [50448.736094] ata1: tag : dhfis dmafis sdbfis sactive [50448.736099] ata1: tag 0x0: 1 1 0 1 [50448.736118] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen [50448.736127] ata1.00: failed command: WRITE FPDMA QUEUED [50448.736141] ata1.00: cmd 61/01:00:e8:2f:20/00:00:05:00:00/40 tag 0 ncq 512 out [50448.736150] ata1.00: status: { DRDY } [50448.736160] ata1: hard resetting link [50448.736164] ata1: nv: skipping hardreset on occupied port [50449.190060] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [50449.193226] ata1.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [50449.193237] ata1.00: revalidation failed (errno=-5) [50454.190038] ata1: hard resetting link [50454.190043] ata1: nv: skipping hardreset on occupied port [50454.644053] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [50454.650338] ata1.00: configured for UDMA/133 [50454.650352] ata1: EH complete -- 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=775746 https://bugzilla.novell.com/show_bug.cgi?id=775746#c6 --- Comment #6 from John Langley 2012-09-08 12:54:51 UTC --- Created an attachment (id=504952) --> (http://bugzilla.novell.com/attachment.cgi?id=504952) dmesg output, hard drive not recognized In very few cases one hard drive is missing completely. I got the boot message "ata2.00: revalidation failed (errno=-19)" Please refer to attached file. The system also states that it is doing a fast boot. I don't know if this could be related? By the way, put the same hard drives in a different computer with new SATA cables and the problem persists. -- 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=775746 https://bugzilla.novell.com/show_bug.cgi?id=775746#c8 --- Comment #8 from John Langley 2012-09-13 10:50:00 UTC --- I don't think that Nvidia driver causes the problems since the other machine didn't use sata_nv. But somewhere else i read about a race condition of sata with usb driver when searching for "ata2.00: revalidation failed (errno=-19)" See also http://johnbokma.com/mexit/2008/08/05/fixing-the-vostro-hang-issue.html They suggested to force load of sata driver before usb. I will try that. -- 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=775746 https://bugzilla.novell.com/show_bug.cgi?id=775746#c9 --- Comment #9 from Joey Lee 2012-09-26 04:25:10 UTC --- Per return error from md_import_device: [ 11.550355] md: could not open unknown-block(8,20). [ 11.550455] md: md_import_device returned -16 The -16 is EBUSY that means 'Device or resource busy', looks it's a race condition. There have something grab block device before md driver. Need find a way(maybe log?) to catch which component grab it. -- 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=775746 https://bugzilla.novell.com/show_bug.cgi?id=775746#c11 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|nfbrown@suse.com |j.langley@gmx.net --- Comment #11 from Neil Brown 2012-09-26 07:32:35 UTC --- If it is a race with mdadm it can probably be fixed by adding 'udev-trigger' to the end of the line that start '# Should-Start:' in /etc/init.d/boot.md. That fixes similar problems. However the fact that it says "unknown-block(8,20)", and that we see errors like: [43299.808156] ata2: hard resetting link looks like there is some recurrent hardware issue. I thought it might be a driver issue, but maybe not. John; can you try making that change to boot.md and see if it improves the situation? It ensures that all udev triggers have fired before boot.md tries to assemble anything. -- 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=775746 https://bugzilla.novell.com/show_bug.cgi?id=775746#c13 --- Comment #13 from Joey Lee 2012-09-26 08:43:51 UTC --- (In reply to comment #12)

(In reply to comment #11)

...

If it is a race with mdadm it can probably be fixed by adding 'udev-trigger' to the end of the line that start '# Should-Start:' in /etc/init.d/boot.md.

I just checked and found the 'udev-trigger' is not in openSUSE 12.2, need use '/sbin/udevadm trigger'

And, openSUSE 12.1 also -- 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=775746 https://bugzilla.novell.com/show_bug.cgi?id=775746#c15 --- Comment #15 from John Langley 2012-10-06 16:45:15 UTC --- I put that into /etc/init.d/boot.md : # Should-Start: boot.scsidev boot.multipath udev-trigger But the problems persist. Should it read udev-trigger or udev-trigger.service ? -- 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=775746 https://bugzilla.novell.com/show_bug.cgi?id=775746#c17 --- Comment #17 from John Langley 2012-11-09 15:09:52 UTC --- Created an attachment (id=512689) --> (http://bugzilla.novell.com/attachment.cgi?id=512689) dmesg log 16.10.2012 Attached is another dmesg file, i will add 2 more later. Regarding hardware error i swapped all parts (different PC, different ATA cables) except hard disks. The errors persist. But i ordered 2 new hard disks which will arrive this week. I will inform you if the errors persist. In fact one hard disk (sda) is reporting a smartd error since some days (refer to dmesg output). Is it possible that the errors are related to the weird way i set up my raid arrays? Instead of having 1 partition per hard disk configured as raid device and the raid device partitioned for file systems - as done with hardware raids, i did it the other way round: Each hard disk with 4 patitions and only (sda2,sdb2) or (sda4,sdb4) respectively is assembled to an raid array: (sda2,sdb2)=>md0, (sda4,sdb4)=>md1 Device Boot Start End Blocks Id System /dev/sda1 2048 2105343 1051648 82 Linux swap / Solaris /dev/sda2 * 2105344 85995519 41945088 fd Linux raid autodetect /dev/sda3 85995520 98574335 6289408 a0 IBM Thinkpad hibernation /dev/sda4 98574336 976773119 439099392 fd Linux raid autodetect -- 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=775746 https://bugzilla.novell.com/show_bug.cgi?id=775746#c19 --- Comment #19 from John Langley 2012-11-09 15:12:01 UTC --- Created an attachment (id=512691) --> (http://bugzilla.novell.com/attachment.cgi?id=512691) dmesg output 8.11.2012 -- 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=775746 https://bugzilla.novell.com/show_bug.cgi?id=775746#c21 Jeffrey Cheung changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED CC| |jcheung@suse.com InfoProvider|j.langley@gmx.net | Resolution| |WONTFIX --- Comment #21 from Jeffrey Cheung 2014-02-07 03:53:20 UTC --- With the release of the gnumeric on January 27th, 2014 the SUSE sponsored maintenance of openSUSE 12.2 has ended. openSUSE 12.2 is now officially discontinued and out of support by SUSE. The bug was created againist openSUSE 12.1, thus closed for WONTFIX. -- 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.