Debian on Iomega StorCenter ix2

there are two versions of this box:

- the "dl" (diskless) version which hast many in common with the ZyXEL NSA325(v2)
- the "ix2-200" which comes with two HDDs (Raid 1) which can compared with the iConnect.

First let's have a look at the default U-Boot env:
(perhaps I've messed something up it was late and minicom is sometimes strange)

http://pastebin.com/z9S3RYen

After looking around in the Stock OS I tried to boot debian with an I think stable Debian Jessie Image with 4.0.0 Kernel:
(sorry for the non existant mount entry and that I've forgot to delete the old 70-persistand-net.rules)

http://pastebin.com/eYhQxPBV


this box has only one ethernet device, but two were recognized

[    0.171110] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.171235] [Firmware Info]: /ocp@f1000000/ethernet-controller@76000/ethernet1-port@0: local-mac-address is not set

Later I found out that the default ethernet device doesn't work.
it looks similar to the NSA310s/NSA320s issue, but with the right speed and such.
so I brought up the second "eth1" device and it's working fine.

Updated to the latest kernel / DTB with the same result:
Modifying /etc/network/interfaces seems to help:

auto lo eth1
iface lo inet loopback
iface eth1 inet dhcp

the last bootlog:

http://pastebin.com/33c7K9HJ

as you can see, there is something wrong with the nand behaviour and so it's mostly impossible to read the U-Boot env via fw_printenv

[    8.553258] __nand_correct_data: uncorrectable ECC error
[   98.650168] __nand_correct_data: uncorrectable ECC error
[   98.662698] blk_update_request: I/O error, dev mtdblock0, sector 0
[   98.674677] __nand_correct_data: uncorrectable ECC error
[   98.680056] blk_update_request: I/O error, dev mtdblock0, sector 0
[   98.704251] __nand_correct_data: uncorrectable ECC error
[   98.709636] blk_update_request: I/O error, dev mtdblock0, sector 0

later I found out that "pwmcontrol" is working, but it doesn't produce a working settings file for "fancontrol"

http://pastebin.com/Svsq4uF3

Atm, U-Boot env is modified to boot debian only


the used image, debian rootfs, kernel 4.2.1-rm-2


Issues:

- NAND not accessable (all related things compiled as module)
- let udev not create the persistant net rules file, otherwhise boot takes longer
- one of my ix2-200 boxes has similar cfq scheduler issue es mentioned here



Edited 13 time(s). Last edit at 11/02/2015 06:36PM by pengu.

pengu,

Remember when you boot with stock u-boot, the u-boot envs are at

0x20000@0xA0000(uboot_env)

and your mtdparts is

console=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x20000@0xA0000(uboot_env),0x300000@0x900000(kernel),0x1400000@0)

So you'll most likely need to adust this is the rootfs. Did you do that?

And the kernel does not know what your mtdparts are

[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootfstype=ext4

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

thanks bodhi
if I set this or not, no nand partitions were recognized



Edited 2 time(s). Last edit at 09/15/2015 03:08AM by pengu.

pengu Wrote:
-------------------------------------------------------
> thanks bodhi
> if I set this or not, no nand partitions were
> recognized

Did you set it to this :)

console=console=ttyS0,115200 mtdparts=orion_nand:0x100000@0(uboot)ro,0x20000@0xA0000(uboot_env),0x300000@0x900000(kernel),0x1400000@0)

Your last bootlog showed that it was not set to anything.

[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootfstype=ext4

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

yes ;-)

