Post Reply
Pi_almighty
Posts: 14
Joined: Sun Aug 26, 2012 3:19 pm

Problem with a freezing ext-hdd

Sat Mar 02, 2013 5:50 pm

Hi,

I have an 1TB WD elements usb-hdd formatted as ext-4 plugged to my raspberry pi and it works perfectly. I also have a Lacie 2TB usb-hdd formatted as ext-4 which I would like to start using. Both are mounted with identical parameters, both are externally powered and connected straight to Pi without a hub.

For some reason the Lacie hangs at some point when copying files to it while the other drive has never suffered from the same problem. I'm a bit confused why only one of the drives is unusable while the other one has worked just fine for months. The problem is repeatable with either WD hdd connected or not. Syslog seems to be giving some hints to what is happening but I can't make anything of it:

Code: Select all

Mar  2 18:00:14 raspberrypi kernel: [  259.178332] usb 1-1.2: new high-speed USB device number 5 using dwc_otg
Mar  2 18:00:14 raspberrypi kernel: [  259.350761] usb 1-1.2: New USB device found, idVendor=059f, idProduct=1053
Mar  2 18:00:14 raspberrypi kernel: [  259.350792] usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Mar  2 18:00:14 raspberrypi kernel: [  259.350808] usb 1-1.2: Product: P'9230 Desktop Drive
Mar  2 18:00:14 raspberrypi kernel: [  259.350822] usb 1-1.2: Manufacturer: LaCie
Mar  2 18:00:14 raspberrypi kernel: [  259.350834] usb 1-1.2: SerialNumber: 00000000e4bc07882009
Mar  2 18:00:14 raspberrypi kernel: [  259.367864] scsi1 : usb-storage 1-1.2:1.0
Mar  2 18:00:21 raspberrypi kernel: [  266.840159] scsi 1:0:0:0: Direct-Access     ST2000DM 001-9YN164       CC4B PQ: 0 ANSI: 5
Mar  2 18:00:21 raspberrypi kernel: [  266.846578] sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Mar  2 18:00:21 raspberrypi kernel: [  266.847688] sd 1:0:0:0: [sdb] Write Protect is off
Mar  2 18:00:21 raspberrypi kernel: [  266.847723] sd 1:0:0:0: [sdb] Mode Sense: 23 00 00 00
Mar  2 18:00:21 raspberrypi kernel: [  266.850613] sd 1:0:0:0: [sdb] No Caching mode page present
Mar  2 18:00:21 raspberrypi kernel: [  266.850649] sd 1:0:0:0: [sdb] Assuming drive cache: write through
Mar  2 18:00:21 raspberrypi kernel: [  266.855195] sd 1:0:0:0: [sdb] No Caching mode page present
Mar  2 18:00:21 raspberrypi kernel: [  266.855230] sd 1:0:0:0: [sdb] Assuming drive cache: write through
Mar  2 18:00:21 raspberrypi kernel: [  266.885112]  sdb: sdb1 < sdb5 >
Mar  2 18:00:21 raspberrypi kernel: [  266.890222] sd 1:0:0:0: [sdb] No Caching mode page present
Mar  2 18:00:21 raspberrypi kernel: [  266.890259] sd 1:0:0:0: [sdb] Assuming drive cache: write through
Mar  2 18:00:21 raspberrypi kernel: [  266.890277] sd 1:0:0:0: [sdb] Attached SCSI disk
Mar  2 18:01:22 raspberrypi kernel: [  327.143136] EXT4-fs (sdb5): recovery complete
Mar  2 18:01:22 raspberrypi kernel: [  327.143988] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null)
Mar  2 18:16:28 raspberrypi kernel: [ 1233.634860] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:17:01 raspberrypi /USR/SBIN/CRON[3943]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar  2 18:18:56 raspberrypi kernel: [ 1381.449820] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:24:49 raspberrypi kernel: [ 1734.152623] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:25:08 raspberrypi kernel: [ 1754.033441] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:25:18 raspberrypi kernel: [ 1763.453708] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:25:37 raspberrypi kernel: [ 1782.174510] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:25:38 raspberrypi kernel: [ 1783.434437] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:25:53 raspberrypi kernel: [ 1798.675130] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:26:01 raspberrypi kernel: [ 1806.495305] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:26:28 raspberrypi kernel: [ 1834.006423] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:26:30 raspberrypi kernel: [ 1835.326479] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:26:52 raspberrypi kernel: [ 1857.907285] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:26:54 raspberrypi kernel: [ 1859.507375] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:26:55 raspberrypi kernel: [ 1860.347378] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:27:00 raspberrypi kernel: [ 1865.997649] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:27:10 raspberrypi kernel: [ 1875.657946] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:27:12 raspberrypi kernel: [ 1878.008652] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:27:25 raspberrypi kernel: [ 1890.268455] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:27:26 raspberrypi kernel: [ 1891.998556] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:28:11 raspberrypi kernel: [ 1936.340205] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278548] INFO: task flush-8:16:3901 blocked for more than 120 seconds.
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278574] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278587] flush-8:16      D c03983e8     0  3901      2 0x00000000
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278691] [<c03983e8>] (__schedule+0x2c4/0x5b0) from [<c0162fe4>] (do_get_write_access+0x24c/0x458)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278727] [<c0162fe4>] (do_get_write_access+0x24c/0x458) from [<c016333c>] (jbd2_journal_get_write_access+0x24/0x38)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278785] [<c016333c>] (jbd2_journal_get_write_access+0x24/0x38) from [<c0150244>] (__ext4_journal_get_write_access+0x2c/0x68)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278824] [<c0150244>] (__ext4_journal_get_write_access+0x2c/0x68) from [<c0156264>] (ext4_mb_mark_diskspace_used+0x5c/0x438)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278855] [<c0156264>] (ext4_mb_mark_diskspace_used+0x5c/0x438) from [<c0157644>] (ext4_mb_new_blocks+0x260/0x4f4)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278897] [<c0157644>] (ext4_mb_new_blocks+0x260/0x4f4) from [<c014e81c>] (ext4_ext_map_blocks+0x9b8/0x1354)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278939] [<c014e81c>] (ext4_ext_map_blocks+0x9b8/0x1354) from [<c013355c>] (ext4_map_blocks+0x184/0x330)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278970] [<c013355c>] (ext4_map_blocks+0x184/0x330) from [<c0137378>] (mpage_da_map_and_submit+0x90/0x5f8)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.278999] [<c0137378>] (mpage_da_map_and_submit+0x90/0x5f8) from [<c0138010>] (ext4_da_writepages+0x294/0x43c)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279044] [<c0138010>] (ext4_da_writepages+0x294/0x43c) from [<c00979cc>] (do_writepages+0x24/0x38)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279086] [<c00979cc>] (do_writepages+0x24/0x38) from [<c00e3f58>] (__writeback_single_inode.isra.20+0x28/0x11c)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279117] [<c00e3f58>] (__writeback_single_inode.isra.20+0x28/0x11c) from [<c00e4280>] (writeback_sb_inodes+0x234/0x40c)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279156] [<c00e4280>] (writeback_sb_inodes+0x234/0x40c) from [<c00e44c8>] (__writeback_inodes_wb+0x70/0xac)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279184] [<c00e44c8>] (__writeback_inodes_wb+0x70/0xac) from [<c00e46e0>] (wb_writeback+0x1dc/0x204)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279210] [<c00e46e0>] (wb_writeback+0x1dc/0x204) from [<c00e514c>] (wb_do_writeback+0x1e8/0x1fc)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279237] [<c00e514c>] (wb_do_writeback+0x1e8/0x1fc) from [<c00e51dc>] (bdi_writeback_thread+0x7c/0x150)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279285] [<c00e51dc>] (bdi_writeback_thread+0x7c/0x150) from [<c003a7b0>] (kthread+0x88/0x94)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279325] [<c003a7b0>] (kthread+0x88/0x94) from [<c000e9fc>] (kernel_thread_exit+0x0/0x8)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279343] INFO: task jbd2/sdb5-8:3902 blocked for more than 120 seconds.
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279352] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279362] jbd2/sdb5-8     D c03983e8     0  3902      2 0x00000000
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279425] [<c03983e8>] (__schedule+0x2c4/0x5b0) from [<c0398c70>] (io_schedule+0x88/0xe4)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279468] [<c0398c70>] (io_schedule+0x88/0xe4) from [<c008e0d4>] (sleep_on_page+0x8/0x10)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279499] [<c008e0d4>] (sleep_on_page+0x8/0x10) from [<c0397280>] (__wait_on_bit+0x7c/0xb4)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279543] [<c0397280>] (__wait_on_bit+0x7c/0xb4) from [<c008e2f8>] (wait_on_page_bit+0xa0/0xb8)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279572] [<c008e2f8>] (wait_on_page_bit+0xa0/0xb8) from [<c008e438>] (filemap_fdatawait_range+0xd8/0x150)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279599] [<c008e438>] (filemap_fdatawait_range+0xd8/0x150) from [<c008e514>] (filemap_fdatawait+0x64/0x7c)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279630] [<c008e514>] (filemap_fdatawait+0x64/0x7c) from [<c016452c>] (jbd2_journal_commit_transaction+0xa34/0x18bc)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279676] [<c016452c>] (jbd2_journal_commit_transaction+0xa34/0x18bc) from [<c0168430>] (kjournald2+0xbc/0x298)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279711] [<c0168430>] (kjournald2+0xbc/0x298) from [<c003a7b0>] (kthread+0x88/0x94)
Mar  2 18:31:56 raspberrypi kernel: [ 2161.279742] [<c003a7b0>] (kthread+0x88/0x94) from [<c000e9fc>] (kernel_thread_exit+0x0/0x8)
Mar  2 18:33:56 raspberrypi kernel: [ 2281.283208] INFO: task flush-8:16:3901 blocked for more than 120 seconds.
Mar  2 18:33:56 raspberrypi kernel: [ 2281.283234] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
After a few tries the log starts filling with these:

Code: Select all

Mar  2 19:10:09 raspberrypi kernel: [ 4454.297918] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 19:10:09 raspberrypi kernel: [ 4454.469363] sd 1:0:0:0: [sdb] Unhandled error code
Mar  2 19:10:09 raspberrypi kernel: [ 4454.469397] sd 1:0:0:0: [sdb]
Mar  2 19:10:09 raspberrypi kernel: [ 4454.469411] Result: hostbyte=0x07 driverbyte=0x00
Mar  2 19:10:09 raspberrypi kernel: [ 4454.469437] sd 1:0:0:0: [sdb] CDB:
Mar  2 19:10:09 raspberrypi kernel: [ 4454.469449] cdb[0]=0x2a: 2a 00 96 8f 2a 00 00 00 f0 00
Mar  2 19:10:09 raspberrypi kernel: [ 4454.470025] EXT4-fs warning (device sdb5): ext4_end_bio:250: I/O error writing to inode 315719712 (offset 2580480 size 126976 starting block 31574560)
Mar  2 19:20:46 raspberrypi kernel: [ 5091.593510] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Mar  2 19:20:46 raspberrypi kernel: [ 5091.764945] sd 1:0:0:0: [sdb] Unhandled error code
Mar  2 19:20:46 raspberrypi kernel: [ 5091.764978] sd 1:0:0:0: [sdb]
Mar  2 19:20:46 raspberrypi kernel: [ 5091.764990] Result: hostbyte=0x07 driverbyte=0x00
Mar  2 19:20:46 raspberrypi kernel: [ 5091.765018] sd 1:0:0:0: [sdb] CDB:
Mar  2 19:20:46 raspberrypi kernel: [ 5091.765030] cdb[0]=0x2a: 2a 00 96 8f 2a f0 00 00 f0 00
Mar  2 19:20:46 raspberrypi kernel: [ 5091.765603] EXT4-fs warning (device sdb5): ext4_end_bio:250: I/O error writing to inode 315719712 (offset 2703360 size 126976 starting block 31574560)
I'm using Raspbian with kernel

Code: Select all

Linux raspberrypi 3.6.11+ #377 PREEMPT Sat Feb 16 17:31:02 GMT 2013 armv6l GNU/Linux
Anyone out there with a good idea from where to start?
User avatar
malakai
Posts: 1382
Joined: Sat Sep 15, 2012 10:35 am
Contact: Website

Re: Problem with a freezing ext-hdd

Sat Mar 02, 2013 6:07 pm

I found this and they had a very similar issue as your having both with Lacie drives

http://www.raspberrypi.org/phpBB3/viewt ... ie#p241286 in the end they formatted it differently not sure if it helps but seems strange how similar your setups seem to be.
http://www.raspians.com - always looking for content feel free to ask to have it posted. Or sign up and message me to become a contributor to the site. Raspians is not affiliated with the Raspberry Pi Foundation. (RPi's + You = Raspians)
User avatar
PeterO
Posts: 5877
Joined: Sun Jul 22, 2012 4:14 pm

Re: Problem with a freezing ext-hdd

Sat Mar 02, 2013 6:10 pm

Code: Select all

Mar  2 19:10:09 raspberrypi kernel: [ 4454.297918] usb 1-1.2: reset high-speed USB device number 5 using dwc_otg
Its a USB problem, nothing to do with how the disk is formatted !
PeterO
Discoverer of the PI2 XENON DEATH FLASH!
Interests: C,Python,PIC,Electronics,Ham Radio (G0DZB),1960s British Computers.
"The primary requirement (as we've always seen in your examples) is that the code is readable. " Dougie Lawson
User avatar
malakai
Posts: 1382
Joined: Sat Sep 15, 2012 10:35 am
Contact: Website

Re: Problem with a freezing ext-hdd

Sat Mar 02, 2013 6:17 pm

I was wondering about the USB as well if it's a 3.0 drive that has support for 2.0 I wonder if that could be an issue. Just seems weird one drive works without issue other drive has issues to me that points to the drive having issues as being the problem in some way. Be it format, internal architecture, or maybe even a failing drive.
http://www.raspians.com - always looking for content feel free to ask to have it posted. Or sign up and message me to become a contributor to the site. Raspians is not affiliated with the Raspberry Pi Foundation. (RPi's + You = Raspians)
Pi_almighty
Posts: 14
Joined: Sun Aug 26, 2012 3:19 pm

Re: Problem with a freezing ext-hdd

Mon Mar 04, 2013 8:04 pm

malakai wrote:I was wondering about the USB as well if it's a 3.0 drive that has support for 2.0 I wonder if that could be an issue. Just seems weird one drive works without issue other drive has issues to me that points to the drive having issues as being the problem in some way. Be it format, internal architecture, or maybe even a failing drive.
I was a bit reluctant to believe there could be anything wrong with the drive itself because it's fairly new. I know I'm its second owner because I bought it as a customer return from a reputable shop's outlet. After testing it on my windows pc I'm now certain my problems were caused by a faulty hard drive. I have requested for a warranty replacement/refund.
Post Reply

Return to “Troubleshooting”