Welcome! Log In Create A New Profile

Advanced

What version of Rescue am I running?

Posted by jcconnell 
What version of Rescue am I running?
May 10, 2018 09:40AM
I recently pulled my GoFlex Home out of the closet to start working with it again. It's running an installation of the rescue provided on these forums, but I installed it so long ago that I can't recall the details.

I'd like to update it to the most recent version of the rescue and then install Debian/Arch onto a thumbdrive. I know that the details are important, so I'm trying to determine what version of the rescue I installed before I proceed.

Could you anyone help me determine the version and/or provide some guidance on installing Debian/Arch onto a thumbdrive?
Attachments:
open | download - 2018-05-10 11_30_39-GoFlex_Home.png (14.5 KB)
Re: What version of Rescue am I running?
May 10, 2018 04:08PM
jcconnell,

You are running Arch Linux ARM (ALARM) rescue system. I would not recomend installing other rescue system, because the one you have right now is quite good.

> and/or provide some guidance on installing
> Debian/Arch onto a thumbdrive?

If you want to install Debian, see the manual installation instruction here (I am not using any script):
https://forum.doozan.com/read.php?2,12096

If you want to install Arch then visit ALARM site:
https://archlinuxarm.org/forum/index.php

Note: you are running ALARM u-boot on your box. So installing Arch is probably the most logical approach, if you don't have a distro preference,

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 05/10/2018 04:10PM by bodhi.
Re: What version of Rescue am I running?
May 10, 2018 05:34PM
Thank you bodhi. I was wondering why I wasn't able to find any references to Arch on these forums.

It looks like your uboot and rescue system are more actively maintained and more recently updated. I'm also more familiar with Debian. I think I'd still prefer to have your rescue environment and Debian on my machine. What steps should I follow and in what order? I sincerely appreciate the help.
Re: What version of Rescue am I running?
May 10, 2018 10:30PM
jcconnell,

As I've mentioned, this Arch rescue is quite new and robust enough that it is not necessary to install new one. But we'll come to that after you have done Debian installation and running it.

It seems you don't have serial console connected so it is not apparent which version of u-boot you have on this GFHome. But I'm certain, because you are running Arch rescue, you are running a relative new Arch u-boot. To verify that, log in to Arch rescue using alarm user and at command line

fw_printenv
And post the log of the terminal session here.

==========


1. To start Debian installation on USB. See this thread to extract tthe Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 to USB drive.
https://forum.doozan.com/read.php?2,12096


Scroll dow to this section:
Quote

Updated 24 Jul 2017:

Basic Debian stretch Kirkwood rootfs for most Kirwood plugs:

- tarball size: 188M
- install size: 488M
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils.
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:

Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

md5:
bf3d29569943875df348fb5ca03b348c
sha256:
4ed5714fdb123cdb40e973f3d0754e91cd199b75a9874018f2b5dc9cfa8ae8bb

And remember to check the hash of what you download, as always.

Installation:

Installation can be done on any Linux box, with a fresh USB drive (SD card or HDD would work fine too).

Note: all steps below must be done while logging in as root user (not sudo). If you are not the root user then don't continue, because the rootfs will not work.

1. Format a new USB drive with a single Ext3 partition, and label it rootfs. If you are running the latest U-Boot for Kirkwood then you can use Ext4.

2. Mount the drive on a Linux box. cd to top level directory and extract it. It is assuming the USB drive is mounted at /media/sdb1
cd /media/sdb1
tar -xjf Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

3. Adjust fstab (optional).

Edit /media/sdb1/etc/fstab entry for root device to match the rootfstype of your rootfstype if you use Ext4 or Ext2. However, you can keep it as is without problem in booting since the kernel will figure out which file system the rootfs was formatted.

LABEL=rootfs / ext3 noatime,errors=remount-ro 0 1

4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time).

Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box (see the folder /media/sdb1/boot/dts for the exact spelling of your Kirkwood box name).

Generate the uImage with DTB embedded inside:
cd /media/sdb1/boot
cp -a zImage-4.12.1-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.12.1-kirkwood-tld-1 -d zImage.fdt uImage
sync

