• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Guruplug USB harddisk, journal i/o errors  (Read 3795 times)
Nestor
Newbie
*

Karma: 0
Posts: 1


View Profile
« on: January 14, 2011, 07:30:49 AM »

Recently I bought a Freecom XXS (500 GB) external USB disk to attach to the Guruplug Server Plus. Let me first say I am sure the disk works perfect on my laptop (formatted it, can copy files to/from it).

But when I have mounted the USB disk (tried both USB ports on the Guruplug) and start copying files from the Guruplug to the external USB disk I get random I/O errors and the disk gets disconnected:

First it can transfer some files, but soon I get the message the USB harddisk file system has become 'read only':

Quote
cp: cannot create regular file `./erode_comparison.png': Read-only file system
cp: cannot create regular file `./face.gif': Read-only file system
cp: cannot create regular file `./fietsroute.jpg': Read-only file system
cp: cannot create regular file `./film.jpg': Read-only file system
cp: cannot create regular file `./fonzie.jpg': Read-only file system

And the kernel says:
Quote
[442511.593520] kjournald starting.  Commit interval 5 seconds
[442511.600446] EXT3 FS on sdc1, internal journal
[442538.556684] Aborting journal on device sdc1.
[442538.561108] journal commit I/O error
[442538.568669] EXT3-fs error (device sdc1): ext3_journal_start_sb: Detected aborted journal

But within a few seconds the kernel reassigns a new block device. Plugging it in for the first time the block device might be /dev/sdc1, but when the journal I/O errors appear it disconnects
and reconnects and appears under a new block device name, for example /dev/sdd1. Then I remount under the new name, but soon I get the same errors again and it disconnects/reconnects
again and choses /dev/sde1. This keeps incrementing.

I am running Debian with kernel 2.6.32-5-kirkwood  and when I plugin the USB harddisk the first time I get:

Quote
[436171.601709] usb 1-1.3: new high speed USB device using orion-ehci and address 4
[436171.712299] usb 1-1.3: New USB device found, idVendor=07ab, idProduct=fc88
[436171.719299] usb 1-1.3: New USB device strings: Mfr=3, Product=11, SerialNumber=5
[436171.726835] usb 1-1.3: Product: Freecom Mobile Drive XXS
[436171.732293] usb 1-1.3: Manufacturer: Freecom
[436171.736667] usb 1-1.3: SerialNumber: C2272F141A0C
[436171.743057] usb 1-1.3: configuration #1 chosen from 1 choice
[436171.749781] scsi1 : SCSI emulation for USB Mass Storage devices
[436171.757170] usb-storage: device found at 4
[436171.757180] usb-storage: waiting for device to settle before scanning
[436176.751708] usb-storage: device scan complete
[436176.793873] scsi 1:0:0:0: Direct-Access     Freecom  Mobile Drive XXS      PQ: 0 ANSI: 2 CCS
[436176.807089] sd 1:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[436176.819451] sd 1:0:0:0: [sdc] Write Protect is off
[436176.824405] sd 1:0:0:0: [sdc] Mode Sense: 28 00 00 00
[436176.824416] sd 1:0:0:0: [sdc] Assuming drive cache: write through
[436176.832310] sd 1:0:0:0: [sdc] Assuming drive cache: write through
[436176.838524]  sdc: sdc1
[436176.872066] sd 1:0:0:0: [sdc] Assuming drive cache: write through
[436176.878278] sd 1:0:0:0: [sdc] Attached SCSI disk

I mount the external harddisk as follows:

Quote
mount -o rw -t ext3 /dev/sdc1 /media/freecom500gb/

The journal I/O errors appear random, I can copy a few files, but soon it will result in the filesystem becoming read only and giving journal I/O errors. I read on the internet there might be issues with the USB being too fast to handle by the current kernels? Is there anyone out there who is also using an external USB harddisk which is working without any problems? Or does anyone have an idea what is going on?

« Last Edit: January 14, 2011, 07:32:52 AM by Nestor » Logged

pietsnot
Newbie
*

Karma: 1
Posts: 41


View Profile
« Reply #1 on: January 17, 2011, 04:02:52 AM »


iŽam using sometimes a (ad-hoc/hotplugged) 1Tb usb disk, default automounted, working without any problems:

df
/dev/sde3            960681352 924988004  35693348  97% /media/usb1
/dev/sde1               252960    120020    132940  48% /media/usb3

mtab
/dev/sde3 /media/usb1 ext3 rw,noexec,nodev,sync,noatime,nodiratime 0 0
/dev/sde1 /media/usb3 ext3 rw,noexec,nodev,sync,noatime,nodiratime 0 0

lsusb
Bus 001 Device 005: ID 152d:2336 JMicron Technology Corp. / JMicron USA Technology Corp. Hard Disk Drive
  idVendor           0x152d JMicron Technology Corp. / JMicron USA Technology Corp.
  idProduct          0x2336 Hard Disk Drive
  bcdDevice            1.00
  iManufacturer           1 JMicron
  iProduct                2 JM20336 SATA, USB Combo

sdparm -i /dev/sde
    /dev/sde: SAMSUNG   HD103UJ


tune2fs -l /dev/sde3
tune2fs 1.41.12 (17-May-2010)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          3183efd8-dd37-4fa2-8204-60defb3812f3
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal filetype needs_recovery sparse_super large_file
Filesystem flags:         unsigned_directory_hash
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              122011648
Block count:              243999236
Reserved block count:     0
Free blocks:              8923337
Free inodes:              121876596
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16384
Inode blocks per group:   512
Filesystem created:       Sun May 24 16:44:30 2009
Last mount time:          Thu Jan 13 22:10:22 2011
Last write time:          Thu Jan 13 22:10:22 2011
Mount count:              220
Maximum mount count:      23

Logged

[unbricked]2xguruplug-server+2xjtag>nslu2;debian squeeze; [4|8]gb mmc:rootFS+swapFS; sata-hd 2tb; Linux-kernel-2.6.35.12; U-Boot_2010.03-01266; iptables:FW+router+gw;dhcpd;sshd;sabnzbd;vsftpd;exim4;rTorrent; nfs[d]; autofs; xorg; icewm; iceweasel; xrdp; privoxy+tor; apache; smbd; mediatomb>pch-a110

entropy
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #2 on: January 19, 2011, 05:44:15 PM »


But within a few seconds the kernel reassigns a new block device. Plugging it in for the first time the block device might be /dev/sdc1, but when the journal I/O errors appear it disconnects
and reconnects and appears under a new block device name, for example /dev/sdd1. Then I remount under the new name, but soon I get the same errors again and it disconnects/reconnects
again and choses /dev/sde1. This keeps incrementing.


Any chance you're using the plug to power the drive? I had a very similar symptom but it was caused by the fan going out.  The fan would drag down with resistance and slow down.  That would drag down the power supply voltage and everything on the USB bus would reset.  If you're powering the drive from the plug, you might be dragging down the power supply voltage.
Logged

aliosa27
Newbie
*

Karma: 0
Posts: 6


View Profile
« Reply #3 on: March 18, 2011, 07:51:12 AM »

I have noticed that anything i/o intensive  when you have a usb device as a root device will cause
journel errors and remounts. In my case, I have my my root on microsd and 1 atsc and 1 dvb-s
receiver all on the usb bus. using 2 atsc cards and the microsd for root works great, using 1 dvb-s and
root via microsd causes a remount of the card to ro and missing data.

So its really a limitation of usb that causes this whole mess.

If I use the esata for root, then i can happily use 2 dvbs tuners and no forced remounts happen,no corrupting of the card.
Logged

Pages: [1]
Print
Jump to: