Iomega ix4-200d U-boot needed

Thanks Bodhi

I'll check your config After the weekend :)

Have a look to the diff: https://github.com/u-boot/u-boot/compare/v2022.07...ggirou:u-boot:v2022.07-ix4-200d
I set the registers for gpio with the same values from my stock u-boot.

Hi empgg3,

> I made a specific u-boot for ix4-200d, sata drive
> is detected but I didn't try to boot from it.
>

Did you see all 4 drives detected? Or just 2 drives?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------

> Did you see all 4 drives detected? Or just 2
> drives?

Hi Bodhi,

I can't say right now, I didn't look any further since I boot from USB.
I'll try again tomorrow or the day after and I'll send you some logs.

Can you share with me a copy of your complied u-boot and I can give feedback on it too?

I see from the bugzilla report that it could be an issue with certain disks. Maybe my 6Tb are a bit much for this old Nas although all 4 are detected and usable with stock u-boot and bohdis kernel. It's just that stock u-boot does not allow booting from them in gpt

> Can you share with me a copy of your complied
> u-boot and I can give feedback on it too?
>
> I see from the bugzilla report that it could be an
> issue with certain disks. Maybe my 6Tb are a bit
> much for this old Nas although all 4 are detected
> and usable with stock u-boot and bohdis kernel.
> It's just that stock u-boot does not allow booting
> from them in gpt

Hi CodeJack, you can download my compiled u-boot here:
https://github.com/ggirou/u-boot/releases/download/v2022.07-alpha%2B20220919/ix4-200d-u-boot-2022.07.kwb

> Did you see all 4 drives detected? Or just 2
> drives?

Hi Bodhi, drives are only detected on slots 3 and 4. I can list files on it.
Here is the logs:

U-Boot 2022.07-00008-g835bba8e40-dirty (Sep 19 2022 - 22:26:07 +0200)
Iomega ix4-200d

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
Core:  12 devices, 9 uclasses, devicetree: separate
NAND:  32 MiB
MMC:   
Loading Environment from NAND... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet-controller@72000, eth1: ethernet-controller@76000
Hit any key to stop autoboot:  3  0
=> sata init
=> sata info
Failed to wait for completion on port 0
ATA operation timed out
Failed to wait for completion on port 0
ATA operation timed out
Device 0: Model:  Firm:  Ser#: 
            Type: Hard Disk
            Capacity: not available
Device 1: Model: PNY CS900 120GB SSD Firm: CS900615 Ser#: PNY22192205120100FDC
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 114473.4 MB = 111.7 GB (234441648 x 512)
=> sata info
Device 0: Model:  Firm:  Ser#: 
            Type: Hard Disk
            Capacity: not available
Device 1: Model: PNY CS900 120GB SSD Firm: CS900615 Ser#: PNY22192205120100FDC
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 114473.4 MB = 111.7 GB (234441648 x 512)
=> ext4ls sata 1:1
<DIR>       1024 .
<DIR>       1024 ..
<DIR>       2048 bin
<DIR>       4096 lib
<DIR>       4096 sbin
<DIR>       1024 sys
<DIR>       1024 usr
<DIR>       1024 mnt
<DIR>       1024 var
<DIR>       1024 proc
<DIR>       3072 etc
<DIR>       1024 tmp
<DIR>       1024 ram
<DIR>       1024 dev
<DIR>       1024 lost+found
         2076824 zImage
         3032589 initrd

Edited 1 time(s). Last edit at 10/12/2022 04:15PM by empgg3.

empgg3,

> Hi Bodhi, drives are only detected on slots 3 and
> 4. I can list files on it.

So that's the same as where I was with version 2022.10-rc3-tld-0.2 in this thread

https://forum.doozan.com/read.php?3,25120,132900#msg-132900

Try kwboot with 2022.10-rc3-tld-0.2 and the mainline Debian kernel. See if you can see and use all 4 disks Debian.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks empgg3.

When I kwboot with you image, none of my disks are found, at least not using the sata init/part commands. They trigger a sting of errors:

 98 % [..................................................]
[Type Ctrl-\ + c to quit]


U-Boot 2022.07-00008-g835bba8e40-dirty (Sep 19 2022 - 22:26:07 +0200)
Iomega ix4-200d

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
Core:  12 devices, 9 uclasses, devicetree: separate
NAND:  32 MiB
MMC:   
Loading Environment from NAND... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   
Warning: ethernet-controller@72000 (eth0) using random MAC address - 66:79:e3:8e:c6:51
eth0: ethernet-controller@72000
Warning: ethernet-controller@76000 (eth1) using random MAC address - 7e:ab:36:39:5c:f3
, eth1: ethernet-controller@76000
Hit any key to stop autoboot:  0 
=> printenv
baudrate=115200
bootcmd=run x_bootcmd_usb; run x_bootcmd_kernel; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm ${loadaddr};
bootdelay=3
eth1addr=7e:ab:36:39:5c:f3
ethaddr=66:79:e3:8e:c6:51
fdtcontroladdr=1fb48aa0
loadaddr=0x2000000
mtdparts=mtdparts=orion_nand:896k(uboot),128k(env),-(rootfs)
x_bootargs=console=ttyS0,115200 mtdparts=${mtdparts}
x_bootargs_root=root=/dev/sda1 rw rootfstype=ext4
x_bootcmd_kernel=ubi part rootfs && ubifsmount ubi:rootfs && ubifsload ${loadaddr} /uImage
x_bootcmd_usb=usb start; ext4load usb 0:1 ${loadaddr} uEnv.txt; env import -t ${loadaddr} ${filesize}

Environment size: 600/131068 bytes
=> sata init
Err: Failed to identify SATA device 0
Err: Failed to identify SATA device 1
=> scsi scan
Unknown command 'scsi' - try 'help'

If I wait a few seconds and run the same again, these are the errors I get:

=> sata info
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
GPT: first_usable_lba incorrect: 22 > 0
find_valid_gpt: *** ERROR: Invalid GPT ***

There is no scsi command in your u-boot, is that correct? The stock u-boot uses SCSI for slot 3 and 4. So maybe the controllers work differently?



Edited 1 time(s). Last edit at 10/11/2022 08:08PM by CodeJACK.

> Try kwboot with 2022.10-rc3-tld-0.2 and the
> mainline Debian kernel. See if you can see and use
> all 4 disks Debian.

Hi Bodhi,

I was not able to detect any drive with U-Boot 2022.10-rc3-tld-0.2 and I was not able to boot to debian, see logs below.

U-Boot 2022.10-rc3-tld-0.2 (Aug 24 2022 - 16:52:00 -0700)
Lenovo-ix4-200d

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
Core:  12 devices, 9 uclasses, devicetree: separate
NAND:  32 MiB
MMC:   
Loading Environment from NAND... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   
Warning: ethernet-controller@72000 (eth0) using random MAC address - c6:80:d7:c7:96:6a
eth0: ethernet-controller@72000
Warning: ethernet-controller@76000 (eth1) using random MAC address - 86:2c:65:7c:84:9f
, eth1: ethernet-controller@76000
Hit any key to stop autoboot:  0 
=> 
=> sata init
=> sata info
=> 
=> usb start; ext4load usb 0:1 ${loadaddr} uEnv.txt; env import -t ${loadaddr} ${filesize}
starting USB...
Bus ehci@50000: USB EHCI 1.00
scanning bus ehci@50000 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
546 bytes read in 6 ms (88.9 KiB/s)
=> 
=> ext4load usb 0:1 ${loadaddr} /boot/uImage
19153076 bytes read in 478 ms (38.2 MiB/s)
=> setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm ${loadaddr}
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=> 
=> ext4load usb 0:1 0x1000000 /vmlinuz ; ext4load usb 0:1 0x2000000 /initrd.img ; ext4load usb 0:1 0x3000000 /boot/kirkwood-ix4-200d.dtb
2453864 bytes read in 70 ms (33.4 MiB/s)
16686140 bytes read in 417 ms (38.2 MiB/s)
9252 bytes read in 7 ms (1.3 MiB/s)
=> bootz 0x1000000 0x2000000 0x3000000
Kernel image @ 0x1000000 [ 0x000000 - 0x257168 ]
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
=>

CodeJack,

Indeed, SCSI command is not enable in my u-boot. Maybe some GPT configs are missing, that's why you got those errors.
I'll try to rebuild u-boot with more config.

I'm pretty sure the env settings you need to boot from HDD are in this post.

https://forum.doozan.com/read.php?3,25120,132904#msg-132904



Edited 1 time(s). Last edit at 10/13/2022 03:14AM by CodeJACK.

empgg3,

> I was not able to detect any drive with U-Boot
> 2022.10-rc3-tld-0.2 and I was not able to boot to
> debian, see logs below.

I had not complete the settings for GPIOs in that tld-0.2 version, so these memory pokes are needed when you start.

=> mw.l 0xF1010100 0x1000d080
=> mw.l 0xf1010140  0x0001000c
=> sleep 5
=> sata init

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Bodhi,

Sorry, I missed these commands.
I tested again and only disks on slots 3 and 4 work.

I also succeeded to boot with mainline debian kernel and also only slots 3 and 4 work. But there is some errors when I hot plug disk on slot 2, see full logs attached.

empgg3 Wrote:
-------------------------------------------------------
> Hi Bodhi,
>
> Sorry, I missed these commands.
> I tested again and only disks on slots 3 and 4
> work.
>
> I also succeeded to boot with mainline debian
> kernel and also only slots 3 and 4 work. But there
> is some errors when I hot plug disk on slot 2, see
> full logs attached.

Please rename this log to use extension .txt and re-upload (I have problem reading it).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

> Please rename this log to use extension .txt and
> re-upload (I have problem reading it).

I edited my previous post.

Hi Bodhi,

For my testing, I tested with a SSD and it was correctly detected.
Now, I put a 3.5" HDD, it's not.

Do you think it's a power issue like in this thread: https://forum.doozan.com/read.php?2,96444,96459 ?
How can I find the correct GPIO to enable sata power?