If your Linux box does not have mkimage, then install it

apt-get install u-boot-tools

5. Done. Take this USB rootfs to your plug and cold start. After booted into Debian, see Note1 and Note2 below. It is very important that you do Note1 steps to secure your box.


Note: you can skip step 4, since you are running a relative new u-boot from Arch.


2. After you have created the Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs on USB drive. To run Debian rootfs with Arch u-boot, see Part 1 of this post:
https://forum.doozan.com/read.php?3,23727

This step 2 is necessary because you are running Arch u-boot. If you'd rather install my released u-boot then we'll revise the instructions further. But I thought you would get Debian running first, and then take time to think about this subject later.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 05/10/2018 10:32PM by bodhi.
Re: What version of Rescue am I running?
May 11, 2018 04:38AM
Thank you Bodhi! This is great information.

Here is the output of fw_printenv:
(rescue)[root@alarm ~]# fw_printenv
baudrate=115200
bootdelay=3
bootm=echo Booting from ${disk} ...; run setargs; bootm ${loadaddr};
bootz=echo Booting from ${disk} ...; run setargs; bootz ${loadaddr} - ${fdt_addr};
console=ttyS0
ethact=egiga0
fdt_addr=0x800000
fdt_file=/boot/dtbs/kirkwood-goflexnet.dtb
importbootenv=echo Importing environment (uEnv.txt)...; env import -t $loadaddr $filesize
load=echo Attempting to boot from ${type} ${disk}:1...;if run loadbootenv; then run importbootenv;fi;echo Checking if uenvcmd is set ..
.;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;echo Running default loadzimage ...;if run loadzimage; then run loa
dfdt;run bootz;fi;echo Running default loaduimage ...;if run loaduimage; then run bootm;fi;
loadaddr=0x810000
loadbootenv=load ${type} ${disk}:1 ${loadaddr} /boot/uEnv.txt
loadfdt=load ${type} ${disk}:1 ${fdt_addr} ${fdt_file}
loaduimage=load ${type} ${disk}:1 ${loadaddr} ${uimage}
loadzimage=load ${type} ${disk}:1 ${loadaddr} ${zimage}
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),-(rootfs)
setargs=setenv bootargs console=${console},${baudrate} ${optargs} root=/dev/sd${letter}1 rw rootwait ${mtdparts}
uimage=/boot/uImage
zimage=/boot/zImage
ethaddr=02:50:43:92:a6:65
mountubi=ubi part rootfs; ubifsmount ubi0:rootfs
loadubizimage=ubifsload ${loadaddr} ${zimage}
loadubifdt=ubifsload ${fdt_addr} ${fdt_file}
bootzubi=echo Booting from nand ...; run setargsubi; bootz ${loadaddr} - ${fdt_addr};
setargsubi=setenv bootargs console=${console},${baudrate} ${optargs} ubi.mtd=1 root=ubi0:rootfs ro rootfstype=ubifs  rootwait ${mtdpart
s}
loadubi=echo Trying to boot from NAND ...;if run mountubi; then run loadubizimage;run loadubifdt;ubifsumount;run bootzubi;fi
bootcmd=ide reset; usb start; setenv letter 9;for type in ide usb; do for disk in 0; do if ${type} part ${disk};then setexpr letter $le
tter + 1; run load;fi;done;done;run loadubi

I will try to install Debian for now as you've suggested and I'l report back my findings here. Again thank you so much for the help, it's sincerely appreciated.
Re: What version of Rescue am I running?
May 11, 2018 03:38PM
jcconnell,

This is a quite recent version of Arch u-boot.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
May 12, 2018 04:52PM
Well I'm having some issues. I've attempted to install both Arch and Debian onto a thumbdrive without success. I'm having trouble using bsdtar to unpack Arch. Debian unpacks without an issue, but it doesn't boot after a restart. The LED goes orange and stays that way.

I also have an older laptop HDD attached to the dock, but the device isn't recognizing it. I'm not sure if it's an issue with the device or the HDD and I don't have a spare HDD to test with. I might have to wait a few more days before I can revisit this location and test again. The Go Flex Home is located at my parents house and it's a bit of a drive.
Re: What version of Rescue am I running?
May 13, 2018 03:14PM
jcconnell,

> Debian unpacks without an issue,
> but it doesn't boot after a restart. The LED goes
> orange and stays that way.

This Debian rootfs was not prepared correctly. Orange LED means that u-boot could not find the kernel files.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
June 02, 2018 10:15AM
bodhi Wrote:
-------------------------------------------------------
> jcconnell,
>
> This is a quite recent version of Arch u-boot.

Just wondered how you could tell which u-boot was being used... I didn't spot any version information. Just curious...
Re: What version of Rescue am I running?
June 02, 2018 04:08PM
balanga Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > jcconnell,
> >
> > This is a quite recent version of Arch u-boot.
>
> Just wondered how you could tell which u-boot was
> being used... I didn't spot any version
> information. Just curious...

The u-boot envs are from Arch u-boot. And some of the commands used in those envs are only available in recent versions of u-boot (i.e. not stock u-boot).

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
June 03, 2018 01:28AM
I installed ALARM very recently using instructions here https://archlinuxarm.org/platforms/armv5/seagate-goflex-home but don't have an fw_printenv command. Is this something I can install via ssh?

I haven't dismantled this unit so do not have serial access. How can I get any information about the u-boot version?
Re: What version of Rescue am I running?
June 03, 2018 06:53AM
@balanga, I believe you need to install the uboot-tools package: https://www.archlinux.org/packages/community/x86_64/uboot-tools/
Re: What version of Rescue am I running?
June 03, 2018 07:11AM
jcconnell Wrote:
-------------------------------------------------------
> @balanga, I believe you need to install the
> uboot-tools package:
> https://www.archlinux.org/packages/community/x86_64/uboot-tools/

Thanks @jcconnnell.

Do I just use wget to retrieve and then extract to / ?
Re: What version of Rescue am I running?
June 03, 2018 07:12AM
pacman -Syu uboot-tools



Edited 1 time(s). Last edit at 06/03/2018 07:12AM by jcconnell.
Re: What version of Rescue am I running?
June 03, 2018 12:28PM
Many thanks that worked fine but when running fw_printenv I get:
[root@alarm ~]# fw_printenv
Cannot parse config file '/etc/fw_env.config': Invalid argument
Do I need to edit /etc/fw_env.config first?
Re: What version of Rescue am I running?
June 03, 2018 01:06PM
Are you also on a Go Flex Home? If so, or if you are running a similar device, it's possible that you'll need one of the packages listed here as well: https://github.com/archlinuxarm/u-boot/wiki
Re: What version of Rescue am I running?
June 03, 2018 03:38PM
balanga,

>
[root@alarm ~]# fw_printenv
> Cannot parse config file '/etc/fw_env.config':
> Invalid argument
>
> Do I need to edit /etc/fw_env.config first?

The fact that you are running Arch, then during installation, u-boot has been installed. And the content of the /etc/fw_env.config file should be:

cat /etc/fw_env.config
# MTD device name	Device offset	Env. size	Flash sector size	Number of sectors 
/dev/mtd0 0xc0000 0x20000 0x20000


To check u-boot version without serial/net console, run this command at the shell (Note: there will be a lot of error messages coming out of dmesg when you run this, you can safely ignore them).

grep -a --null-data U-Boot /dev/mtd0ro

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
June 03, 2018 03:46PM
jcconnell Wrote:
-------------------------------------------------------
> Are you also on a Go Flex Home? If so, or if you
> are running a similar device, it's possible that
> you'll need one of the packages listed here as
> well: https://github.com/archlinuxarm/u-boot/wiki

I have a GoFlex Home but I suspect the installation of my Alarm was different to yours.... I followed the installation instructions here:-

https://archlinuxarm.org/platforms/armv5/seagate-goflex-home

I notice I don't have a

/boot/dtbs/kirkwood-goflexnet.dtb

or

/boot/zImage

uname -a shows:
Linux alarm 4.4.97-1-ARCH #1 PREEMPT Sat Nov 11 04:51:38 UTC 2017 armv5tel GNU/Linux
Re: What version of Rescue am I running?
June 03, 2018 03:48PM
Quote

Linux alarm 4.4.97-1-ARCH #1 PREEMPT Sat Nov 11 04:51:38 UTC 2017 armv5tel GNU/Linux

is a non-FDT kernel. To maximize the potentials, you will need to upgrade this rootfs to FDT.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
June 03, 2018 04:49PM
bodhi Wrote:
-------------------------------------------------------
>
Quote

Linux alarm 4.4.97-1-ARCH #1 PREEMPT Sat
> Nov 11 04:51:38 UTC 2017 armv5tel
> GNU/Linux
>
> is a non-FDT kernel. To maximize the potentials,
> you will need to upgrade this rootfs to FDT.


How do I do that?
Re: What version of Rescue am I running?
June 03, 2018 05:00PM
balanga,

> > is a non-FDT kernel. To maximize the
> potentials,
> > you will need to upgrade this rootfs to FDT.

> How do I do that?

You need to ask this question at Arch site. We only deal with Debian here.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
June 03, 2018 09:13PM
Somewhere in this thread, arti mentioned how to upgrade Arch FDT kernel:

https://forum.doozan.com/read.php?3,58144

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 06/03/2018 09:13PM by bodhi.
Re: What version of Rescue am I running?
June 03, 2018 09:57PM
bodhi Wrote:
-------------------------------------------------------
> balanga,
>
> >
[root@alarm ~]# fw_printenv
> > Cannot parse config file '/etc/fw_env.config':
> > Invalid argument
> >
> > Do I need to edit /etc/fw_env.config first?
>
> The fact that you are running Arch, then during
> installation, u-boot has been installed. And the
> content of the /etc/fw_env.config file should be:
>
> cat /etc/fw_env.config
>
> # MTD device name	Device offset	Env. size	Flash
> sector size	Number of sectors 
> /dev/mtd0 0xc0000 0x20000 0x20000
>

I have this:-

[root@alarm ~]# cat /etc/fw_env.config
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundand
# environment sector is assumed present.
# MTD device name       Device offset   Env. size       Flash sector size
#/dev/mtd2               0x0000          0x20000         0x20000

# segate dockstar:
# /dev/mtd0               0xc0000         0x20000         0x20000

# iomega iconnect
# /dev/mtd0               0xa0000         0x20000         0x20000

# CuBox
# /dev/mtd0               0xc0000         0x10000         0x10000

# CuBox-i/Hummingboard
# /dev/mmcblk0              0x60000         0x2000         0x2000

# Utilite 1
# /dev/mtd1               0x0000          0x2000          0x2000

It is all commented out, so do I simply uncomment the 'segate dockstar' entry?

> To check u-boot version without serial/net
> console, run this command at the shell (Note:
> there will be a lot of error messages coming out
> of dmesg when you run this, you can safely ignore
> them).
>
>
> grep -a --null-data U-Boot /dev/mtd0ro
>

[root@alarm ~]# grep -a --null-data U-Boot /dev/mtd0ro
Warning: U-Boot configured device %s at address %llx,
 but the device tree has it address %llx.
U-Boot** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot BUG at %s:%d!
U-Boot 2014.04.R2-1 (May 15 2014 - 14:36:05) Arch Linux ARM

Should I change /etc/fw_env.config, reboot and try again?
Re: What version of Rescue am I running?
June 03, 2018 10:36PM
balanga Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
>
> It is all commented out, so do I simply uncomment
> the 'segate dockstar' entry?
>
> > To check u-boot version without serial/net
> > console, run this command at the shell (Note:
> > there will be a lot of error messages coming
> out
> > of dmesg when you run this, you can safely
> ignore
> > them).
> >
> >
> > grep -a --null-data U-Boot /dev/mtd0ro
> >
>
>
> [root@alarm ~]# grep -a --null-data U-Boot
> /dev/mtd0ro
> Warning: U-Boot configured device %s at address
> %llx,
>  but the device tree has it address %llx.
> U-Boot** Invalid partition type "%.32s" (expect
> "U-Boot")
> U-Boot BUG at %s:%d!
> U-Boot 2014.04.R2-1 (May 15 2014 - 14:36:05) Arch
> Linux ARM
>
>
> Should I change /etc/fw_env.config, reboot and try
> again?

After changing /etc/fw_env.config, fw_printenv shows:-
baudrate=115200
bootcmd=ide reset; usb start; setenv letter 9;for type in ide usb; do for disk in 0; do if ${type} part ${disk};then setexpr letter $letter + 1;run load;fi;done;done;
bootdelay=3
bootm=echo Booting from ${disk} ...; run setargs; bootm ${loadaddr};
bootz=echo Booting from ${disk} ...; run setargs; bootz ${loadaddr} - ${fdt_addr};
console=ttyS0
ethact=egiga0
fdt_addr=0x800000
fdt_file=/boot/dtbs/kirkwood-goflexnet.dtb
importbootenv=echo Importing environment (uEnv.txt)...; env import -t $loadaddr $filesize
load=echo Attempting to boot from ${type} ${disk}:1...;if run loadbootenv; then run importbootenv;fi;echo Checking if uenvcmd is set ...;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;echo Running default loadzimage ...;if run loadzimage; then run loadfdt;run bootz;fi;echo Running default loaduimage ...;if run loaduimage; then run bootm;fi;
loadaddr=0x810000
loadbootenv=load ${type} ${disk}:1 ${loadaddr} /boot/uEnv.txt
loadfdt=load ${type} ${disk}:1 ${fdt_addr} ${fdt_file}
loaduimage=load ${type} ${disk}:1 ${loadaddr} ${uimage}
loadzimage=load ${type} ${disk}:1 ${loadaddr} ${zimage}
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),-(rootfs)
setargs=setenv bootargs console=${console},${baudrate} ${optargs} root=/dev/sd${letter}1 rw rootwait ${mtdparts}
uimage=/boot/uImage
zimage=/boot/zImage
ethaddr=00:10:75:2C:A9:58

but
grep -a --null-data U-Boot /dev/mtd0ro

shows the same as before.
Re: What version of Rescue am I running?
June 03, 2018 11:07PM
Quote

It is all commented out, so do I simply uncomment the 'segate dockstar' entry?

Correct.

Quote

[root@alarm ~]# grep -a --null-data U-Boot /dev/mtd0ro
Warning: U-Boot configured device %s at address %llx,
but the device tree has it address %llx.
U-Boot** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot BUG at %s:%d!
U-Boot 2014.04.R2-1 (May 15 2014 - 14:36:05) Arch Linux ARM

So your u-boot version is: U-Boot 2014.04.R2-1. Which is one of Arch releases, and relatively modern.


Quote

After changing /etc/fw_env.config, fw_printenv shows:-
baudrate=115200
bootcmd=ide reset; usb start; setenv letter 9;for type in ide usb; do for disk in 0; do if ${type} part ${disk};then setexpr letter $letter + 1;run load;fi;done;done;
bootdelay=3
bootm=echo Booting from ${disk} ...; run setargs; bootm ${loadaddr};
bootz=echo Booting from ${disk} ...; run setargs; bootz ${loadaddr} - ${fdt_addr};
console=ttyS0
ethact=egiga0
fdt_addr=0x800000
fdt_file=/boot/dtbs/kirkwood-goflexnet.dtb
importbootenv=echo Importing environment (uEnv.txt)...; env import -t $loadaddr $filesize
load=echo Attempting to boot from ${type} ${disk}:1...;if run loadbootenv; then run importbootenv;fi;echo Checking if uenvcmd is set ...;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;echo Running default loadzimage ...;if run loadzimage; then run loadfdt;run bootz;fi;echo Running default loaduimage ...;if run loaduimage; then run bootm;fi;
loadaddr=0x810000
loadbootenv=load ${type} ${disk}:1 ${loadaddr} /boot/uEnv.txt
loadfdt=load ${type} ${disk}:1 ${fdt_addr} ${fdt_file}
loaduimage=load ${type} ${disk}:1 ${loadaddr} ${uimage}
loadzimage=load ${type} ${disk}:1 ${loadaddr} ${zimage}
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),-(rootfs)
setargs=setenv bootargs console=${console},${baudrate} ${optargs} root=/dev/sd${letter}1 rw rootwait ${mtdparts}
uimage=/boot/uImage
zimage=/boot/zImage
ethaddr=00:10:75:2C:A9:58