[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootfstype=ext4 mtdparts=orion_nand:0x100000@0(uboot)ro,0x20000@0xA0000(uboot_env)
...
...
[    1.873362] nand: device found, Manufacturer ID: 0xad, Chip ID: 0x75
[    1.879794] nand: Hynix NAND 32MiB 3,3V 8-bit
[    1.884195] nand: 32 MiB, SLC, erase size: 16 KiB, page size: 512, OOB size: 16
[    1.891546] Scanning device for bad blocks
[    1.921348] Bad eraseblock 232 at 0x0000003a0000
[    2.126458] 2 cmdlinepart partitions found on MTD device orion_nand
[    2.132761] Creating 2 MTD partitions on "orion_nand":
[    2.137953] 0x000000000000-0x000000100000 : "uboot"
[    2.144241] 0x0000000a0000-0x0000000c0000 : "uboot_env"

the error still persists

[    8.329837] __nand_correct_data: uncorrectable ECC error
[   98.634972] __nand_correct_data: uncorrectable ECC error
[   98.661087] __nand_correct_data: uncorrectable ECC error
[   98.683240] __nand_correct_data: uncorrectable ECC error
[  100.061823] blk_update_request: I/O error, dev mtdblock0, sector 0
[  100.081826] __nand_correct_data: uncorrectable ECC error
[  100.094164] blk_update_request: I/O error, dev mtdblock0, sector 0
[  100.104300] __nand_correct_data: uncorrectable ECC error
[  100.109679] blk_update_request: I/O error, dev mtdblock0, sector 0

and fw_printenv doesn't work

/etc/fw_env.config should be like this:

/dev/mtd1 0  0x20000

fw_printenv
Warning: Bad CRC, using default environment
...

Edited 7 time(s). Last edit at 09/15/2015 03:29AM by pengu.

> /etc/fw_env.config should be like this:
>
>

> /dev/mtd1 0  0x20000
>

>

This looks wrong:

[    2.144241] 0x0000000a0000-0x0000000c0000 : "uboot_env"

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

bodhi Wrote:
-------------------------------------------------------
> > /etc/fw_env.config should be like this:
> >
> >

> > /dev/mtd1 0  0x20000
> >

> >
>
> This looks wrong:
>
>

> [    2.144241] 0x0000000a0000-0x0000000c0000 :
> "uboot_env"
>

could be but why?
I don't see anything in "mtdparts"

pengu Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > > /etc/fw_env.config should be like this:
> > >
> > >

> > > /dev/mtd1 0  0x20000
> > >

> > >
> >
> > This looks wrong:
> >
> >

> > [    2.144241] 0x0000000a0000-0x0000000c0000 :
> > "uboot_env"
> >

>
> could be but why?
> I don't see anything in "mtdparts"

You should have 4 mtd partitions, not 2.

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

I said that there could be something hosed ...
If I add the kernel partition I cannot start because of an unexpectat character (kernel panic)

for me, it's enough to have the 2 partitions and get the U-Boot env readable / writable



Edited 1 time(s). Last edit at 09/16/2015 01:54AM by pengu.

pengu Wrote:
-------------------------------------------------------
> I said that there could be something hosed ...
> If I add the kernel partition I cannot start
> because of an unexpectat character (kernel panic)
>
> for me, it's enough to have the 2 partitions and
> get the U-Boot env readable / writable

You need to define them correctly, it does not matter how many partitions you have.

- Redefine with 4 partitions as they were in original stock defintion.
- Boot with Debian rootfs on USB only.
- Capture the serial log and post here.

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

I'll do so.
As I sead, this doesn't solve the problem of reading / writing to the flash in debian.

Edit
I couldn't find the right mtdparts line, so I try to get this from my next ix2-200 but I don't know when it will arrive.



Edited 1 time(s). Last edit at 09/20/2015 03:40AM by pengu.

pengu Wrote:
-------------------------------------------------------
> I'll do so.
> As I sead, this doesn't solve the problem of
> reading / writing to the flash in debian.
>

Once you defined the mtd1 correctly, then see if the error still occur. As it is right now, mtd1 is wrong, so hard to say.

> Edit
> I couldn't find the right mtdparts line, so I try
> to get this from my next ix2-200 but I don't know
> when it will arrive.

It's in your bootlog :)

mtdparts=nand_mtd:0x100000@0(uboot)ro,0x20000@0xA0000(uboot_env),0x300000@0x900000(kernel),0x1400000@0)

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

bodhi Wrote:

> It's in your bootlog :)
>

> mtdparts=nand_mtd:0x100000@0(uboot)ro,0x20000@0xA0
> 000(uboot_env),0x300000@0x900000(kernel),0x1400000
> @0)
>

I get a kernel panic wich this because of an unexpected character "("

pengu,

> I get a kernel panic wich this because of an
> unexpected character "("

