1

When I plug my 1-terabyte Seagate hard drive in a USB port on my desktop PC, it mounts NTFS filesystem /dev/sdc1 successfully but fails to mount ext filesystem /dev/sdc2 because of an apparent error loading the filesystem journal.

Here is what appears in /var/log/syslog during the few seconds after I plug the drive in:

Jun 24 20:48:11 somehost kernel: [6670321.891087] usb 1-1.2: new high-speed USB device number 44 using ehci-pci
Jun 24 20:48:11 somehost kernel: [6670322.010683] usb 1-1.2: New USB device found, idVendor=0bc2, idProduct=2332
Jun 24 20:48:11 somehost kernel: [6670322.010689] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 24 20:48:11 somehost kernel: [6670322.010693] usb 1-1.2: Product: Portable
Jun 24 20:48:11 somehost kernel: [6670322.010696] usb 1-1.2: Manufacturer: Seagate
Jun 24 20:48:11 somehost kernel: [6670322.010699] usb 1-1.2: SerialNumber: 2GHH43FZ
Jun 24 20:48:11 somehost mtp-probe: checking bus 1, device 44: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2"
Jun 24 20:48:11 somehost mtp-probe: bus: 1, device: 44 was not an MTP device
Jun 24 20:48:11 somehost kernel: [6670322.011257] usb-storage 1-1.2:1.0: USB Mass Storage device detected
Jun 24 20:48:11 somehost kernel: [6670322.011309] scsi50 : usb-storage 1-1.2:1.0
Jun 24 20:48:12 somehost kernel: [6670323.011231] scsi 50:0:0:0: Direct-Access     Seagate  Portable         SF04 PQ: 0 ANSI: 4
Jun 24 20:48:12 somehost kernel: [6670323.011508] sd 50:0:0:0: Attached scsi generic sg3 type 0
Jun 24 20:48:12 somehost kernel: [6670323.012501] sd 50:0:0:0: [sdc] 1953525164 512-byte logical blocks: (1.00 TB/931 GiB)
Jun 24 20:48:12 somehost kernel: [6670323.014587] sd 50:0:0:0: [sdc] Write Protect is off
Jun 24 20:48:12 somehost kernel: [6670323.014591] sd 50:0:0:0: [sdc] Mode Sense: 1c 00 00 00
Jun 24 20:48:12 somehost kernel: [6670323.017357] sd 50:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 24 20:48:12 somehost kernel: [6670323.059605]  sdc: sdc1 sdc2
Jun 24 20:48:12 somehost kernel: [6670323.124689] sd 50:0:0:0: [sdc] Attached SCSI disk
Jun 24 20:48:15 somehost kernel: [6670325.576840] end_request: critical target error, dev sdc, sector 0
Jun 24 20:48:15 somehost kernel: [6670325.576848] JBD2: recovery failed
Jun 24 20:48:15 somehost kernel: [6670325.576852] EXT4-fs (sdc2): error loading journal
Jun 24 20:48:16 somehost ntfs-3g[508]: Version 2013.1.13AR.1 external FUSE 29
Jun 24 20:48:16 somehost ntfs-3g[508]: Mounted /dev/sdc1 (Read-Write, label "Expansion Drive", NTFS 3.1)
Jun 24 20:48:16 somehost ntfs-3g[508]: Cmdline options: rw,nosuid,nodev,uhelper=udisks2,uid=1000,gid=1000,dmask=0077,fmask=0177
Jun 24 20:48:16 somehost ntfs-3g[508]: Mount options: rw,nosuid,nodev,uhelper=udisks2,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdc1,blkdev,blksize=4096
Jun 24 20:48:16 somehost ntfs-3g[508]: Global ownership and permissions enforced, configuration type 7
Jun 24 20:48:16 somehost udisksd[2934]: Mounted /dev/sdc1 at /media/ps/Expansion Drive on behalf of uid 1000

In this case, the sdc2 partition is inaccessible, but other times, it gets mounted successfully, except that it is read-only, and I see this:

Jun 24 20:56:21 somehost kernel: [6670811.293826] EXT4-fs (sdc2): warning: mounting fs with errors, running e2fsck is recommended
Jun 24 20:56:21 somehost kernel: [6670811.295543] EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: (null)
Jun 24 20:56:21 somehost udisksd[2934]: Mounted /dev/sdc2 at /media/ps/f9940392-a20f-461d-a7c3-6c1132acf20b on behalf of uid 1000
Jun 24 20:56:26 somehost kernel: [6670816.539506] end_request: critical target error, dev sdc, sector 1218352432
Jun 24 20:56:26 somehost kernel: [6670816.539518] Aborting journal on device sdc2-8.

When I try "touch foobar" in the sdc2 mount point, I get "cannot touch ‘foobar’: Read-only file system".

I plugged this same drive on a ChromeBook, and the sdc2 partition is successfully mounted as read-write, and I can create files on it.

Back on the PC, I tried "e2fsck/dev/sdc2" and got this:

e2fsck 1.42.9 (4-Feb-2014)
/dev/sdc2: recovering journal
/dev/sdc2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdc2: 2131785/45793280 files (0.2% non-contiguous), 128417943/183154845 blocks

When I mount the partitions again, I still get this:

Jun 24 21:05:44 somehost kernel: [6671374.212541] end_request: critical target error, dev sdc, sector 1218352432
Jun 24 21:05:44 somehost kernel: [6671374.212568] Aborting journal on device sdc2-8.

fdisk says this:

Disk /dev/sdc: 1000.2 GB, 1000204883968 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525164 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
Disk identifier: 0xa03cb026

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1              63   488281367   244140652+   7  HPFS/NTFS/exFAT
/dev/sdc2       488281368  1953520127   732619380   83  Linux

This problem did not happen before I upgraded Ubuntu from 12.04 to 14.04, but that is likely a coincidence.

Questions:

  1. Could this be a hardware problem with the drive?

  2. Should I try e2fsck with any command-line options to force it to fix the problem, if possible?

  3. Is the only solution to reformat sdc2 (with mke2fs)? (The data is not very important, as it is a bunch of backups.)

Thanks.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.