Cool. It means you're all set to boot with this Arch non-FDT kernel.

ALARM has their own package installation, where you can log into Arch and run some pacman commands to install their new u-boot and FDT kernel. For that I'd suggest asking at Arch site (I'd rather not give you advice for Arch specific how-to, you should consult the experts there).

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
June 04, 2018 05:57AM
What I'm still unsure about after messing about with u-boot for some time, is how the boot process works...Is u-boot in NAND and it loads the OS using bootcmd from fw_printenv?

ALARM is currently on a SATA disk. If I insert a USB stick with either Arch Linux or Debian on it, should I expect it to boot?

The original Seagate GoFlex Home stock software was installed in NAND so the system would boot up without any devices attached. Is it possible to install a replacement which does not require external devices?
Re: What version of Rescue am I running?
June 04, 2018 08:53PM
balanga Wrote:
-------------------------------------------------------
> What I'm still unsure about after messing about
> with u-boot for some time, is how the boot process
> works...Is u-boot in NAND and it loads the OS
> using bootcmd from fw_printenv?

It helps to see Wiki thread. I described at the high level how the boot process works in "How to set up U-Boot for booting in multiple drives configuration"

Quote
Wiki thread
Booting Debian on Pogoplug

How to set up U-Boot for booting in multiple drives configuration
Backup and Restore NAND mtds
UART Booting HowTo for Selected Kirkwood Devices
Migrating from Arch to Debian?
How to boot new Debian rootfs using stock u-boot tftp - Pogo E02
How to boot new Debian rootfs on USB using stock u-boot - NSA325

>
> ALARM is currently on a SATA disk. If I insert a
> USB stick with either Arch Linux or Debian on it,
> should I expect it to boot?

Not really. If it booted with Arch on USB, then you can expect it to work with Arch rootfs in SATA.

>
> The original Seagate GoFlex Home stock software
> was installed in NAND so the system would boot up
> without any devices attached. Is it possible to
> install a replacement which does not require
> external devices?

The GoFlex Home NAND storge is too small to house Debian or Arch rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
June 05, 2018 05:01AM
Actually I've found that I can boot both Arch and Debian from the same uboot. Not sure how to identify which uboot it is.

The info about the boot process is very useful.

Is it possible to mount NAND storage?
Re: What version of Rescue am I running?
June 05, 2018 01:36PM
balanga Wrote:
-------------------------------------------------------

> Is it possible to mount NAND storage?

Yes, if you are running my released kernel, NAND UBIS is already initialized (assuming that UBI file system is what you have on your NAND mtd), you just need to mount it.

Assuming you want to mount mtd3 file system:

mkdir -p  /tmp/nand/
mount -t ubifs /dev/mtdblock3 /tmp/nand/


If it has not been initialized (if running a different kernel other than my release), then you need to run ubiattach to bring it up before mounting:
ubiattach /dev/ubi_ctrl -m 3

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: What version of Rescue am I running?
June 05, 2018 01:40PM
balanga Wrote:
-------------------------------------------------------

> Actually I've found that I can boot both Arch and
> Debian from the same uboot.

It means either your Arch rootfs has been "upgraded" to have uInitrd, or my u-boot envs set up has been tweaked a little.

-bodhi
===========================
Forum Wiki
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: