Unable to mount second hard drive

[unwir3d]

Hello Guys,

I really need help here, my laptop has 2 X 160GB hard disk. First disk is able to mount successfully but second disk i am unable to do so, here is some details for your reference.

p/s: I am able to mount both disk successfully using ubuntu live cd however.

5uh4imiX ~ # mount -t ntfs /dev/sdb1 /mnt/sdb1/
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

5uh4imiX ~ # fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        7833    62914560+   7  HPFS/NTFS
/dev/sda2            7833        7845      100370+  83  Linux
/dev/sda3            7846        7970     1004062+  82  Linux swap
/dev/sda4            7971       10461    20008957+  83  Linux

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
256 heads, 63 sectors/track, 19381 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      266306  2147483647+  ee  EFI GPT

From dmesg

sdb: rw=0, want=4294967045, limit=312581808
attempt to access beyond end of device

[bofh28]

Hello Guys,

I really need help here, my laptop has 2 X 160GB hard disk. First disk is able to mount successfully but second disk i am unable to do so, here is some details for your reference.

p/s: I am able to mount both disk successfully using ubuntu live cd however.

5uh4imiX ~ # mount -t ntfs /dev/sdb1 /mnt/sdb1/
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

5uh4imiX ~ # fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        7833    62914560+   7  HPFS/NTFS
/dev/sda2            7833        7845      100370+  83  Linux
/dev/sda3            7846        7970     1004062+  82  Linux swap
/dev/sda4            7971       10461    20008957+  83  Linux

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
256 heads, 63 sectors/track, 19381 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      266306  2147483647+  ee  EFI GPT

From dmesg

sdb: rw=0, want=4294967045, limit=312581808
attempt to access beyond end of device

I have never seen a EFI GPT filesystem before. Where did the drive come from?

Looking into this a little further the BackTrack 3 kernel doesn't support the EFI GPT filesystem. You will have to recompile the kernel to enable
CONFIG_EFI_PARTITION.

What I learned is EFI GPT is a partition type that supports a partition size greater than 2TB. Then you format it with whatever filesystem you want (ext3, ext4, or ntfs).

[Barry]

I have never seen a EFI GPT filesystem before. Where did the drive come from?

Looking into this a little further the BackTrack 3 kernel doesn't support the EFI GPT filesystem. You will have to recompile the kernel to enable
CONFIG_EFI_PARTITION.

What I learned is EFI GPT is a partition type that supports a partition size greater than 2TB. Then you format it with whatever filesystem you want (ext3, ext4, or ntfs).

Looks like a Mac, or a Mac formatted drive.

[Andy90]

I'm no expert at this, but does that partition not look bigger than the disk? (i.e. partition table being read wrong/corrupt?)

Am prob very very wrong

[streaker69]

I'm no expert at this, but does that partition not look bigger than the disk? (i.e. partition table being read wrong/corrupt?)

Am prob very very wrong

I think you're right.