search

hn / seagate-blackarmor-nas

Technical data (reverse engineered) and an alternative firmware (Debian GNU/Linux) for the Seagate Blackarmor NAS
82 stars 21 forks source link

Test on Seagate 110 NAS - SUCCESS #6

Closed luctrev closed 5 years ago

luctrev commented 5 years ago

Hello

I have a problem here! I'm trying to install Debian 9 Stretch on a NAS110, but after successfully performed the Flashing Das U-Boot bootloader. When I try start the Debian installation I get the following error message:

nas220> fatload usb 0:1 0x40000 uImage-dtb Unable to read file uImage-dtb nas220> fatload usb 0:1 0x800000 uInitrd Unable to read file uInitrd

Could reading failure be caused by a problem with my USB stick (FAT formatted)? Does anyone have a guess?

Here the full terminal output:

U-Boot 2017.11 (Dec 18 2018 - 09:52:13 +0100) NAS 220

SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB WARNING: Caches not enabled NAND: 32 MiB In: serial Out: serial Err: serial Net: egiga0 88E1116 Initialized on egiga0 IDE: ide_preinit failed nas220> setenv bootargs console=ttyS0,115200 nas220> usb start starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found nas220> fatload usb 0:1 0x40000 uImage-dtb Unable to read file uImage-dtb nas220> fatload usb 0:1 0x800000 uInitrd Unable to read file uInitrd nas220>

PS:

cheers LST

hn commented 5 years ago

Looks like a problem with the USB stick or maybe the file is missing? Try fatls to list the directory contents

luctrev commented 5 years ago

Looks like a problem with the USB stick or maybe the file is missing? Try fatls to list the directory contents

Hi Hajo

Thanks for reply!

For some reason it was not possible to read the USB stick file system [a common mistake, I did not check if the file system was readable before opening the thread].

I wiped the partition table and reformatted the USB stick and everything worked perfectly. I'm going to do some configuration and testing, but the default installation of Debian has run smoothly!

YES, WORK ON BA110!

Soon I will test on BA440 too and I will report the result...

Cheers LST - from Brazil

PS: A question: In case I want to do a new installation, just wipe partition table from the hard drive?

hn commented 5 years ago

Congratulations :) And thank you for contributing back your findings! To re-install the system, just wipe the partition table and start the Debian installation again.

wellsouz commented 5 years ago

Looks like a problem with the USB stick or maybe the file is missing? Try fatls to list the directory contents

Hi Hajo

Thanks for reply!

For some reason it was not possible to read the USB stick file system [a common mistake, I did not check if the file system was readable before opening the thread].

I wiped the partition table and reformatted the USB stick and everything worked perfectly. I'm going to do some configuration and testing, but the default installation of Debian has run smoothly!

YES, WORK ON BA110!

Soon I will test on BA440 too and I will report the result...

Cheers LST - from Brazil

PS: A question: In case I want to do a new installation, just wipe partition table from the hard drive?

@luctrev , I have I Seagate 110 NAS too, but I'm getting CPU reset when loading the kernel/bootloader. How did you do to bootloader upgrade? Mine is as follow:

| | | | | ) __ | | | | | || \ / \ / | | | || || |) | () | () | | / |__/ _/ _/ | uboot_ver:v0.0.5

** MARVELL BOARD: MONO LE

U-Boot 1.1.4 (Nov 6 2009 - 11:15:26) Marvell version: 3.4.18

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CDE60

Soc: 88F6192 A1 (DDR2) CPU running @ 800Mhz L2 running @ 400Mhz SysClock = 200Mhz , TClock = 166Mhz

DRAM CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3 DRAM CS[0] base 0x00000000 size 128MB DRAM Total size 128MB 16bit width Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done NAND:32 MB

Marvell Serial ATA Adapter Integrated Sata device found

CPU : Marvell Feroceon (Rev 1) Scanning partition header: Found sign PrEr at c0000 Found sign KrNl at 2c0000 Found sign RoOt at 540000

Streaming disabled Write allocate disabled

USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME] Hit any key to stop autoboot: 0 Marvell>>

w6s8 commented 5 years ago

Hi @luctrev and @wellsouz do you know a right pinout for serial connector on BA110 board? Can you describe it please?

wellsouz commented 5 years ago

Hi @w6s8,

You can find more info here and here. You can use a CA42 cable or any other USB->TTL-Serial converter. In my case, I have modded my BA110 with a permanent serial port using this module.

Good luck!

w6s8 commented 5 years ago

Hello wellsouz, thank you very much for quick response! in the picture is not plain visible: is RX on top (beside GND) and TX at bottom (beside 3.3v)? like this:

__
| 
     GND      RX

     3.3v     TX

And a question again: is there any information as to whether >4 TB HD's are supported by BA110?

Thanks and Best regards

wellsouz commented 5 years ago

Hello @w6s8

I'm not sure (I did it a couple of years ago), but I think it's correct. I'm not at home to check it, but you can safely verify the correct pinout connecting just the GND, 3.3v, and T1IN line of the MAX3232 and booting up the BA110 (the boot process is very verbose). If nothing appears, try the other pin.

Regarding the >4 TB HD's, the main problem is the bootloader support, but I think it's OK with this new version @hn created. It upgrades the bootloader and stores the new kernel entirely in flash, so the hard disk is really required only by the kernel when is already running. The real HD limit is the Linux kernel, so >4 TB is totally fine.

I think a good approach to avoid any HD issues is to unplug it and use a fast USB flash drive (> 8GB) to upgrade the bootloader/firmware and to install the Debian OS on it. After the whole system is OK, you can reconnect the HD and use it just as a huge mounting point. This is the setup I'm using right now.

Best's.

w6s8 commented 5 years ago

Thanks @all! Upgrade was successful. Bevor I start, I found first the ground with a multimeter and then Rx by testing. AS USB->TTL-Serial converter I use just one, what I have for ESP01 programming. USB stick was fat formatted.

Pinout is exactly like on this picture

cdixon1 commented 3 years ago

Hey @luctrev, @w6s8 —sorry to bring this back from the dead but I'm also trying to Install Debian on my NAS110. You mentioned you were able to flash the Das U-Boot bootloader. I've been trying to do this myself but have not been able to stop the autoboot from running. No matter what keystrokes I press it does not stop. Any tips?

w6s8 commented 3 years ago

Hey cdixon1, can you please explain which instructions you are using and what step you are in? Terminal output are also helpful. maybe just swapped Rx and Tx?

cdixon1 commented 3 years ago

Hi @w6s8,

Sure. I am using the instructions here: https://github.com/hn/seagate-blackarmor-nas

As for what step I am in, I have gotten to the point in those instructions where it says to, "Use the serial terminal to stop the Seagate boot process and to show the ethernet MAC address:".

For some more context, I asked a very detailed question on stack overflow here that might help you understand what I'm trying to do: https://stackoverflow.com/questions/67169585/having-trouble-stopping-u-boot-autoboot

Thanks!

hn commented 3 years ago

Install Seagates original linux system to your HDDs. Then use fw_printenv and fw_setenv to read/write the bootdelay variable (0 = autoboot do not wait for keypress, N (N>0) autoboot wait N seconds, -1 no autoboot at all).

cdixon1 commented 3 years ago

Hi @hn,

Thanks for your response. I'm also having trouble getting the board to respond to any commands. Here is a link to what the boot process looks like: https://streamable.com/87zvxf. At the end I'm hitting keys on my keyboard but nothing seems to be happening.

Here is a complete copy of the serial terminal output:

Welcome to minicom 2.7.1

OPTIONS: 
Compiled on Nov 15 2020, 08:12:42.
Port /dev/tty.usbserial-AQ00KV6T, 17:22:08

Press Meta-Z for help on special keys

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__|  ** uboot_ver:v0.0.5 **

 ** MARVELL BOARD: MONO LE 

U-Boot 1.1.4 (Nov  6 2009 - 11:15:26) Marvell version: 3.4.18

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CDE60

Soc: 88F6192 A1 (DDR2)
CPU running @ 800Mhz L2 running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz 

DRAM CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3
DRAM CS[0] base 0x00000000   size 128MB 
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:32 MB

Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
  Device 0 @ 0 0:
Model: WDC WD1600BEVT-22ZCT0                    Firm: 11.01A11 Ser#:      WD-WXC908395046
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)

CPU : Marvell Feroceon (Rev 1)
Scanning partition header:
Found sign PrEr at c0000
Found sign KrNl at 2c0000
Found sign RoOt at 540000

Streaming disabled 
Write allocate disabled

USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0 

NAND read: device 0 offset 0xc4000, size 0x197200

Reading data from 0x25b000 -- 100% complete.
 1667584 bytes read: OK
Calculate CRC32:
crc32 checksum Pass

NAND read: device 0 offset 0x2c4000, size 0x21c000

Reading data from 0x4dfe00 -- 100% complete.
 2211840 bytes read: OK
Calculate CRC32:
crc32 checksum Pass
## Booting image at 00040000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-11-06   3:38:29 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2211388 Bytes =  2.1 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.......................................................................................................................................... done, booting the kernel.
Linux version 2.6.22.18 (root@jasonDev.localdomain) (gcc version 4.2.1) #1 Fri Nov 6 11:38:22 CST 2009 v0.0.7
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists.  Total pages: 32512
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x000a0000@0x0(uboot),0x00010000@0x000a0000(param),0x00200000@0x000c0000(preroot),0x00280000@0x002c0000(uimage),0x01a000000
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB 0MB 0MB 0MB = 128MB total
Memory: 109056KB available (4048K code, 289K data, 128K init)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 128MB 
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB 
PEX0_IO ....base f2000000, size   1MB 
INTER_REGS ....base f1000000, size   1MB 
NFLASH_CS ....base fa000000, size   2MB 
SPI_CS ....base f4000000, size  16MB 
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size   2MB 

  Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- MONO  Soc: 88F6192 A1 LE

 Detected Tclk 166666667 and SysClk 200000000 
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c05b4600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
Freeing initrd memory: 16384K
RTC registered
Use the XOR engines (acceleration) for enhancing the following functions:
  o RAID 5 Xor calculation
  o kernel memcpy
  o kenrel memzero
Number of XOR engines to use: 4
cesadev_init(c00116c4)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
MV Buttons Driver Load
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) ?Â?© 2001-2006 Red Hat, Inc.
fuse init (API version 7.8)
SGI XFS with large block numbers, no debug enabled
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
RAMDISK driver initialized: 2 RAM disks of 16384K size 1024 blocksize
loop: module loaded
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o Single RX Queue support - ETH_DEF_RXQ=0
  o Single TX Queue support - ETH_DEF_TXQ=0
  o TCP segmentation offload enabled
  o Receive checksum offload enabled
  o Transmit checksum offload enabled
  o Network Fast Processing (Routing) supported
  o Driver ERROR statistics enabled
  o Driver INFO statistics enabled
  o Proc tool API enabled
  o Rx descripors: q0=256
  o Tx descripors: q0=532
  o Loading network interface(s):
    o egiga0, ifindex = 1, GbE port = 0

Warning: Giga 1 is Powered Off

mvFpRuleDb (c73ab000): 1024 entries, 4096 bytes
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
Integrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
scsi 0:0:0:0: Direct-Access     WDC      WD1600BEVT-22ZCT 11.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
 sda: sda1 sda2 sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bit)
Scanning device for bad blocks
7 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 7 MTD partitions on "nand_mtd":
0x00000000-0x000a0000 : "uboot"
0x000a0000-0x000b0000 : "param"
0x000c0000-0x002c0000 : "preroot"
0x002c0000-0x00540000 : "uimage"
0x00540000-0x01f40000 : "rootfs"
0x01f40000-0x02000000 : "misc"
0x00000000-0x02000000 : "flash"
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usb 1-1: new high speed USB device using ehci_marvell and address 2
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
attach_adapter....
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
raid6: int32x1     73 MB/s
raid6: int32x2     80 MB/s
raid6: int32x4     83 MB/s
raid6: int32x8     74 MB/s
raid6: using algorithm int32x4 (83 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
   arm4regs  :   722.800 MB/sec
   8regs     :   503.200 MB/sec
   32regs    :   600.000 MB/sec
raid5: using function: arm4regs (722.800 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
wix gpio_init
Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC).
ALSA device list:
  No soundcards found.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sda4 ...
md:  adding sda4 ...
md: sda3 has different UUID to sda4
md: sda2 has different UUID to sda4
md: sda1 has different UUID to sda4
md: created md3
md: bind<sda4>
md: running: <sda4>
raid1: raid set md3 active with 1 out of 2 mirrors
md: considering sda3 ...
md:  adding sda3 ...
md: sda2 has different UUID to sda3
md: sda1 has different UUID to sda3
md: created md2
md: bind<sda3>
md: running: <sda3>
raid1: raid set md2 active with 1 out of 2 mirrors
md: considering sda2 ...
md:  adding sda2 ...
md: sda1 has different UUID to sda2
md: created md1
md: bind<sda2>
md: running: <sda2>
raid1: raid set md1 active with 1 out of 2 mirrors
md: considering sda1 ...
md:  adding sda1 ...
md: created md0
md: bind<sda1>
md: running: <sda1>
raid1: raid set md0 active with 1 out of 2 mirrors
md: ... autorun DONE.
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 1628KiB [1 disk] into ram disk... done.
VFS: Mounted root (cramfs filesystem) readonly.
Freeing init memory: 128K
Enter Pre-Root FileSystem:
FW_UPDATE_FLAG_RES:1
BOARDTEST_FALG:0
1       100MB   1169MB  1069MB  ext3                               raid
2       1169MB  2239MB  1070MB  linux-swap                         raid
3       2239MB  2773MB  534MB   ext3                               raid
4       2773MB  160GB   157GB   ext3                               raid
DSK1_RES:0
DSK2_RES:1
DSK3_RES:1
DSK4_RES:1
DSK1_S_RES:1
DSK2_S_RES:0
DSK3_S_RES:0
DSK4_S_RES:0
CHK_RES:1
MD0CHK_RES:0
CHK_RES:1
/dev/md0: recovering journal
/dev/md0: clean, 4051/130560 files, 29495/260960 blocks
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1044792k swap on /dev/md1.  Priority:-1 extents:1 across:1044792k
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md2, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.

==> Updating disk information ............................. [ OK ]
==> Disabling HDD standby for /dev/sda .................... [ OK ]
==> Disabling HDD standby for /dev/sdb .................... [ OK ]
==> Disabling HDD standby for /dev/sdc .................... [ OK ]
==> Disabling HDD standby for /dev/sdd .................... [ OK ]
==> Disabling HDD standby for /dev/sde .................... [ OK ]
==> Disabling HDD standby for /dev/sdf .................... [ OK ]
==> Disabling HDD standby for /dev/sdg .................... [ OK ]
==> Disabling HDD standby for /dev/sdh .................... [ OK ]
==> Inserting NTFS (ufsd) module ....................... ufsd: module license 'Commercial product' taints kernel.
ufsd: driver loaded at bf000000 built on Jun  5 2009 15:42:37
UFSD version 7.04 (Jun  5 2009, 15:37:57)
NTFS read/write support included
$Id: ufsdvfs.c,v 1.207.4.1 2009/05/14 14:37:07 shura Exp $ (LBD=ON)
[ OK ]
==> Removing all usb storage setting ...................... [ OK ]

==> Mounting /dev/md3 to /DataVolume ... 
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md3, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.

==> Starting quota check .................................. [ OK ]
==> Mounting all shares with bind property ................ [ OK ]
==> Updating the file "raclient_volume" ................... [ OK ]
==> Starting portmap ...................................... [ OK ] 
==> Inserting bonding module .............................. [ NO ]
==> Starting network ...................................... 
udhcpc[696]: udhcpc (v0.9.9-pre) started
egiga0: started
udhcpc[696]: Sending discover...
udhcpc[696]: Sending discover...
udhcpc[696]: Sending discover...
udhcpc[696]: Sending discover...
udhcpc[696]: Sending discover...
udhcpc[696]: No lease, failing.
udhcpc[709]: udhcpc (v0.9.9-pre) started
udhcpc[709]: SIOCGIFINDEX failed!: No such device
egiga0    Link encap:Ethernet  HWaddr 00:10:75:23:03:84  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:532 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:11 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

SIOCSIFADDR: No such device
==> Starting mini_httpd ................................... [ OK ]
==> Starting inetd ........................................ [ OK ]
==> Printer's spooler is GOOD ............................. 
==> Starting cupsd ........................................ [ OK ]
==> Starting NTP client ................................... [ OK ]
==> Starting recyclebind .................................. [ OK ]
==> Starting smbd ......................................... [ OK ]
==> Starting nmbd ......................................... [ OK ]
==> Starting alias recheck............................. ==> Starting backup scheduled.............................. [ OK ]
==> Starting backup getIPd................................. [ OK ]
==> Starting logrotate .................................... [ OK ]
==> Starting network interface plugging daemon ............ [ OK ]
==> Initializing LCD H/W .................................. [ OK ]
==> Showing "System Ready" in LCD ......................... [ OK ]
==> Starting LCD button monitor ........................... [ OK ]
==> Starting udevd ........................................ [ OK ]
==> Starting udevadm trigger .............................. 
Doing MONO udev initial 
sda should be harddisk
Checking USB printer
ifplugd_action completed
==> Starting aronis license server ........................ 
==> Starting crond ........................................ 
Start SharesManaged.
crond[1011]: crond 2.3.2 dillon, started, log level 0

==> Deleting /etc/restore folder ........................[ OK ]
==> Starting WiAutoConfig ................................. [ OK ]
==> Starting dragsortd .................................... [ OK ]
==> Starting lltd ......................................... lld2d[1058]: osl_write_pidfile: /var/run/lld2d-egiga0.pid contains pid 1058 which is still running; aborting

[ OK ]
==> Starting mDNSResponder ................................ [ OK ]
==> Set readahead 2048 for /dev/md3 ....................... [ OK ]
==> Set readahead 2048 for /dev/md4 ....................... [ OK ]
==> Set readahead 2048 for /dev/md5 ....................... [ OK ]
==> Set readahead 2048 for /dev/md6 ....................... [ OK ]
==> Set readahead 2048 for /dev/mapper/encmd3 ............. [FAIL]
==> Set readahead 2048 for /dev/mapper/encmd4 ............. [FAIL]
==> Set readahead 2048 for /dev/mapper/encmd5 ............. [FAIL]
==> Set readahead 2048 for /dev/mapper/encmd6 ............. [FAIL]
==> Starting syslogd ...................................... [ OK ]
==> Setting trustees ...................................... [ OK ]
==> Syncing time from system clock to H/W clock ........... [ OK ]
==> Deleting the critical event(s) ........................ [ OK ]
==> Cleaning flag for Downloader .......................... [ OK ]
==> Starting Downloader monitor ........................... [ OK ]
==> Setting UPnP for both of HTTP(S) and FTP ports ........ [ OK ]
==> Checking preferred language in system_var ............. [ en ]
==> Starting alarmd ....................................... [ OK ]
==> Starting hwmonitord ................................... [ OK ]
==> Disabling wiki Server ................................. [ OK ]
==> Starting IP monitor for DDNS .......................... [ OK ]
==> Mounting encrypted volume(s) in background ............ [ OK ]

==> Generating Factory Default Restore page ............... 
>> FDR already existed. (VlFSRFhHS2xUVl5VRVxFb0VQQUdfQV0=)

==> Set parmaters for lan ports ........................... 
GbE port 0: TxEnable WA - Enabled, deep=1, tx_en_bk=1

==> Starting I/O Monitor for HDD standby .................. 
==> Forcedly set passwd for username "licenser" ......... 
==> Checking whether system get abnormal shutdown ......... [ AB ]
==> Socket connection for raclientd ....................... 
==> Stopping nas_conf_db.xml tracker ...................... iomonitor[1305]: terminate iomonitor becasue HDD standby was disabled
[FAIL]
==> Stopping raclient ..................................... [FAIL]
==> Starting raclientd .................................... [ OK ]
==> Starting config.xml tracker ........................... [ OK ]
==> Starting backup server service ........................ 

insmod: usblp.ko: 
BA-230384 login:
cdixon1 commented 3 years ago

Another update—I had purchased the shell of a BlackArmor NAS 220 and was able to stop the autoboot which is great. However now I'm having an issue where when I issue the fatload usb 0:1 0x800000 u-boot.kwb command the interface just hangs after printing reading u-boot.kwb. I've tried two different usb drives and both give me the same problem. How long is the reading u-boot.kwb supposed to take?

wellsouz commented 3 years ago

Another update—I had purchased the shell of a BlackArmor NAS 220 and was able to stop the autoboot which is great. However now I'm having an issue where when I issue the fatload usb 0:1 0x800000 u-boot.kwb command the interface just hangs after printing reading u-boot.kwb. I've tried two different usb drives and both give me the same problem. How long is the reading u-boot.kwb supposed to take?

@cdixon1, try using extload instead of fatload. The usb drive needs to be formatted in ext2. You will probably need to upgrade the bootloader. Please, check this: https://github.com/hn/seagate-blackarmor-nas/issues/7#issue-486502338

cdixon1 commented 3 years ago

Another update—I had purchased the shell of a BlackArmor NAS 220 and was able to stop the autoboot which is great. However now I'm having an issue where when I issue the fatload usb 0:1 0x800000 u-boot.kwb command the interface just hangs after printing reading u-boot.kwb. I've tried two different usb drives and both give me the same problem. How long is the reading u-boot.kwb supposed to take?

@cdixon1, try using extload instead of fatload. The usb drive needs to be formatted in ext2. You will probably need to upgrade the bootloader. Please, check this: #7 (comment)

Thanks! Following the instructions in that thread worked! I just now have to find out the issue with my NAS110. After my experience working with the NAS220 it seems that maybe the RX pin on the board isn't working. Is there any way around that?

To be clear my issue with that device is that none of my keyboard commands seem to be received by the device. If I hit keys nothing happens while connected via TTL serial.

wellsouz commented 3 years ago

Another update—I had purchased the shell of a BlackArmor NAS 220 and was able to stop the autoboot which is great. However now I'm having an issue where when I issue the fatload usb 0:1 0x800000 u-boot.kwb command the interface just hangs after printing reading u-boot.kwb. I've tried two different usb drives and both give me the same problem. How long is the reading u-boot.kwb supposed to take?

@cdixon1, try using extload instead of fatload. The usb drive needs to be formatted in ext2. You will probably need to upgrade the bootloader. Please, check this: #7 (comment)

Thanks! Following the instructions in that thread worked! I just now have to find out the issue with my NAS110. After my experience working with the NAS220 it seems that maybe the RX pin on the board isn't working. Is there any way around that?

To be clear my issue with that device is that none of my keyboard commands seem to be received by the device. If I hit keys nothing happens while connected via TTL serial.

After a complete boot, are you able to enter letters at the prompt BA-230384 login: ?

You can use a multimeter to confirm that you are using the correct pin and the soldering is in good shape. Also, you can follow the RX and TX tracks and test continuity with your TTL-serial converter.

cdixon1 commented 3 years ago

After a complete boot, are you able to enter letters at the prompt BA-230384 login: ?

No, when I get to a prompt nothing shows up when I type.

You can use a multimeter to confirm that you are using the correct pin and the soldering is in good shape.

With the board powered on and using my multimeter:

The values are the same if I use a screw on the board instead of the ground pin for measuring the voltage at the RX and TX pins. This seems to suggest that all the connections are good?

Also, you can follow the RX and TX tracks and test continuity with your TTL-serial converter.

Sorry for my lack of knowledge, but how would I do this?

Edit: After doing some testing with the multimeter there is continuity between the +3.3V and RX pins. I assume this is bad?

wellsouz commented 3 years ago

With the board powered on and using my multimeter:

* RX to Ground = 3.27V

* TX to Ground = 3.27V

The values are the same if I use a screw on the board instead of the ground pin for measuring the voltage at the RX and TX pins. This seems to suggest that all the connections are good?

Maybe you have done a short-circuit between the pins during the soldering process. Try using the the multimeter at the continuity scale (the one that beeps when you put the black and red probes together).

Unplug the power supply and test each pin with the others. It must not beep continuously.

Also, you can follow the RX and TX tracks and test continuity with your TTL-serial converter.

Sorry for my lack of knowledge, but how would I do this?

Using the same approach above, you can test continuity between the pins and the circuit components, following the track that starts at the pin.

wellsouz commented 3 years ago

Edit: After doing some testing with the multimeter there is continuity between the +3.3V and RX pins. I assume this is bad?

Yes. This is bad. But remember to test continuity with the power supply unplugged. If the problem remains, try to remove all soldering you did and test the pins without the TTL converter. There should be no continuity between the pins.

cdixon1 commented 3 years ago

First of all, thanks for all of your help!

Maybe you have done a short-circuit between the pins during the soldering process. Try using the the multimeter at the continuity scale (the one that beeps when you put the black and red probes together).

I haven't done any soldering, the pins were already there when I cracked open the box. From seeing posts from others it seems it's like that from the factory. When I test resistance between the pins of the serial port the multimeter measures a ~2kΩ but no beeping on the continuity setting.

Unplug the power supply and test each pin with the others. It must not beep continuously.

No beeping.

Using the same approach above, you can test continuity between the pins and the circuit components, following the track that starts at the pin.

I don't see any tracks starting from the pins of the serial ports. Possibly a multilayer board?

Yes. This is bad. But remember to test continuity with the power supply unplugged. If the problem remains, try to remove all soldering you did and test the pins without the TTL converter. There should be no continuity between the pins.

Tested with the board unplugged and there is no beeping, but it does measure a resistance (~2kΩ). Should it be 0?

If the board is toast it's not big deal as I have the 220.

wellsouz commented 3 years ago

Tested with the board unplugged and there is no beeping, but it does measure a resistance (~2kΩ). Should it be 0? I will check mine and report tomorrow.

cdixon1 commented 3 years ago

Tested with the board unplugged and there is no beeping, but it does measure a resistance (~2kΩ). Should it be 0? I will check mine and report tomorrow.

Thanks!

wellsouz commented 3 years ago

Tested with the board unplugged and there is no beeping, but it does measure a resistance (~2kΩ). Should it be 0? You can also compare the measurements with the BA220 as well. It's pretty the same board with and additional SATA port.

cdixon1 commented 3 years ago

So it turns out there is a short between the RX and +3.3V pins so that's probably why I can't send any commands with the 110. It's not the end of the world I can still use one of the modified stock firmwares floating around to at least have SSH access.

With the 220 I completed the installation, but on the first boot I ran into this error:

U-Boot 2017.11 (Dec 18 2018 - 09:52:13 +0100)                                   
NAS 220                                                                         

SoC:   Kirkwood 88F6281_A0                                                      
DRAM:  128 MiB                                                                  
WARNING: Caches not enabled                                                     
NAND:  32 MiB                                                                   
In:    serial                                                                   
Out:   serial                                                                   
Err:   serial                                                                   
Net:   egiga0                                                                   
88E1116 Initialized on egiga0                                                   
IDE:   Bus 0: .OK Bus 1: not available                                          
  Device 0: Model: WDC WD1600BEVT-22ZCT0  Firm: 11.01A11 Ser#:  WD-WXC908395046 
            Type: Hard Disk                                                     
            Supports 48-bit addressing                                          
            Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)                  
Hit any key to stop autoboot:  0                                                

NAND read: device 0 offset 0xc0000, size 0x500000                               
 5242880 bytes read: OK                                                         

NAND read: device 0 offset 0x5c0000, size 0x1a3fff0                             
Attempt to read outside the flash area                                          
 0 bytes read: ERROR                                                            
## Booting kernel from Legacy Image at 00040000 ...                             
   Image Name:   kernel 4.19.0-16-marvell                                       
   Created:      2021-04-22   6:12:29 UTC                                       
   Image Type:   ARM Linux Kernel Image (uncompressed)                          
   Data Size:    2065442 Bytes = 2 MiB                                          
   Load Address: 00040000                                                       
   Entry Point:  00040000                                                       
   Verifying Checksum ... OK                                                    
Wrong Ramdisk Image Format                                                      
Ramdisk image is corrupt or invalid                                             
nas220>

Thoughts?

Edit: Using the information here and running the command nand bad I found out I have a bad block at 0x016e8000. Then when I run nand read.e 0x800000 0x5c0000 0x1a30000 I get:

NAND read: device 0 offset 0x5c0000, size 0x1a30000
Skipping bad block 0x016e8000
 27459584 bytes read: OK

After that if I run boot the system loads. I'm not exactly sure what's going on but would you be able to point me in the right direction to fix this?

