Install Debian on old GoFlex Home

I have old "GoFlex Home" Device.
I am Noob and want to install the latest Debian.
Which instruction is the most relevant for installing latest Debian on my device GoFlex Home ?
Many thanks for any help!

Here is my Device info:

Quote

===============================
bash-3.2# cat /proc/cpuinfo
Processor : ARM926EJ-S rev 1 (v5l)
BogoMIPS : 1192.75
Features : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant : 0x2
CPU part : 0x131
CPU revision : 1
Cache type : write-back
Cache clean : cp15 c7 ops
Cache lockdown : format C
Cache format : Harvard
I size : 16384
I assoc : 4
I line length : 32
I sets : 128
D size : 16384
D assoc : 4
D line length : 32
D sets : 128

Hardware : Feroceon-KW
Revision : 0000
Serial : 0000000000000000

===============================
bash-3.2# cat /proc/meminfo
MemTotal: 125800 kB
MemFree: 5752 kB
Buffers: 7356 kB
Cached: 57136 kB
SwapCached: 2576 kB
Active: 50268 kB
Inactive: 40028 kB
SwapTotal: 127992 kB
SwapFree: 119904 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 24748 kB
Mapped: 16492 kB
Slab: 24652 kB
SReclaimable: 2032 kB
SUnreclaim: 22620 kB
PageTables: 1132 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 190892 kB
Committed_AS: 209832 kB
VmallocTotal: 516096 kB
VmallocUsed: 1580 kB
VmallocChunk: 514512 kB

===============================
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00600000 00020000 "uImage"
mtd2: 0f900000 00020000 "root"

===============================
bash-3.2# cat /proc/interrupts
CPU0
1: 7765820 - kw_tick
11: 552389 - mv_ethernet
19: 0 - ehci_hcd:usb1
21: 121439 - mvSata
22: 0 - cesa
33: 623 - serial
Err: 0

===============================

Edited 1 time(s). Last edit at 10/27/2018 04:21AM by valery.

valery,

From inside stock OS. Install,

U-boot: uboot.2017.07-tld-1.goflexhome.bodhi.tar

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

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

https://forum.doozan.com/read.php?2,12096

Read these 2 posts and see if you're comfortable with running those installation procedures.

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

bodhi, Thanks!

bodhi, on U-boot topic at https://forum.doozan.com/read.php?3,12381
wrote:

Quote

fw_setenv mtdparts 'xxxxxxxxx'
fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx'

ethaddr this is MAC of my box, but where can i find the correct value of the mtdparts?

Also I did not quite understand - In which case the box boot from SATA, and in which with the NAND?
This is my case?
I need it?:

Quote

fw_setenv bootcmd_uenv 'run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3'

valery,

> where can i find the correct value of the mtdparts?

Usually you would see it from stock OS when logged in. But for this GoFlexHome, you don't need to set it, because the default in the env image is already correct for this box.

> Also I did not quite understand - In which case
> the box boot from SATA, and in which with the
> NAND?

It will not boot from NAND any more after you install new u-boot. You will boot from either the USB or SATA with the new rootfs Debian-4..12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on it.

>

Quote

fw_setenv bootcmd_uenv 'run uenv_load; if
> test $uenv_loaded -eq 1; then run uenv_import; fi;
> sleep 3'

This is optional. This is good to have, but in a normal case it is likely not needed.

BTW, do you have serial console connected? It would be great to have it in case you need to trouble shoot booting problem.

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

bodhi, Many Thanks for help

Hello Bodhi,

