RaspberryPi and HDD

This forum is for topics specific to the Raspberry Pi and Arch Linux ARM

RaspberryPi and HDD

Postby pttournesol » Tue May 24, 2016 8:44 pm

Hello,
As you can see I'm new in this forum and I want to say thanks for further help. :)
A week ago I have decided to build up a NAS server with my Raspberry PI and a HDD, I have used this HDD before with debian installed Beaglebone Black without any error.
But some reason I couldn't use this HDD with Arch Linux installed RPi properly.
The problem is, I can read without any problem but when it is the time to write something to this HDD (from SSH login or Samba), this HDD stops working. After power off/on the RPi, eveything works well and able to write something (even transfer big files with samba). HDD is plugged in powered USB hub, RPi supplied with 5V/1A phone charger.

Related records included below.
$this->bbcode_second_pass_code('', '
DMESG:
[10984.031350] sd 1:0:0:0: Device offlined - not ready after error recovery
[10984.038315] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
[10984.046798] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 24 00 08 80 00 00 08 00
[10984.054596] blk_update_request: I/O error, dev sdb, sector 603981952
[10984.068971] EXT4-fs error (device sdb1): ext4_read_inode_bitmap:223: comm smbd: Cannot read inode bitmap - block_group = 2304, inode_bitmap = 75497488
[10984.082963] usb 1-1.3.3: USB disconnect, device number 7
[10984.176009] EXT4-fs (sdb1): I/O error while writing superblock
[10984.205287] Aborting journal on device sdb1-8.
[10984.209982] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[10984.232085] EXT4-fs error (device sdb1) in ext4_create:2458: IO failure
[10984.253620] EXT4-fs (sdb1): previous I/O error to superblock detected
[10984.260398] EXT4-fs error (device sdb1): ext4_journal_check_start:56: Detected aborted journal
[10984.269454] EXT4-fs (sdb1): Remounting filesystem read-only
[10984.275273] EXT4-fs (sdb1): previous I/O error to superblock detected
[10998.821471] usb 1-1.3.3: new high-speed USB device number 9 using dwc_otg
[10998.942861] usb 1-1.3.3: New USB device found, idVendor=13fd, idProduct=0840
[10998.950119] usb 1-1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10998.963454] usb 1-1.3.3: Product: External
[10998.970615] usb 1-1.3.3: Manufacturer: Generic
[10998.978103] usb 1-1.3.3: SerialNumber:
[10999.001001] usb-storage 1-1.3.3:1.0: USB Mass Storage device detected
[10999.016147] scsi host2: usb-storage 1-1.3.3:1.0
[11000.022775] scsi 2:0:0:0: Direct-Access Generic External 1.14 PQ: 0 ANSI: 4
[11000.044541] sd 2:0:0:0: [sdc] 625142447 512-byte logical blocks: (320 GB/298 GiB)
[11000.077777] sd 2:0:0:0: [sdc] Write Protect is off
[11000.085392] sd 2:0:0:0: [sdc] Mode Sense: 23 00 00 00
[11000.096508] sd 2:0:0:0: [sdc] No Caching mode page found
[11000.104548] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[11000.147679] sdc: sdc1
[11000.164537] sd 2:0:0:0: [sdc] Attached SCSI disk
[20660.766653] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20660.835025] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20660.887061] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20663.515271] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20663.559328] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20663.611301] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20670.044265] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20670.091650] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20670.143661] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20707.850259] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20708.066193] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20708.222139] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20725.063364] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20725.151355] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20725.211421] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20762.251477] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20762.313399] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20762.353305] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20768.862684] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20768.898255] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20768.937324] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20779.703017] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20779.755089] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20779.801325] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20812.049244] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20812.113205] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20812.163436] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20923.152621] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20933.017435] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
[20994.373475] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm ls: error -5 reading directory block
[21011.556794] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm bash: error -5 reading directory block
[21011.601245] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm bash: error -5 reading directory block
[21011.625303] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm bash: error -5 reading directory block
[21011.644171] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm bash: error -5 reading directory block
[21028.562782] sd 2:0:0:0: Device offlined - not ready after error recovery
[21028.573515] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00
[21028.589390] sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00
[21028.604631] blk_update_request: I/O error, dev sdc, sector 0
[21028.614200] Buffer I/O error on dev sdc, logical block 0, async page read
[21028.624907] sd 2:0:0:0: rejecting I/O to offline device
[21028.633749] sd 2:0:0:0: [sdc] killing request
[21028.641689] sd 2:0:0:0: rejecting I/O to offline device
[21028.650661] sd 2:0:0:0: [sdc] UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[21028.677845] sd 2:0:0:0: [sdc] CDB: opcode=0x28 28 00 00 00 00 01 00 00 01 00
[21028.694718] blk_update_request: I/O error, dev sdc, sector 1
[21028.710192] Buffer I/O error on dev sdc, logical block 1, async page read
[21028.732243] usb 1-1.3.3: USB disconnect, device number 9
[21042.802981] usb 1-1.3.3: new high-speed USB device number 10 using dwc_otg
[21042.914401] usb 1-1.3.3: New USB device found, idVendor=13fd, idProduct=0840
[21042.924843] usb 1-1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[21042.938783] usb 1-1.3.3: Product: External
[21042.946145] usb 1-1.3.3: Manufacturer: Generic
[21042.953764] usb 1-1.3.3: SerialNumber:
[21042.975483] usb-storage 1-1.3.3:1.0: USB Mass Storage device detected
[21042.988019] scsi host3: usb-storage 1-1.3.3:1.0
[21043.994295] scsi 3:0:0:0: Direct-Access Generic External 1.14 PQ: 0 ANSI: 4
[21044.015984] sd 3:0:0:0: [sdc] 625142447 512-byte logical blocks: (320 GB/298 GiB)
[21044.049695] sd 3:0:0:0: [sdc] Write Protect is off
[21044.057315] sd 3:0:0:0: [sdc] Mode Sense: 23 00 00 00
[21044.068110] sd 3:0:0:0: [sdc] No Caching mode page found
[21044.076192] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[21044.118805] sdc: sdc1
[21044.136139] sd 3:0:0:0: [sdc] Attached SCSI disk
[21128.766283] EXT4-fs warning (device sdb1): dx_probe:740: inode #2: lblock 0: comm smbd: error -5 reading directory block
')

$this->bbcode_second_pass_code('', 'lsusb:
Bus 001 Device 006: ID 13fd:0840 Initio Corporation INIC-1618L SATA
Bus 001 Device 005: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. SMC9512/9514 USB Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub')

$this->bbcode_second_pass_code('', 'uname -r:
4.4.8-2-ARCH')

$this->bbcode_second_pass_code('', 'fdisk -l:
Disk /dev/sdb: 298.1 GiB, 320072932864 bytes, 625142447 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos')
pttournesol
 
Posts: 1
Joined: Tue May 24, 2016 8:40 pm

Re: RaspberryPi and HDD

Postby sdjf » Wed May 25, 2016 12:39 am

I bet the HDD would not work now on raspbian, have you tried it again there? Looks like corruption, hopefully you have everything on the HDD backed up. It may be that the charger is not supplying enough power? Have you run fsck.ext4 on the HDD? You don't want to attempt any write operations unless the journal has a clean bill of health.

In some cases, I have found that the Pi will tell me a usb device is corrupt, and after I remove and reinsert it, the Pi changes it's mind. So if you have another box, you might want to run the fsck there to make sure you aren't correcting problems that aren't there. Could be faulty cable, loose connection, inadequate power, or dust on the connectors.
sdjf
 
Posts: 178
Joined: Wed May 08, 2013 1:55 pm


Return to Raspberry Pi

Who is online

Users browsing this forum: No registered users and 5 guests