cant detect 1tb HD

[unixchaos]

hi im new to Salix and kinda got spoiled by a Debian OS. im having problems with my 1TB HD. recently i decided to wipe my ubuntu and go with Salix because source based is much better and i first learned linux on slackware 6. any ways back to the point.

cant locate and mount my 1tb hd. it was /dev/sdb1 in the dev folder i see it but only as the entire drive /dev/sdb so i go to mount this and fail. tried to create a folder in /mnt called 1tb and mount it and failed. so i decided to add it to the fstab and nothing still. obviously im missing something. the HD is ext3

any help would be appreciated thnx

love the speed and friendliness of Salix

[Shador]

Can you post the output of fdisk -l and parted /dev/sdb -s print. If necessary install parted before issuing that command.

[thenktor]

And what is the exact error message of mount -t ext3 /dev/sdb1 /mnt/1tb?

[unixchaos]

Code: Select all

root[jza873]# fdisk -l

Disk /dev/sda: 164.6 GB, 164696555520 bytes
255 heads, 63 sectors/track, 20023 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x5a2b26fa

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1          31      248976   83  Linux
/dev/sda2              32        5502    43945807+  83  Linux
/dev/sda3            5503       16775    90550342    5  Extended
/dev/sda4   *       16776       20022    26081527+   7  HPFS/NTFS
/dev/sda5            5503        5751     2000061   82  Linux swap
/dev/sda6            5752       16775    88550248+  83  Linux

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xffffffff

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 300.0 GB, 300090728448 bytes
255 heads, 63 sectors/track, 36483 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x57b4fd21

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1       36483   293049666    b  W95 FAT32

Code: Select all

root[jza873]# parted /dev/sdb -s print
Model: ATA SAMSUNG HD103UJ (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: bsd

Number  Start  End     Size    File system  Flags
 1      512B   1000GB  1000GB  ext3 

Code: Select all

root[jza873]# mount -t ext3 /dev/sdb1 /mnt/1tb
mount: special device /dev/sdb1 does not exist

[Shador]

Disk /dev/sdb doesn't contain a valid partition table

Partition Table: bsd

The partition table is the problem. I was already assuming a bad or unknown one.
Which version of Salix are you using? What's the output of grep -i "config_bsd_disklabel" /boot/config?

There are two solutions to this problems either you get a kernel that works with that partition table or you switch to another one. That grep command should show whether your kernel supports bsd partitions.

[unixchaos]

13.0 i just downloaded and installed it

Code: Select all

jza873[~]$ grep -i "config_bsd_disklabel" /boot/config
CONFIG_BSD_DISKLABEL=y
jza873[~]$ 

thats all the output is when i put the ubuntu live cd in it detects it if that helps

[Shador]

Can you have a look at this: http://tldp.org/HOWTO/Linux+FreeBSD-2.html
I would be especially interested what happens if you try the procedure in 2.1 on your drive.
dmesg | grep sdb might reveal something too.
Oh and try modprobe ufs.

[unixchaos]

Code: Select all

root[jza873]# modprobe ufs
root[jza873]# dmesg | grep sdb
sd 5:0:0:0: [sdb] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 5:0:0:0: [sdb] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: unknown partition table
sd 5:0:0:0: [sdb] Attached SCSI disk

if it was formatted as ext3 but ubuntu attached it with a uuid when it mounted it but i dont know if that makes any diffrence

[unixchaos]

more info i found

GParted 0.4.8

Libparted 1.8.8
Check and repair file system (ext3) on /dev/sdb1 00:00:00 ( ERROR )

calibrate /dev/sdb1 00:00:00 ( SUCCESS )

path: /dev/sdb1
start: 1
end: 1953520064
size: 1953520064 (931.51 GiB)
check file system on /dev/sdb1 for errors and (if possible) fix them 00:00:00 ( ERROR )

e2fsck -f -y -v /dev/sdb1


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>

e2fsck 1.41.8 (11-July-2009)
e2fsck: No such file or directory while trying to open /dev/sdb1



what if i try making a uuid for /dev/sdb1 and put it in fstab think that will work

[Shador]

sdb: unknown partition table

As long as you get that line and /dev/sdb is the only device created, nothing will work.
If you use UUIDs the actual devices like e.g. /dev/sdb1 are still needed. UUIDs are just another way of identifying them. Compare it to passports. If I wanted to obtain the information in your passport, I could search for your name (like for /dev/sdb1) or I could search for your passport id (like the UUIDs). But whatever I search for if there is no such passport, I won't find it.

if it was formatted as ext3 but ubuntu attached it with a uuid when it mounted it but i dont know if that makes any diffrence

As long as the only device created is /dev/sdb the filesystem on the first partition of that disk doesn't matter. Because that means the kernel is unable to recognize that partition using the information provided by the disk label (e.g. because there's no disk label or it is broken or unknown). I don't know what's the case for you.
After fixing the disk with gparted, are any new devices created for that disk? (e.g. sdb1, dmesg | grep sdb should show you that).