Перестал монтироваться внешний usb винт

 
Oct 14 10:36:29 arch kernel: scsi 3:0:0:0: Direct-Access     StoreJet Transcend             PQ: 0 ANSI: 2 CCS
Oct 14 10:36:29 arch kernel: sd 3:0:0:0: Attached scsi generic sg3 type 0
Oct 14 10:36:29 arch kernel: sd 3:0:0:0: [sdc] 312581808 512-byte logical blocks: (160 GB/149 GiB)
Oct 14 10:36:29 arch kernel: sd 3:0:0:0: [sdc] Write Protect is off
Oct 14 10:36:29 arch kernel: sdc: sdc1
Oct 14 10:36:29 arch kernel: sd 3:0:0:0: [sdc] Attached SCSI disk
Oct 14 10:36:37 arch kernel: usb 1-3: reset high speed USB device using ehci_hcd and address 9
Oct 14 10:36:37 arch kernel: usb 1-3: reset high speed USB device using ehci_hcd and address 9
Oct 14 10:36:38 arch kernel: usb 1-3: reset high speed USB device using ehci_hcd and address 9
Oct 14 10:36:39 arch kernel: usb 1-3: reset high speed USB device using ehci_hcd and address 9
Oct 14 10:36:39 arch kernel: sd 3:0:0:0: Device offlined - not ready after error recovery
Oct 14 10:36:39 arch kernel: usb 1-3: USB disconnect, address 9
Oct 14 10:36:39 arch kernel: usb 1-3: new high speed USB device using ehci_hcd and address 10
Oct 14 10:36:40 arch kernel: usb 1-3: new high speed USB device using ehci_hcd and address 11
Oct 14 10:36:40 arch kernel: usb 1-3: new high speed USB device using ehci_hcd and address 12
Oct 14 10:36:41 arch kernel: usb 1-3: new high speed USB device using ehci_hcd and address 13
Oct 14 10:36:41 arch kernel: usb 3-1: new full speed USB device using uhci_hcd and address 10
Oct 14 10:36:42 arch kernel: usb 3-1: new full speed USB device using uhci_hcd and address 11
Oct 14 10:36:42 arch kernel: usb 3-1: new full speed USB device using uhci_hcd and address 12
Oct 14 10:36:43 arch kernel: usb 3-1: new full speed USB device using uhci_hcd and address 13

[410][demas.arch: /home/demas]$ fsck /dev/sdc1
fsck from util-linux-ng 2.16
e2fsck 1.41.9 (22-Aug-2009)
fsck.ext2: Нет такого файла или каталога while trying to open /dev/sdc1

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>