cdixon1 commented 3 years ago

Alright I have figured out what I need to change in the u-boot environment variables but I cant figure out how the change them and have the changes save persistently .

My current u-boot environment variables are:

nas220> printenv
autoload=no
autostart=no
baudrate=115200
bootargs=console=ttyS0,115200
bootargs_base=console=ttyS0,115200
bootcmd=run bootcmd_nand
bootcmd_nand=setenv bootargs console=ttyS0,115200 cmdlinepart.mtdparts=orion_nand:0xa0000@0x0(uboot),0x010000@0xa0000(env),0x500000@0xc0000(uimage),0x1a40000@0x5c0000(rootfs)
bootcmd_rescue=setenv bootargs_extra rescue/enable=true; run bootcmd_usb
bootcmd_usb=setenv bootargs ${bootargs_base} ${mtdparts} ${bootargs_extra}; usb start; fatload usb 0:1 0x40000 uImage-dtb; fatload usb 0:1 0x800000 uInitrd; bootm 0x40000 0x800000
bootdelay=3
ethact=egiga0
ethaddr=00:10:75:07:0D:8D
ethadr=00:10:75:07:0D:8D
mtdids=nand0=orion_nand
mtdparts=cmdlinepart.mtdparts=orion_nand:0xa0000@0x0(uboot),0x010000@0xa0000(env),0x500000@0xc0000(uimage),0x1a40000@0x5c0000(rootfs)
stderr=serial
stdin=serial
stdout=serial

Environment size: 876/65532 bytes

I have figured out I have to change:

bootcmd_nand=setenv bootargs console=ttyS0,115200 cmdlinepart.mtdparts=orion_nand:0xa0000@0x0(uboot),0x010000@0xa0000(env),0x500000@0xc0000(uimage),0x1a40000@0x5c0000(rootfs)

to

bootcmd_nand=setenv bootargs console=ttyS0,115200 cmdlinepart.mtdparts=orion_nand:0xa0000@0x0(uboot),0x010000@0xa0000(env),0x500000@0xc0000(uimage),0x1a30000@0x5c0000(rootfs)

I know I can do this by using setenv bootcmd_nand... and then saveenv. However when I try to run the setenv command the system reads from the nand and boots and I don't have a chance to run the saveenv command and the change does not persist after a power cycle. Does anyone know how I do this?

Edit: I figured out that I have to enclose the variable in single quotes to get it to set without running the code. I could then run saveenv and everything works now.