Page 1 of 1

Sam460ex and Segate 2TB SSHD

PostPosted: Mon Sep 19, 2016 5:16 pm
by Spectre660
I am unable to get my Sam460ex with any sii3x1x sata card to boot with a Segate Desktop SSHD 2TB hybrid Hard drive.
Tried all 3 supported pci sii sata models 3112,3114,3512 .

I get the FLB: no SLB found in any of the designated boot sources;returning to u-boot.

The drive will boot from the onboard sam460ex sata port and via USB when installed in an external USB drive case .

Drive model ST2000DX001

Re: Sam460ex and Segate 2TB SSHD

PostPosted: Tue Sep 20, 2016 2:40 am
by tonyw
All those cards will work OK, so it's a problem with your settings.

How far does the boot get? Does it load Kickstart modules before it gives up?

From a working system or U-Boot, check the setting of "sii3x1xide_conf" - it should reflect your drive connections. If in doubt, clear the variable with (for instance) [setenv sii3114ide_conf ""].
I'm using the square brackets as quotes in that example, just enter everything within the brackets (including the ""). Don't forget to "saveenv" afterwards.

Re: Sam460ex and Segate 2TB SSHD

PostPosted: Tue Sep 20, 2016 3:50 am
by Spectre660
No kickstart loaded.
No "sii3x1xide_conf" settings.
Current settings work ok with sii3512 and a 500GB Western digital 3.5" drive 0,0 and DVD writer 1,0 .
I am using a removable Hard drive rack so sata and power connection are not an issue.

https://www.startech.com/HDD/Mobile-Rac ... SB100SATBK

baudrate=115200
loads_echo=1
hostname=Sam460ex
stdout=vga
stdin=usbkbd
ide_doreset=on
ide_reset_timeout=15
ide_cd_timeout=20
pcie_mode=RP:RP
pciconfighost=1
ethaddr=00:50:C2:80:D5:00
bootcmd=menu; run menuboot_cmd
menucmd=menu
boot_method=boota
usb_enable_4x0=1
usb_retry=1
usb_ohci_power_down_before_reset=1
scan_usb_storage=1
ethact=ppc_4xx_eth0
video_activate=pci
hush=1
x86emu=1
serdes=pci-e
ver=U-Boot 2015.a (May 16 2015 - 14:20:11)
boot1=usb
boot2=ssiicdrom
boot3=ssii
boota_timeout=2
menuboot_delay=2
os4_commandline=debuglevel=0
menuboot_cmd=boota
bootargs=root=/dev/sda6 console=ttyS0,115200 console=tty0 fb=false quiet splash
serverip=192.168.1.14
ipaddr=192.168.1.15
ui=uImage-460
dt=sam460.dtb
ur=uRamdisk
pt=usb 0:3
kl=1000000
dl=2000000
rl=3000000
usb=ext2load ${pt} ${kl} ${ui};ext2load ${pt} ${dl} ${dt};bootm ${kl} - ${dl}
lan=tftp ${kl} ${ui};tftp ${dl} ${dt};bootm ${kl} - ${dl}

Re: Sam460ex and Segate 2TB SSHD

PostPosted: Tue Sep 20, 2016 11:45 am
by Spectre660
Changed the menuboot_delay to 10 and set boot1 to ssii and got an error message .

Error (no IRQ) dev 0 blk 0: status 0x51

Re: Sam460ex and Segate 2TB SSHD

PostPosted: Tue Sep 27, 2016 1:05 am
by Spectre660
Looks like this could be a U-boot issue with the sii cards.
Drive works ok in an external case via USB.
Connected to the sii3512 card there are write problems under both AmigaOS 4.1 and Linux .

Re: Sam460ex and Segate 2TB SSHD

PostPosted: Tue Sep 27, 2016 2:21 am
by tonyw
I know the 3112 and 3114 work OK, since I have used both in my Sam 460. I can't speak for the 3512.

There is a U-Boot problem in addressing the various units on the cards - you get timeouts and error messages on the U-Boot screen with the "wrong" unit numbers, but that should be obvious.

Re: Sam460ex and Segate 2TB SSHD

PostPosted: Tue Sep 27, 2016 2:40 am
by Spectre660
I tested as thoroughly as I could. I tried a 3112 and a 3114 as well as the 3512. also the Sam460ex on board controller.
Swapped sata cables and power cables. Also tried a second drive of the same model that is working ok with a x86 system.
Would only work with the Sam460ex on board controller . With the sii controllers I could not boot and there were errors in attempting to install or create partitions in media toolbox after booting from the AmigaOS 4.1FE CD.
Booting and creating partition was ok via USB in a removable external case .
My only other 2 TB non hybrid drive is a damaged hitachi model and I have just created a partition table and ext4 partition under LInux so the 2TB size of the drive is not the problem.Probably the hybrid mechanism of moving data to SSD area of the drive.
Or maybe that ssd area is mapped at a location that causes a problem.


tonyw wrote:I know the 3112 and 3114 work OK, since I have used both in my Sam 460. I can't speak for the 3512.

There is a U-Boot problem in addressing the various units on the cards - you get timeouts and error messages on the U-Boot screen with the "wrong" unit numbers, but that should be obvious.