search

raspberrypi / linux

Kernel source tree for Raspberry Pi-provided kernel builds. Issues unrelated to the linux kernel should be posted on the community forum at https://forums.raspberrypi.com/
Other
11.22k stars 5.02k forks source link

UNKNOWN(0x2003) SCSI Error #1287

Closed rickysarraf closed 7 years ago

rickysarraf commented 8 years ago

I've recently staretd seeing this error with my USB attached SATA 3.5" HDD. The device has been under use for more than a year. This error has been seen very recently. My guess, given the error code, and what I've understood from the conversation on debian-user [1], this could be a generic problem than being a hardware malfunction.

[62711.477903] sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
[62711.485701] sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 9d 40 01 47 00 00 08 00
[62711.492910] blk_update_request: I/O error, dev sda, sector 2638217543
[84370.313684] sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
[84370.321532] sd 0:0:0:0: [sda] CDB: opcode=0x28 28 00 a1 40 01 47 00 00 08 00
[84370.328721] blk_update_request: I/O error, dev sda, sector 2705326407
Reporting here hoping the latter.

I forgot to mention that I had also run a full fsck on the device, with no errors reported.

130 pi@pi:~$ sudo fsck -cvkv /dev/sdb1 
[sudo] password for pi: 
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
Checking for bad blocks (read-only test): done                                                 
SEAGATE: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

SEAGATE: ***** FILE SYSTEM WAS MODIFIED *****

       20013 inodes used (0.02%, out of 122101760)
        8944 non-contiguous files (44.7%)
          53 non-contiguous directories (0.3%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 16695/3216/62
   416471936 blocks used (85.28%, out of 488378008)
           0 bad blocks
          63 large files

       17086 regular files
        2885 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
          33 symbolic links (32 fast symbolic links)
           0 sockets
------------
       20004 files
1 pi@pi:~$

[1] https://lists.debian.org/debian-user/2016/02/msg00194.html

popcornmix commented 8 years ago

What does uname -a report? If you believe it used to be more reliable, then find an older kernel that does work better. You can find older kernel/firmware releases here: https://github.com/Hexxeh/rpi-firmware/commits/master

click on a commit and you will the git hash at the end of the URL. sudo rpi-update <git hash> will get you that version.

If you can find an older version that doesn't have this issue that may give a starting point to diagnose.

Is this Pi1 or Pi2? How are Pi and disk powered? Insufficient power supply would be one possible cause of these errors. As would a failing disk drive.

rickysarraf commented 8 years ago

Thank you for your reply.

On Wed, 2016-02-10 at 10:44 -0800, popcornmix wrote:

What does uname -a report?

pi@pi:~$ uname -a Linux pi 4.1.16-v7+ #833 SMP Wed Jan 27 14:32:22 GMT 2016 armv7l GNU/Linux

If you believe it used to be more reliable, then find an older kernel that does work better.

I'm trying to recollect what all was changed recently. One item that came to mind was smartmontools. I've purged it now and am waiting (24+hrs) to see if the error pops up again.

You can find older kernel/firmware releases here: https://github.com/Hexxeh/rpi-firmware/commits/master click on a commit and you will the git hash at the end of the URL. sudo rpi-update will get you that version.

This is good. Wasn't aware of it. Thanks for sharing this information.

If you can find an older version that doesn't have this issue that may give a starting point to diagnose. Is this Pi1 or Pi2? How are Pi and disk powered? Insufficient power supply would be one possible cause of these errors. As would a failing disk drive.

This is an RPi2. The Pi is powered with its dedicated power cord, which further is connected to my UPS. The USB HDD Drives are 3.5" disks and they too have dedicated external power connected to the UPS.

With smartmontools purged, I'm still monitoring. I'll post my findings here on this tracker.

Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."

mathieugouin commented 8 years ago

Hello, I was wondering if you have updates for this issue because I'm experiencing very similar symptoms.

If it can help, I'm running a pi 3 with Seagate backup plus slim 2TB.

[75617.284826] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [75617.284849] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] [75617.284857] sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 [75617.284869] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0xa1 a1 06 20 da 00 00 4f c2 00 b0 00 00 [77417.115145] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [77417.115163] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] [77417.115172] sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 [77417.115184] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0xa1 a1 06 20 00 00 00 00 00 00 e5 00 00

rickysarraf commented 8 years ago

@mathieugouin There are a couple of things I did.

  1. Ensured that the USB cable from the HDD to the RPi was not on top of the device. Turns out, both the devices generate enough heat.
  2. Make some air vent for the HDD device.

Point no 1 and 2 are just physical precautions. I don't have data to prove if they have made any difference.

3 Given that my HDD and RPi had only 5 mins of UPS Backup, I ended up writing a vUPS (Virtual UPS) script to detect and cleanly unmount my HDD before the battery ran out and the RPi (and HDD) got off.

Maybe point no. 3 has made the difference. I haven't seen those errors since these changes, which now is around 4+ months.

And I'm currently running on:

pi@pi:~$ uname -a
Linux pi 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux

pi@pi:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 8.0 (jessie)
Release:        8.0
Codename:       jessie
rickysarraf commented 8 years ago

I just did a quick 10 GiB write on the drive. And no SCSI errors. So it could very well be one of the points above, or just a fix with the newer kernel.

@mathieugouin What kernel are you on? And what kernel did you see the errors on?

pi@pi:/media/SEAGATE$ dd if=/dev/zero of=foo.img bs=1M count=10000; rm -f foo.img
10000+0 records in
10000+0 records out
10485760000 bytes (10 GB) copied, 404.873 s, 25.9 MB/s

pi@pi:/media/SEAGATE$ dmesg | tail 
[46982.945998] smsc95xx 1-1.1:1.0 eth0: link down
[46984.522834] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[133370.215425] smsc95xx 1-1.1:1.0 eth0: link down
[133374.311640] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[133375.839476] smsc95xx 1-1.1:1.0 eth0: link down
[133377.311895] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x5DE1
[133379.336016] smsc95xx 1-1.1:1.0 eth0: link down
[133381.600670] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[133382.920601] smsc95xx 1-1.1:1.0 eth0: link down
[133384.496955] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
mathieugouin commented 8 years ago

I'm using

Linux xbian 4.4.14+ #1 SMP PREEMPT Wed Jun 29 13:04:58 CEST 2016 armv7l GNU/Linux

I hope the dd you did was not the cause of the repeated link down/up?

rickysarraf commented 8 years ago

I am not sure. I do have my router rebooting once a day, but these links falling are much more frequent. And that many link changes have happened in the uptime of 3 days, so there definitely is another bug too.

But, btw, I did see the SCSI error in the logs again.

pi@pi:~$ uptime
 14:52:13 up 3 days, 22:53,  1 user,  load average: 0.92, 0.90, 0.89