Did you post the kernel panic log?

And did you try to reformat this mtdpart string to look like one in other Kirkwood boxes? Such as:

mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)

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

this doesn't work because this device has only 32 mb flash.
whatever I do with the mtdparts it stalls at boot for some time because the flash can't accessed corectly.
I'll see later with another ix2-200 (with correct mtdparts)

Now I also have the ix2-dl which has similar issues with NAND access on debian.
but this is another thing and because of other problems I'll open another thread for this.

Pengu,

"To look like" meaning you have to calculate the space for each mtd. And the syntax should be the same.

Look closely. Your mtd1 is simply too big.

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



Edited 1 time(s). Last edit at 10/13/2015 04:34PM by bodhi.

news news :-)

the one minute stall at boot isn't related to NAND.
I've built all NAND related stuff as module and its still stalling for one minute after initialing the watchdog.

I've seen something on the NSA310 when the ethernet port needs more time to come up (DHCP and stuff).
One solution is to let udev not create the 70-persistant-net.rules file.
When this file isn't there, the ix2-200 is booting fine.
When it's there, it takes one minute longer.

Another solution could be to modifiy the DTS to only bring up one ethernet port, because this box only have one.
I'll try this later.


Edit

deleting 70-persistant-net.rules and creating a directory with the same name fixes the boot delay for now.



Edited 1 time(s). Last edit at 11/02/2015 08:08AM by pengu.

Because of some issues raised on Kernel 4.2.x,
I tried the next stable 4.3.x kernel.


They are gone completely and also the boot deley when loading dhe NAND driver at boot.
You still see some error messages while accessing the NAND and it's still not possible to read/write uEnv variables.
Perhaps this could be solved.

Hello Pengu,

What is the current status for the ix2-200 ? Is it working now correctly ?
Could you post a howto installation ? I want to install mine as well, but I have some problems finding and installing a correct kernel/version on it. Debian wheezy was ok, but I'm sure there is an updated kernel somewhere for this NAS.

didierw Wrote:
-------------------------------------------------------
> Hello Pengu,
>
> What is the current status for the ix2-200 ? Is it
> working now correctly ?
> Could you post a howto installation ? I want to
> install mine as well, but I have some problems
> finding and installing a correct kernel/version on
> it. Debian wheezy was ok, but I'm sure there is an
> updated kernel somewhere for this NAS.

Kernel and rootfs:
http://forum.doozan.com/read.php?2,12096

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

sorry for the late response.

The ix2-200 is working fine


The ix2-dl is working but:

- NAND isn't "recognized" correctly
- power off doesn't work

@didierw

you can use the mentioned rootfs and howto.
Since there is no modern U-Boot vor this device, you have to emded the DTB as described in 4b

pengu,

> The ix2-dl is working but:
>
> - NAND isn't "recognized" correctly
> - power off doesn't work

Bring this subject back, and I'll take a look at these:

Post:
fw_printenv - or printenv in serial console
serial log - post serial log

Verify:
DTS - which version are you using? from mainline for the ix2-200?

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

I'm using the patched DTB from here.
The one with proper configured MTD partitions isn't there so I have to fix this first.
I'm still using Kernel 4.3.2 patched with the 4.2.0 one.
This was the first one which is "stable" on this device.

But as I see now, the env isn't accessable via debian.
No problem with kernel 4.2.

The actual bootlog:
http://pastebin.com/qYtmxvgM

U-Boot env:
http://pastebin.com/1G6KDH0G


tried to use the new rootfs but cannot access the device.. let's see why ..


seems that the ethernet device doesn't come up properly.

http://pastebin.com/irLCnuBc

                                                                                                                                                                         
Listening on LPF/eth0/00:d0:b8:15:dc:5d                                                                                                                                  
Sending on   LPF/eth0/00:d0:b8:15:dc:5d                                                                                                                                  
Sending on   Socket/fallback                                                                                                                                             
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3                                                                                                               
                                                                                                                                                                         
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3                                                                                                               
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8                                                                                                               
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20                                                                                                              
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7                                                                                                               
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16                                                                                                              
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4                                                                                                               
No DHCPOFFERS received.                                                                                                                                                  
No working leases in persistent database - sleeping.                                                                                                                     
done.