I have been reading through this forum for last couple of weeks and now I feel that I can handle installing Debian on my GoFlex Home. I was following your U-boot instructions ( https://forum.doozan.com/read.php?3,12381 ) and was stumped by the following:
-----------------------------------------------------------------
bash-3.2# fw_printenv ethaddr
Warning: Bad CRC, using default environment
## Error: "ethaddr" not defined
-----------------------------------------------------------------
Is it ok to continue with your instructions after this error?

Following are the changes I have made to the stock OS so far:

1) Downloaded Uboot Flashing utilities from ( https://forum.doozan.com/read.php?3,27280 ) and
2) copied following files to Stock OS /usr/bin folder: busybox, e2fsck, nanddump, fw_printenv, flash_erase, nandwrite
3) Copied fw_env.config file to Stock OS /etc folder.

I am new to Linux and learning at a slow pace.

Your help will be appreciated.

Here is the info about my device:
---------------------------------------------------------------
bash-3.2# cat /proc/cpuinfo
Processor : ARM926EJ-S rev 1 (v5l)
BogoMIPS : 1192.75
Features : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant : 0x2
CPU part : 0x131
CPU revision : 1
Cache type : write-back
Cache clean : cp15 c7 ops
Cache lockdown : format C
Cache format : Harvard
I size : 16384
I assoc : 4
I line length : 32
I sets : 128
D size : 16384
D assoc : 4
D line length : 32
D sets : 128

Hardware : Feroceon-KW
Revision : 0000
Serial : 0000000000000000
bash-3.2#
---------------------------------------------------------------

Regards,

Navi

Navi,

> bash-3.2# fw_printenv ethaddr
> Warning: Bad CRC, using default environment
> ## Error: "ethaddr" not defined
> -----------------------------------------------------------------
> Is it ok to continue with your instructions after
> this error?

That error is OK when you run fw_printenv in stock OS.

Go ahead with the u-boot installation. After you've flashed new u-boot, that error should not occur.

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

Thanks for Prompt reply.

Should I prepare a new usb flash drive and plug it in the GoFlex home before I proceed further?

Regards,

Navi

Thanks a ton Bodhi,

This was a difficult installation for me, but I was able to do it, again thanks for your help.
Below is the print out of how I did it:

=======================================================================

bash-3.2# flash_erase /dev/mtd0 0 4
Erasing 128 Kibyte @ 60000 -- 100 % complete
bash-3.2# nandwrite /dev/mtd0 uboot.2017.07-tld-1.goflexhome.mtd0.kwb
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
bash-3.2# fw_setenv arcNumber 3338
bash: fw_setenv: command not found
bash-3.2# ln -s fw_printenv fw_setenv
bash-3.2# fw_setenv arcNumber 3338
bash-3.2# fw_setenv machid
bash-3.2# fw_setenv ethaddr 'X00:00:00:00:00:00X'
bash-3.2# fw_setenv preboot_nc 'setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi'
bash-3.2# fw_setenv preboot 'run preboot_nc'
bash-3.2# fw_setenv ipaddr '192.168.x.xxx'
bash-3.2# fw_setenv serverip '192.168.x.xxx'
bash-3.2# fw_printenv
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
ethact=egiga0
if_netconsole=ping $serverip
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb_addr=0x1c00000
load_initrd_addr=0x1100000
load_uimage_addr=0x800000
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start"; setenv scan_ide "ide reset"; setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read; fi; else if $devtype part $disknum; then run uenv_read; fi; fi
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
usb_ready_retry=15
arcNumber=3338
dtb_file=/boot/dts/kirkwood-goflexhome.dtb
ethaddr=00:00:00:00:00:00
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
preboot=run preboot_nc
ipaddr=192.168.x.xxx
serverip=192.168.x.xxx
bash-3.2#
------------------------------------------------------------------------
success booting into debian!!!!!!!!!!!!
---------------------------------------------------------------------------
root@mint:~# ssh root@192.168.x.x
The authenticity of host '192.168.x.x (192.168.x.x)' can't be established.
ECDSA key fingerprint is SHA256:X3OIp2RLSH4.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.x.x' (ECDSA) to the list of known hosts.
root@192.168.x.x's password:
Linux debian 4.12.1-kirkwood-tld-1 #1 PREEMPT Sat Jul 15 21:40:50 PDT 2017 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 Dec 31 16:01:32 1969 from 192.168.x.x
root@debian:~# fw_printenv
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
ethact=egiga0
if_netconsole=ping $serverip
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb_addr=0x1c00000
load_initrd_addr=0x1100000
load_uimage_addr=0x800000
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start"; setenv scan_ide "ide reset"; setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read; fi; else if $devtype part $disknum; then run uenv_read; fi; fi
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
usb_ready_retry=15
arcNumber=3338
dtb_file=/boot/dts/kirkwood-goflexhome.dtb
ethaddr=00:00:00:00:00:00
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
preboot=run preboot_nc
ipaddr=192.168.x.x
serverip=192.168.x.x
root@debian:~#

Regards,

Navi

I have GoFlex Home, after resetting have no possibility to register and connect to device. I have firmware file to install from usb-pen, with initrd, uImage and hipserv2_seagateplug-20160314.ubi . Can I make .ubi file with debian to install it using usb pen without ssh access to my device?

Hello Skia,

As I am a new to Linux, I am afraid I wont be of much help. However, Bodhi is the Guru and I am sure your situation can be resolved. To make it easier to understand your situation can you please answer the following questions:

1) Were you running stock OS when you reset your device?
2) How was the device reset? Did you try to install other firmware or did you do manual reset on the stock OS?
3) Have your tried to restore original firmware? http://support.goflexhome.hipserv.com/en/reflash/index.html

Regards,

Navi

1.I have a last stock firmware now, but i can`t add user
2.I reseted it by press side button and install last stock firmware from usb-pen.
3.I did it, and now i have original firmware, but cannot use it - seageta turned off their servers
So I want to install debian or any other OS with possibility to set up samba and transmission

Install Debian:
https://forum.doozan.com/read.php?2,12096

Install U-Boot:
https://forum.doozan.com/read.php?3,12381

You can do both inside stock OS.

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

bodhi, I can`t connect to device by ssh, becouse I cannot create user without registration. So i can only change firmware by loading ubi file from usb-pen.
I read instruction, but don`t understand - do i have to do all steps on PC with linux(now i am in ubuntu 18.04) and prepeared usb-pen will be bootable for goflex home? according the instruction pen must be formatted to ext3, but stock firmware installing from fat32 only. Will GoFlexHome load debian from ext3 usb-pen with stock uboot?

Hi Bodhi and Skia,

I think there may be a larger issue involved here. In coming days you will see many more users stuck with a box they cannot access after they have factory reset it.

Seagate turned their server off on Dec 31, 2018. Any one who resets their device after this date will be unable to create a user name and password to access the Goflex Home. Unless someone figures out a hidden root user name and password. Though there may be a way to hack it using serial cable and installing Debian on it, but I am sure a username and password will still be needed when connecting through the physical serial cable.

(I was also thinking of restoring it back to factory because I am having difficult time installing Samba and OpenMediaVault on my box, both give some strange fork error). But Now I will wait until a solution is found for Skia's issue, until then my box will be hibernating or I will figure out how to install Samba and OpenMediaVault on it.

So everyone running debian on these boxes is now stuck and should not try to revert to factory OS, unless they have a backup somewhere that includes username and passwords from before flashing Debian.

Regards,

Navi

Here is info from Seagate site on this issue:

====================================================================================

http://knowledge.seagate.com/articles/en_US/FAQ/007867en/?language=en-us

This article is for informational purposes only and no longer being updated by Seagate.
What to know about GoFlex Home and the Discontinuation of Remote Access.
GoFlex Home Remote Access will be shut off December 31st, 2018.

All other GoFlex Home features should continue to work on your local network. The data on the device should not be deleted or altered in any way. Only the remote access feature will be discontinued.

Once the service has been shut down there are a few important things you need to know.
How to disable port forwarding
How to access your data locally
What not to do

How to disable UPnP (port forwarding) on the GoFlex Home:
Open a Browser and type the following in the URL field: http://goflex_home

Login with your Username and Password.
Choose Preferences.
Under Server Preferences, UPnP Router Configuration, select No for Configure Router via UPnP.
Click Submit.
Reboot the router.

Note: If you manually set up port forwarding in the router’s setup page, those entries should be deleted. Please refer to your router’s documentation for instructions.

It may be necessary to go into your router’s setup page and disable UPNP then re-enable UPnP. This would clear any unused port forwarding in the UPnP list. Please see your router's documentation for instructions.

How to access the GoFlex home on your local network:

Via Web browser
Open a Browser and type the following in the URL field.
http://goflex_home
Login with your Username and Password.
To connect via Finder or File Explorer see the article below.
Connecting to a Seagate Consumer NAS


The following information is very important:


Do not use the Factory Reset Button on the side of the device’s base to reset the device.

Note: After resetting the GoFlex Home the Setup Wizard will attempt to re-activate the GoFlex Home and would prompt for a new GoFlex Home Name and Password. Since the Remote Access Service is no longer available, the device would be unable to authenticate the new Name and Password. Therefore Setup would not be able to complete.

Do not attempt to upgrade or downgrade the GoFlex Home firmware.
=======================================================================================================

Navi , I have already read this article, but my device didn`t load without reset (( So now i try to find the way to use GoFlex Home without seagate servers

When Seagate service is EOL like this, we should not try to keep stock OS. As a matter of fact, this forum mission is to help users install and run the latest Linux kernel on Debian (we don't care about stock).

For most of the Kirkwood boxes, such as the GF Home, when you cannot log in to stock using SSH, the path to install new system is to connect serial console. And then use kwboot to load and run the new u-boot, and run new u-boot and Debian.

1. Create a new rootfs using the tarball Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from the release thread.

2. Download the latest u-boot tarball uboot.2017.07-tld-1.goflexhome.bodhi.tar from the u-boot release thread..

3. Download latest kwboot binary from this post. This is an ARM version. If you are running another ARM or x86 Ubuntu-like box to connect serial console, you can also use kwboot version on that system by installing u-boot-tools. It is not possible to run kwboot on Windows system.

4. Run kwboot to load the u-boot image uboot.2017.07-tld-1.goflexhome.mtd0.kwb. And example for the Kirkwood NSA320S can be found here:
https://forum.doozan.com/read.php?3,51739,51919#msg-51919

5. Adjust the u-boot env dtb_file to the GoFlex Home version. And boot.

6. After you can boot into the new Debian rootfs, you can install new u-boot from there to make it permanent.

I'll create a new post for the detailed instruction to run kwboot on GF Home, to help make it easier.

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

Skia,

This from Jude Periera blog may be helpful:

https://judepereira.com/blog/hacking-your-goflex-home-2-uart-serial-console/
-----------------------------------------------------------------------------

PIN Configuration:
On the GoFlex Home:

10 9 8 7 6
5 4 3 2 1

1 => GND (Ground for the serial communication)
2 => RX (Receiving bits)
3 => TX (Transmitting bits)

Note: The RX and TX are interchanged at one end, this is because the RX of the GoFlex becomes the TX of the USB adapter, and vice cersa.

After you connect the USB end to your desktop/laptop, you can use screen to display the serial console:

# screen /dev/ttyUSB0 115200

The serial console is especially useful for debugging the kernel boot and setting the u-boot environment.

> Note: The RX and TX are interchanged at one end,
> this is because the RX of the GoFlex becomes the
> TX of the USB adapter, and vice cersa.

That's not entirely accurate. The GoFlex Home serial port, like all other serial ports, have defined pinouts that are true.

It depends on what type of serial converter being used, that the TX and RX might need to be crossed. The CP2xxx type converter do not cross (eg. its RX should be connected to the box RX). The Prolific PL3xxx type converter must be crossed (eg. its RX should be connected to the box TX).

For further info, see forum Wiki

Quote

Serial Console & JTAG console

Repair Pogo E02 with Raspberry PI (JTAG) and OpenOCD
Serial Port connector - what are people using to make it work
Serial Console hookup - GoFlex Net (external link)
Serial Console hookup - Pogoplug E02 and Pogoplug Pro V3 (external link)
OSX Serial/Net Console
Use Phone Jack - Phone Jack Serial Console Pics
Adding serial connector to Pogoplug Mobile (external link)
WD Mycloud EX2100/4100 Serial Console pic1, also pic2, pic3
Dreamplug Serial Console
How to unbrick your box using serial console with kwboot
kwboot on Mac OSX 10
Unbrick a Pogoplug Pro v3 OXNAS by flashing u-boot in serial console

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

Hi Navi,

Installing Samba should straightforward. Bodhi provides a tutorial in the wiki

Here’s the link;
Samba install

If that gives errors your USB stick may be faulty, create a new rootfs and try again.

OMV is too resource intensive for the Goflex, I believe older versions worked on Debian8 though. Again there’s details in the Wiki thread.

Hi jdwl101,

Thanks, got Samba working. Now on to OMV. However I am getting comfortable using the command line to configure Debian so may not need OMV after all.

Regards,

Navi

Congrats! The Goflex is a great little box once you getting running.

I've used only the command line to set up mine and it is chugging along nicely with Samba, NFS and AFP.

If you decide to setup OMV search the forum, there's a few posts on getting it working on kirkwoods. The lack of RAM will be an issue though.

Happy to answer any questions you have.

J

Edit: Here's the thread I was thinking of; OMV4 on Kirkwood



Edited 1 time(s). Last edit at 01/31/2019 07:07PM by jdwl101.

Hi,

Now, I plan to move the Debian to a new Hard Drive and Boot from it without having to depend on USB for booting and I have following questions:

1) (i) what is the recommended partition layout for the New 250 GB WD2500AAJS? Should I (a) create single ext3 Partition? or (b) Two Partitions with one being ext3 and other Swap? or (c) Three Partitions one ext3 for rootfs, other Swap and third ext4 for data? and (ii) what should be the ideal size for these partitions?

2) I should install a rescue system before I do this, what is the recommended rescue system to install on this Box?

I am running Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 with uboot.2017.07-tld-1.goflexhome.bodhi.tar.

:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
`-sda1 8:1 0 232.9G 0 part
sdb 8:16 1 14.3G 0 disk
|-sdb1 8:17 1 2G 0 part /
`-sdb2 8:18 1 512M 0 part
mtdblock0 31:0 0 1M 0 disk
mtdblock1 31:1 0 4M 0 disk
mtdblock2 31:2 0 32M 0 disk
mtdblock3 31:3 0 219M 0 disk

-------------------------------------------------------------------------
:~# fdisk -l
Disk /dev/mtdblock0: 1 MiB, 1048576 bytes, 2048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock2: 32 MiB, 33554432 bytes, 65536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock3: 219 MiB, 229638144 bytes, 448512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0006328e

Device Boot Start End Sectors Size Id Type
/dev/sda1 1 488397167 488397167 232.9G 7 HPFS/NTFS/exFAT


Disk /dev/sdb: 14.3 GiB, 15376318464 bytes, 30031872 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x522ef038

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 4196351 4194304 2G 83 Linux
/dev/sdb2 4196352 5244927 1048576 512M 82 Linux swap / Solaris

---------------------------------------------------------------------------------------------------------------

Regards,

Navi

Navi,

> 1) (i) what is the recommended partition layout
> for the New 250 GB WD2500AAJS? Should I (a) create
> single ext3 Partition? or (b) Two Partitions with
> one being ext3 and other Swap? or (c) Three
> Partitions one ext3 for rootfs, other Swap and
> third ext4 for data? and (ii) what should be the
> ideal size for these partitions?

With the new u-boot uboot.2017.07-tld-1 for goflexhome, you can use EXT3 or EXT4, it will work fine with either.

- I would use a swap file, dont use swap partition. You can create a swap file on any partition type EXT3 or EXT4. The good swap file size for the GoFlex Home is 512MB or greater.
- The simplest configuration is that the HDD has only 1 partition that houses the rootfs. And then use different HDD for data.
- Since the GoFlex Home has only 1 SATA port, you might want to use 2 partition: rootfs and data. The rootfs should be about 20 GB to allow for furture growth.

> 2) I should install a rescue system before I do
> this, what is the recommended rescue system to
> install on this Box?

If you have serial console, or have activated netconsole, the rescue system is less necessary. However, if you want to install rescue system for convenient (and have remote access to do the rescue), then

Rescue System V2 (use GoflexNet setup)
https://forum.doozan.com/read.php?4,3896

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

Bodhi,

Since I have activated Netconsole, I am skipping rescue system install.

I am using cfdisk command to partion the new 250G WD drive.

1) Should the 20G partition that contains rootfs be 83 Linux type? (I have made it Primary and x83 Linux. I will mark it as bootable later after I copy rootfs files to this partition. Also I am assuming that the swap file will be made in this partiton).

2) Should remaining space for data be partitioned as Primary or Extended? (I have made it Primary and x83 Linux.)

3) Should I leave some unallocated space on this drive for future use?

4) Should I be concerned about "Disklable Type: dos" that fdisk -l command shows below?

Here is what I have executed so far:

-------------------------------------------------------------------------
root@GoFlexHome:~# cfdisk /dev/sda
Syncing disks.
root@GoFlexHome:~# fdisk -l
Disk /dev/mtdblock0: ...........

Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0006328e

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 41945087 41943040 20G 83 Linux
/dev/sda2 41945088 488397167 446452080 212.9G 83 Linux
root@GoFlexHome:~#
------------------------------------------------------------------

Again, Thanks for your valuable input and time.

Regards,

Navi

Navi,

> 2) Should remaining space for data be partitioned
> as Primary or Extended? (I have made it Primary
> and x83 Linux.)

Primary.

> 3) Should I leave some unallocated space on this
> drive for future use?

No need to. The rootfs in the 1st partition is all you need to care about. 20GB is plenty for rootfs.

> 4) Should I be concerned about "Disklable Type:
> dos" that fdisk -l command shows below?

That's normal.


> root@GoFlexHome:~# cfdisk /dev/sda
> Syncing disks.
> root@GoFlexHome:~# fdisk -l
> Disk /dev/mtdblock0: ...........
>
> Disk /dev/sda: 232.9 GiB, 250059350016 bytes,
> 488397168 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512
> bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x0006328e
>
> Device Boot Start End Sectors
> Size Id Type
> /dev/sda1 2048 41945087 41943040
> 20G 83 Linux
> /dev/sda2 41945088 488397167 446452080
> 212.9G 83 Linux

All look good.

Remember to label the rootfs partition rootfs, to ensure correct system booting.

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

Hi Bodhi,

Can't seem to figure out how to format the "cp -R Src_directory Dest_directory" command to move rootfs from USB to HD. Should I be using "cp -R /dev/sdb1/boot /dev/sda1/boot" ?

Regards,

Navi

Navi,

The Wiki thread has a couple cloning procedures.

Quote

Backup and Cloning rootfs

CrashPlan 4.3.0
Backup/Restore rootfs using tar command
Adjust udev rules after cloning rootfs
Stock Pogoplug rootfs
How to clone a rootfs from one Kirkwood box to another: Step 1 and Step 2
How to clone SATA rootfs to USB rootfs

It is best to do the copy when both drives are mounted on another Linux box. So asuming the USB drive is /media/sda1, and HDD is /media/sdb1.

Become root

su -

And copy

cd /media/sdb1
time cp -aR /media/sda1/* . &

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