Skip to contentSkip to conversation

Bug during media scan, k ernel 2.4.23-pre9

3ware.com #1741 Stephan von Krawczynski 1 participant 1 message Nov 3, 2003

lore
Share & tools
lore
#0 lore raw
Quoted 43 lines · On Mon, 3 Nov 2003 14:16:15 -0800 "Tom Tran via RT"…
Quoted 9 lines

-----Original Message-----
From: Stephan von Krawczynski [mailto:[email protected]]
Sent: Monday, November 03, 2003 9:47 AM
To: Linux
Cc:
Subject: Bug during media scan, kernel 2.4.23-pre9

Quoted 4 lines

Hello,

I just encountered a real bad problem with using media scan on 3ware controllers. I have 3 hds connected and configured a RAID5. I use

media scan

Quoted 3 lines

regularly (daily basis). Since two days I see this problem:

Nov  3 18:12:11 box 3w-xxxx[2039]: INFORMATION: Verify started on 

unit 0 on

Quoted 2 lines

controller ID:2. (0x29)

Nov  3 18:19:41 box kernel: 3w-xxxx: scsi2: Unit #0: Command 

(f6e5d800)

Quoted 5 lines

timed
out, resetting card.

After that the box has problems, the controller obviously hangs. This in itself can be considered a bug, but what is really annoying

is that

Quoted 3 lines

one
has no chance finding out _which_ port caused the problem. So at this point you can play roulette and replace one of the hds

hoping

Quoted 4 lines

that
it was indeed the bad one.

It would be really a lot better to degrade the unit in this case and

give a

Quoted 7 lines

hint which port has problems (command timed out on port ...). This would:
a) not hang the box
b) give you a chance to replace the hd, as you would expect in RAID5

The current situation is absolutely _no good_.

Quoted 7 lines
Quoted 2 lines

Regards,
Stephan

What motherboard do you have? Does your motherboard bios has an option called "APIC" ? Disable APIC MODE if it is enabled.

Sorry to say that: this setup works since months. It has already showed correct RAID5 "dropouts" (hd failures, replacements etc). My problem is not that it does not work or does hang. Sure this is not nice, but the absolute bug is really _only_ that there is no information about the _cause_ (port) of the failure. This has nothing to do with apic or not, it is a simple lack of output information.

Quoted 3 lines

If the problems persist, please send us 3dm details, 3dm alarms page, and 3dm error log (download from 3dm ALARMS).

The problem will persist, because apic doesn't help the driver to show output. There is no other useful information in the 3dm logs. In fact the problem does not even show up there. Last reports are visible in syslog output as stated in the report.

Regards,
Stephan

PS 3ware: if you send mails for support with questions, please set a reply-address that is deliverable...