From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 89511] USB-storage mount error
Date: Wed, 10 Dec 2014 22:33:54 +0000 [thread overview]
Message-ID: <bug-89511-13602-4qE24D1CZT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-89511-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=89511
--- Comment #2 from Jun Itou <itou_jun@infoseek.jp> ---
(In reply to Alan from comment #1)
> Are you configuration options for the two kernels exactly the same ?
Yes.
> Can you try with a more modern kernel base (3.16+) ?
I did the following tries.
A partition and the practice of the format are gone with ver.3.2.62.
Each environment is the same.
root@sv-server:~# uname -a
Linux sv-server 3.18.0 #1 SMP Wed Dec 10 09:05:25 JST 2014 x86_64 GNU/Linux
root@sv-server:~# mount /dev/sdb1 /mnt/usb1
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
root@sv-server:~# dmesg
[ 133.987321] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 134.521663] usb 2-1: New USB device found, idVendor=04bb, idProduct=0109
[ 134.521668] usb 2-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 134.521671] usb 2-1: Product: I-O DATA HDZ-UES
[ 134.521672] usb 2-1: Manufacturer: I-O DATA DEVICE INC.
[ 134.521674] usb 2-1: SerialNumber: 0000000075A7
[ 134.746148] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 134.746260] scsi host3: usb-storage 2-1:1.0
[ 134.746422] usbcore: registered new interface driver usb-storage
[ 135.748525] scsi 3:0:0:0: Direct-Access I-O DATA HDZ-UE2.0TS 6706
PQ: 0 ANSI: 0 CCS
[ 135.749165] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 135.752517] sd 3:0:0:0: [sdb] 3907092672 512-byte logical blocks: (2.00
TB/1.81 TiB)
[ 135.758532] sd 3:0:0:0: [sdb] Write Protect is off
[ 135.758536] sd 3:0:0:0: [sdb] Mode Sense: 34 00 00 00
[ 135.763999] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 135.784529] sdb: sdb1
[ 135.801515] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 195.009482] blk_update_request: critical target error, dev sdb, sector 0
[ 195.009758] JBD2: recovery failed
[ 195.009766] EXT4-fs (sdb1): error loading journal
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-12-10 22:33 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 2:35 [Bug 89511] New: USB-storage mount error bugzilla-daemon
2014-12-10 17:17 ` [Bug 89511] " bugzilla-daemon
2014-12-10 22:33 ` bugzilla-daemon [this message]
2014-12-10 22:51 ` bugzilla-daemon
2014-12-11 10:00 ` bugzilla-daemon
2014-12-11 19:31 ` bugzilla-daemon
2014-12-12 13:01 ` bugzilla-daemon
2014-12-13 7:41 ` bugzilla-daemon
2014-12-16 21:50 ` bugzilla-daemon
2014-12-19 8:36 ` bugzilla-daemon
2014-12-19 8:41 ` bugzilla-daemon
2014-12-19 8:42 ` bugzilla-daemon
2014-12-19 8:44 ` bugzilla-daemon
2014-12-19 8:44 ` bugzilla-daemon
2014-12-19 8:48 ` bugzilla-daemon
2014-12-19 8:50 ` bugzilla-daemon
2014-12-19 18:51 ` bugzilla-daemon
2014-12-19 21:15 ` bugzilla-daemon
2014-12-19 21:16 ` bugzilla-daemon
2014-12-19 21:19 ` bugzilla-daemon
2014-12-19 22:11 ` bugzilla-daemon
2014-12-20 1:48 ` bugzilla-daemon
2014-12-20 1:50 ` bugzilla-daemon
2014-12-20 1:50 ` bugzilla-daemon
2014-12-20 1:55 ` bugzilla-daemon
2014-12-25 7:45 ` bugzilla-daemon
2014-12-25 21:03 ` bugzilla-daemon
2014-12-26 7:56 ` bugzilla-daemon
2014-12-26 15:51 ` bugzilla-daemon
2014-12-26 22:08 ` bugzilla-daemon
2014-12-27 12:51 ` bugzilla-daemon
2014-12-27 13:01 ` bugzilla-daemon
2014-12-28 8:15 ` bugzilla-daemon
2014-12-28 8:24 ` bugzilla-daemon
2014-12-28 8:32 ` bugzilla-daemon
2015-01-02 0:49 ` bugzilla-daemon
2015-01-03 23:47 ` bugzilla-daemon
2015-01-04 20:12 ` bugzilla-daemon
2015-01-05 12:10 ` bugzilla-daemon
2015-01-05 13:48 ` bugzilla-daemon
2015-01-06 1:08 ` bugzilla-daemon
2015-01-06 1:42 ` bugzilla-daemon
2015-01-07 1:55 ` bugzilla-daemon
2015-01-08 13:01 ` bugzilla-daemon
2015-01-08 14:14 ` bugzilla-daemon
2015-01-09 13:46 ` bugzilla-daemon
2015-01-09 13:46 ` bugzilla-daemon
2015-01-09 19:54 ` bugzilla-daemon
2015-01-09 20:56 ` bugzilla-daemon
2015-01-09 21:19 ` bugzilla-daemon
2015-01-10 21:13 ` bugzilla-daemon
2015-01-11 1:29 ` bugzilla-daemon
2015-01-11 2:22 ` bugzilla-daemon
2015-06-04 7:47 ` bugzilla-daemon
2015-06-05 14:54 ` bugzilla-daemon
2015-06-07 10:22 ` bugzilla-daemon
2015-06-07 14:35 ` bugzilla-daemon
2015-06-07 22:12 ` bugzilla-daemon
2015-06-09 20:40 ` bugzilla-daemon
2015-06-09 21:11 ` bugzilla-daemon
2015-06-11 2:01 ` bugzilla-daemon
2015-06-11 13:56 ` bugzilla-daemon
2015-06-11 18:22 ` bugzilla-daemon
2015-06-11 18:46 ` bugzilla-daemon
2015-06-17 17:05 ` bugzilla-daemon
2015-06-17 17:18 ` bugzilla-daemon
2015-06-17 17:54 ` bugzilla-daemon
2015-06-17 19:56 ` bugzilla-daemon
2015-06-19 23:50 ` bugzilla-daemon
2015-06-21 8:59 ` bugzilla-daemon
2015-06-22 14:33 ` bugzilla-daemon
2015-07-22 17:39 ` bugzilla-daemon
2015-12-03 1:18 ` bugzilla-daemon
2015-12-03 23:25 ` bugzilla-daemon
2015-12-03 23:52 ` bugzilla-daemon
2017-09-17 12:12 ` bugzilla-daemon
2017-09-18 20:59 ` bugzilla-daemon
2017-09-19 14:46 ` bugzilla-daemon
2017-09-19 15:04 ` bugzilla-daemon
2017-09-19 17:18 ` bugzilla-daemon
[not found] <bug-89511-1728-xp33cMoHb4@https.bugzilla.kernel.org/>
2015-06-05 14:54 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-89511-13602-4qE24D1CZT@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.