Welcome! Log In Create A New Profile

Advanced

GoFlex Net problem with Ext4 on USB

Posted by jay 
jay
GoFlex Net problem with Ext4 on USB
May 17, 2016 05:50AM
hi, i have a problem at a goflexnet:

[ 1256.923314] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[ 1257.094226] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1257.102558] sd 1:0:0:0: [sda] tag#0 Sense Key : Unit Attention [current]
[ 1257.109437] sd 1:0:0:0: [sda] tag#0 Add. Sense: Not ready to ready change, medium may have changed
[ 1257.118481] sd 1:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 16 a0 00 00 08 00
[ 1257.125859] blk_update_request: I/O error, dev sda, sector 5792
[ 1257.132191] EXT4-fs error (device sda1): ext4_wait_block_bitmap:499: comm dpkg: Cannot read block bitmap - block_group = 1, block_bitmap = 468
[ 1257.145357] Aborting journal on device sda1-8.
[ 1257.149909] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[ 1257.157716] EXT4-fs (sda1): Remounting filesystem read-only
[ 1257.163383] EXT4-fs error (device sda1) in ext4_do_update_inode:4555: Journal has aborted
[ 1257.171597] EXT4-fs (sda1): previous I/O error to superblock detected
[ 1257.178583] EXT4-fs error (device sda1) in ext4_alloc_file_blocks:4727: IO failure
[ 1257.186235] EXT4-fs (sda1): previous I/O error to superblock detected

also sometimes:
[ 20.566200] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 20.573131] EXT4-fs (sda1): write access will be enabled during recovery
[ 20.943311] usb 1-1: reset high-speed USB device number 2 using orion-ehci
[ 21.114335] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 21.122662] sd 1:0:0:0: [sda] tag#0 Sense Key : Unit Attention [current]
[ 21.129536] sd 1:0:0:0: [sda] tag#0 Add. Sense: Not ready to ready change, medium may have changed
[ 21.138576] sd 1:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 44 44 18 00 00 88 00
[ 21.145954] blk_update_request: I/O error, dev sda, sector 4473880
[ 21.152223] JBD2: Failed to read block at offset 1936
[ 21.157376] JBD2: recovery failed
[ 21.160783] EXT4-fs (sda1): error loading journal

i tried different usb sticks,
i formatted with -cc
i tried different goflex.
i tried ext3 and 4.

i use the 2015 uboot.

hints?

jay



Edited 3 time(s). Last edit at 05/17/2016 04:13PM by bodhi.
Re: Linux Kernel 4.5 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
May 17, 2016 02:12PM
I've seen this on my GFN's with earlier kernels too one day after the device boot.
The only way to solve this for me was to use an USB HUB.
Re: GoFlex Net problem with Ext4 on USB
May 17, 2016 04:17PM
jay Wrote:
-------------------------------------------------------
> hi, i have a problem at a goflexnet:
>
> [ 1256.923314] usb 1-1: reset high-speed USB
> device number 2 using orion-ehci
> [ 1257.094226] sd 1:0:0:0: [sda] tag#0 FAILED
> Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> [ 1257.102558] sd 1:0:0:0: [sda] tag#0 Sense Key :
> Unit Attention [current]
> [ 1257.109437] sd 1:0:0:0: [sda] tag#0 Add. Sense:
> Not ready to ready change, medium may have
> changed
> [ 1257.118481] sd 1:0:0:0: [sda] tag#0 CDB:
> Read(10) 28 00 00 00 16 a0 00 00 08 00
> [ 1257.125859] blk_update_request: I/O error, dev
> sda, sector 5792
> [ 1257.132191] EXT4-fs error (device sda1):
> ext4_wait_block_bitmap:499: comm dpkg: Cannot read
> block bitmap - block_group = 1, block_bitmap =
> 468
> [ 1257.145357] Aborting journal on device sda1-8.
> [ 1257.149909] JBD2: Error -5 detected when
> updating journal superblock for sda1-8.
> [ 1257.157716] EXT4-fs (sda1): Remounting
> filesystem read-only
> [ 1257.163383] EXT4-fs error (device sda1) in
> ext4_do_update_inode:4555: Journal has aborted
> [ 1257.171597] EXT4-fs (sda1): previous I/O error
> to superblock detected
> [ 1257.178583] EXT4-fs error (device sda1) in
> ext4_alloc_file_blocks:4727: IO failure
> [ 1257.186235] EXT4-fs (sda1): previous I/O error
> to superblock detected
>
> also sometimes:
> [ 20.566200] EXT4-fs (sda1): INFO: recovery
> required on readonly filesystem
> [ 20.573131] EXT4-fs (sda1): write access will
> be enabled during recovery
> [ 20.943311] usb 1-1: reset high-speed USB
> device number 2 using orion-ehci
> [ 21.114335] sd 1:0:0:0: [sda] tag#0 FAILED
> Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> [ 21.122662] sd 1:0:0:0: [sda] tag#0 Sense Key :
> Unit Attention [current]
> [ 21.129536] sd 1:0:0:0: [sda] tag#0 Add. Sense:
> Not ready to ready change, medium may have
> changed
> [ 21.138576] sd 1:0:0:0: [sda] tag#0 CDB:
> Read(10) 28 00 00 44 44 18 00 00 88 00
> [ 21.145954] blk_update_request: I/O error, dev
> sda, sector 4473880
> [ 21.152223] JBD2: Failed to read block at
> offset 1936
> [ 21.157376] JBD2: recovery failed
> [ 21.160783] EXT4-fs (sda1): error loading
> journal
>
> i tried different usb sticks,
> i formatted with -cc
> i tried different goflex.
> i tried ext3 and 4.
>
> i use the 2015 uboot.
>
> hints?
>
> jay


How many devices are you plugging in to this GFNet?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: GoFlex Net problem with Ext4 on USB
May 17, 2016 04:26PM
I think he has one device connected
this device only has one USB port.
Re: GoFlex Net problem with Ext4 on USB
May 17, 2016 07:38PM
bodhi Wrote:
-------------------------------------------------------
> jay Wrote:
> --------------------------------------------------
> -----
> > hi, i have a problem at a goflexnet:
> >
> > [ 1256.923314] usb 1-1: reset high-speed USB
> > device number 2 using orion-ehci
> > [ 1257.094226] sd 1:0:0:0: [sda] tag#0 FAILED
> > Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > [ 1257.102558] sd 1:0:0:0: [sda] tag#0 Sense Key
> :
> > Unit Attention [current]
> > [ 1257.109437] sd 1:0:0:0: [sda] tag#0 Add.
> Sense:
> > Not ready to ready change, medium may have
> > changed
> > [ 1257.118481] sd 1:0:0:0: [sda] tag#0 CDB:
> > Read(10) 28 00 00 00 16 a0 00 00 08 00
> > [ 1257.125859] blk_update_request: I/O error,
> dev
> > sda, sector 5792
> > [ 1257.132191] EXT4-fs error (device sda1):
> > ext4_wait_block_bitmap:499: comm dpkg: Cannot
> read
> > block bitmap - block_group = 1, block_bitmap =
> > 468
> > [ 1257.145357] Aborting journal on device
> sda1-8.
> > [ 1257.149909] JBD2: Error -5 detected when
> > updating journal superblock for sda1-8.
> > [ 1257.157716] EXT4-fs (sda1): Remounting
> > filesystem read-only
> > [ 1257.163383] EXT4-fs error (device sda1) in
> > ext4_do_update_inode:4555: Journal has aborted
> > [ 1257.171597] EXT4-fs (sda1): previous I/O
> error
> > to superblock detected
> > [ 1257.178583] EXT4-fs error (device sda1) in
> > ext4_alloc_file_blocks:4727: IO failure
> > [ 1257.186235] EXT4-fs (sda1): previous I/O
> error
> > to superblock detected
> >
> > also sometimes:
> > [ 20.566200] EXT4-fs (sda1): INFO: recovery
> > required on readonly filesystem
> > [ 20.573131] EXT4-fs (sda1): write access
> will
> > be enabled during recovery
> > [ 20.943311] usb 1-1: reset high-speed USB
> > device number 2 using orion-ehci
> > [ 21.114335] sd 1:0:0:0: [sda] tag#0 FAILED
> > Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > [ 21.122662] sd 1:0:0:0: [sda] tag#0 Sense Key
> :
> > Unit Attention [current]
> > [ 21.129536] sd 1:0:0:0: [sda] tag#0 Add.
> Sense:
> > Not ready to ready change, medium may have
> > changed
> > [ 21.138576] sd 1:0:0:0: [sda] tag#0 CDB:
> > Read(10) 28 00 00 44 44 18 00 00 88 00
> > [ 21.145954] blk_update_request: I/O error,
> dev
> > sda, sector 4473880
> > [ 21.152223] JBD2: Failed to read block at
> > offset 1936
> > [ 21.157376] JBD2: recovery failed
> > [ 21.160783] EXT4-fs (sda1): error loading
> > journal
> >
> > i tried different usb sticks,
> > i formatted with -cc
> > i tried different goflex.
> > i tried ext3 and 4.
> >
> > i use the 2015 uboot.
> >
> > hints?
> >
> > jay
>
>
> How many devices are you plugging in to this
> GFNet?

Devices meant USB, SATA, .... anything.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: