uboot reporting drive read errors on brand new drive

This forum is for all AmigaOne 500, Sam440 and Sam460 specific issues.
barana
Posts: 21
Joined: Sun Sep 04, 2011 7:49 am

uboot reporting drive read errors on brand new drive

Post by barana »

gday, ive installed a 2.5" laptop 7200rpm 750gb sata II drive to my 460lite and it reports a long error message which i will retype verbatim at the end of this.
It always occurs whilst loading the kickstart . I have tried to reinstall several times since (with the default 1024 and 512, currently 512 sector sise)
If I use the sdcard to boot and switch booting to the hdd during early boot menu, 4.1.2 will boot off the drive (yeah ive tried installing 4.1.3 and 4.1.4 and no change)
I have noticed when I changed the sector sise, It no longer errored at the 3dfx driver (which i experimented with removing and also removed from the kicklayout, but it just errored at the pcidisplaycard, and another time at the radeonHD driver)but errored at the sam460sata driver funnily enough
to avoid this at one stage I moved the partition 1gb ahead incase it was a hdd problem, but it still gave the error.
does uboot take advantage of ahci? maybe if it doesnt, it may have a problem with pio 1-6 (or the drive does)
has someone come across this problem, or is able to spot it? anyway heres the error typed out
ps this last time, it errored at the silxxxx driver

set port freese.
failed to READ SECTORS (I/O error, err_mask=0x4)
sata_dwc :Hard disk read error.
Machine check Exception.
Caused by (from msr) :regs 0df6c340 Data Write PLB error
IP:0FFB40C0 XER: 00000000 LR:0FFB409C REGS: 0df6c340 TRAP:0200 DEAR:58081180
MSR: 00029000 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 00

GPR00: 00000000 0DF6C430 0DF6CB24 00000058 FFFFFFB3 00000005 00000005 046B8CDB
GPR08: 0FF70FE0 E2OD1020 0794BA2D E20D1018 44002028 00000000 0FFF9038 01416C20
GPR16: 01406044 01416C2C 0DF6C500 01416C30 0FFFB9E8 0DF6C450 00000001 0E8A7BE8
GPR32: 00009BC5 0000009B 00000000 000000A7 0FFFB9E8 00000000 0FFD0834 0FFFAA40
Call backtrace:
0FFB409C 0FFB4CA8 OFFB4E90 OFF8AC84 014000F8 01404144 014015E8
014003C0 0140303C 0FF8A8B8 0FF81140 0FF8121C OFF81140 0FF815F4
0FF70C24 OFF6F728
machine check

User avatar
Slayer
Beta Tester
Beta Tester
Posts: 851
Joined: Tue Dec 21, 2010 4:19 am
Location: New Zealand

Re: uboot reporting drive read errors on brand new drive

Post by Slayer »

Sata II you say? Not sure if that has any bearing on anything. I have quite a few "modern" drives across my systems and not sure if any are Sata II or not.

Lets see.

Why don't we start again, now I know AmigaOS can address a 1TB drive or partition (since I have several of these, as a personal choice I always try to have complete drives as partitions. The only drive I have partitioned in half is a 1.5TB USB2/3 drive that I brought to test for size etc. If I mount it as a Sata HD in the machine it shows two 700GB partitions but if I put it back in its USB housing it only shows the first partition - anyway, I'm getting distracted here)

Why not reset the harddrive back to factory settings and just create a 10GB partition at the very start of it (forget SWAP etc) set it for SFS2 and 512 block. Format it and install AmigaOS4.1 on it.

Just to be clear

Boot off your AmigaOS4.1 CDRom with your undefined Sata II HD attached. Go through the installation procedure electing to partition and format etc... then boot off the HD when instructed

Of course, if you haven't got a AmigaOS4.1 CDRom for your Sam460 we might have a wee problem ;)

Apologies but I don't have an Sam460 just yet so a bit of guess work 8-)
~Yes I am a Kiwi, No, I did not appear as an extra in 'Lord of the Rings'~
1x AmigaOne X5000 2.0GHz 2gM RadeonR9280X AOS4.x
3x AmigaOne X1000 1.8GHz 2gM RadeonHD7970 AOS4.x

barana
Posts: 21
Joined: Sun Sep 04, 2011 7:49 am

Re: uboot reporting drive read errors on brand new drive

Post by barana »

yes slayer

the second time around i formatted without a swap partition and no difference.
My system partition was around the 5GB mark each time theres no need in my mind for any more...

maybe not 'SataII' but 3GB/s
(well cache to sata chip - i believe this is where most modern plattered hdd's get their performance from, as the specs say the sustained speed is 130kb/s)
my sata/ide3.5/ide2.5 to usb bidge doesnt seem to work at boot time for my cdrom, nor does it work for the hdd's during boot. after ks is loaded, they are fine!
I dont understand 'factory settings, as there is no way to alter any settings on it (there are jumpers, but unlabeled, and theres nothing in the drive's manual about them).
so yeah no point, as I've done that. thanks though.

User avatar
Slayer
Beta Tester
Beta Tester
Posts: 851
Joined: Tue Dec 21, 2010 4:19 am
Location: New Zealand

Re: uboot reporting drive read errors on brand new drive

Post by Slayer »

I was just refering to the sub menu in Media Toolbox - "Edir RDB/Reinstall" then select the "install/read configuration" option at the top of the next menu

Which wipes all your previous settings and restores the factory layout

Maybe we just have to entertain that your setup isn't compatiable since it sounds like you have other 3rd party stuff in there too... wish I could get my hands on it all since I love trouble shooting hardware and alike...

In situations like this it is always good to start with the very least you can so it's easier to test and eliminate and formulate a practical strategy

good luck?

btw, once you've installed it, do you get to enter the early startup menu at all? I can't recall if you get this far or not
~Yes I am a Kiwi, No, I did not appear as an extra in 'Lord of the Rings'~
1x AmigaOne X5000 2.0GHz 2gM RadeonR9280X AOS4.x
3x AmigaOne X1000 1.8GHz 2gM RadeonHD7970 AOS4.x

barana
Posts: 21
Joined: Sun Sep 04, 2011 7:49 am

Re: uboot reporting drive read errors on brand new drive

Post by barana »

I've tried to boot it without anything else attached, cd, catweasel etc. no change and have kept it like that.
I dont quite understand you when it comes to returning it to factory specs? It was either formatted with fat, seroed (sed key isnt working here atm) or blank (doubtful due to all the tests a manufacturer puts drives thru when theyre first manufactured)
The drive never actually booted 4.1 firstup so it never officially worked, its brand new! but i will try installing aros x86 on it and see if it gives the same fault.
but when I first boot off the install sdcard -thats the acube install media - and load KS, , then invoke the early start menu and select the 4.1.2 installation on the new drive, then it loads workbench.

will let you know if it boots aros properly on my x86.

lozspd4
Posts: 41
Joined: Mon May 28, 2012 10:13 pm

Re: uboot reporting drive read errors on brand new drive

Post by lozspd4 »

Hi Barana
I Have a AmigaOne with sam MotherBoard i Had a similar Problem with a 500GB Samsung 2.5 Drive with Hardware error it to was spanking New.

I used O&O SafeErase Program on my PC Completely erase the HD its then set to factory Setting without the format.Then without formating put it in the Amiga, Start from Amigaos4.1 cd set the drive up as per the instructions on manuell and used this as a guide http://intuitionbase.com/static.php?sec ... kthrough#1, and afterwards i Haven,t had a Problem with it
about 6 days Nows.

But i only use it as a backup drive with one Partition. Give that a try maybe it works, Safe erase you can download from http://www.oo-software.com/de/products/ ... x.html?r=s as a fully working test Version for 30 days.

GoodLuck on sorting your Problem.

Regards Laurence

User avatar
javierdlr
Beta Tester
Beta Tester
Posts: 380
Joined: Sun Jun 19, 2011 10:13 pm
Location: Donostia (GUIPUZCOA) - Spain
Contact:

Re: uboot reporting drive read errors on brand new drive

Post by javierdlr »

Can you try with another SODIMM (ram module)?
IIRC I had some kind of uboot crash too with my SATA hdd, then I changed from 1GB SODIMM to 2GB ram module and haven't see such uboot_crashes again.

barana
Posts: 21
Joined: Sun Sep 04, 2011 7:49 am

Re: uboot reporting drive read errors on brand new drive

Post by barana »

ok tried zeroing drive with windows app linked to, repartitioned a 5 gig partition, and same uboot error. :( i will now try initializing with sfs/00 (68k?) if i get the same errors i will try with the slow ffs also.
I will try one single partition (the whole drive)
I will also try the uboot ram testing routines and let you all know. thanks to all, -Barana

barana
Posts: 21
Joined: Sun Sep 04, 2011 7:49 am

Re: uboot reporting drive read errors on brand new drive

Post by barana »

ok, so I tried formatting with sfs/00 and ffs, no change.

I'm running mtest in uboot atm, 10 mins in, and there is no errors...

I will add that my old 1.5gb/s 1st gen sata drive will still boot and work fine!

next i will try hooking it upto my laptop, and install aros into it (both aros installer and ubuntu's gparted dont like deating with a usb connected usb-to-sata bridged hdd...

and no, the hdd,when connected to my amiga is via the onboard sata port.
hmm.......

lozspd4
Posts: 41
Joined: Mon May 28, 2012 10:13 pm

Re: uboot reporting drive read errors on brand new drive

Post by lozspd4 »

Hi Barana
mmm thats wierd, just for info what sataII Controller are you using on board or pci sata (ie sii3112,sii3114 etc), is the uboot set to the correct Controller if pci controller maybe Settings in uboot are set wrong causing a Problem accessing the Drive, it may not be the drive it sounds like a Hardware Setup Problem. can you do a list of uboot Setting when possible so we can Compare it.

Here is a copy of my backup file for uboot

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
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
ethaddr=00:50:c2:80:d5:5a
video_activate=pci
hush=0
ipaddr=192.168.2.50
serverip=192.168.2.280
serdes=pci-e
boot1=s4siicdrom
boot2=usb
boot3=s4sii
boota_timeout=1
menuboot_delay=2
os4_commandline=debuglevel=0
bootargs=root=/dev/sda3 console=tty0
ver=U-Boot 2010.06.05a (Jan 30 2012 - 16:06:56)
s4sii_maxbus=1
menuboot_cmd=boota

Maybe this will help you find the Problem

Regards Laurence

Post Reply