[46970.248030] smsc95xx 1-1.1:1.0 eth0: link down
[46974.368925] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[46975.881075] smsc95xx 1-1.1:1.0 eth0: link down
[46977.345893] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x5DE1
[46979.385132] smsc95xx 1-1.1:1.0 eth0: link down
[46981.617818] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[46982.945998] smsc95xx 1-1.1:1.0 eth0: link down
[46984.522834] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[133370.215425] smsc95xx 1-1.1:1.0 eth0: link down
[133374.311640] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[133375.839476] smsc95xx 1-1.1:1.0 eth0: link down
[133377.311895] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x5DE1
[133379.336016] smsc95xx 1-1.1:1.0 eth0: link down
[133381.600670] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[133382.920601] smsc95xx 1-1.1:1.0 eth0: link down
[133384.496955] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[219770.013955] smsc95xx 1-1.1:1.0 eth0: link down
[219774.078746] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[219775.638209] smsc95xx 1-1.1:1.0 eth0: link down
[219777.126994] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x5DE1
[219779.159523] smsc95xx 1-1.1:1.0 eth0: link down
[219781.367303] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[219782.687242] smsc95xx 1-1.1:1.0 eth0: link down
[219784.247568] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[219854.463396] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: delalloc,lazytime
[219855.590835] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: delalloc,lazytime
[280683.236435] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
[280683.245048] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 12 00 01 3f 00 00 08 00
[280683.252948] blk_update_request: I/O error, dev sdb, sector 301990207
[306168.788142] smsc95xx 1-1.1:1.0 eth0: link down
[306172.972925] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[306174.412760] smsc95xx 1-1.1:1.0 eth0: link down
[306175.901305] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x5DE1
[306177.901347] smsc95xx 1-1.1:1.0 eth0: link down
[306180.126169] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[306181.461791] smsc95xx 1-1.1:1.0 eth0: link down
[306183.022949] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1

pi@pi:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        15G  5.3G  8.6G  38% /
devtmpfs        396M     0  396M   0% /dev
tmpfs           400M   41M  359M  11% /run
tmpfs           400M     0  400M   0% /sys/fs/cgroup
tmpfs            80M     0   80M   0% /run/user/1000
/dev/mmcblk0p1   57M   20M   37M  36% /boot
/dev/sdb1       1.8T  102G  1.7T   6% /media/SEAGATE
/dev/sda1       3.6T  2.9T  655G  82% /media/4TBWD
pi@pi:~$
mathieugouin commented 8 years ago

I just upgraded to kernel Linux xbian 4.4.15+ and the issue is still present.

ezar commented 8 years ago

Same here! Using minibian 4.4.16+ 

[   12.255296] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[   12.256967] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] 
[   12.258878] sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 
[   12.260598] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
[   12.399218] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[   12.400713] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor] 
[   12.402132] sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0 
[   12.403541] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x85 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
mathieugouin commented 8 years ago

@ezar, just by curiosity what is the make and model of your USB drive? Mine is Seagate Backup Slim 2TB. It is currently formatted as NTFS. Let's see if we can find commonalities...

ezar commented 8 years ago

@mathieugouin mine is Seagate 3TB. Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-1ER166

It's formatted as EXT4.

mathieugouin commented 8 years ago

I just found out by analyzing more the dmesg message that I always have the following 4 lines in block that are logged:

sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] [descriptor]
sd 0:0:0:0: [sda] tag#0 ASC=0x0 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0xa1 a1 06 20 00 00 00 00 00 00 e5 00 00

By enabling the "human readable output" (command line option -T), I was able to see that the blocks repeat roughly every 30 minutes...

dmesg -T | grep tag#0 | grep UNKNOWN

Could you check if you have something similar?

jantyikt commented 8 years ago

Hm, I am seeing in my rpi3-s dmesg the same lines for a while. (and never before) My root fs is on an usb drive. Slightly overclocked, but with a dektop cpu cooler, with the official rpi3 power supply, with raspbian. I use it for light desktop workloads every day, plus as a wireless access point (via the onboard chip, bt disabled).

I have two and two "half" setup to reproduce this:

  1. big old wd mybook (2?) with separate power adaptor (WD5000AAVS inside)
  2. samsung 840 evo in a cheap noname (sharkoon, I think) bus powered case
  3. samsung ssd with WDmybook's sata-to-usb controller (disassembled, then reassembled with the ssd)
  4. samsung ssd with a slight modification on the bus powered case (usb cable extended with power and ground wires fed with an external power source /ssd side/ )

I cannot report any problems, data corruptions/loss, slowdowns or crashes. From my dmesg: http://pastebin.com/atRCBkRQ

Linux ***\ 4.4.16-v7+ #899 SMP Thu Jul 28 12:40:33 BST 2016 armv7l GNU/Linux Bus 001 Device 005: ID 1058:1100 Western Digital Technologies, Inc.

I hope it helps somewhat, maybe, I don't know.

ps: sorry for my English

Ruffio commented 8 years ago

@rickysarraf has your issue been resolved? If so, please close this issue. Thanks.

rickysarraf commented 8 years ago

@Ruffio Resolved? No. But is it really a bug? I don't know.

My inclination is that it is just may be a faulty hardware. But then, like I mentioned in the comments above, I've been able to avoid the scsi errors most of the times.

But given the number of users that have reported this issue, I'm not sure if this is a sign of faulty hardware.

rickysarraf commented 8 years ago

I just wrote 80 GiB of Data to the drive, without any SCSI errors. Given that it connects over USB to the RPi, I have my own hunch on what may have been the cause.

Feel free to close the bug if you want to, but it'd be nice if others could also comment first.

mathieugouin commented 8 years ago

Please don't close the issue. I still have the problem. I'm glad to help but would require further guidance on what commands to run. Thanks.

Kevin-McIsaac commented 8 years ago

I'm seeing the same problem (output of log below) on a new PI 3 running Linux dozer 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux

My device works fine for a day or two then the USB drive mount changes from RW to RO. When I umount the process hangs and I have to reboot.

On reboot I run efsck and get this error "Inodes that were part of a corrupted orphan linked list found", which I then fix. Remounting etc, the machine runs fine for a few days then the problem repeats.

/var/log/messages Aug 22 03:59:17 dozer kernel: [74516.369314] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Aug 22 03:59:17 dozer kernel: [74516.369358] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Aug 22 03:59:17 dozer kernel: [74516.369379] sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Aug 22 03:59:17 dozer kernel: [74516.369403] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 0a f2 24 c5 00 00 01 00

rickysarraf commented 8 years ago

@mathieugouin If you really want to narrow down the bug, you may want to try out @popcornmix's suggestion about trying different revisions of the kernel. The details are mentioned in comment 1 of this bug.

Kevin-McIsaac commented 8 years ago

After upgrading to the latest firmware I had the same problem about 12 hrs later. I installed 0a3df181c71b02d933f4431e97a5ae7933041427 (committed on 24 Oct 2015) but by system now won't boot. I get the splash screen, and can get to NOOB. However when I exit the consol is blank and the system does not boot.

Any way to upgrade the firmware on a machine that only boots to the NOOB screen or do I just reinstall raspbian?

rickysarraf commented 8 years ago

Sorry that you have an unbootalble state now.

In the past, I've done is to plug the sdcard into my laptop and them chroot into it and then fix. May not be very straightforward as laptops usually are x86.

s3nt fr0m a $martph0ne, excuse typ0s

On 22-Aug-2016 15:37, "Fractal Feeling" notifications@github.com wrote:

After upgrading to the latest firmware I had the same problem about 12 hrs later. I installed 0a3df181c71b02d933f4431e97a5ae7933041427 (committed on 24 Oct 2015) but by system now won't boot. I get the splash screen, and can get to NOOB. However when I exit the consol is blank and the system does not boot.