Edit

I have to bring up eth1 and not eth0 sorry for that ;-)


fw_printenv still doesn't working .. it has with kernel 4.2 but not 4.3 or 4.4



Edited 3 time(s). Last edit at 04/03/2016 11:02AM by pengu.

pengu,

> fw_printenv still doesn't working .. it has with
> kernel 4.2 but not 4.3 or 4.4

You are using the ix2-200 DTS for the ix2-dl. Are you sure they are based on the same box? what are the differences between these 2?

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

bodhi Wrote:
-------------------------------------------------------
> You are using the ix2-200 DTS for the ix2-dl. Are
> you sure they are based on the same box? what are
> the differences between these 2?


- more flash (1 GiB)
- 1.6 GHz Marvell Kirkwood 88F6282
- eth0 is coming up fine
- same shutdown behaviour as NSA320s / NSA325v2

pengu,

> - more flash (1 GiB)
> - 1.6 GHz Marvell Kirkwood 88F6282
> - eth0 is coming up fine
> - same shutdown behaviour as NSA320s / NSA325v2

OK, it does make sense! so I think the env problem is just a matter of a wrong definition or wrong setting.

Quote

fw_printenv still doesn't working .. it has with kernel 4.2 but not 4.3 or 4.4

This observation is interesting. So fw_printenv in 4.2 worked for both boxes. But fw_printenv only works for the ix2-200 in 4.3+ ?

Quote

> - more flash (1 GiB)

What is the stock MTD partition differences, if any?

In stock u-boot console, printenv for ix2-200 and ix2-dl mtdparts. Are they the same, and are they used in bootargs? Please list the relevant envs.

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

U-Boot stuff from ix2-dl:

http://pastebin.com/wYKsvPY0

I hope that I've backed up it correctly:

mtdparts ix2-200:

mtdparts=nand_mtd:0x100000@0(uboot)ro,0x20000@0xA0000(uboot_env),0x300000@0x900000(kernel),0x1400000@0xC00000(root),0x6000000@0x2000000(root2),0x300000@0x100000(iomega_zImage),0x300000@0x540000(iomega_initrd)

mtdparts ix2-dl:

mtdparts=nand_mtd:0x80000@0(uboot),0x20000@0xa0000(env),0x20000@0xc0000(env2),$(kernel_size)@$(kernel_start)(uImage),$(initrd_size)@$(initrd_start)(initrd),0x3f800000@0x800000(boot),1024m@0x0(flash)

Edit this isn't working so I changed it to:

mtdparts=orion_nand:0x80000@0(uboot),0x20000@0xa0000(env),0x20000@0xc0000(env2),0x300000@0x100000(uImage),0x300000@0x400000(initrd),0x3f800000@0x800000(boot),1024m@0x0(flash)'

now it looks like this after booting:

[   40.206705] 7 cmdlinepart partitions found on MTD device orion_nand
[   40.213011] Creating 7 MTD partitions on "orion_nand":
[   40.218188] 0x000000000000-0x000000080000 : "uboot"
[   40.224212] 0x0000000a0000-0x0000000c0000 : "env"
[   40.229946] 0x0000000c0000-0x0000000e0000 : "env2"
[   40.235745] 0x000000100000-0x000000400000 : "uImage"
[   40.241734] 0x000000400000-0x000000700000 : "initrd"
[   40.247726] 0x000000800000-0x000040000000 : "boot"
[   40.254898] 0x000000000000-0x000040000000 : "flash"

hmm it's there ..
(ix2-200)

 hexdump -C -n200 /dev/mtd1
