dave.opc, you got it working :) (just what I've suspected, the machid was needed). The installation script must have detected your machine type. But current uBoot version still needs machid to work properly.
dmesg
fdisk
If the disk has been formatted and has data then mount it. Or you can try to format it (if it's OK to erase) as Ext3, ntfs, .... and mount it on a directory such as /media/SATAHDD.
dmesg
> [ 20.993836] libata version 3.00 loaded. > [ 20.995642] sata_mv sata_mv.0: version 1.28 > [ 20.995733] sata_mv sata_mv.0: slots 32 ports > 1 > [ 21.004562] scsi0 : sata_mv > [ 21.007983] ata1: SATA max UDMA/133 irq 21 >
fdisk
> Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes > 255 heads, 63 sectors/track, 243201 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Sector size (logical/physical): 512 bytes / 4096 > bytes > I/O size (minimum/optimal): 4096 bytes / 4096 > bytes > Disk identifier: 0x00000000 > > Device Boot Start End Blocks > Id System > /dev/sdb1 1 2433 19543041 > 83 Linux > Partition 1 does not start on physical sector > boundary. > /dev/sdb2 2434 243201 1933968960 > 83 Linux > Partition 2 does not start on physical sector > boundary.
If the disk has been formatted and has data then mount it. Or you can try to format it (if it's OK to erase) as Ext3, ntfs, .... and mount it on a directory such as /media/SATAHDD.