Any way to upgrade the firmware on a machine that only boots to the NOOB screen?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/raspberrypi/linux/issues/1287#issuecomment-241368784, or mute the thread https://github.com/notifications/unsubscribe-auth/AAD_yPtgx7KoaMS11RO4GqpxyEhIicHZks5qiXTggaJpZM4HXimv .

Kevin-McIsaac commented 8 years ago

All my fault :-)

I found this but it seemed easier and more reliable to reinstall from NOOB.

How do I know which version of the firmware are compatable with my kernel version?

Kevin-McIsaac commented 8 years ago

@mathieugouin my drive reports its a ST2000DM001-1E6164, which I think is a Seagate Barracuda 2tb

Kevin-McIsaac commented 8 years ago

This thread discusses the same issue on a PI 2.

Looks like code 0x2003 should be FAILED, rather than UNKNOWN, but no resolution. Interesting to see this person's drive is also Seagate

Based on this I'm setting libata.force=1.5Gbps in /boot/cmdline.txt

ezar commented 8 years ago

@Kevin-McIsaac Works with libata.force=1.5Gbp?

rickysarraf commented 8 years ago

@Kevin-McIsaac That person is me. :-)

I'm not sure if that'd help but it'd be nice to get some users to confirm it. RPi uses USB1/2 which, by spec, should only be able to do 480 Mbps.

I've been using the workaround you've mentioned, for a bug in the sata driver, for my laptop. https://www.researchut.com/blog/lenovo-yoga-2-13-debian

Kevin-McIsaac commented 8 years ago

@ezar I'm not sure at this stage. The system just hung last night and the disk need fsck repairs. So probably not.

I've placed an order for a new drive and will try that when it arrives

kristofejro commented 8 years ago

I have the same problem in my RPi2

In syslog every 5 minutes there is:

Aug 24 14:23:09 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
Aug 24 14:23:09 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 Sense Key : 0x4 [current] [descriptor]
Aug 24 14:23:09 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 ASC=0x0 ASCQ=0x0
Aug 24 14:23:09 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Aug 24 14:23:10 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
Aug 24 14:23:10 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 Sense Key : 0x4 [current] [descriptor]
Aug 24 14:23:10 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 ASC=0x0 ASCQ=0x0
Aug 24 14:23:10 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Aug 24 14:28:17 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
Aug 24 14:28:17 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 Sense Key : 0x4 [current] [descriptor]
Aug 24 14:28:17 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 ASC=0x0 ASCQ=0x0
Aug 24 14:28:17 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
Aug 24 14:28:17 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
Aug 24 14:28:17 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 Sense Key : 0x4 [current] [descriptor]
Aug 24 14:28:17 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 ASC=0x0 ASCQ=0x0
Aug 24 14:28:17 raspberrypi kernel: sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00

I am sure it was not showing earlier. I have 2.5 USB attached WD HDD and there is enough current because I have dedicated powered USB HUB. HDD itself is new and there is no problem with it (no errors, SMART is clean) I have just upgraded to 4.4.19-v7+ and problem still persits.

mathieugouin commented 8 years ago

@kristofejro Out of curiosity, what OS are you using for your Pi2. I'm using xbian.

It's interesting because you have the same repeating 4 lines as I do, but mine are every 30 min.

Could you try this and see the output:

dmesg -T | grep tag#0 | grep UNKNOWN

kristofejro commented 8 years ago

@mathieugouin I run: Raspbian GNU/Linux 8.0 (jessie) 4.4.19-v7+ Just part of dmesg query:

[Wed Aug 24 18:13:39 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[Wed Aug 24 18:13:39 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[Wed Aug 24 18:18:49 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[Wed Aug 24 18:18:49 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[Wed Aug 24 18:23:59 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[Wed Aug 24 18:23:59 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[Wed Aug 24 18:29:01 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[Wed Aug 24 18:29:02 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[Wed Aug 24 18:34:10 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[Wed Aug 24 18:34:10 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[Wed Aug 24 18:39:20 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[Wed Aug 24 18:39:20 2016] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
rickysarraf commented 8 years ago

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512

On Wed, 2016-08-24 at 06:41 -0700, kristofejro wrote:

I am sure it was not showing earlier.  I have 2.5 USB attached WD HDD and there is enough current because I have dedicated powered USB HUB. HDD itself is new and there is no problem with it (no errors, SMART is clean) I have just upgraded to 4.4.19-v7+ and problem still persits.

Honestly, I'm glad more and more people are hitting this bug. The best would be to take this up on linux-scsi mailing list and use this bug report as a reference.

Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." -----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXvdsNAAoJEKY6WKPy4XVpvocP+gMWoObesuNQRIKFWnozWuEq t4R9NSpsETFAfJ3CHyX0W+uyjei4+btIyMeraDTUsE6oIZr/7xdLBLHJV8Kd2h9v J1dO9omIor+nau6uCVmNDJQXIXfORj3IAmbOOywX0mkhHHNGCo+0/6ixcAKcJ16K 7iUWlEqylA0qfyLN/ZZGlspXii7I5QBzEsytOSBshKjNs94D55oaot8aOmMXNehY kmVjNIGjHTAITKrpzlKSx27t7qAbqB5i09BIlZP75gqAggQuI5/1nKi0mlW9ZWzl 3rx1uHPpspCcg0E5YrY47ojm4tXQVvYcnvOPvsJ9HP+9F5y4Y0G4xXbVN14OcVxu IxRaw/sznOMZlNIiUfpOaoM1byqlToHym5YxWDKXbWOrdXPz2QcCZpu5E95uXHzs ENwcjHww5oA9RnpIQI3I8GfUQL87wZIvHhFtT59c7diDpEzLggXLhpwXKQnJ67Js 4fKw/goaJ4ETmxru4R9me3X1bs+SYZM5C20PwEDINjyFZ/uSCWyVqjxWRL3Etrwb HpoG3fAlLMXCjqNWXtp2K/Y6Ir7TvE9TecxrgulUVBEyVAj99bHvMwm141FUXuk5 DIDwgG6xVDXIZ7rlzRMa6NumxugkrFnGwLgqq2OTxxe6cqe4CdUPZexvUTS3esdT iiYxxYAXJc4tPx5ULusb =dVry -----END PGP SIGNATURE-----

kristofejro commented 8 years ago

I have downgraded kernel to 4.4.13 and problem is gone (so far) Mabe someone else can confirm (perform kernel downgrade).

Kevin-McIsaac commented 8 years ago

@kristofejro , I'm running 4.4.13-v7+ #894 and still get the messages a few times a day.

@ezar , using libata.force=1.5Gbp did not eliminate the issue

I also discovered this morning that the filesystem was marked as RO, indicating the filesystem is became corrupted. When umount the filesystem the command takes a very long time to complete. WHen I run fsck it shows the filesystem it tries to recover the journal but hangs. I tried to reboot and that hangs so I cycled the power.

When the machine reboots fsck completes showing no errors.

kristofejro commented 8 years ago

Isn't it very similar to: https://github.com/raspberrypi/linux/issues/1549 ?

ezar commented 8 years ago

Same problem in 4.4.20+ Any news?

[Sun Sep 11 10:00:39 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 10:00:44 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 10:30:39 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 10:30:44 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 11:00:39 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 11:00:44 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 11:30:39 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 11:30:44 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 12:00:38 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 12:00:43 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 12:30:38 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 12:30:43 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 13:00:38 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 13:00:43 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 13:30:38 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 13:30:43 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 14:00:38 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 14:00:43 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 14:30:39 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08 [Sun Sep 11 14:30:44 2016] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08

Dmole commented 8 years ago

This is not raspberrypi specific.

AFAIK it's just that some drives do things the kernal is not expecting (someone should update a driver).

I get this (non-fatal warning) on a XU4 with 5TB Seagate drives;

> uname -r
4.8.6+
> lsusb | grep Seagate
Bus 002 Device 006: ID 0bc2:3312 Seagate RSS LLC SRD00F2 Expansion Desktop Drive (STBV)
Bus 002 Device 005: ID 0bc2:3312 Seagate RSS LLC SRD00F2 Expansion Desktop Drive (STBV)
Bus 002 Device 004: ID 0bc2:3312 Seagate RSS LLC SRD00F2 Expansion Desktop Drive (STBV)
> dmesg |tail -n 4
[216006.391906] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[216006.391924] sd 2:0:0:0: [sdc] tag#0 Sense Key : 0x4 [current] [descriptor] 
[216006.391932] sd 2:0:0:0: [sdc] tag#0 ASC=0x0 ASCQ=0x0 
[216006.391945] sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x85 85 06 2c 00 da 00 00 00 00 00 4f 00 c2 00 b0 00
rickysarraf commented 8 years ago

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512

On Thu, 2016-11-03 at 19:45 -0700, Tim wrote: This is not raspberrypi specific.

AFAIK it's just that some drives do things the kernal is not expecting (someone should update a driver).

If you are certain this is a generic SCSI issue in the Linux kernel, could you please report it upstream ?

Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." -----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYHGEXAAoJEKY6WKPy4XVprGcP/3RH02JBNBM2GgSJkvLOVm9w 1LcSkPFmbK+QjrAXfyVDud7YCV1C98Ii9+ILca6ludfx1LxHCxPzJU5HyhWTjR+G pdzexw2O32b+koUFDQ9oY1x4OqmzQo0iXRdqPY0dMurVy3ucMKXnsd36s0L5s9Va XQxQvZcPaIXArkVi9nAiOTq2QjMZgXS7QP3KS9sxDqlq7+X0btVJiA8V3/904YG7 mUJ4a3kQSko6/ijREJS/C56VXe1cP6aFloy6e3QJdK89gyY5ADVgaKbFGJH5R3e3 BqrQIW6wtP+ihx+pS/THLwFA0OuqD9zOSHfeZZLU0JbrLt3T8Pnqqfa+sUSd5wlJ cul59LynVXwiogOK4dfqZ47/QuzTd1ABlgXE6hIzwfzdlLTJ2BYBWJHz9kp5y2Yj wXqA/YMEwz+3s2xH+8TJjVKq/PcV3JlN3EgaLvuipP3mS5y8+lLWfyoBLTB4VMQ9 ZZgBeRLo4Uz6kfE/Z3ssi2H2+1LgKbtGg9Rth+YBcIBb5Iw+WXJFgfM3dvGX8rS5 btcHQuSB5SXVsAy2LVupQT6SZ4XqZ82dCFsGy4GJQfFvhiIIZ3K3j1ReZtAyI/Ct OZAZaqfzfnSdCbTmu9GygwiJgkUtKhHd67od0hrTyUEfvDe1q+b//H5Sz1Tt/S/p 3OQlbDuRhK66TvPYuDns =T4o5 -----END PGP SIGNATURE-----

NewToTheStory commented 8 years ago

@Hi Guys,

i'am not sure, but i think i have the same or at least similiar problem,

I have two Hitachi Travelstar 5K1000 HTS541010J22413, installed in 2 cases, which also are the same models used with a rapsberry 3. On first hdd i have bootpartition and also seafile-data. The second hdd is planned as backup for hdd1. All worked fine, till today, when i shutdown raspi, siwtched of power, replaced hardware to another place in flat and powerd on. Since i connected both hdd i get an I/O Error on SDA1 (non-backup HDD) and OS run in RO. Currently i only can use the system with unplugged second hdd, thats really annoying

sebastian@raspberrypi:~$ dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 4.4.26-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #915 SMP Thu Oct 20 17:08:44 BST 2016 [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: Raspberry Pi 3 Model B Rev 1.2 [ 0.000000] cma: Reserved 8 MiB at 0x3a800000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] On node 0 totalpages: 241664 [ 0.000000] free_area_init_node: node 0, pgdat 808c2f80, node_mem_map b9fa6000 [ 0.000000] Normal zone: 2124 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 241664 pages, LIFO batch:31 [ 0.000000] [bcm2709_smp_init_cpus] enter (9520->f3003010) [ 0.000000] [bcm2709_smp_init_cpus] ncores=4 [ 0.000000] PERCPU: Embedded 13 pages/cpu @b9f62000 s22592 r8192 d22464 u53248 [ 0.000000] pcpu-alloc: s22592 r8192 d22464 u53248 alloc=13*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 239540 [ 0.000000] Kernel command line: 8250.nr_uarts=0 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa02082 bcm2709.serial=0x97c05755 smsc95xx.macaddr=B8:27:EB:C0:57:55 bcm2708_fb.fbswap=1 bcm2709.uart_clock=48000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/sda1 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 939072K/966656K available (6348K kernel code, 432K rwdata, 1716K rodata, 476K init, 764K bss, 19392K reserved, 8192K cma-reserved) [ 0.000000] Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xbb800000 - 0xff800000 (1088 MB) lowmem : 0x80000000 - 0xbb000000 ( 944 MB) modules : 0x7f000000 - 0x80000000 ( 16 MB) .text : 0x80008000 - 0x807e8584 (8066 kB) .init : 0x807e9000 - 0x80860000 ( 476 kB) .data : 0x80860000 - 0x808cc290 ( 433 kB) .bss : 0x808cf000 - 0x8098e1ec ( 765 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 32. [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] Architected cp15 timer(s) running at 19.20MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns [ 0.000008] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns [ 0.000026] Switching to timer-based delay loop, resolution 52ns [ 0.000293] Console: colour dummy device 80x30 [ 0.001345] console [tty1] enabled [ 0.001390] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000) [ 0.001459] pid_max: default: 32768 minimum: 301 [ 0.001798] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.001842] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.002800] Disabling cpuset control group subsystem [ 0.002858] Initializing cgroup subsys io [ 0.002910] Initializing cgroup subsys memory [ 0.002975] Initializing cgroup subsys devices [ 0.003019] Initializing cgroup subsys freezer [ 0.003062] Initializing cgroup subsys net_cls [ 0.003135] CPU: Testing write buffer coherency: ok [ 0.003224] ftrace: allocating 21225 entries in 63 pages [ 0.052930] CPU0: update cpu_capacity 1024 [ 0.053000] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.053033] [bcm2709_smp_prepare_cpus] enter [ 0.053198] Setting up static identity map for 0x8240 - 0x8274 [ 0.054856] [bcm2709_boot_secondary] cpu:1 started (0) 18 [ 0.055046] [bcm2709_secondary_init] enter cpu:1 [ 0.055089] CPU1: update cpu_capacity 1024 [ 0.055096] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.055471] [bcm2709_boot_secondary] cpu:2 started (0) 17 [ 0.055635] [bcm2709_secondary_init] enter cpu:2 [ 0.055656] CPU2: update cpu_capacity 1024 [ 0.055662] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.056024] [bcm2709_boot_secondary] cpu:3 started (0) 17 [ 0.056155] [bcm2709_secondary_init] enter cpu:3 [ 0.056175] CPU3: update cpu_capacity 1024 [ 0.056181] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.056242] Brought up 4 CPUs [ 0.056340] SMP: Total of 4 processors activated (153.60 BogoMIPS). [ 0.056370] CPU: All CPU(s) started in HYP mode. [ 0.056396] CPU: Virtualization extensions available. [ 0.057030] devtmpfs: initialized [ 0.067935] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4 [ 0.068308] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.069065] pinctrl core: initialized pinctrl subsystem [ 0.069600] NET: Registered protocol family 16 [ 0.074777] DMA: preallocated 4096 KiB pool for atomic coherent allocations [ 0.081641] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.081690] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.081868] Serial: AMBA PL011 UART driver [ 0.082020] uart-pl011 3f201000.uart: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe [ 0.082220] bcm2835-mbox 3f00b880.mailbox: mailbox enabled [ 0.145050] bcm2835-dma 3f007000.dma: DMA legacy API manager at f3007000, dmachans=0x1 [ 0.145649] SCSI subsystem initialized [ 0.145857] usbcore: registered new interface driver usbfs [ 0.145968] usbcore: registered new interface driver hub [ 0.146088] usbcore: registered new device driver usb [ 0.152478] raspberrypi-firmware soc:firmware: Attached to firmware from 2016-10-20 14:57 [ 0.179633] clocksource: Switched to clocksource arch_sys_counter [ 0.224833] FS-Cache: Loaded [ 0.225133] CacheFiles: Loaded [ 0.237403] NET: Registered protocol family 2 [ 0.238285] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.238423] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 0.238633] TCP: Hash tables configured (established 8192 bind 8192) [ 0.238747] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 0.238815] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 0.239067] NET: Registered protocol family 1 [ 0.239407] RPC: Registered named UNIX socket transport module. [ 0.239440] RPC: Registered udp transport module. [ 0.239468] RPC: Registered tcp transport module. [ 0.239496] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.240592] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available [ 0.241929] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.255213] VFS: Disk quotas dquot_6.6.0 [ 0.255545] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.257809] FS-Cache: Netfs 'nfs' registered for caching [ 0.258732] NFS: Registering the id_resolver key type [ 0.258815] Key type id_resolver registered [ 0.258843] Key type id_legacy registered [ 0.261197] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 0.261363] io scheduler noop registered [ 0.261405] io scheduler deadline registered (default) [ 0.261481] io scheduler cfq registered [ 0.263996] BCM2708FB: allocated DMA memory fac00000 [ 0.264043] BCM2708FB: allocated DMA channel 0 @ f3007000 [ 0.272743] Console: switching to colour frame buffer device 82x26 [ 1.250756] bcm2835-rng 3f104000.rng: hwrng registered [ 1.253230] vc-cma: Videocore CMA driver [ 1.255611] vc-cma: vc_cma_base = 0x00000000 [ 1.257988] vc-cma: vc_cma_size = 0x00000000 (0 MiB) [ 1.260287] vc-cma: vc_cma_initial = 0x00000000 (0 MiB) [ 1.262662] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB) [ 1.281717] brd: module loaded [ 1.292377] loop: module loaded [ 1.295295] vchiq: vchiq_init_state: slot_zero = 0xbac80000, is_master = 0 [ 1.298855] Loading iSCSI transport class v2.0-870. [ 1.301652] usbcore: registered new interface driver smsc95xx [ 1.303913] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [ 1.506343] Core Release: 2.80a [ 1.508426] Setting default values for core params [ 1.510590] Finished setting default values for core params [ 1.713121] Using Buffer DMA mode [ 1.715286] Periodic Transfer Interrupt Enhancement - disabled [ 1.717526] Multiprocessor Interrupt Enhancement - disabled [ 1.719836] OTG VER PARAM: 0, OTG VER FLAG: 0 [ 1.722090] Dedicated Tx FIFOs mode [ 1.724552] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xbac14000 dma = 0xfac14000 len=9024 [ 1.729185] FIQ FSM acceleration enabled for : Non-periodic Split Transactions Periodic Split Transactions High-Speed Isochronous Endpoints Interrupt/Control Split Transaction hack enabled [ 1.740993] dwc_otg: Microframe scheduler enabled [ 1.741048] WARN::hcd_init_fiq:413: FIQ on core 1 at 0x804476e0 [ 1.743484] WARN::hcd_init_fiq:414: FIQ ASM at 0x80447a50 length 36 [ 1.745849] WARN::hcd_init_fiq:439: MPHI regs_base at 0xbb9a8000 [ 1.748205] dwc_otg 3f980000.usb: DWC OTG Controller [ 1.750534] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1 [ 1.752894] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000 [ 1.755209] Init: Port Power? op_state=1 [ 1.757459] Init: Power Port (0) [ 1.759845] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.762146] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.764438] usb usb1: Product: DWC OTG Controller [ 1.766679] usb usb1: Manufacturer: Linux 4.4.26-v7+ dwc_otg_hcd [ 1.768944] usb usb1: SerialNumber: 3f980000.usb [ 1.772001] hub 1-0:1.0: USB hub found [ 1.774198] hub 1-0:1.0: 1 port detected [ 1.776823] dwc_otg: FIQ enabled [ 1.776833] dwc_otg: NAK holdoff enabled [ 1.776841] dwc_otg: FIQ split-transaction FSM enabled [ 1.776880] Module dwc_common_port init [ 1.777149] usbcore: registered new interface driver usb-storage [ 1.779526] mousedev: PS/2 mouse device common for all mice [ 1.782414] bcm2835-cpufreq: min=600000 max=1200000 [ 1.784880] sdhci: Secure Digital Host Controller Interface driver [ 1.787140] sdhci: Copyright(c) Pierre Ossman [ 1.789681] sdhost: log_buf @ bac13000 (fac13000) [ 1.849663] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1) [ 1.854167] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0 [ 1.856456] mmc-bcm2835 3f300000.mmc: DMA channel allocated [ 1.906500] mmc0: host does not support reading read-only switch, assuming write-enable [ 1.909749] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.910136] ledtrig-cpu: registered to indicate activity on CPUs [ 1.910248] hidraw: raw HID events driver (C) Jiri Kosina [ 1.910425] usbcore: registered new interface driver usbhid [ 1.910428] usbhid: USB HID core driver [ 1.910947] Initializing XFRM netlink socket [ 1.910981] NET: Registered protocol family 17 [ 1.911133] Key type dns_resolver registered [ 1.911630] Registering SWP/SWPB emulation handler [ 1.912437] registered taskstats version 1 [ 1.912622] vc-sm: Videocore shared memory driver

[ 1.920890] [vc_sm_connected_init]: end - returning 0 [ 1.922251] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2 [ 1.922621] of_cfs_init [ 1.922699] of_cfs_init: OK [ 1.950175] Waiting for root device /dev/sda1... [ 1.951864] mmc0: new high speed SDHC card at address 0001 [ 1.952438] mmcblk0: mmc0:0001 00000 29.3 GiB [ 1.955138] mmcblk0: p1 p2 [ 1.969752] Indeed it is in host mode hprt0 = 00021501 [ 1.972998] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 1.976565] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.980033] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.984640] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 2.077088] mmc1: new high speed SDIO card at address 0001 [ 2.149664] usb 1-1: new high-speed USB device number 2 using dwc_otg [ 2.151658] Indeed it is in host mode hprt0 = 00001101 [ 2.349908] usb 1-1: New USB device found, idVendor=0424, idProduct=9514 [ 2.351902] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.354590] hub 1-1:1.0: USB hub found [ 2.356640] hub 1-1:1.0: 5 ports detected [ 2.639658] usb 1-1.1: new high-speed USB device number 3 using dwc_otg [ 2.739901] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00 [ 2.741870] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.746576] smsc95xx v1.0.4 [ 2.812823] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:c0:57:55 [ 2.909658] usb 1-1.3: new high-speed USB device number 4 using dwc_otg [ 3.012515] usb 1-1.3: New USB device found, idVendor=05e3, idProduct=0610 [ 3.014856] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.017204] usb 1-1.3: Product: USB2.0 Hub [ 3.019491] usb 1-1.3: Manufacturer: GenesysLogic [ 3.022824] hub 1-1.3:1.0: USB hub found [ 3.025700] hub 1-1.3:1.0: 4 ports detected [ 3.509658] usb 1-1.3.4: new high-speed USB device number 7 using dwc_otg [ 3.690676] usb 1-1.3.4: New USB device found, idVendor=152d, idProduct=2590 [ 3.693191] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.697975] usb 1-1.3.4: Product: Generic USB Device [ 3.700452] usb 1-1.3.4: Manufacturer: USB to ATA/ATAPI Brid [ 3.702887] usb 1-1.3.4: SerialNumber: 00A12345AFD0 [ 3.706402] usb-storage 1-1.3.4:1.0: USB Mass Storage device detected [ 3.709287] scsi host0: usb-storage 1-1.3.4:1.0 [ 4.710470] scsi 0:0:0:0: Direct-Access USB3.0 8105 PQ: 0 ANSI: 6 [ 4.717382] sd 0:0:0:0: [sda] Spinning up disk... [ 5.729650] .ready [ 5.732306] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) [ 5.737264] sd 0:0:0:0: [sda] Write Protect is off [ 5.739680] sd 0:0:0:0: [sda] Mode Sense: 33 00 00 08 [ 5.740004] sd 0:0:0:0: [sda] No Caching mode page found [ 5.742347] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 5.767334] sda: sda1 sda2 sda3 [ 5.771902] sd 0:0:0:0: [sda] Attached SCSI disk [ 5.861472] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 5.866406] VFS: Mounted root (ext4 filesystem) readonly on device 8:1. [ 5.891843] devtmpfs: mounted [ 5.895059] Freeing unused kernel memory: 476K (807e9000 - 80860000) [ 6.421127] random: systemd: uninitialized urandom read (16 bytes read, 106 bits of entropy available) [ 6.435443] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR) [ 6.441519] systemd[1]: Detected architecture 'arm'. [ 6.639474] NET: Registered protocol family 10 [ 6.643776] systemd[1]: Inserted module 'ipv6' [ 6.655803] systemd[1]: Set hostname to . [ 6.876898] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 120 bits of entropy available) [ 7.203150] random: nonblocking pool is initialized [ 7.798467] systemd[1]: [/lib/systemd/system/certbot.timer:6] Unknown lvalue 'RandomizedDelaySec' in section 'Timer' [ 8.357334] systemd[1]: Starting Forward Password Requests to Wall Directory Watch. [ 8.363577] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 8.369474] systemd[1]: Starting Remote File Systems (Pre). [ 8.375894] systemd[1]: Reached target Remote File Systems (Pre). [ 8.378951] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point. [ 8.388366] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 8.394511] systemd[1]: Starting Encrypted Volumes. [ 8.401068] systemd[1]: Reached target Encrypted Volumes. [ 8.404323] systemd[1]: Expecting device dev-sda2.device... [ 8.410809] systemd[1]: Expecting device dev-mmcblk0p1.device... [ 8.417242] systemd[1]: Expecting device dev-disk-by\x2duuid-c94efc73\x2d7d63\x2d420c\x2dabc2\x2d646aa49452ee.device... [ 8.426816] systemd[1]: Starting Root Slice. [ 8.433260] systemd[1]: Created slice Root Slice. [ 8.436287] systemd[1]: Starting User and Session Slice. [ 8.442664] systemd[1]: Created slice User and Session Slice. [ 8.445666] systemd[1]: Starting Delayed Shutdown Socket. [ 8.451776] systemd[1]: Listening on Delayed Shutdown Socket. [ 8.454617] systemd[1]: Starting /dev/initctl Compatibility Named Pipe. [ 8.460618] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [ 8.463517] systemd[1]: Starting Journal Socket (/dev/log). [ 8.469588] systemd[1]: Listening on Journal Socket (/dev/log). [ 8.472595] systemd[1]: Starting udev Control Socket. [ 8.478563] systemd[1]: Listening on udev Control Socket. [ 8.481438] systemd[1]: Starting udev Kernel Socket. [ 8.487031] systemd[1]: Listening on udev Kernel Socket. [ 8.489741] systemd[1]: Starting Journal Socket. [ 8.495215] systemd[1]: Listening on Journal Socket. [ 8.497935] systemd[1]: Starting System Slice. [ 8.503448] systemd[1]: Created slice System Slice. [ 8.506074] systemd[1]: Starting File System Check on Root Device... [ 8.540237] systemd[1]: Starting system-systemd\x2dfsck.slice. [ 8.546118] systemd[1]: Created slice system-systemd\x2dfsck.slice. [ 8.548788] systemd[1]: Starting system-getty.slice. [ 8.554707] systemd[1]: Created slice system-getty.slice. [ 8.557437] systemd[1]: Starting Increase datagram queue length... [ 8.565454] systemd[1]: Starting Restore / save the current clock... [ 8.585155] systemd[1]: Starting udev Coldplug all Devices... [ 8.631547] systemd[1]: Started Set Up Additional Binary Formats. [ 8.634691] systemd[1]: Mounting Debug File System... [ 8.680574] systemd[1]: Starting Create list of required static device nodes for the current kernel... [ 8.692057] systemd[1]: Mounted Huge Pages File System. [ 8.695455] systemd[1]: Mounting POSIX Message Queue File System... [ 8.806826] systemd[1]: Starting Load Kernel Modules... [ 8.850484] systemd[1]: Starting Slices. [ 8.856816] systemd[1]: Reached target Slices. [ 8.865180] systemd[1]: Mounted POSIX Message Queue File System. [ 8.871648] systemd[1]: Mounted Debug File System. [ 8.878519] systemd[1]: Started Increase datagram queue length. [ 8.918653] systemd[1]: Started Create list of required static device nodes for the current kernel. [ 8.974317] systemd[1]: Started udev Coldplug all Devices. [ 8.994208] systemd[1]: Started Restore / save the current clock. [ 9.005162] fuse init (API version 7.23) [ 9.007018] systemd[1]: Time has been changed [ 9.041689] systemd[1]: Started Load Kernel Modules. [ 9.075824] systemd[1]: Mounting FUSE Control File System... [ 9.100250] systemd[1]: Starting Apply Kernel Variables... [ 9.109340] systemd[1]: Mounting Configuration File System... [ 9.118616] systemd[1]: Starting Create Static Device Nodes in /dev... [ 9.127858] systemd[1]: Starting Syslog Socket. [ 9.134543] systemd[1]: Listening on Syslog Socket. [ 9.137555] systemd[1]: Starting Journal Service... [ 9.148704] systemd[1]: Started Journal Service. [ 9.445001] systemd-udevd[146]: starting version 215 [ 10.045599] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer [ 10.120563] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000 [ 10.450720] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 10.619182] EXT4-fs (sda1): re-mounted. Opts: (null) [ 10.845550] usbcore: registered new interface driver brcmfmac [ 11.095939] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: May 27 2016 00:13:38 version 7.45.41.26 (r640327) FWID 01-df77e4a7 [ 11.116422] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 11.724189] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 11.724217] cfg80211: World regulatory domain updated: [ 11.724227] cfg80211: DFS Master region: unset [ 11.724236] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 11.724250] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 11.724263] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 11.724301] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 11.724337] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 11.724353] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 11.724365] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 11.724378] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 11.724411] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 15.739199] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 15.844737] systemd-journald[140]: Received request to flush runtime journal from PID 1 [ 16.396439] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists [ 16.396456] brcmfmac: brcmf_add_if: ignore IF event [ 16.400702] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 16.400734] brcmfmac: power management disabled [ 16.539555] uart-pl011 3f201000.uart: no DMA platform data [ 17.740559] Adding 102396k swap on /var/swap. Priority:-1 extents:1 across:102396k FS [ 18.135811] cfg80211: Regulatory domain changed to country: GB [ 18.135828] cfg80211: DFS Master region: ETSI [ 18.135833] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 18.135841] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 18.135849] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 18.135857] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 18.135863] cfg80211: (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s) [ 18.135870] cfg80211: (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A) [ 18.920853] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup [ 18.921150] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 20.435020] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 20.435452] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1 [ 22.325753] Bluetooth: Core ver 2.21 [ 22.325833] NET: Registered protocol family 31 [ 22.325844] Bluetooth: HCI device and connection manager initialized [ 22.325867] Bluetooth: HCI socket layer initialized [ 22.325884] Bluetooth: L2CAP socket layer initialized [ 22.325920] Bluetooth: SCO socket layer initialized [ 22.355449] Bluetooth: HCI UART driver ver 2.3 [ 22.355469] Bluetooth: HCI UART protocol H4 registered [ 22.355479] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 22.355651] Bluetooth: HCI UART protocol BCM registered [ 22.614330] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 22.614351] Bluetooth: BNEP filters: protocol multicast [ 22.614373] Bluetooth: BNEP socket layer initialized [ 32.988725] ip_tables: (C) 2000-2006 Netfilter Core Team [ 285.781032] usb 1-1.3.2: new high-speed USB device number 12 using dwc_otg [ 285.962318] usb 1-1.3.2: New USB device found, idVendor=152d, idProduct=2590 [ 285.962339] usb 1-1.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 285.962353] usb 1-1.3.2: Product: Generic USB Device [ 285.962365] usb 1-1.3.2: Manufacturer: USB to ATA/ATAPI Brid [ 285.962378] usb 1-1.3.2: SerialNumber: 00A12345AFD0 [ 285.963718] usb-storage 1-1.3.2:1.0: USB Mass Storage device detected [ 285.966185] scsi host1: usb-storage 1-1.3.2:1.0 [ 286.961887] scsi 1:0:0:0: Direct-Access USB3.0 8105 PQ: 0 ANSI: 6 [ 286.963208] sd 1:0:0:0: Attached scsi generic sg1 type 0 [ 286.964515] sd 1:0:0:0: [sdb] Spinning up disk... [ 287.971025] . [ 288.092029] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [ 288.092070] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current] [ 288.092092] sd 0:0:0:0: [sda] tag#0 ASC=0x47 ASCQ=0x3 [ 288.092120] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 44 11 20 00 00 20 00 [ 288.092138] blk_update_request: I/O error, dev sda, sector 4460832 [ 288.092361] Aborting journal on device sda1-8. [ 288.191629] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [ 288.191667] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current] [ 288.191687] sd 0:0:0:0: [sda] tag#0 ASC=0x47 ASCQ=0x3 [ 288.191716] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 44 08 00 00 00 08 00 [ 288.191733] blk_update_request: I/O error, dev sda, sector 4458496 [ 288.191752] Buffer I/O error on dev sda1, logical block 557056, lost sync page write [ 288.191967] JBD2: Error -5 detected when updating journal superblock for sda1-8. [ 288.291638] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [ 288.291669] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current] [ 288.291696] sd 0:0:0:0: [sda] tag#0 ASC=0x47 ASCQ=0x3 [ 288.291726] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 08 00 00 00 08 00 [ 288.291749] blk_update_request: I/O error, dev sda, sector 2048 [ 288.291767] Buffer I/O error on dev sda1, logical block 0, lost sync page write [ 288.291837] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal [ 288.296863] EXT4-fs (sda1): Remounting filesystem read-only [ 288.299422] EXT4-fs (sda1): previous I/O error to superblock detected [ 288.391647] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [ 288.391681] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current] [ 288.391707] sd 0:0:0:0: [sda] tag#0 ASC=0x47 ASCQ=0x3 [ 288.391739] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 08 00 00 00 08 00 [ 288.391766] blk_update_request: I/O error, dev sda, sector 2048 [ 288.391787] Buffer I/O error on dev sda1, logical block 0, lost sync page write [ 288.981051] .ready [ 288.981583] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) [ 288.981989] sd 1:0:0:0: [sdb] Write Protect is off [ 288.982008] sd 1:0:0:0: [sdb] Mode Sense: 33 00 00 08 [ 288.982408] sd 1:0:0:0: [sdb] No Caching mode page found [ 288.982424] sd 1:0:0:0: [sdb] Assuming drive cache: write through [ 289.021687] sdb: sdb1 [ 289.023743] sd 1:0:0:0: [sdb] Attached SCSI disk [ 293.081661] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [ 293.081702] sd 0:0:0:0: [sda] tag#0 Sense Key : 0xb [current] [ 293.081730] sd 0:0:0:0: [sda] tag#0 ASC=0x47 ASCQ=0x3 [ 293.081756] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 80 16 00 00 00 08 00 [ 293.081785] blk_update_request: I/O error, dev sda, sector 8394240 [ 293.081805] Buffer I/O error on dev sda1, logical block 1049024, lost async page write [ 306.431101] EXT4-fs (sda1): error count since last fsck: 21 [ 306.431135] EXT4-fs (sda1): initial error at time 1479652602: ext4_journal_check_start:56 [ 306.431151] EXT4-fs (sda1): last error at time 1479659146: ext4_journal_check_start:56