00000000  5e 98 a1 2f 62 61 75 64  72 61 74 65 3d 31 31 35  |^../baudrate=115|
00000010  32 30 30 00 6c 6f 61 64  73 5f 65 63 68 6f 3d 30  |200.loads_echo=0|
00000020  00 72 6f 6f 74 70 61 74  68 3d 2f 6d 6e 74 2f 41  |.rootpath=/mnt/A|
00000030  52 4d 5f 46 53 2f 00 43  41 53 73 65 74 3d 6d 69  |RM_FS/.CASset=mi|
00000040  6e 00 4d 41 4c 4c 4f 43  5f 6c 65 6e 3d 31 00 69  |n.MALLOC_len=1.i|
00000050  6d 61 67 65 5f 6e 61 6d  65 3d 75 49 6d 61 67 65  |mage_name=uImage|
00000060  00 73 74 61 6e 64 61 6c  6f 6e 65 3d 66 73 6c 6f  |.standalone=fslo|
00000070  61 64 20 30 78 32 30 30  30 30 30 30 20 24 28 69  |ad 0x2000000 $(i|
00000080  6d 61 67 65 5f 6e 61 6d  65 29 3b 73 65 74 65 6e  |mage_name);seten|
00000090  76 20 62 6f 6f 74 61 72  67 73 20 24 28 63 6f 6e  |v bootargs $(con|
000000a0  73 6f 6c 65 29 20 72 6f  6f 74 3d 2f 64 65 76 2f  |sole) root=/dev/|
000000b0  6d 74 64 62 6c 6f 63 6b  30 20 72 77 20 69 70 3d  |mtdblock0 rw ip=|
000000c0  24 28 69 70 61 64 64 72                           |$(ipaddr|

on ix2-dl I get nothing useful before and after changing the partitions


from the dtb:

        partition@a0000 {
                label = "env";
                reg = <0xa0000 0x20000>;
                read-only;
        };

dmesg:

...
[    1.518263] nand: device found, Manufacturer ID: 0xad, Chip ID: 0x75                                                                                        
[    1.524696] nand: Hynix NAND 32MiB 3,3V 8-bit                                                                                                               
[    1.529094] nand: 32 MiB, SLC, erase size: 16 KiB, page size: 512, OOB size: 16                                                                             
[    1.536469] Scanning device for bad blocks                                                                                                                  
[    1.766465] 2 cmdlinepart partitions found on MTD device orion_nand                                                                                         
[    1.772787] Creating 2 MTD partitions on "orion_nand":                                                                                                      
[    1.777983] 0x000000000000-0x000000100000 : "uboot"                                                                                                         
[    1.784562] 0x0000000a0000-0x0000000c0000 : "uboot_env"   
...

for me it's enough to have these two partitions

Edit

on ix2-dl its' worse when trying to use the NAND inside debian.
tried some other DTBs (NSA325 and NSA320s but it doesn't come up)

and it seems to have a different sensor chip

lm63-i2c-0-4c
Adapter: mv64xxx_i2c adapter
temp1:         -6.0°C  (high =  -6.0°C)                  ALARM (HIGH)
temp2:         +0.0°C  (low  =  +0.0°C, high =  +0.0°C)  ALARM (LOW, HIGH, CRIT)
                       (crit =  -6.0°C, hyst = -256.0°C)

Edited 12 time(s). Last edit at 04/04/2016 12:09PM by pengu.

pengu,

It totally slipped my mind the fact that you're booting with stock u-boot :) No, you can't use fw_printenv or fw_setenv. You need to find the stock version of this. Log into to stock OS and try fw_printenv to see if it even there.

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

bodhi Wrote:
-------------------------------------------------------
No, you can't use
> fw_printenv or fw_setenv. You need to find the
> stock version of this. Log into to stock OS and
> try fw_printenv to see if it even there.


on ix2-200 it can be resolved I think ..
on ix2-dl .. it will be tricky
I don't see any output after

'Starting kernel ... '

but debian is booting fine ...long ago that I have bootet stock OS because it isn't usable withoudh HDDs and I don't remember that I find "fw_printenv" or "fw_setenv" there

pengu Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> No, you can't use
> > fw_printenv or fw_setenv. You need to find the
> > stock version of this. Log into to stock OS and
> > try fw_printenv to see if it even there.
>
>
> on ix2-200 it can be resolved I think ..
> on ix2-dl .. it will be tricky
> I don't see any output after
>
> 'Starting kernel ... '
>
> but debian is booting fine ...long ago that I have
> bootet stock OS because it isn't usable withoudh
> HDDs and I don't remember that I find
> "fw_printenv" or "fw_setenv" there

No. With stock u-boot the envs are not usable by the modern mdt-utils.

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