I think I saw something like this on d-u recently, I'll practice my translating on the post:
2014/12/09 14:27 "Jun Itou" <itou_jun@infoseek.jp>:
>
> Jun Itouです。
>
> お世話になります。
"Hello", etc.
> Debian7.6から7.7に変更してからUSB HDDが書込不可の症状に直面しています。
Jun is having problems writing to USB HDD after installing Debian 7.7.
> (7.6でもapt-get upgradeして同症状が出ているかもしれませんが、今回は新規インストールのため未確認)
> kernelの比較のため、kernel.orgから3.2.62と3.2.63をDLし両者をインストールして比較しました。
Doesn't know if he'd have the same problems on an upgrade from 7.6 to 7.7, he hasn't tried that. (Except he says below that he has, after all. Maybe after the first post.)
> HDDは3.2.62でfdiskとmkfs.ext4を実行し、その状態で3.2.62と3.2.63でmountとumountを実行してdmesgを取得してみました。
He has tried comparing results with the two named kernels, extracts from the dmesgs, with uname, below.
> 以下、両者のuname -aとdmesgのです。
>
> Linux sv-server 3.2.62 #1 SMP Mon Dec 8 16:11:25 JST 2014 x86_64 GNU/Linux
> [ 97.356924] usb 1-1: new high-speed USB device number 2 using ehci_hcd
> [ 97.659888] usb 1-1: New USB device found, idVendor=04bb, idProduct=0109
> [ 97.659892] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 97.659895] usb 1-1: Product: I-O DATA HDZ-UES
> [ 97.659897] usb 1-1: Manufacturer: I-O DATA DEVICE INC.
> [ 97.659899] usb 1-1: SerialNumber: 0000000042A4
> [ 97.710211] Initializing USB Mass Storage driver...
> [ 97.710896] scsi3 : usb-storage 1-1:1.0
> [ 97.711053] usbcore: registered new interface driver usb-storage
> [ 97.711055] USB Mass Storage support registered.
> [ 98.714628] scsi 3:0:0:0: Direct-Access I-O DATA HDZ-UE1.0TS 6706 PQ: 0 ANSI: 0 CCS
> [ 98.716173] sd 3:0:0:0: Attached scsi generic sg2 type 0
> [ 98.720033] sd 3:0:0:0: [sdb] 1953588672 512-byte logical blocks: (1.00 TB/931 GiB)
> [ 98.726121] sd 3:0:0:0: [sdb] Write Protect is off
> [ 98.726125] sd 3:0:0:0: [sdb] Mode Sense: 34 00 00 00
> [ 98.733164] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [ 98.762988] sdb: sdb1
> [ 98.784513] sd 3:0:0:0: [sdb] Attached SCSI disk
> [ 126.657792] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
> Linux sv-server 3.2.63 #1 SMP Mon Dec 8 18:22:55 JST 2014 x86_64 GNU/Linux
> [ 101.331092] usb 1-1: new high-speed USB device number 2 using ehci_hcd
> [ 101.641961] usb 1-1: New USB device found, idVendor=04bb, idProduct=0109
> [ 101.641964] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 101.641967] usb 1-1: Product: I-O DATA HDZ-UES
> [ 101.641968] usb 1-1: Manufacturer: I-O DATA DEVICE INC.
> [ 101.641969] usb 1-1: SerialNumber: 0000000042A4
> [ 101.690910] Initializing USB Mass Storage driver...
> [ 101.692081] scsi3 : usb-storage 1-1:1.0
> [ 101.692298] usbcore: registered new interface driver usb-storage
> [ 101.692299] USB Mass Storage support registered.
> [ 102.696841] scsi 3:0:0:0: Direct-Access I-O DATA HDZ-UE1.0TS 6706 PQ: 0 ANSI: 0 CCS
> [ 102.698543] sd 3:0:0:0: Attached scsi generic sg2 type 0
> [ 102.702731] sd 3:0:0:0: [sdb] 1953588672 512-byte logical blocks: (1.00 TB/931 GiB)
> [ 102.709340] sd 3:0:0:0: [sdb] Write Protect is off
> [ 102.709343] sd 3:0:0:0: [sdb] Mode Sense: 34 00 00 00
> [ 102.716254] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [ 102.743219] sdb: sdb1
> [ 102.763781] sd 3:0:0:0: [sdb] Attached SCSI disk
> [ 112.707426] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
> [ 117.075758] end_request: I/O error, dev sdb, sector 0
> [ 117.081523] end_request: I/O error, dev sdb, sector 973342744
> [ 117.081739] Aborting journal on device sdb1-8.
> [ 117.083837] journal commit I/O error
> [ 117.086427] EXT4-fs error (device sdb1): ext4_put_super:819: Couldn't clean up the journal
> [ 117.086716] EXT4-fs (sdb1): Remounting filesystem read-only
*** I'll flag the above lines, where the dmesg says it couldn't clean up the journal
and mounted it R/O.
Kin-neko opined, 6 days ago, that the hardware was feeling its age and should be replaced.
> ソースのdiffを取るとドライバーやファイルシステム等に手が入っているみたいですね。
> そこから先の問題点の追求はどうやったらいいものか、現在手詰まり状態です。
> どのソースファイルが問題なのか分かれば対応してもらうとかできるんですけど…。
Says he's noticed that the drivers and file system source has been worked on, but doesn't know how to dig deeper. If he knew which file to focus on, he'd try.
> このUSB HDDはIDE形式のHDDが4台入っています。
4 IDE drives in the enclosure.
> 多分、JBODで連結されていると思います。
He thinks they are aggregated by JBOD.
> HDDは単体でHDDメーカーのツールにて物理的な問題が無い事を確認して有ります。
He's tested the individual disks with the manufacturer's utilities.
> HDZ-UESとしては3台持っていて、どれも同じ症状なので個体の問題では無いと思います。
He has three of these HDZ-UES enclosures, all seem to show the same symptoms.
> 一応思い出せる範囲で以下の事を確認しました。
He's tried the following:
> ・各ドライブ単体を取り出し、HDDメーカーの診断ソフトにて全セクターをR/Wして問題無い事を確認
Pulled each drive and run R/W tests on all sectors.
> ・診断ソフトにて全セクターを0で書き潰し、7.7で同症状が再現する事を確認
Confirmed the issue after clearing all sectors to 0.
> ・同症状が出ている状態でLive CDの7.6でfdiskやlsをやってもエラーやroにならない事を確認
He is able to write to the array using a 7.6 Live CD.
> ・I-O DATAの同シリーズのUSB HDDを3台用意し、それぞれ同症状が出る事を確認
Confirmed on three other enclosures of the same series.
> ・sata仕様のHDD×1台のUSB HDDで7.7にて同症状が再現しない事を確認
Confirmed that the system, under 7.7, is able to write to single USB-attached SATA drives with no problems.
> ・sata仕様のHDD×2台のUSB HDDをハードウェアRAID0で構築し7.7にて同症状が再現しない事を確認
Similarly, USB-attached SATA drives attached in hardware RAID0 do not show this symptom.
> ・IDE仕様のHDD×1台のUSB HDDで7.7にて同症状が再現しない事を確認
Likewise, USB-attached single IDE drives do not show the symptom.
> ・一つ前のkernelに戻すと再現しない事を確認
Reverting to the previous kernel, the symptom goes away.
> ・7.6からapt-get upgradeで更新してきたものでも再現する事を確認
Confirmed the symptoms occur on upgrade, as well.
> ・7.7でtouchでファイルを作ろうとすると”touch: `/mnt/test.txt' に touch できません: 読み込み専用ファイルシステムです”となる事を確認
Attmpted touch yields write protect errors.
> ・kernel.orgから3.2.62と3.2.63をDLして導入し、3.2.62で再現せず3.2.63で再現する事を確認
Tried the two kernels, as he says above, error reproduced on 3.2.63, no error on 3.2.62.
> ・フォーマットがext3でも再現する事を確認
Same results with ext3 format.
> なおFedora20でも同症状が再現できるのでkernelの問題だと思います。
Same problems with Fedoran20, suspects the kernel. Fedora uname and dmesg below:
> Fedora20でfdiskを別々のUSB HDDにした時のdmesgです。
> (uname -aはLinux localhost.localdomain 3.17.4-200.fc20.i686+PAE #1 SMP Fri Nov 21 23:45:26 UTC 2014 i686 i686 i386 GNU/Linux)
>
> [root@localhost ~]# dmesg
> [11378.635292] sdb: sdb1
> [11378.644515] end_request: critical target error, dev sdb, sector 0
> [11505.048965] sdc: sdc1
> [11505.070962] end_request: critical target error, dev sdc, sector 0
>
> デバイスは以下のとおりです。
>
> [12323.199222] usb 1-2: USB disconnect, device number 3
> [12323.204864] sd 4:0:0:0: [sdc] Synchronizing SCSI cache
> [12323.204969] sd 4:0:0:0: [sdc]
> [12323.205036] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> [12328.983064] usb 1-2: new high-speed USB device number 4 using ehci-pci
> [12329.254305] usb 1-2: New USB device found, idVendor=04bb, idProduct=0106
> [12329.254310] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [12329.254312] usb 1-2: Product: I-O DATA HDW-UE
> [12329.254317] usb 1-2: Manufacturer: I-O DATA DEVICE,INC.
> [12329.254319] usb 1-2: SerialNumber: 0000000015B4
> [12329.256556] usb-storage 1-2:1.0: USB Mass Storage device detected
> [12329.256668] scsi host5: usb-storage 1-2:1.0
> [12330.306516] usb 1-1: USB disconnect, device number 2
> [12330.311660] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
> [12330.311947] sd 3:0:0:0: [sdb]
> [12330.311959] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> [12335.938510] usb 1-1: new high-speed USB device number 5 using ehci-pci
> [12336.197402] usb 1-1: New USB device found, idVendor=04bb, idProduct=0109
> [12336.197408] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [12336.197411] usb 1-1: Product: I-O DATA HDZ-UES
> [12336.197413] usb 1-1: Manufacturer: I-O DATA DEVICE INC.
> [12336.197416] usb 1-1: SerialNumber: 0000000042A4
> [12336.200728] usb-storage 1-1:1.0: USB Mass Storage device detected
> [12336.202401] scsi host6: usb-storage 1-1:1.0
> [12338.413255] scsi 5:0:0:0: Direct-Access I-O DATA HDW-UE 0100 PQ: 0 ANSI: 2
> [12338.414954] sd 5:0:0:0: Attached scsi generic sg2 type 0
> [12338.418619] sd 5:0:0:0: [sdb] 1953546336 512-byte logical blocks: (1.00 TB/931 GiB)
> [12338.424650] sd 5:0:0:0: [sdb] Write Protect is off
> [12338.424654] sd 5:0:0:0: [sdb] Mode Sense: 53 00 00 08
> [12338.430284] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [12338.457232] sdb: sdb1
> [12338.476721] sd 5:0:0:0: [sdb] Attached SCSI disk
> [12338.739881] scsi 6:0:0:0: Direct-Access I-O DATA HDZ-UE1.0TS 6706 PQ: 0 ANSI: 0 CCS
> [12338.740452] sd 6:0:0:0: Attached scsi generic sg3 type 0
> [12338.743802] sd 6:0:0:0: [sdc] 1953588672 512-byte logical blocks: (1.00 TB/931 GiB)
> [12338.750306] sd 6:0:0:0: [sdc] Write Protect is off
> [12338.750310] sd 6:0:0:0: [sdc] Mode Sense: 34 00 00 00
> [12338.757360] sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [12338.786386] sdc: sdc1
> [12338.807891] sd 6:0:0:0: [sdc] Attached SCSI disk
>
> 何かアドバイスをいただけたら幸いです。
> (kernelの開発チームへ問い合わせればいいんでしょうけど英語オンリーなので敷居が高すぎまして)(^_^;)
>
> 以上、宜しくお願いします。
Wants advice, hasn't contacted the kernel team because of the language barrier.
TIA.
PS--------追伸---------
Jun,
We got another kernel update yesterday (that froze my X11 session). How are things now?
昨日のカーネル更新後どうですか？
--
Joel