NicoHood commented 7 years ago

I've got the same issue every few minutes. I am using ArchLinux with:

Linux alarmpi 4.4.37-1-ARCH #1 SMP Fri Dec 9 19:03:41 MST 2016 armv7l GNU/Linux

What is weird is, that i am using 2 identical usb 2tb (seagate expansion) drives with btrfs raid0. But only sda gives those warnings. The music hangs for a short time when the bug/error occurs.

NewToTheStory commented 7 years ago

I found out that mounting the second hdd, caused this problem. I deleted the hdd completely with dd and after this the problem was gone. But I had to restore the hdd anyway, which caused the problem, because after cleaning I had (or maybe also before) an hardware issue with her (clicking). Now I have again to similar hdd's mounted without this problem... Maybe this helps someone

Von meinem Samsung Gerät gesendet.

-------- Ursprüngliche Nachricht -------- Von: Nico notifications@github.com Datum: 18.12.2016 12:49 (GMT+01:00) An: raspberrypi/linux linux@noreply.github.com Cc: NewToTheStory direkt@mailbox.org, Comment comment@noreply.github.com Betreff: Re: [raspberrypi/linux] UNKNOWN(0x2003) SCSI Error (#1287)

I've got the same issue every few minutes. I am using ArchLinux with: Linux alarmpi 4.4.37-1-ARCH #1 SMP Fri Dec 9 19:03:41 MST 2016 armv7l GNU/Linux

What is weird is, that i am using 2 identical usb 2tb (seagate expansion) drives with btrfs raid0. But only sda gives those warnings. The music hangs for a short time when the bug/error occurs.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/raspberrypi/linux","title":"raspberrypi/linux","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/raspberrypi/linux"}},"updates":{"snippets":[{"icon":"PERSON","message":"@NicoHood in #1287: I've got the same issue every few minutes. I am using ArchLinux with:\r\n\r\nLinux alarmpi 4.4.37-1-ARCH #1 SMP Fri Dec 9 19:03:41 MST 2016 armv7l GNU/Linux\r\n\r\nWhat is weird is, that i am using 2 identical usb 2tb (seagate expansion) drives with btrfs raid0. But only sda gives those warnings. The music hangs for a short time when the bug/error occurs."}],"action":{"name":"View Issue","url":"https://github.com/raspberrypi/linux/issues/1287#issuecomment-267816890"}}}

NicoHood commented 7 years ago

Is it possible that the internal hub of the raspi causes problems? Or undervoltage? I have the official 5.1V 2,5A PSU, so that should be fine. The hdds are self powered. But I remember that one of my hdd crashed 2-3 times and I had to unplug it from power to get it spin up again. I am not sure if this is a driver fault or if my hardware is defective.

Dmole commented 7 years ago

Not likely I put paper + tape over the power pin to isolate the pi from powered USB devices... have tested with 4.8.15 but not 4.9...

JamesH65 commented 7 years ago

I suspect there a number of issues at play, bad power supply and perhaps an upstream driver issue. neither of which should be dealt with here, so will close. If anyone requires it or has more Raspberry specific information, feel free to reopen.

marcotini commented 4 years ago

Just happen to me on Raspberry Pi 4 and my WD My Passport 4TB when I've plugged an ssd on the second usb 3.0 port:

[Thu Jun 11 11:27:05 2020] sd 0:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[Thu Jun 11 17:10:17 2020] sd 0:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[Thu Jun 11 21:11:13 2020] sd 0:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[Fri Jun 12 10:40:17 2020] sd 0:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00

The hard drive made a click (like a bad click for hdd) and I assume that it's a power issue. Even if I use a 30W Apple original power supply.

What can you suggest me to do?

[134073.824203] sd 0:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[134073.824224] sd 0:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 c5 07 8b 00 00 00 01 00 00 00
[134073.824239] print_req_error: I/O error, dev sdb, sector 3305605888
[182617.523776] sd 0:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[182617.523795] sd 0:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 29 08 97 f8 00 00 00 08 00 00
[182617.523809] print_req_error: I/O error, dev sdb, sector 688429048

And I'm on:

Linux raspberrypi 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux

JamesH65 commented 4 years ago

This is very old issue, and closed, but, this is purely a power problem. The Pi can provide 1.2A total across all the USB ports. You are likely exceeding that. Use a powered hub.

marcotini commented 4 years ago

This is very old issue, and closed, but, this is purely a power problem. The Pi can provide 1.2A total across all the USB ports. You are likely exceeding that. Use a powered hub.

And a cable like this one can make a difference (plugging the other one on a different power supply)?

tim-devel commented 4 years ago

I have been having this issue for 2+ years with a usb hard drive via a powered hub so not sure it is a power issue. I've never lost any data so just ignore the errors

3dr14n commented 4 years ago

Same issue with my powered (12V2A) external drive bay Orico NS1066 for my WD80EZAZ-11T (ext4) connected to Raspberry Pi 4. The behavior is repeatable because as soon as iowait become high while playing 60GB H265 video via Kodi installed in Raspbian, the HDD disconnects from, for example sdb then reconnects to sdc .

Jul 5 19:04:04 megaserver kernel: [81232.365054] usb 2-2: Disable of device-initiated U1 failed. Jul 5 19:04:09 megaserver kernel: [81237.393757] usb 2-2: Disable of device-initiated U2 failed. Jul 5 19:04:18 megaserver kernel: [81246.141910] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 Jul 5 19:04:18 megaserver kernel: [81246.141920] usb 2-2: USB disconnect, device number 3 Jul 5 19:04:18 megaserver kernel: [81246.141930] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 a4 ee 3e e0 00 00 04 00 00 00 Jul 5 19:04:18 megaserver kernel: [81246.142295] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 Jul 5 19:04:18 megaserver kernel: [81246.142313] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 a4 ee 4a e0 00 00 02 00 00 00

The only solution is to restart, for the hdd to reconnect again via its default mount-point in fstab.

pelwell commented 4 years ago

Try disabling UAS by following this guide: https://www.raspberrypi.org/forums/viewtopic.php?t=245931

3dr14n commented 4 years ago

Try disabling UAS by following this guide: https://www.raspberrypi.org/forums/viewtopic.php?t=245931

UAS was already disabled when issuing a lsusb -t the driver was already in usb-storage even without applying quirks in cmdline.txt. Sure enough, I tried it anyway as instructed in the link provided for curiosity's sake but still the same behavior, disconnection and reconnection.

My main issue now could be because Norelsys NS1066 could be faulty but this issue does not happen on the earlier days of Pi4. Before I can copy 100GB of zip file to the same drive without any problem (via ethernet) but now I can't do the same, even media playback via Kodi makes the drive disconnect and reconnect afterwards.

I won't associate this with power issue because the dock was already powered via 12V2A. The drive disconnects as soon as iowait became red while being monitored via terminal using glances. Thermal is not an issue either because the Pi and the HDD are cooled via 120mm fan intake. The Pi4 were kept cool below 55°C while playing Kodi. I'm not doing any Overclocking with the Pi4.

I'm wondering if there were changes with the USB 3 chip in Pi4 that could cause this issue?

Addendum:

I tried to copy a 2.6GB video from Windows 10 to the HDD connected via samba and the file were copied successfully, copying the same video from the HDD causes the drive to disconnect and reconnect which interrupts the file copy. sudo mount -a will mount it to its proper mounting point specified in fstab.

Update Yep, the issue is due to Norelsys NS1066. Lots of reports in Linux forums with the same chip.