Crash when accessing LVM2 partions using SAMBA

Enyo · 02-07-2009, 04:58 PM

Hi,

i have a VIA 1.6 ghz embeded ITX NAS box, running debian etch with lvm2 and samba, using 2 ports of the onboard sata controller and 2 ports of a pci sata controller, to share 2 750gb + 2 1000gb drives as one network share.

i can fsck, and access the partion localy just fine, however when the partion is accessed through a samba share, the server randomly locks up, the video out continues to display the flashing cursor for login, but the network and any input devices stop working, so far i'm also unable to find any log messages that reference the crash, it just seems to completly lock up.

i'd post some logs, but i can't seem to find any that look relevant.

Enyo · 02-07-2009, 06:38 PM

Hi, i just managed to trigger it again and pulled this from the syslog

Code:

Feb  8 00:25:40 Kotoko kernel: hub 2-0:1.0: over-current change on port 1
Feb  8 00:25:42 Kotoko kernel: hub 2-0:1.0: connect-debounce failed, port 1 disabled
Feb  8 00:25:42 Kotoko kernel: hub 2-0:1.0: over-current change on port 2
Feb  8 00:25:42 Kotoko kernel: usb 2-2: USB disconnect, address 2
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.0: host system error, PCI problems?
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.0: host controller process error, something bad happened!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.1: host system error, PCI problems?
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.1: host controller process error, something bad happened!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.1: host controller halted, very bad!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.1: HCRESET not completed yet!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.1: HC died; cleaning up
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: host system error, PCI problems?
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: host controller process error, something bad happened!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.3: host system error, PCI problems?
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.3: host controller process error, something bad happened!
Feb  8 00:25:42 Kotoko kernel: ehci_hcd 0000:00:10.4: HC died; cleaning up
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.0: host system error, PCI problems?
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.0: host controller process error, something bad happened!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.0: host controller halted, very bad!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.0: HCRESET not completed yet!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.0: HC died; cleaning up
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: host system error, PCI problems?
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: host controller process error, something bad happened!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: host controller halted, very bad!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: HCRESET not completed yet!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: HC died; cleaning up
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: host system error, PCI problems?
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: host controller process error, something bad happened!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: host controller halted, very bad!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: HCRESET not completed yet!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.2: HC died; cleaning up
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.3: host system error, PCI problems?
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.3: host controller process error, something bad happened!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.3: host controller halted, very bad!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.3: HCRESET not completed yet!
Feb  8 00:25:42 Kotoko kernel: uhci_hcd 0000:00:10.3: HC died; cleaning up
Feb  8 00:25:42 Kotoko kernel: hub 2-0:1.0: hub_port_status failed (err = -19)
Feb  8 00:25:42 Kotoko kernel: hub 2-0:1.0: connect-debounce failed, port 2 disabled
Feb  8 00:25:42 Kotoko kernel: hub 2-0:1.0: cannot disable port 2 (err = -19)
Feb  8 00:25:43 Kotoko kernel: irq 201: nobody cared (try booting with the "irqpoll" option)
Feb  8 00:25:43 Kotoko kernel:  [<c01402a7>] __report_bad_irq+0x2b/0x69
Feb  8 00:25:43 Kotoko kernel:  [<c0140494>] note_interrupt+0x1af/0x1e7
Feb  8 00:25:43 Kotoko kernel:  [<c013fa9b>] handle_IRQ_event+0x23/0x49
Feb  8 00:25:43 Kotoko kernel:  [<c013fb74>] __do_IRQ+0xb3/0xe8
Feb  8 00:25:43 Kotoko kernel:  [<c01050e5>] do_IRQ+0x43/0x52
Feb  8 00:25:43 Kotoko kernel:  [<c01036b6>] common_interrupt+0x1a/0x20
Feb  8 00:25:43 Kotoko kernel:  [<dc8265ac>] acpi_processor_idle+0x1ec/0x380 [processor]
Feb  8 00:25:43 Kotoko kernel:  [<c0101b52>] cpu_idle+0x9f/0xb9
Feb  8 00:25:43 Kotoko kernel:  [<c03196fd>] start_kernel+0x379/0x380
Feb  8 00:25:43 Kotoko kernel: handlers:
Feb  8 00:25:43 Kotoko kernel: [<dc8c147b>] (usb_hcd_irq+0x0/0x50 [usbcore])
Feb  8 00:25:43 Kotoko last message repeated 4 times
Feb  8 00:25:43 Kotoko kernel: Disabling IRQ #201

rtspitz · 02-07-2009, 07:28 PM

When you do a short google search for "over-current change on port", you'll get some posts on linuxquestions.org referring to power supply problems possibly causing this problem.

Right at the top of your log file the system complains about a usb power malfunction. If there's nothing connected to the ports there is no other reason for it I see.

You could mount these partitions as read_only (prevents fs corruption) and do a torture test of your machine. maximize the power requirement of your machine (maybe mprime or whatever) start read tests on the disks adding disk after disk to increase the current supplied by the PSU and watch the log files. If the error pops up as soon as the machine draws more current...

Enyo · 03-23-2009, 04:03 PM

just an update on a very dead thread.. but it might be useful...

the usb reported in the logs was my testing keyboard, for some reason it likes to mention that theres a keyboard plugged in when it crashes, it still crashes when no keyboard is plugged in.

however i seem to have fixed the problem by using the fourth NIC on the ITX box, for some reason the 3 NIC daughter board is acting a bit screwy and causing systematic failures and ETH3 is the motherboards onboard NIC.

for those intrested the motherboard was a Jetway J7F2 1.5GHz C7D with a Jetway 3x LAN Motherboard Module, which is realtek branded

(3x Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169SC Gigabit Ethernet (rev 10))

and the onboard - which works - is (VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78))