You are not logged in.
I have external hard drive which works fine when connected via usb. I removed the drive from its casing to connect it via sata to my pc. Unfortunately it doesn't mount this way.
Might it be that the usb->sata controller in the case was shuffling some bits around? The drive in question is a "Seagte Desktop Extension 2TB"
Does anybody have a clue on how to get this working via sata?
> fdisk -l /dev/sdb
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x90aabb15
Partition 1 does not start on physical sector boundary.
Device Boot Start End Blocks Id System
/dev/sdb1 63 3907029159 1953514548+ 83 Linux> mount /dev/sdb1 /mnt/
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.fsck -v /dev/sdb1
fsck from util-linux 2.24.2
e2fsck 1.42.10 (18-May-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb1
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
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>
or
e2fsck -b 32768 <device>Offline
please check this link http://linuxexpresso.wordpress.com/2010 … in-ubuntu/ it seems that you have some issues with superblock's
___________________
Adevarul se afla dincolo de noi ...
IT Engineer
Offline
Thanks Caralin,
Though unfortunately this did not solve my problem. e2fsck cannot restore the superblock, giving the exact same output as fsck from my last post.
I might have to clarify that if I reconnect the drive via the usb->sata controller everything works fine again. Just not directly via sata.
Offline