Iomega ix4-200d U-boot needed
Posted by Reto
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 05:16PM |
Admin Registered: 13 years ago Posts: 18,543 |
Basically, that md is memory display command.
The Kirkwood GPIO registers are mapped to memory at these 2 locations. And we dumping 1 long integer value at each location.
Take this value. It says that bit 12,14,15 are on (bit 0 is righ-most).
1000d080
I've missed one bit, so only bit 14 and 15 are on.
1000c080
GPIOs are what enable SATA, USB power. And also specify other hardware aspect.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/28/2022 05:19PM by bodhi.
The Kirkwood GPIO registers are mapped to memory at these 2 locations. And we dumping 1 long integer value at each location.
md.l 0xF1010100 1 md.l 0xF1010140 1
Take this value. It says that bit 12,14,15 are on (bit 0 is righ-most).
1000d080
I've missed one bit, so only bit 14 and 15 are on.
1000c080
GPIOs are what enable SATA, USB power. And also specify other hardware aspect.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/28/2022 05:19PM by bodhi.
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 05:32PM |
Admin Registered: 13 years ago Posts: 18,543 |
Attached here is version tld-0.6
This time, kwboot it. And then dump the registers again
And,
If at least 2 SATA drives were initialized, boot into Debian USB rootfs. See if kernel behavior is different or not regarding the 4 HDDs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
This time, kwboot it. And then dump the registers again
md.l 0xF1010000 8 md.l 0xF1010100 1 md.l 0xF1010140 1
And,
sata init sata info sata part
If at least 2 SATA drives were initialized, boot into Debian USB rootfs. See if kernel behavior is different or not regarding the 4 HDDs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 05:56PM |
Registered: 1 year ago Posts: 52 |
No change:
99 % [....................................] [Type Ctrl-\ + c to quit] U-Boot 2022.10-rc3-tld-0.6 (Aug 28 2022 - 15:21:44 -0700) Lenovo-ix4-200d SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB Core: 16 devices, 12 uclasses, devicetree: separate NAND: 32 MiB MMC: Loading Environment from NAND... OK In: serial Out: serial Err: serial pcie0.0: Link up Net: eth0: ethernet-controller@72000, eth1: ethernet-controller@76000 Hit any key to stop autoboot: 0 IX4-200D> md.l 0xF1010000 8 f1010000: 01111111 00003311 33331140 33003333 .....3..@.3333.3 f1010010: 00000033 00000000 00000000 00000000 3............... IX4-200D> md.l 0xF1010100 1 f1010100: 1000d080 .... IX4-200D> md.l 0xF1010140 1 f1010140: 0001000c .... IX4-200D> sata init IX4-200D> sata info IX4-200D> sata part no sata partition table available
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 06:09PM |
Admin Registered: 13 years ago Posts: 18,543 |
CodeJACK,
> IX4-200D> md.l 0xF1010000 8
> f1010000: 01111111 00003311 33331140 33003333
> .....3..@.3333.3
> f1010010: 00000033 00000000 00000000 00000000
> 3...............
> IX4-200D> md.l 0xF1010100 1
> f1010100: 1000d080
> ....
> IX4-200D> md.l 0xF1010140 1
> f1010140: 0001000c
> ....
Insert a sleep 5 before and after sata init.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> IX4-200D> md.l 0xF1010000 8
> f1010000: 01111111 00003311 33331140 33003333
> .....3..@.3333.3
> f1010010: 00000033 00000000 00000000 00000000
> 3...............
> IX4-200D> md.l 0xF1010100 1
> f1010100: 1000d080
> ....
> IX4-200D> md.l 0xF1010140 1
> f1010140: 0001000c
> ....
Insert a sleep 5 before and after sata init.
sleep 5 sata init sleep 5 sata info sata part
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 06:15PM |
Registered: 1 year ago Posts: 52 |
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 06:22PM |
Admin Registered: 13 years ago Posts: 18,543 |
Power down, kwboot again and
> IX4-200D> sleep 5
> IX4-200D> sata init
> IX4-200D> sleep 5
> IX4-200D> sata info
> IX4-200D> sata part
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> IX4-200D> sleep 5
> IX4-200D> sata init
> IX4-200D> sleep 5
> IX4-200D> sata info
> IX4-200D> sata part
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 06:27PM |
Registered: 1 year ago Posts: 52 |
90 % [......................................................................] 92 % [......................................................................] 94 % [......................................................................] 95 % [......................................................................] 97 % [......................................................................] 99 % [....................................] [Type Ctrl-\ + c to quit] U-Boot 2022.10-rc3-tld-0.6 (Aug 28 2022 - 15:21:44 -0700) Lenovo-ix4-200d SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB Core: 16 devices, 12 uclasses, devicetree: separate NAND: 32 MiB MMC: Loading Environment from NAND... OK In: serial Out: serial Err: serial pcie0.0: Link up Net: eth0: ethernet-controller@72000, eth1: ethernet-controller@76000 Hit any key to stop autoboot: 0 IX4-200D> sleep 5 IX4-200D> sata init IX4-200D> sleep 5 IX4-200D> sata info IX4-200D> sata part no sata partition table available IX4-200D>
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 07:05PM |
Admin Registered: 13 years ago Posts: 18,543 |
That is strange. So let do these pokes step with the 0.6 version.
Power cyle, kwboot with uboot.2022.10-rc3-tld-0.6.ix4_200d.mtd0.kwb
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Power cyle, kwboot with uboot.2022.10-rc3-tld-0.6.ix4_200d.mtd0.kwb
md.l 0xF1010000 8 mw.l 0xF1010100 0x1000d080 mw.l 0xf1010140 0x0001000c sleep 5 sata init sata info
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 07:11PM |
Registered: 1 year ago Posts: 52 |
:-(
94 % [......................................................................] 95 % [......................................................................] 97 % [......................................................................] 99 % [....................................] [Type Ctrl-\ + c to quit] U-Boot 2022.10-rc3-tld-0.6 (Aug 28 2022 - 15:21:44 -0700) Lenovo-ix4-200d SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB Core: 16 devices, 12 uclasses, devicetree: separate NAND: 32 MiB MMC: Loading Environment from NAND... OK In: serial Out: serial Err: serial pcie0.0: Link up Net: eth0: ethernet-controller@72000, eth1: ethernet-controller@76000 Hit any key to stop autoboot: 0 IX4-200D> md.l 0xF1010000 8 f1010000: 01111111 00003311 33331140 33003333 .....3..@.3333.3 f1010010: 00000033 00000000 00000000 00000000 3............... IX4-200D> mw.l 0xF1010100 0x1000d080 IX4-200D> mw.l 0xf1010140 0x0001000c IX4-200D> sleep 5 IX4-200D> sata init IX4-200D> sata info IX4-200D>
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 07:19PM |
Admin Registered: 13 years ago Posts: 18,543 |
OK I must have broken something :) Let's go back to that version back in tld-0.2 and rerun
https://forum.doozan.com/read.php?3,25120,132878#msg-132878
And then boot into Debian on USB. See if SATA behavior changes.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
https://forum.doozan.com/read.php?3,25120,132878#msg-132878
And then boot into Debian on USB. See if SATA behavior changes.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 07:41PM |
Registered: 1 year ago Posts: 52 |
SATA and SCSI disks appear to be detected by parted:
97 % [......................................................................]
99 % [....................................]
[Type Ctrl-\ + c to quit]
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... OK
In: serial
Out: serial
Err: serial
Net: eth0: ethernet-controller@72000, eth1: ethernet-controller@76000
Hit any key to stop autoboot: 0
=> mw.l 0xF1010100 0x1000d080
=> mw.l 0xf1010140 0x0001000c
=> sleep 5
=> sata init
Err: Failed to identify SATA device 0
Err: Failed to identify SATA device 1
=> sata info
Device 0: Model: Firm: Ser#:
Type: Hard Disk
Capacity: not available
Device 1: Model: Firm: Ser#:
Type: Hard Disk
Capacity: not available
=> sleep 5
=> sata init
=> sata reset
sata - SATA sub system
Usage:
sata init - init SATA sub system
sata stop [dev] - disable SATA sub system or device
sata info - show available SATA devices
sata device [dev] - show or set current device
sata part [dev] - print partition table
sata read addr blk# cnt
sata write addr blk# cnt
=> sata device
IDE device 0: Model: ST6000NM021A-2R7101 Firm: SN03 Ser#: WSE0QQ6A
Type: Hard Disk
Supports 48-bit addressing
Capacity: 5723166.5 MB = 5589.0 GB (11721045168 x 512)
=> sata part
Partition Map for SATA device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 1 4294967295 00000000-01 ee
Partition Map for SATA device 1 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 1 4294967295 00000000-01 ee
=> sata info
Device 0: Model: ST6000NM021A-2R7101 Firm: SN03 Ser#: WSE0QQ6A
Type: Hard Disk
Supports 48-bit addressing
Capacity: 5723166.5 MB = 5589.0 GB (11721045168 x 512)
Device 1: Model: ST6000NM021A-2R7101 Firm: SN03 Ser#: WSE0QPSQ
Type: Hard Disk
Supports 48-bit addressing
Capacity: 5723166.5 MB = 5589.0 GB (11721045168 x 512)
=> scsi init
Unknown command 'scsi' - try 'help'
=> setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts'
=> setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage.orig'
=> setenv load_uinitrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
=> setenv load_dtb 'ext2load usb 0:1 0x2c00000 /boot/dts/kirkwood-iomega_ix4_200d.dtb'
=> setenv usb_boot 'usb reset; run set_bootargs; run load_uimage; run load_uinitrd; run load_dtb; bootm 0x800000 0x1100000 0x2c00000'
=> saveenv
Saving Environment to NAND... Erasing NAND...
Erasing at 0xdc000 -- 100% complete.
Writing to NAND... OK
OK
=> run usb_boot
resetting 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
5729264 bytes read in 247 ms (22.1 MiB/s)
11127733 bytes read in 479 ms (22.2 MiB/s)
9274 bytes read in 27 ms (335 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: linux-5.18.6-kirkwood-tld-1.patc
Created: 2022-08-24 23:03:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5729200 Bytes = 5.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-5.18.6-kirkwood-tld-1
Created: 2022-08-03 18:44:18 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 11127669 Bytes = 10.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02c00000
Booting using the fdt blob at 0x2c00000
Loading Kernel Image
Loading Ramdisk to 1f0b4000, end 1fb50b75 ... OK
Loading Device Tree to 0fffa000, end 0ffff439 ... OK
Starting kernel ...
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 5.18.6-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1.0 PREEMPT Fri Jun 24 15:26:02 PDT 2022
[ 0.000000][ T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000][ T0] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000][ T0] OF: fdt: Machine model: Iomega ix4-200d
[ 0.000000][ T0] Memory policy: Data cache writeback
[ 0.000000][ T0] Zone ranges:
[ 0.000000][ T0] Normal [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000][ T0] Movable zone start for each node
[ 0.000000][ T0] Early memory node ranges
[ 0.000000][ T0] node 0: [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000][ T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000][ T0] Built 1 zonelists, mobility grouping on. Total pages: 130048
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000@0x0(u-boot),0x0500000@0x100000(uImage),-(rootfs)
[ 0.000000][ T0] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000][ T0] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[ 0.000000][ T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[ 0.000000][ T0] Memory: 488452K/524288K available (11264K kernel code, 1633K rwdata, 4936K rodata, 1024K init, 300K bss, 35836K reserved, 0K cma-reserved)
[ 0.000000][ T0] trace event string verifier disabled
[ 0.000000][ T0] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000][ T0] Trampoline variant of Tasks RCU enabled.
[ 0.000000][ T0] Tracing variant of Tasks RCU enabled.
[ 0.000000][ T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000][ T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000][ T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 0.000002][ T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.000058][ T0] Switching to timer-based delay loop, resolution 5ns
[ 0.001588][ T0] Console: colour dummy device 80x30
[ 0.001664][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[ 0.001707][ T0] pid_max: default: 32768 minimum: 301
[ 0.002376][ T0] LSM: Security Framework initializing
[ 0.002809][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.002859][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.004739][ T0] CPU: Testing write buffer coherency: ok
[ 0.007777][ T1] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.007814][ T1] cblist_init_generic: Setting shift to 0 and lim to 1.
[ 0.008212][ T1] cblist_init_generic: Setting shift to 0 and lim to 1.
[ 0.008695][ T1] Setting up static identity map for 0x100000 - 0x100058
[ 0.009024][ T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.009429][ T1] rcu: Hierarchical SRCU implementation.
[ 0.011307][ T1] devtmpfs: initialized
[ 0.017695][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.017753][ T1] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[ 0.056164][ T1] prandom32: self test passed (less than 6 bits correlated)
[ 0.056211][ T1] prandom: seed boundary self test passed
[ 0.060518][ T1] prandom: 100 self tests passed
[ 0.060549][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.063087][ T1] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.063972][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.065252][ T1] audit: initializing netlink subsys (disabled)
[ 0.067305][ T1] thermal_sys: Registered thermal governor 'step_wise'
[ 0.067746][ T16] audit: type=2000 audit(0.060:1): state=initialized audit_enabled=0 res=1
[ 0.067909][ T1] cpuidle: using governor ladder
[ 0.068006][ T1] cpuidle: using governor menu
[ 0.068559][ T1] Feroceon L2: Enabling L2
[ 0.068615][ T1] Feroceon L2: Cache support initialised.
[ 0.078997][ T1] No ATAGs?
[ 0.260231][ T1] raid6: int32x8 gen() 108 MB/s
[ 0.430288][ T1] raid6: int32x4 gen() 95 MB/s
[ 0.600222][ T1] raid6: int32x2 gen() 138 MB/s
[ 0.770498][ T1] raid6: int32x1 gen() 98 MB/s
[ 0.770522][ T1] raid6: using algorithm int32x2 gen() 138 MB/s
[ 0.940166][ T1] raid6: .... xor() 81 MB/s, rmw enabled
[ 0.940186][ T1] raid6: using intx1 recovery algorithm
[ 0.941050][ T1] SCSI subsystem initialized
[ 0.941736][ T1] usbcore: registered new interface driver usbfs
[ 0.941853][ T1] usbcore: registered new interface driver hub
[ 0.941917][ T1] usbcore: registered new device driver usb
[ 0.942205][ T1] pps_core: LinuxPPS API ver. 1 registered
[ 0.942223][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.942261][ T1] PTP clock support registered
[ 0.944031][ T1] vgaarb: loaded
[ 0.944805][ T1] clocksource: Switched to clocksource orion_clocksource
[ 1.081629][ T1] VFS: Disk quotas dquot_6.6.0
[ 1.081751][ T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.107019][ T1] NET: Registered PF_INET protocol family
[ 1.107379][ T1] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 1.115403][ T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 1.115657][ T1] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 1.115699][ T1] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[ 1.115775][ T1] TCP bind hash table entries: 4096 (order: 2, 16384 bytes, linear)
[ 1.115837][ T1] TCP: Hash tables configured (established 4096 bind 4096)
[ 1.116150][ T1] MPTCP token hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 1.116256][ T1] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 1.116310][ T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 1.116641][ T1] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 1.117699][ T1] RPC: Registered named UNIX socket transport module.
[ 1.117724][ T1] RPC: Registered udp transport module.
[ 1.117737][ T1] RPC: Registered tcp transport module.
[ 1.117750][ T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.117769][ T1] PCI: CLS 0 bytes, default 32
[ 1.117956][ T1] NetWinder Floating Point Emulator V0.97 (double precision)
[ 1.125236][ T30] Trying to unpack rootfs image as initramfs...
[ 3.084868][ T30] Freeing initrd memory: 10868K
[ 3.845793][ T1] Initialise system trusted keyrings
[ 3.845934][ T1] Key type blacklist registered
[ 3.846310][ T1] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[ 3.846487][ T1] zbud: loaded
[ 3.848811][ T1] NFS: Registering the id_resolver key type
[ 3.848872][ T1] Key type id_resolver registered
[ 3.848890][ T1] Key type id_legacy registered
[ 3.848958][ T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 3.848985][ T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[ 3.849002][ T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 3.849443][ T1] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 3.849975][ T1] fuse: init (API version 7.36)
[ 3.850452][ T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 3.850773][ T1] orangefs_init: module version upstream loaded
[ 3.850794][ T1] SGI XFS with ACLs, security attributes, realtime, scrub, quota, no debug enabled
[ 3.949833][ T1] xor: measuring software checksum speed
[ 3.958801][ T1] arm4regs : 1112 MB/sec
[ 3.973574][ T1] 8regs : 667 MB/sec
[ 3.984001][ T1] 32regs : 947 MB/sec
[ 3.984019][ T1] xor: using function: arm4regs (1112 MB/sec)
[ 3.984042][ T1] async_tx: api initialized (async)
[ 3.984063][ T1] Key type asymmetric registered
[ 3.984078][ T1] Asymmetric key parser 'x509' registered
[ 4.021782][ T1] alg: self-tests for CTR-KDF (hmac(sha256)) passed
[ 4.022039][ T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 4.022208][ T1] io scheduler bfq registered
[ 4.211790][ T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 4.214191][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@82000000 ranges:
[ 4.214293][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[ 4.214344][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 4.214381][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 4.214494][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: pcie0.0: legacy INTx interrupts cannot be masked individually, /mbus@f1000000/pcie@82000000/pcie@1,0 does not contain intx interrupt
[ 4.215050][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[ 4.215081][ T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 4.215109][ T1] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[ 4.215133][ T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 4.215154][ T1] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 4.215275][ T1] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400
[ 4.216526][ T1] PCI: bus0: Fast back to back transfers disabled
[ 4.216566][ T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.216876][ T1] pci 0000:01:00.0: [11ab:6121] type 00 class 0x01018f
[ 4.216919][ T1] pci 0000:01:00.0: reg 0x10: [io 0x8000-0x8007]
[ 4.216949][ T1] pci 0000:01:00.0: reg 0x14: [io 0x8040-0x8043]
[ 4.216978][ T1] pci 0000:01:00.0: reg 0x18: [io 0x8200-0x8207]
[ 4.217006][ T1] pci 0000:01:00.0: reg 0x1c: [io 0x8800-0x8803]
[ 4.217034][ T1] pci 0000:01:00.0: reg 0x20: [io 0x900000-0x90000f]
[ 4.217062][ T1] pci 0000:01:00.0: reg 0x24: [mem 0x00800000-0x008003ff]
[ 4.217168][ T1] pci 0000:01:00.0: supports D1
[ 4.217188][ T1] pci 0000:01:00.0: PME# supported from D0 D1 D3hot
[ 4.217552][ T1] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 4.218399][ T1] PCI: bus1: Fast back to back transfers disabled
[ 4.218433][ T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 4.218496][ T1] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[ 4.218523][ T1] pci 0000:00:01.0: BAR 13: assigned [io 0x10000-0x10fff]
[ 4.218554][ T1] pci 0000:01:00.0: BAR 5: assigned [mem 0xe0000000-0xe00003ff]
[ 4.218583][ T1] pci 0000:01:00.0: BAR 4: assigned [io 0x10000-0x1000f]
[ 4.218610][ T1] pci 0000:01:00.0: BAR 0: assigned [io 0x10010-0x10017]
[ 4.218636][ T1] pci 0000:01:00.0: BAR 2: assigned [io 0x10018-0x1001f]
[ 4.218661][ T1] pci 0000:01:00.0: BAR 1: assigned [io 0x10020-0x10023]
[ 4.218687][ T1] pci 0000:01:00.0: BAR 3: assigned [io 0x10024-0x10027]
[ 4.218713][ T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 4.218734][ T1] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
[ 4.218765][ T1] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]
[ 4.218931][ T1] pcieport 0000:00:01.0: enabling device (0140 -> 0143)
[ 4.219622][ T1] mv_xor f1060800.xor: Marvell shared XOR driver
[ 4.275937][ T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 4.279921][ T1] mv_xor f1060900.xor: Marvell shared XOR driver
[ 4.336008][ T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 4.340302][ T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 4.342007][ T1] printk: console [ttyS0] disabled
[ 4.342114][ T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[ 5.473942][ T1] printk: console [ttyS0] enabled
[ 5.489317][ T1] loop: module loaded
[ 5.494125][ T1] sata_mv f1080000.sata: slots 32 ports 2
[ 5.504147][ T1] scsi host0: sata_mv
[ 5.509046][ T1] scsi host1: sata_mv
[ 5.513239][ T1] ata1: SATA max UDMA/133 irq 33
[ 5.518122][ T1] ata2: SATA max UDMA/133 irq 33
[ 5.523947][ T1] nand: device found, Manufacturer ID: 0xec, Chip ID: 0x75
[ 5.531133][ T1] nand: Samsung NAND 32MiB 3,3V 8-bit
[ 5.536414][ T1] nand: 32 MiB, SLC, erase size: 16 KiB, page size: 512, OOB size: 16
[ 5.544489][ T1] Scanning device for bad blocks
[ 5.897607][ T1] 3 cmdlinepart partitions found on MTD device orion_nand
[ 5.904612][ T1] Creating 3 MTD partitions on "orion_nand":
[ 5.910530][ T1] 0x000000000000-0x000000100000 : "u-boot"
[ 5.916925][ T1] 0x000000100000-0x000000600000 : "uImage"
[ 5.923374][ T1] 0x000000600000-0x000002000000 : "rootfs"
[ 5.931155][ T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[ 5.939771][ T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[ 5.983836][ T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 6.024856][ T48] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 6.034247][ T48] ata1.00: ATA-11: ST6000NM021A-2R7101, SN03, max UDMA/133
[ 6.041372][ T48] ata1.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 6.056558][ T48] ata1.00: configured for UDMA/133
[ 6.072105][ T8] scsi 0:0:0:0: Direct-Access ATA ST6000NM021A-2R7 SN03 PQ: 0 ANSI: 5
[ 6.082487][ T33] sd 0:0:0:0: [sda] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
[ 6.091699][ T33] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 6.097852][ T33] sd 0:0:0:0: [sda] Write Protect is off
[ 6.103523][ T33] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.163086][ T33] sda: sda1
[ 6.167710][ T33] sd 0:0:0:0: [sda] Attached SCSI disk
[ 6.594859][ T50] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 6.604228][ T50] ata2.00: ATA-11: ST6000NM021A-2R7101, SN03, max UDMA/133
[ 6.611356][ T50] ata2.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 6.628621][ T50] ata2.00: configured for UDMA/133
[ 6.644170][ T30] scsi 1:0:0:0: Direct-Access ATA ST6000NM021A-2R7 SN03 PQ: 0 ANSI: 5
[ 6.654551][ T33] sd 1:0:0:0: [sdb] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
[ 6.663523][ T33] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[ 6.669670][ T33] sd 1:0:0:0: [sdb] Write Protect is off
[ 6.675413][ T33] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.686046][ T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:d0:b8:13:1d:15
[ 6.801611][ T33] sdb: sdb1
[ 6.806221][ T33] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 7.435938][ T1] mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC address 00:d0:b8:13:1d:16
[ 7.445652][ T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 7.452946][ T1] ehci-pci: EHCI PCI platform driver
[ 7.458207][ T1] ehci-orion: EHCI orion driver
[ 7.463199][ T1] orion-ehci f1050000.ehci: EHCI Host Controller
[ 7.469495][ T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 7.478108][ T1] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[ 7.504844][ T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 7.511910][ T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.18
[ 7.520954][ T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 7.528942][ T1] usb usb1: Product: EHCI Host Controller
[ 7.534547][ T1] usb usb1: Manufacturer: Linux 5.18.6-kirkwood-tld-1 ehci_hcd
[ 7.542004][ T1] usb usb1: SerialNumber: f1050000.ehci
[ 7.548256][ T1] hub 1-0:1.0: USB hub found
[ 7.552811][ T1] hub 1-0:1.0: 1 port detected
[ 7.558382][ T1] usbcore: registered new interface driver usb-storage
[ 7.565688][ T1] mousedev: PS/2 mouse device common for all mice
[ 7.573188][ T1] rtc-mv f1010300.rtc: registered as rtc0
[ 7.578904][ T1] rtc-mv f1010300.rtc: setting system clock to 2022-08-29T00:34:56 UTC (1661733296)
[ 7.588531][ T1] i2c_dev: i2c /dev entries driver
[ 7.595455][ T1] device-mapper: uevent: version 1.0.3
[ 7.601148][ T1] device-mapper: ioctl: 4.46.0-ioctl (2022-02-22) initialised: dm-devel@redhat.com
[ 7.611025][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 7.618363][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 7.625747][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 7.633185][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 7.640040][ T1] device-mapper: raid: Loading target version 1.15.1
[ 7.647482][ T1] hid: raw HID events driver (C) Jiri Kosina
[ 7.653761][ T1] drop_monitor: Initializing network drop monitor service
[ 7.661440][ T1] NET: Registered PF_INET6 protocol family
[ 7.669409][ T1] Segment Routing with IPv6
[ 7.673804][ T1] RPL Segment Routing with IPv6
[ 7.678703][ T1] In-situ OAM (IOAM) with IPv6
[ 7.683504][ T1] NET: Registered PF_PACKET protocol family
[ 7.689668][ T1] Key type dns_resolver registered
[ 7.695561][ T1] registered taskstats version 1
[ 7.700433][ T1] Loading compiled-in X.509 certificates
[ 7.707210][ T1] zswap: loaded using pool lzo/zbud
[ 7.713042][ T1] Key type ._fscrypt registered
[ 7.717873][ T1] Key type .fscrypt registered
[ 7.722522][ T1] Key type fscrypt-provisioning registered
[ 7.734200][ T1] Key type big_key registered
[ 7.770927][ T1] Key type encrypted registered
[ 7.844887][ T45] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 7.876093][ T106] "cryptomgr_test" (106) uses obsolete ecb(arc4) skcipher
[ 8.046741][ T45] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=77.63
[ 8.064827][ T45] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 8.072710][ T45] usb 1-1: Product: USB2.0 Hub
[ 8.096009][ T45] hub 1-1:1.0: USB hub found
[ 8.104839][ T45] hub 1-1:1.0: 4 ports detected
[ 8.434841][ T45] usb 1-1.2: new high-speed USB device number 3 using orion-ehci
[ 8.605988][ T45] usb 1-1.2: New USB device found, idVendor=0781, idProduct=557c, bcdDevice= 1.27
[ 8.624829][ T45] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8.632883][ T45] usb 1-1.2: Product: Cruzer Orbit
[ 8.654826][ T45] usb 1-1.2: Manufacturer: SanDisk
[ 8.659828][ T45] usb 1-1.2: SerialNumber: 4C530012311126108485
[ 8.675700][ T45] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[ 8.695350][ T45] scsi host2: usb-storage 1-1.2:1.0
[ 9.770199][ T33] scsi 2:0:0:0: Direct-Access SanDisk Cruzer Orbit 1.27 PQ: 0 ANSI: 6
[ 9.803902][ T30] sd 2:0:0:0: [sdc] 62530624 512-byte logical blocks: (32.0 GB/29.8 GiB)
[ 9.830401][ T30] sd 2:0:0:0: [sdc] Write Protect is off
[ 9.845638][ T30] sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 9.895646][ T30] sdc: sdc1
[ 9.925391][ T30] sd 2:0:0:0: [sdc] Attached SCSI removable disk
[ 12.428072][ T1] Freeing unused kernel image (initmem) memory: 1024K
[ 12.455757][ T1] Checked W+X mappings: passed, no W+X pages found
[ 12.462171][ T1] Run /init as init process
Loading, please wait...
Starting version 247.3-6
[ 13.470086][ T146] ahci 0000:01:00.0: Disabling your PATA port. Use the boot option 'ahci.marvell_enable=0' to avoid this.
[ 13.537500][ T146] ahci 0000:01:00.0: controller can't do NCQ, turning off CAP_NCQ
[ 13.568312][ T146] ahci 0000:01:00.0: controller can't do PMP, turning off CAP_PMP
[ 13.607551][ T146] ahci 0000:01:00.0: masking port_map 0x7 -> 0x3
[ 13.613948][ T146] ahci 0000:01:00.0: SSS flag set, parallel bus scan disabled
[ 13.656051][ T150] usbcore: registered new interface driver uas
[ 13.683457][ T146] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x3 impl IDE mode
[ 13.758306][ T146] ahci 0000:01:00.0: flags: 64bit stag led slum part
[ 13.818281][ T146] scsi host3: ahci
[ 13.844049][ T146] scsi host4: ahci
[ 13.880769][ T146] scsi host5: ahci
[ 13.916331][ T146] ata3: SATA max UDMA/133 abar m1024@0xe0000000 port 0xe0000100 irq 38
[ 13.924512][ T146] ata4: SATA max UDMA/133 abar m1024@0xe0000000 port 0xe0000180 irq 38
[ 14.023230][ T146] ata5: DUMMY
[ 14.376779][ T155] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 14.385541][ T155] ata3.00: ATA-11: ST6000NM021A-2R7101, SN03, max UDMA/133
[ 14.392717][ T155] ata3.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 14.403215][ T155] ata3.00: configured for UDMA/133
[ 14.418806][ T30] scsi 3:0:0:0: Direct-Access ATA ST6000NM021A-2R7 SN03 PQ: 0 ANSI: 5
[ 14.431163][ T163] sd 3:0:0:0: [sdd] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
[ 14.441532][ T163] sd 3:0:0:0: [sdd] 4096-byte physical blocks
[ 14.447735][ T163] sd 3:0:0:0: [sdd] Write Protect is off
[ 14.453497][ T163] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 14.757466][ T163] sdd: sdd1
[ 14.763752][ T163] sd 3:0:0:0: [sdd] Attached SCSI disk
[ 14.779429][ T157] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 14.788331][ T157] ata4.00: ATA-11: ST6000NM021A-2R7101, SN03, max UDMA/133
[ 14.795526][ T157] ata4.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 14.806212][ T157] ata4.00: configured for UDMA/133
[ 14.821964][ T33] scsi 4:0:0:0: Direct-Access ATA ST6000NM021A-2R7 SN03 PQ: 0 ANSI: 5
[ 14.840770][ T163] sd 4:0:0:0: [sde] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
[ 14.857482][ T163] sd 4:0:0:0: [sde] 4096-byte physical blocks
[ 14.869363][ T163] sd 4:0:0:0: [sde] Write Protect is off
[ 14.882034][ T163] sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 14.936901][ T163] sde: sde1
[ 14.943240][ T163] sd 4:0:0:0: [sde] Attached SCSI disk
Begin: Loading essential drivers ... [ 16.250825][ T168] Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=no
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
[ 26.350041][ C0] random: crng init done
done.
Begin: Will now check root file system ... fsck from util-linux 2.36.1
[/sbin/fsck.ext2 (1) -- /dev/sdc1] fsck.ext2 -a -C0 /dev/sdc1
rootfs: clean, 43173/1954064 files, 678655/7815936 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[ 27.654178][ T1] systemd[1]: Inserted module 'autofs4'
[ 27.758112][ T1] systemd[1]: systemd 247.3-7 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[ 27.782318][ T1] systemd[1]: Detected architecture arm.
Welcome to Debian GNU/Linux 11 (bullseye)!
[ 27.827139][ T1] systemd[1]: Set hostname to <debian>.
[ 30.437248][ T1] systemd[1]: Queued start job for default target Graphical Interface.
[ 30.448758][ T1] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
[ 30.462057][ T1] systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
[ 30.473615][ T1] systemd[1]: Created slice system-getty.slice.
[ OK ] Created slice system-getty.slice.
[ 30.516442][ T1] systemd[1]: Created slice system-modprobe.slice.
[ OK ] Created slice system-modprobe.slice.
[ 30.556423][ T1] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ OK ] Created slice system-serial\x2dgetty.slice.
[ 30.596041][ T1] systemd[1]: Created slice User and Session Slice.
[ OK ] Created slice User and Session Slice.
[ 30.635653][ T1] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Started Dispatch Password …ts to Console Directory Watch.
[ 30.675578][ T1] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ OK ] Started Forward Password R…uests to Wall Directory Watch.
[ 30.716669][ T1] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ OK ] Set up automount Arbitrary…s File System Automount Point.
[ 30.755483][ T1] systemd[1]: Reached target Local Encrypted Volumes.
[ OK ] Reached target Local Encrypted Volumes.
[ 30.795978][ T1] systemd[1]: Reached target Paths.
[ OK ] Reached target Paths.
[ 30.835548][ T1] systemd[1]: Reached target Slices.
[ OK ] Reached target Slices.
[ 30.875290][ T1] systemd[1]: Reached target Swap.
[ OK ] Reached target Swap.
[ 30.905279][ T1] systemd[1]: Reached target System Time Set.
[ OK ] Reached target System Time Set.
[ 30.946462][ T1] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ OK ] Listening on Device-mapper event daemon FIFOs.
[ 30.985931][ T1] systemd[1]: Listening on LVM2 poll daemon socket.
[ OK ] Listening on LVM2 poll daemon socket.
[ 31.026279][ T1] systemd[1]: Listening on RPCbind Server Activation Socket.
[ OK ] Listening on RPCbind Server Activation Socket.
[ 31.067535][ T1] systemd[1]: Listening on Syslog Socket.
[ OK ] Listening on Syslog Socket.
[ 31.107219][ T1] systemd[1]: Listening on fsck to fsckd communication Socket.
[ OK ] Listening on fsck to fsckd communication Socket.
[ 31.145677][ T1] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ OK ] Listening on initctl Compatibility Named Pipe.
[ 31.186527][ T1] systemd[1]: Listening on Journal Audit Socket.
[ OK ] Listening on Journal Audit Socket.
[ 31.226036][ T1] systemd[1]: Listening on Journal Socket (/dev/log).
[ OK ] Listening on Journal Socket (/dev/log).
[ 31.266279][ T1] systemd[1]: Listening on Journal Socket.
[ OK ] Listening on Journal Socket.
[ 31.307520][ T1] systemd[1]: Listening on Network Service Netlink Socket.
[ OK ] Listening on Network Service Netlink Socket.
[ 31.346301][ T1] systemd[1]: Listening on udev Control Socket.
[ OK ] Listening on udev Control Socket.
[ 31.386079][ T1] systemd[1]: Listening on udev Kernel Socket.
[ OK ] Listening on udev Kernel Socket.
[ 31.426157][ T1] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[ 31.440638][ T1] systemd[1]: Mounting POSIX Message Queue File System...
Mounting POSIX Message Queue File System...
[ 31.468879][ T1] systemd[1]: Mounting RPC Pipe File System...
Mounting RPC Pipe File System...
[ 31.520328][ T1] systemd[1]: Mounting Kernel Debug File System...
Mounting Kernel Debug File System...
[ 31.570056][ T1] systemd[1]: Mounting Kernel Trace File System...
Mounting Kernel Trace File System...
[ 31.615664][ T1] systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped.
[ 31.627013][ T1] systemd[1]: Finished Availability of block devices.
[ OK ] Finished Availability of block devices.
[ 31.672549][ T1] systemd[1]: Starting Create list of static device nodes for the current kernel...
Starting Create list of st…odes for the current kernel...
[ 31.730113][ T1] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Starting Monitoring of LVM…meventd or progress polling...
[ 31.790690][ T1] systemd[1]: Starting Load Kernel Module configfs...
Starting Load Kernel Module configfs...
[ 31.860710][ T1] systemd[1]: Starting Load Kernel Module drm...
Starting Load Kernel Module drm...
[ 31.930579][ T1] systemd[1]: Starting Load Kernel Module fuse...
Starting Load Kernel Module fuse...
[ 31.985533][ T1] systemd[1]: Condition check resulted in OpenVSwitch configuration for cleanup being skipped.
[ 32.017890][ T1] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[ 32.028560][ T1] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[ 32.049192][ T1] systemd[1]: Starting Journal Service...
Starting Journal Service...
[ 32.106509][ T1] systemd[1]: Starting Load Kernel Modules...
Starting Load Kernel Modules...
[ 32.146571][ T1] systemd[1]: Starting Remount Root and Kernel File Systems...
Starting Remount Root and Kernel File Systems...
[ 32.216389][ T1] systemd[1]: Starting Coldplug All udev Devices...
Starting Coldplug All udev Devices...
[ 32.320780][ T1] systemd[1]: Mounted POSIX Message Queue File System.
[ OK ] Mounted POSIX Message Queue File System.
[ 32.369237][ T1] systemd[1]: Mounted RPC Pipe File System.
[ OK ] Mounted RPC Pipe File System.
[ 32.417436][ T1] systemd[1]: Mounted Kernel Debug File System.
[ OK ] Mounted Kernel Debug File System.
[ 32.446523][ T1] systemd[1]: Mounted Kernel Trace File System.
[ OK ] Mounted Kernel Trace File System.
[ 32.487400][ T1] systemd[1]: Finished Create list of static device nodes for the current kernel.
[ 32.499591][ T241] ext2 filesystem being remounted at / supports timestamps until 2038 (0x7fffffff)
[ OK ] Finished Create list of st… nodes for the current kernel.
[ 32.595068][ T1] systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
[ OK ] Finished Monitoring of LVM… dmeventd or progress polling.
[ 32.657438][ T1] systemd[1]: modprobe@configfs.service: Succeeded.
[ 32.685676][ T1] systemd[1]: Finished Load Kernel Module configfs.
[ OK ] Finished Load Kernel Module configfs.
[ 32.717750][ T1] systemd[1]: modprobe@drm.service: Succeeded.
[ 32.745652][ T1] systemd[1]: Finished Load Kernel Module drm.
[ OK ] Finished Load Kernel Module drm.
[ 32.787896][ T1] systemd[1]: modprobe@fuse.service: Succeeded.
[ 32.805839][ T1] systemd[1]: Finished Load Kernel Module fuse.
[ OK ] Finished Load Kernel Module fuse.
[ 32.827690][ T1] systemd[1]: Finished Load Kernel Modules.
[ OK ] Finished Load Kernel Modules.
[ 32.867517][ T1] systemd[1]: Finished Remount Root and Kernel File Systems.
[ OK ] Finished Remount Root and Kernel File Systems.
[ 32.955597][ T1] systemd[1]: Mounting FUSE Control File System...
Mounting FUSE Control File System...
[ 33.045191][ T1] systemd[1]: Mounting Kernel Configuration File System...
Mounting Kernel Configuration File System...
[ 33.101222][ T1] systemd[1]: Starting pNFS block layout mapping daemon...
Starting pNFS block layout mapping daemon...
[ 33.161671][ T1] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[ 33.185571][ T1] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[ 33.210057][ T1] systemd[1]: Starting Load/Save Random Seed...
Starting Load/Save Random Seed...
[ 33.270097][ T1] systemd[1]: Starting Apply Kernel Variables...
Starting Apply Kernel Variables...
[ 33.340454][ T1] systemd[1]: Starting Create System Users...
Starting Create System Users...
[ 33.423178][ T1] systemd[1]: Started Journal Service.
[ OK ] Started Journal Service.
[ OK ] Mounted FUSE Control File System.
[ OK ] Mounted Kernel Configuration File System.
[ OK ] Started pNFS block layout mapping daemon.
[ OK ] Finished Load/Save Random Seed.
[ OK ] Finished Apply Kernel Variables.
Starting Flush Journal to Persistent Storage...
[ OK ] Finished Create System Users.
Starting Create Static Device Nodes in /dev...
[ 33.856364][ T237] systemd-journald[237]: Received client request to flush runtime journal.
[ OK ] Finished Coldplug All udev Devices.
Starting Helper to synchronize boot up for ifupdown...
[ OK ] Finished Helper to synchronize boot up for ifupdown.
[ OK ] Finished Create Static Device Nodes in /dev.
[ OK ] Reached target Local File Systems (Pre).
Mounting /tmp...
Starting Rule-based Manage…for Device Events and Files...
[ OK ] Mounted /tmp.
[ OK ] Reached target Local File Systems.
Starting Raise network interfaces...
Starting Preprocess NFS configuration...
Starting Cleanup monit state file...
Starting Cleanup PHP session files...
[ OK ] Finished Preprocess NFS configuration.
[ OK ] Reached target NFS client services.
[ OK ] Finished Cleanup monit state file.
[ OK ] Finished Cleanup PHP session files.
[ OK ] Started Rule-based Manager for Device Events and Files.
Starting Network Service...
[ OK ] Started Network Service.
Starting Wait for Network to be Configured...
[ OK ] Finished Raise network interfaces.
[ OK ] Found device /dev/ttyS0.
[ 37.077583][ T288] orion_wdt: Initial timeout 21 sec
[ 37.091816][ T278] adt7475 0-002e: ADT7473 device, revision 0
[ 37.136176][ T278] adt7475 0-002e: Optional features: fan4 pwm2
[ 37.708560][ T324] marvell-cesa f1030000.crypto: CESA device successfully registered
[ OK ] Finished Flush Journal to Persistent Storage.
Starting Create Volatile Files and Directories...
[ 37.825880][ T278] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 38.005183][ T278] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 38.105147][ T278] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ OK 38.169075][ T278] sd 3:0:0:0: Attached scsi generic sg3 type 0
0m] Finished Create Volatile Files and Directories.
Starting RPC b[ 38.232433][ T278] sd 4:0:0:0: Attached scsi generic sg4 type 0
ind portmap service...
Starting Network Name Resolution...
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started RPC bind portmap service.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
[ OK ] Reached target RPC Port Mapper.
[ OK ] Finished Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Avahi mDNS/DNS-SD Stack...
Starting LSB: Starts syslogd...
[ OK ] Started Regular background program processing daemon.
[ OK ] Started D-Bus System Message Bus.
Starting Remove Stale Onli…t4 Metadata Check Snapshots...
Starting LSB: Load kernel …d to enable cpufreq scaling...
Starting LSB: service and resource monitoring daemon...
Starting System Logging Service...
Starting User Login Management...
Starting WPA supplicant...
[ 39.763461][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 39.774238][ T17] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ OK ] Started LSB: Starts syslogd.
[ OK ] Started System Logging Service.
[ OK ] Finished Wait for Network to be Configured.
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Started WPA supplicant.
Starting LSB: Starts klogd...
[ OK ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.
[ OK ] Started LSB: Starts klogd.
[ OK ] Started LSB: service and resource monitoring daemon.
[ OK ] Started User Login Management.
[ OK ] Started Network Name Resolution.
[ OK ] Reached target Network.
[ OK ] Reached target Network is Online.
[ OK ] Reached target Host and Network Name Lookups.
Starting chrony, an NTP client/server...
Starting A high performanc… and a reverse proxy server...
Starting The OpenMediaVaul…t processes the RPC request...
Starting Generate the prelogin message...
Starting The PHP 7.4 FastCGI Process Manager...
Starting /etc/rc.local Compatibility...
Starting OpenBSD Secure Shell server...
Starting Permit User Sessions...
[ OK ] Started LSB: Load kernel m…ded to enable cpufreq scaling.
Starting LSB: set CPUFreq kernel parameters...
[ OK ] Finished Permit User Sessions.
[ OK ] Started LSB: set CPUFreq kernel parameters.
[ OK ] Started OpenBSD Secure Shell server.
[ OK ] Started The OpenMediaVault…hat processes the RPC request.
[FAILED] Failed to start chrony, an NTP client/server.
See 'systemctl status chrony.service' for details.
[ OK ] Started A high performance…er and a reverse proxy server.
[ OK ] Started The PHP 7.4 FastCGI Process Manager.
[ OK ] Reached target System Time Synchronized.
[ OK ] Started Trigger anacron every hour.
[ OK ] Started Daily apt download activities.
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Started Periodic ext4 Onli…ata Check for All Filesystems.
[ OK ] Started Daily rotation of log files.
[ OK ] Started Daily man-db regeneration.
[ OK ] Started Clean PHP session files every 30 mins.
[ OK ] Reached target Timers.
[ OK ] Started Run anacron jobs.
Starting LSB: start or stop rrdcached...
Starting Clean php session files...
[ 49.056735] rc.local[495]: Starting ssh (via systemctl): ssh.service.
Starting Rotate log files...
Starting Daily man-db regeneration...
[ OK ] Started /etc/rc.local Compatibility.
[ OK ] Started Getty on tty1.
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Started LSB: start or stop rrdcached.
Starting Statistics collection and monitoring daemon...
[ OK ] Started Statistics collection and monitoring daemon.
Starting Online ext4 Metad…a Check for All Filesystems...
[ OK ] Finished Online ext4 Metadata Check for All Filesystems.
[ OK ] Finished Clean php session files.
[ OK ] Finished Daily man-db regeneration.
openmediavault 6.0.37-1 (Shaitan) debian ttyS0
Copyright (C) 2009-2022 by Volker Theile. All rights reserved.
To manage the system visit the openmediavault web control panel:
eth0: 192.168.42.150
By default the web control panel administrator account has the
username 'admin' and password 'openmediavault'.
It is recommended that you change the password for this account
within the web control panel or using the 'omv-firstaid' CLI
command.
For more information regarding this appliance, please visit the
web site: https://www.openmediavault.org
debian login: [ 69.347091][ T157] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 74.404917][ T157] ata4.00: qc timeout (cmd 0xec)
[ 74.409895][ T157] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 74.419578][ T157] ata4.00: revalidation failed (errno=-5)
[ 74.757089][ T157] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 84.964904][ T157] ata4.00: qc timeout (cmd 0xec)
[ 84.969786][ T157] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 84.979441][ T157] ata4.00: revalidation failed (errno=-5)
[ 84.986657][ T157] ata4: limiting SATA link speed to 1.5 Gbps
[ 85.316885][ T157] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 85.329680][ T157] ata4.00: configured for UDMA/133
debian login: root
Password:
Linux debian 5.18.6-kirkwood-tld-1 #1.0 PREEMPT Fri Jun 24 15:26:02 PDT 2022 armv5tel
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Aug 24 17:39:55 PDT 2022 on ttyS0
debian
192.168.42.15
Iomega ix4-200d
Linux version 5.18.6-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1.0 PREEMPT Fri Jun 24 15:26:02 PDT 2022
Debian 11.0
Sun Aug 28 17:36:28 PDT 2022 up 1 minute
root@debian:~# parted
GNU Parted 3.4
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
Model: ATA ST6000NM021A-2R7 (scsi)
Disk /dev/sda: 6001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 6001GB 6001GB ext4 primary
Model: ATA ST6000NM021A-2R7 (scsi)
Disk /dev/sdb: 6001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 6001GB 6001GB ext4 primary
Model: SanDisk Cruzer Orbit (scsi)
Disk /dev/sdc: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 32.0GB 32.0GB primary ext2
Model: ATA ST6000NM021A-2R7 (scsi)
Disk /dev/sdd: 6001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 6001GB 6001GB primary
[ 108.088904][ T255] sdd: sdd1
Model: ATA ST6000NM021A-2R7 (scsi)
Disk /dev/sde: 6001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 6001GB 6001GB ext4 primary
(parted) [ 108.245253][ T255] sde: sde1
(parted) [ 140.387154][ T155] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
quit
root@debian:~# [ 142.857271][ T255] sda: sda1
[ 145.444960][ T155] ata3.00: qc timeout (cmd 0xec)
[ 145.450063][ T155] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 145.460040][ T155] ata3.00: revalidation failed (errno=-5)
[ 145.797237][ T155] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
root@debian:~# [ 156.004919][ T155] ata3.00: qc timeout (cmd 0xec)
[ 156.009966][ T155] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 156.018672][ T155] ata3.00: revalidation failed (errno=-5)
[ 156.024376][ T155] ata3: limiting SATA link speed to 1.5 Gbps
[ 156.357315][ T155] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 156.369740][ T155] ata3.00: configured for UDMA/133
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 08:05PM |
Admin Registered: 13 years ago Posts: 18,543 |
Cool!
So looks like 2 HDDs are detected in u-boot, and all 4 HDDS are detected in the kernel (which is more important than what u-boot sees).
Am I correct? hard to see because they are identical :)
/dev/sdc1 is the USB rootfs.
Please mount the HDDs, if they already have partition.
Check capacity
=====
I'll will be slow producing the coming test versions (out of free time). So I can squueze in a hour now and then, I will upload new version.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/28/2022 08:08PM by bodhi.
So looks like 2 HDDs are detected in u-boot, and all 4 HDDS are detected in the kernel (which is more important than what u-boot sees).
[ 6.024856][ T48] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300) [ 6.034247][ T48] ata1.00: ATA-11: ST6000NM021A-2R7101, SN03, max UDMA/133 [ 6.041372][ T48] ata1.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 6.056558][ T48] ata1.00: configured for UDMA/133 [ 6.072105][ T8] scsi 0:0:0:0: Direct-Access ATA ST6000NM021A-2R7 SN03 PQ: 0 ANSI: 5 [ 6.082487][ T33] sd 0:0:0:0: [sda] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) [ 6.091699][ T33] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 6.097852][ T33] sd 0:0:0:0: [sda] Write Protect is off [ 6.103523][ T33] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 6.163086][ T33] sda: sda1 [ 6.167710][ T33] sd 0:0:0:0: [sda] Attached SCSI disk [ 6.594859][ T50] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300) [ 6.604228][ T50] ata2.00: ATA-11: ST6000NM021A-2R7101, SN03, max UDMA/133 [ 6.611356][ T50] ata2.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 6.628621][ T50] ata2.00: configured for UDMA/133 [ 6.644170][ T30] scsi 1:0:0:0: Direct-Access ATA ST6000NM021A-2R7 SN03 PQ: 0 ANSI: 5 [ 6.654551][ T33] sd 1:0:0:0: [sdb] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) [ 6.663523][ T33] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 6.669670][ T33] sd 1:0:0:0: [sdb] Write Protect is off [ 6.675413][ T33] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 13.916331][ T146] ata3: SATA max UDMA/133 abar m1024@0xe0000000 port 0xe0000100 irq 38 [ 13.924512][ T146] ata4: SATA max UDMA/133 abar m1024@0xe0000000 port 0xe0000180 irq 38 [ 14.023230][ T146] ata5: DUMMY [ 14.376779][ T155] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 14.385541][ T155] ata3.00: ATA-11: ST6000NM021A-2R7101, SN03, max UDMA/133 [ 14.392717][ T155] ata3.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 14.403215][ T155] ata3.00: configured for UDMA/133 [ 14.418806][ T30] scsi 3:0:0:0: Direct-Access ATA ST6000NM021A-2R7 SN03 PQ: 0 ANSI: 5 [ 14.431163][ T163] sd 3:0:0:0: [sdd] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) [ 14.441532][ T163] sd 3:0:0:0: [sdd] 4096-byte physical blocks [ 14.447735][ T163] sd 3:0:0:0: [sdd] Write Protect is off [ 14.453497][ T163] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 14.757466][ T163] sdd: sdd1 [ 14.763752][ T163] sd 3:0:0:0: [sdd] Attached SCSI disk [ 14.779429][ T157] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 14.788331][ T157] ata4.00: ATA-11: ST6000NM021A-2R7101, SN03, max UDMA/133 [ 14.795526][ T157] ata4.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 14.806212][ T157] ata4.00: configured for UDMA/133 [ 14.821964][ T33] scsi 4:0:0:0: Direct-Access ATA ST6000NM021A-2R7 SN03 PQ: 0 ANSI: 5 [ 14.840770][ T163] sd 4:0:0:0: [sde] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB) [ 14.857482][ T163] sd 4:0:0:0: [sde] 4096-byte physical blocks [ 14.869363][ T163] sd 4:0:0:0: [sde] Write Protect is off [ 14.882034][ T163] sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Am I correct? hard to see because they are identical :)
/dev/sdc1 is the USB rootfs.
Please mount the HDDs, if they already have partition.
mkdir -p /media/sda1 mkdir -p /media/sdb1 mkdir -p /media/sdd1 mkdir -p /media/sde1
mount -o noatime /dev/sda1 /media/sda1 mount -o noatime /dev/sdb1 /media/sdb1 mount -o noatime /dev/sdd1 /media/sdd1 mount -o noatime /dev/sde1 /media/sde1 mount
Check capacity
lsblk df -h
=====
I'll will be slow producing the coming test versions (out of free time). So I can squueze in a hour now and then, I will upload new version.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/28/2022 08:08PM by bodhi.
|
Re: Iomega ix4-200d U-boot needed August 28, 2022 08:13PM |
Admin Registered: 13 years ago Posts: 18,543 |
Sorry I did not read your post carefully. parted saw them, then we're OK.
Perhaps it's time to make the SATA 0 or 1 disk a rootfs and boot with it.
I will come back and post u-boot envs to boot HDD rootfs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/28/2022 08:17PM by bodhi.
Perhaps it's time to make the SATA 0 or 1 disk a rootfs and boot with it.
I will come back and post u-boot envs to boot HDD rootfs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/28/2022 08:17PM by bodhi.
|
Re: Iomega ix4-200d U-boot needed August 29, 2022 05:23PM |
Admin Registered: 13 years ago Posts: 18,543 |
CodeJACK,
After you've created the new rootfs on one of the 2 HDDs. Unplug the USB rootfs, kwboot with tld-0.2 version and then,
And then
Note: There is no need to save the envs each time you run the test. Only when you are done and sure that they work, then save them.
=======
The controller inside these HDDs are quite slow in response. Sleep is just a work around.
It seems "sata init" does need some improvement. When you see "failed to identify", that means the HDDs were power up, but the HDD controller failed to respond properly to command sending to it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
After you've created the new rootfs on one of the 2 HDDs. Unplug the USB rootfs, kwboot with tld-0.2 version and then,
setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts' setenv load_uimage_sata 'ext2load usb 0:1 0x800000 /boot/uImage' setenv load_uinitrd_sata 'ext2load usb 0:1 0x1100000 /boot/uInitrd' setenv load_dtb_sata 'ext2load usb 0:1 0x2c00000 /boot/dts/kirkwood-iomega_ix4_200d.dtb' setenv sata_config 'mw.l 0xF1010100 0x1000d080; mw.l 0xf1010140 0x0001000c; sleep 1; sata init; sleep 1; sata init; sata info' setenv sata_boot 'run set_bootargs; run load_uimage_sata; run load_uinitrd_sata; run load_dtb_sata; bootm 0x800000 0x1100000 0x2c00000'
And then
run sata_configIf sata_config showed the 2 HDDs partition OK, proceed to boot. If not, run sata_config again.
run sata_boot
Note: There is no need to save the envs each time you run the test. Only when you are done and sure that they work, then save them.
=======
The controller inside these HDDs are quite slow in response. Sleep is just a work around.
It seems "sata init" does need some improvement. When you see "failed to identify", that means the HDDs were power up, but the HDD controller failed to respond properly to command sending to it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Iomega ix4-200d U-boot needed September 01, 2022 03:22PM |
Registered: 1 year ago Posts: 52 |
|
Re: Iomega ix4-200d U-boot needed September 01, 2022 05:39PM |
Admin Registered: 13 years ago Posts: 18,543 |
CodeJACK,
> I understand what you say about the disk slow to
> respond but it does not do that with the current
> stock u-boot. Disk are detected quickly and start
> up fast.
True, stock u-boot is a customized version so they always patch any shortcoming and implement some work-around in the code. And usually in way that is not acceptable to mainline. I can do the same too. However, that's more investigation and take time (because I don't have the HW).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I understand what you say about the disk slow to
> respond but it does not do that with the current
> stock u-boot. Disk are detected quickly and start
> up fast.
True, stock u-boot is a customized version so they always patch any shortcoming and implement some work-around in the code. And usually in way that is not acceptable to mainline. I can do the same too. However, that's more investigation and take time (because I don't have the HW).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Iomega ix4-200d U-boot needed September 01, 2022 05:51PM |
Registered: 1 year ago Posts: 52 |
Yeah, that sounds about right. Better to stay mainline :-)
Im still doing the rootfs on disk but took some time to see what disk slot gets assigned to each controller at boot and in what order on each controller. It might not make any difference but Lenovo imaging process states that the bottom most disk must be the only one inserted. I thought that would be SATA controller and disk 0. Nope, that's actually the "SCSI" controller that loads after SATA and the bottom most slot is disk 0 on that controller.
I also noted that with just the bottom disks, at initial boot they are not reported as connected by u-boot. Once I reset and start the boot process over, they do appear.
Im still doing the rootfs on disk but took some time to see what disk slot gets assigned to each controller at boot and in what order on each controller. It might not make any difference but Lenovo imaging process states that the bottom most disk must be the only one inserted. I thought that would be SATA controller and disk 0. Nope, that's actually the "SCSI" controller that loads after SATA and the bottom most slot is disk 0 on that controller.
I also noted that with just the bottom disks, at initial boot they are not reported as connected by u-boot. Once I reset and start the boot process over, they do appear.
|
Re: Iomega ix4-200d U-boot needed September 01, 2022 06:07PM |
Admin Registered: 13 years ago Posts: 18,543 |
CodeJACK,
> Im still doing the rootfs on disk but took some
> time to see what disk slot gets assigned to each
> controller at boot and in what order on each
> controller. It might not make any difference but
> Lenovo imaging process states that the bottom most
> disk must be the only one inserted. I thought that
> would be SATA controller and disk 0. Nope, that's
> actually the "SCSI" controller that loads after
> SATA and the bottom most slot is disk 0 on that
> controller.
After you see 2 HDDs, do this:
It will show the content of the /boot folder for the rootfs. That's when you know which slot the HDD rootfs should be in.
> I also noted that with just the bottom disks, at
> initial boot they are not reported as connected by
> u-boot. Once I reset and start the boot process
> over, they do appear.
I think that was because the disks were powered up in Linux. And the reboot did not power it down.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Im still doing the rootfs on disk but took some
> time to see what disk slot gets assigned to each
> controller at boot and in what order on each
> controller. It might not make any difference but
> Lenovo imaging process states that the bottom most
> disk must be the only one inserted. I thought that
> would be SATA controller and disk 0. Nope, that's
> actually the "SCSI" controller that loads after
> SATA and the bottom most slot is disk 0 on that
> controller.
After you see 2 HDDs, do this:
ext2ls sata 0:1 /boot ext2ls sata 1:1 /boot
It will show the content of the /boot folder for the rootfs. That's when you know which slot the HDD rootfs should be in.
> I also noted that with just the bottom disks, at
> initial boot they are not reported as connected by
> u-boot. Once I reset and start the boot process
> over, they do appear.
I think that was because the disks were powered up in Linux. And the reboot did not power it down.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Iomega ix4-200d U-boot needed September 01, 2022 07:28PM |
Registered: 1 year ago Posts: 52 |
No joy using the SATA controller, swapping to the SCSI to see if any different
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... OK
In: serial
Out: serial
Err: serial
Net: eth0: ethernet-controller@72000, eth1: ethernet-controller@76000
Hit any key to stop autoboot: 0
=> setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts'
=> setenv load_uimage_sata 'ext2load usb 0:1 0x800000 /boot/uImage'
=> setenv load_uinitrd_sata 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
=> setenv load_dtb_sata 'ext2load usb 0:1 0x2c00000 /boot/dts/kirkwood-iomega_ix4_200d.dtb'
=> setenv sata_config 'mw.l 0xF1010100 0x1000d080; mw.l 0xf1010140 0x0001000c; sleep 1; sata init; sleep 1; sata init; sata info'
=> setenv sata_boot 'run set_bootargs; run load_uimage_sata; run load_uinitrd_sata; run load_dtb_sata; bootm 0x800000 0x1100000 0x2c00000'
=> run sata_config
Err: Failed to identify SATA device 0
Device 0: Model: Firm: Ser#:
Type: Hard Disk
Capacity: not available
Failed to wait for completion on port 1
ATA operation timed out
Failed to wait for completion on port 1
ATA operation timed out
Device 1: Model: Firm: Ser#:
Type: Hard Disk
Capacity: not available
=> run sata_boot
** Bad device specification usb 0 **
Couldn't find partition usb 0:1
Can't set block device
** Bad device specification usb 0 **
Couldn't find partition usb 0:1
Can't set block device
** Bad device specification usb 0 **
Couldn't find partition usb 0:1
Can't set block device
Wrong Image Format for bootm command
ERROR: can't get kernel image!
=>
|
Re: Iomega ix4-200d U-boot needed September 01, 2022 07:35PM |
Registered: 1 year ago Posts: 52 |
Interesting, nothing much attempted when disk in the lower, SCSI slots
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... OK In: serial Out: serial Err: serial Net: eth0: ethernet-controller@72000, eth1: ethernet-controller@76000 Hit any key to stop autoboot: 0 => setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts' => setenv load_uimage_sata 'ext2load usb 0:1 0x800000 /boot/uImage' => setenv load_uinitrd_sata 'ext2load usb 0:1 0x1100000 /boot/uInitrd' => setenv load_dtb_sata 'ext2load usb 0:1 0x2c00000 /boot/dts/kirkwood-iomega_ix4_200d.dtb' => setenv sata_config 'mw.l 0xF1010100 0x1000d080; mw.l 0xf1010140 0x0001000c; sleep 1; sata init; sleep 1; sata init; sata info' => setenv sata_boot 'run set_bootargs; run load_uimage_sata; run load_uinitrd_sata; run load_dtb_sata; bootm 0x800000 0x1100000 0x2c00000' => run sata_config => run sata_boot ** Bad device specification usb 0 ** Couldn't find partition usb 0:1 Can't set block device ** Bad device specification usb 0 ** Couldn't find partition usb 0:1 Can't set block device ** Bad device specification usb 0 ** Couldn't find partition usb 0:1 Can't set block device Wrong Image Format for bootm command ERROR: can't get kernel image! =>
|
Re: Iomega ix4-200d U-boot needed September 01, 2022 10:57PM |
Admin Registered: 13 years ago Posts: 18,543 |
In this post,
https://forum.doozan.com/read.php?3,25120,132923#msg-132923
When you see the Indentify error message, increase the sleep period
and run it again
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
https://forum.doozan.com/read.php?3,25120,132923#msg-132923
=> run sata_config
Err: Failed to identify SATA device 0
Device 0: Model: Firm: Ser#:
Type: Hard Disk
Capacity: not available
When you see the Indentify error message, increase the sleep period
Quote
=> setenv sata_config 'mw.l 0xF1010100 0x1000d080; mw.l 0xf1010140 0x0001000c; sleep 5; sata init; sata info'
and run it again
run sata_config
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Iomega ix4-200d U-boot needed September 07, 2022 06:16PM |
Registered: 1 year ago Posts: 52 |
Sorry bodhi, I've had a bust few days and not gotten back to this yet.
As for the sleep, it didnt seem to make any difference, Im not hearing the disk spin up the same way they do with stock u-boot.
I hope to get back to this over the weekend and ill get more detail then with outputs etc.
As for the sleep, it didnt seem to make any difference, Im not hearing the disk spin up the same way they do with stock u-boot.
I hope to get back to this over the weekend and ill get more detail then with outputs etc.
|
Re: Iomega ix4-200d U-boot needed September 23, 2022 02:04AM |
Registered: 1 year ago Posts: 7 |
|
Re: Iomega ix4-200d U-boot needed September 23, 2022 08:30AM |
Registered: 1 year ago Posts: 52 |
AmitMa Wrote:
-------------------------------------------------------
> I have the same model and I'm currently booting
> Debian from a USB stick.
> Could you guys point me to the right message/guide
> explaining how to boot from an HDD disk?
> After that, I would like to install OMV on the box
> so reference for that would be great also.
>
> Thanks!
Check the Wiki page Wiki
Scroll down to RAID and you have some options there to choose from.
once you copy the USB rootfs over to whatever disk partitions you like, you need to change the env variables in uboot to boot from it and not USB.
bohdi has listed ways to do that with me in this thread but some reading will be needed to decipher :-)
-------------------------------------------------------
> I have the same model and I'm currently booting
> Debian from a USB stick.
> Could you guys point me to the right message/guide
> explaining how to boot from an HDD disk?
> After that, I would like to install OMV on the box
> so reference for that would be great also.
>
> Thanks!
Check the Wiki page Wiki
Scroll down to RAID and you have some options there to choose from.
once you copy the USB rootfs over to whatever disk partitions you like, you need to change the env variables in uboot to boot from it and not USB.
bohdi has listed ways to do that with me in this thread but some reading will be needed to decipher :-)
|
Re: Iomega ix4-200d U-boot needed October 05, 2022 07:06PM |
Registered: 1 year ago Posts: 52 |
Hey bodhi. I've been looking at this the past few days but changing the delay does not make any difference to the disks being detected. Could EMC/Iomega have put in their own custom controller that u-boot would need their code to make it work??
I've tried googling to figure this out on my own but that's been a black hole of old sites where your name pops up a bit :-)
What do you think, have you any time to work with me on this more or will we call it dead and move on?
I've tried googling to figure this out on my own but that's been a black hole of old sites where your name pops up a bit :-)
What do you think, have you any time to work with me on this more or will we call it dead and move on?
|
Re: Iomega ix4-200d U-boot needed October 06, 2022 06:01PM |
Registered: 1 year ago Posts: 52 |
I've been googling too much for this box already but hey, Im cheap and got this thing for free so I'd like to try make it work :-)
I came across seagate-blackarmor-nas while reading up on ways to create my own u-boot and found their script that references their own diff and dtb files for the Seagate specific NAS devices. There was mention of the ix4-200d being similar so i decided to kwboot their u-boot-nas440.kwb file and it does somewhat start up. The dtb is not right and i think thats why I see the issues loading environment but it does allow me to view all disks attached. See below:
Would it be viable for me to adapt that script to focus only on the ix4-200d and rather than using their dtb, reference a local ix4 dtb and see what happens?
Is that the way to go for compiling u-boot myself bodhi? Wasting my time?
There is also a link on their GIT for the Lenovo Source Code and I can find a reference to board configs that match this board but really I don't know what I'm actually looking at. The same files do not exist in the denx u-boot tree but maybe they are cleared over time. I'll try asking via GIT for some help/advise too as maybe the known HDD issue with the 4 disk Seagate nas is the same on this ix4 too. Possibly help each other out lol
I came across seagate-blackarmor-nas while reading up on ways to create my own u-boot and found their script that references their own diff and dtb files for the Seagate specific NAS devices. There was mention of the ix4-200d being similar so i decided to kwboot their u-boot-nas440.kwb file and it does somewhat start up. The dtb is not right and i think thats why I see the issues loading environment but it does allow me to view all disks attached. See below:
97 % [......................................................................]
99 % [..................................]
[Type Ctrl-\ + c to quit]
U-Boot 2022.04 (Apr 11 2022 - 15:58:53 +0200)
NAS 440
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
Core: 13 devices, 9 uclasses, devicetree: separate
NAND: 32 MiB
Loading Environment from NAND... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net:
Error: ethernet-controller@72000 address not set.
Error: ethernet-controller@76000 address not set.
No ethernet found.
pcie0.0: Link up
nas440> sata info
Err: Failed to identify SATA device 0
Err: Failed to identify SATA device 1
Device 0: Model: Firm: Ser#:
Type: Hard Disk
Capacity: not available
Device 1: Model: Firm: Ser#:
Type: Hard Disk
Capacity: not available
nas440> sleep 10
nas440> sata info
Device 0: Model: Firm: Ser#:
Type: Hard Disk
Capacity: not available
Device 1: Model: Firm: Ser#:
Type: Hard Disk
Capacity: not available
nas440> sata part
Partition Map for SATA device 0 -- Partition Type: EFI
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 ***
Partition Map for SATA device 1 -- Partition Type: EFI
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 ***
nas440> scsi init
scsi - SCSI sub-system
Usage:
scsi reset - reset SCSI controller
scsi info - show available SCSI devices
scsi scan - (re-)scan SCSI bus
scsi device [dev] - show or set current device
scsi part [dev] - print partition table of one or all SCSI devices
scsi read addr blk# cnt - read `cnt' blocks starting at block `blk#'
to memory address `addr'
scsi write addr blk# cnt - write `cnt' blocks starting at block
`blk#' from memory address `addr'
nas440> scsi scan
scanning bus for devices...
Target spinup took 0 ms.
Target spinup took 0 ms.
SATA link 2 timeout.
AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x7 impl SATA mode
flags: 64bit ncq stag led pmp slum part
Device 0: (0:0) Vendor: ATA Prod.: ST6000NM021A-2R7 Rev: SN03
Type: Hard Disk
Capacity: 5723166.5 MB = 5589.0 GB (11721045168 x 512)
Device 1: (1:0) Vendor: ATA Prod.: ST6000NM021A-2R7 Rev: SN03
Type: Hard Disk
Capacity: 5723166.5 MB = 5589.0 GB (11721045168 x 512)
nas440> scsi info
Device 0: (0:0) Vendor: ATA Prod.: ST6000NM021A-2R7 Rev: SN03
Type: Hard Disk
Capacity: 5723166.5 MB = 5589.0 GB (11721045168 x 512)
Device 1: (1:0) Vendor: ATA Prod.: ST6000NM021A-2R7 Rev: SN03
Type: Hard Disk
Capacity: 5723166.5 MB = 5589.0 GB (11721045168 x 512)
nas440> sata init
nas440> sata info
Device 0: Model: ST6000NM021A-2R7101 Firm: SN03 Ser#:
Type: Hard Disk
Supports 48-bit addressing
Capacity: 5723166.5 MB = 5589.0 GB (11721045168 x 512)
Device 1: Model: ST6000NM021A-2R7101 Firm: SN03 Ser#:
Type: Hard Disk
Supports 48-bit addressing
Capacity: 5723166.5 MB = 5589.0 GB (11721045168 x 512)
nas440> Terminated
Would it be viable for me to adapt that script to focus only on the ix4-200d and rather than using their dtb, reference a local ix4 dtb and see what happens?
Is that the way to go for compiling u-boot myself bodhi? Wasting my time?
There is also a link on their GIT for the Lenovo Source Code and I can find a reference to board configs that match this board but really I don't know what I'm actually looking at. The same files do not exist in the denx u-boot tree but maybe they are cleared over time. I'll try asking via GIT for some help/advise too as maybe the known HDD issue with the 4 disk Seagate nas is the same on this ix4 too. Possibly help each other out lol
|
Re: Iomega ix4-200d U-boot needed October 07, 2022 12:35AM |
Registered: 1 year ago Posts: 8 |
Hi,
I'm also working on this box, check my github:
https://github.com/ggirou/ix4-200d/
https://github.com/ggirou/u-boot/tree/v2022.07-ix4-200d
I made a specific u-boot for ix4-200d, sata drive is detected but I didn't try to boot from it.
After that, Debian kernel doesn't detect all drives but Bodhi's one does very well. I'm trying to find why.
I'm also working on this box, check my github:
https://github.com/ggirou/ix4-200d/
https://github.com/ggirou/u-boot/tree/v2022.07-ix4-200d
I made a specific u-boot for ix4-200d, sata drive is detected but I didn't try to boot from it.
After that, Debian kernel doesn't detect all drives but Bodhi's one does very well. I'm trying to find why.
|
Re: Iomega ix4-200d U-boot needed October 07, 2022 12:45AM |
Admin Registered: 13 years ago Posts: 18,543 |
CodeJACK ,
> There was mention of the ix4-200d being
> similar so i decided to kwboot their
> u-boot-nas440.kwb
> file and it does somewhat start up.
> U-Boot 2022.04 (Apr 11 2022 - 15:58:53 +0200)
> NAS 440
Cool! that's promising, I will take a look at this u-boot. I am quite busy, but will have more free time in about 3 weeks. Please remind me if you don't see I post about this topic then.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> There was mention of the ix4-200d being
> similar so i decided to kwboot their
> u-boot-nas440.kwb
> file and it does somewhat start up.
> U-Boot 2022.04 (Apr 11 2022 - 15:58:53 +0200)
> NAS 440
Cool! that's promising, I will take a look at this u-boot. I am quite busy, but will have more free time in about 3 weeks. Please remind me if you don't see I post about this topic then.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Iomega ix4-200d U-boot needed October 07, 2022 12:56AM |
Admin Registered: 13 years ago Posts: 18,543 |
empgg3,
> I'm also working on this box, check my github:
> https://github.com/ggirou/ix4-200d/
> https://github.com/ggirou/u-boot/tree/v2022.07-ix4-200d
>
> I made a specific u-boot for ix4-200d, sata drive
> is detected but I didn't try to boot from it.
Thanks, I will also look at your build to see how those SATA drives were detected.
> After that, Debian kernel doesn't detect all
> drives but Bodhi's one does very well. I'm trying
> to find why.
Look for AHCI and PCI in the kernel config. The 2 internal SATA supported by the SoC are automatically detected by the kirkwood*.dtsi.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I'm also working on this box, check my github:
> https://github.com/ggirou/ix4-200d/
> https://github.com/ggirou/u-boot/tree/v2022.07-ix4-200d
>
> I made a specific u-boot for ix4-200d, sata drive
> is detected but I didn't try to boot from it.
Thanks, I will also look at your build to see how those SATA drives were detected.
> After that, Debian kernel doesn't detect all
> drives but Bodhi's one does very well. I'm trying
> to find why.
Look for AHCI and PCI in the kernel config. The 2 internal SATA supported by the SoC are automatically detected by the kirkwood*.dtsi.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Iomega ix4-200d U-boot needed October 07, 2022 08:53AM |
Registered: 1 year ago Posts: 52 |
