PI B+ with an external Seagate 2TB disc drive connected up via USB,
drive formatted as EXT4.  This has happily been running for several
years,

Today is Monday.

Late on Saturday night, accessing the drive became impossible, basic
commands (ls, rm du) would hang indefinitely.

Having been out for most of the day yesterday, it was late afternoon
before I was able to look at it.  It was clear that some files had been
added to the disc, but not everything that I would expect, and soon
after I started to look at it, it started to hang again, so I tried to
reboot it.  /var/log/messages shows that the reboot command was issued
at 17:20.  At 17:44, there is an entry to say that "nfsd: last server
has exited, flushing export cache". At 18:17, the boot process appears
to start, this takes about 10 seconds.

This morning I logged in briefly, and all appeared to be well, files
were written to it overnight, and during the day.  This afternoon, I
logged in again to see if I could work out what had happened, and at
around that time, error messages started to appear :


May  1 14:39:35 ffoilpi1 kernel: [67009.943117] sd 0:0:0:0: [sda]
UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
May  1 14:39:35 ffoilpi1 kernel: [67009.943167] sd 0:0:0:0: [sda] Sense
Key : 0x3 [current]
May  1 14:39:35 ffoilpi1 kernel: [67009.943193] sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x0
May  1 14:39:35 ffoilpi1 kernel: [67009.943222] sd 0:0:0:0: [sda] CDB:
opcode=0x28 28 00 1f ec a8 00 00 00 f0 00

Looking at dmesg, things are getting worse :

[67016.577720] sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00
driverbyte=0x08
[67016.577768] sd 0:0:0:0: [sda] Sense Key : 0x3 [current]
[67016.577793] sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x0
[67016.577824] sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 1f ec a8 80 00
00 08 00
[67016.577848] blk_update_request: critical medium error, dev sda,
sector 535603328
[67201.185193] INFO: task jbd2/sda1-8:2602 blocked for more than 120
seconds.
[67201.185232]       Not tainted 4.1.19+ #858
[67201.185246] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[67201.185262] jbd2/sda1-8     D c0534afc     0  2602      2 0x00000000
[67201.185334] [] (__schedule) from []
(schedule+0x4c/0xa4)
[67201.185373] [] (schedule) from []
(schedule_timeout+0x180/0x1f8)
[67201.185407] [] (schedule_timeout) from []
(io_schedule_timeout+0xc4/0x148)
[67201.185436] [] (io_schedule_timeout) from []
(bit_wait_io+0x48/0x70)
[67201.185464] [] (bit_wait_io) from []
(__wait_on_bit+0x90/0xcc)
[67201.185492] [] (__wait_on_bit) from []
(out_of_line_wait_on_bit+0x78/0x84)
[67201.185532] [] (out_of_line_wait_on_bit) from []
(__wait_on_buffer+0x3c/0x44)
[67201.185575] [] (__wait_on_buffer) from []
(jbd2_journal_commit_transaction+0x1008/0x1700)
[67201.185618] [] (jbd2_journal_commit_transaction) from
[] (kjournald2+0xb8/0x23c)
[67201.185665] [] (kjournald2) from []
(kthread+0xdc/0xf8)
[67201.185706] [] (kthread) from []
(ret_from_fork+0x14/0x3c)
[67321.186203] INFO: task jbd2/sda1-8:2602 blocked for more than 120
seconds.
[67321.186241]       Not tainted 4.1.19+ #858
[67321.186256] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[67321.186271] jbd2/sda1-8     D c0534afc     0  2602      2 0x00000000
[67321.186343] [] (__schedule) from []
(schedule+0x4c/0xa4)
[67321.186381] [] (schedule) from []
(schedule_timeout+0x180/0x1f8)
[67321.186411] [] (schedule_timeout) from []
(io_schedule_timeout+0xc4/0x148)
[67321.186440] [] (io_schedule_timeout) from []
(bit_wait_io+0x48/0x70)
[67321.186471] [] (bit_wait_io) from []
(__wait_on_bit+0x90/0xcc)
[67321.186499] [] (__wait_on_bit) from []
(out_of_line_wait_on_bit+0x78/0x84)
[67321.186537] [] (out_of_line_wait_on_bit) from []
(__wait_on_buffer+0x3c/0x44)
[67321.186583] [] (__wait_on_buffer) from []
(jbd2_journal_commit_transaction+0x1008/0x1700)
[67321.186624] [] (jbd2_journal_commit_transaction) from
[] (kjournald2+0xb8/0x23c)
[67321.186669] [] (kjournald2) from []
(kthread+0xdc/0xf8)
[67321.186711] [] (kthread) from []
(ret_from_fork+0x14/0x3c)
[67373.317504] sd 0:0:0:0: timing out command, waited 360s
[67373.317584] blk_update_request: I/O error, dev sda, sector 1953346160
[67373.317735] Aborting journal on device sda1-8.
[67395.841132] EXT4-fs error (device sda1): ext4_journal_check_start:56:
Detected aborted journal
[67395.849920] EXT4-fs (sda1): Remounting filesystem read-only


It looks as though I've got some sort of disc error, but it is far from
clear (to me) what it is, and what needs to be done.


Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

--- SoupGate-Win32 v1.05