Install debian on Netgear stora

Hi, I own a NETGEAR STORA that I would like to make it a "real nas" :D with Debian and OpenMediaVault inside. To the device I already have root access in SSH following some steps in in the forum topic. Can someone help me by explaining me to simple steps? Do I necessarily have to have Arduino to complete the required operation? Many thanks.

demonside,

>. To the device I already
> have root access in SSH following some steps in in
> the forum topic.

Summary of the steps.

If you are inside stock OS, you can install both new U-Boot and new Debian rootfs:

1. On another Linux box, create the Debian rootfs using Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2

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

2. Dowload the u-boot tarball uboot.2017.07-tld-1.netgear_ms2110.bodhi.tarto this new USB rootfs:

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

3. And then attach the new USB rootfs to the box. Follow the u-boot installation instruction to flash u-boot. Note that serial console is strongly recommended. So you can test UART booting and know there is a recovery path. Flashing u-boot is always risky in that a mis-step will brick the box. Read the new u-boot installation post and take it slow, ask question if you are not sure about anything.


=========

You can also avoid fashing new u-boot. But it only work with serial console, where you can enter u-boot envs to boot the new rootfs and not commiting to save anything. This approach is non-destructive. While installing new u-boot will be make stock FW unusable (you can not boot back to stock with new u-boot).

Boot Kirkwood rootfs with stock u-boot
https://forum.doozan.com/read.php?2,102054,105374#msg-105374

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

Hi Bodhi,
I am in this situation, what did I do wrong?
I only completed step 1 because step 2 I did not understand, what should I do with the file uboot.2017.07-tld-1.netgear_ms2110.bodhi.tar ?
For now I would like to keep debian only in the USB stick and only after everything goes well will I update the FW of the nas.

Many thanks

Alberto

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** MARVELL BOARD: RD-88F6281A LE 

U-Boot 1.1.4 (Sep  4 2009 - 09:36:11) Marvell version: 3.4.14

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

Soc: 88F6281 A0 (DDR2)
CPU running @ 1000Mhz L2 running @ 333Mhz
SysClock = 333Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size  64MB 
DRAM CS[1] base 0x04000000   size  64MB 
DRAM Total size 128MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
CRC in Flash: 82350fef, Calculated CRC: 82350fef

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0, egiga1 [PRIME]
Hit any key to stop autoboot:  3  0
Marvell>> 
Marvell>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
Marvell>> setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
Marvell>> setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
Marvell>> setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000'
Marvell>> setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
Marvell>> setenv bootcmd 'usb reset; run usb_bootcmd; usb stop; reset'
Marvell>> printenv
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
CASset=min
MALLOC_len=1
ethprime=egiga1
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
eth1addr=00:50:43:00:02:02
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loidaddr=0x02000000
autoload=no
mainlineLiNux=no
fw_up=disable
bootargs_root=ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc
console=console=ttyS0,115200
ethaddr=00:26:F2:6E:5F:13
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
hddPowerCtrl=no
loadaddr=0x02000000
enaAutoRecovery=no
ethact=egiga1
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
load_uinitrd=ext2load usb 0:1 0x2100000 /boot/uInitrd
usb_boot=mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000
usb_bootcmd=run usb_set_bootargs; run usb_boot
bootcmd=usb reset; run usb_bootcmd; usb stop; reset

Environment size: 1543/131068 bytes
Marvell>> boot
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
....
.
......
............
.........................
...................................................
......................................................................................................
............................................................................................................................................................................................................
....
.....................................................................................................................

5447395 bytes read
....
.
......
............
.........................
...................................................
......................................................................................................
....................................................................................................................................................................T T T T ..
 ** ext2fs_devread() read error - block

** Unable to read "/boot/uInitrd" from usb 0:1 **
## Booting image at 00800000 ...
   Image Name:   Linux-5.13.6-kirkwood-tld-1
   Created:      2023-01-20  19:11:45 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5447331 Bytes =  5.2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 02100000 ...
   Image Name:   initramfs-5.13.6-kirkwood-tld-1
   Created:      2021-09-24   1:06:32 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9671027 Bytes =  9.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC 

Alberto,

This error indictates that the rootfs was not created correctly.

> ** ext2fs_devread() read error - block

You need follow the instruction in the rootfs release thread very closely. If you'd like, post the terminal session log when you create the rootfs here (copy/paste everything on the screen), and I'll check it for you.

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

Hi Bodhi,
first of all thanks for the support, now I will list what I did.
1) I opened a terminal as root (su -)

maga@maga:~$ su -
Password: 
root@maga:~# fdisk -l
...
Disk /dev/sdc: 7,51 GiB, 8053063680 bytes, 15728640 sectors
Disk model: Flash Disk      
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: 0x8993836e

Dispositivo Avvio Start     Fine  Settori  Size Id Tipo
/dev/sdc1          2048 15728639 15726592  7,5G 83 Linux

root@maga:~# sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL
NAME   FSTYPE     SIZE MOUNTPOINT                    LABEL
...
sdc               7,5G                               
└─sdc1 ext3       7,5G /media/maga/rootfs            rootfs

2) I copied the Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 file to the USB stick.

root@maga:~# ls -l /media/maga/rootfs/
totale 16
drwx------ 2 root root 16384 gen 21 10:32 lost+found
root@maga:~# cp /home/maga/Documenti/Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 /media/maga/rootfs/
root@maga:~# ls -l /media/maga/rootfs/
totale 239492
-rw-r--r-- 1 root root 244975242 gen 21 10:44 Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2
drwx------ 2 root root     16384 gen 21 10:32 lost+found
root@maga:~# cd /media/maga/rootfs/
root@maga:/media/maga/rootfs# 
root@maga:/media/maga/rootfs# tar -xjf Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 
root@maga:/media/maga/rootfs# 
root@maga:/media/maga/rootfs# cat etc/fstab 
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
LABEL=rootfs    /               ext3    noatime,errors=remount-ro 0 1
tmpfs          /tmp            tmpfs   defaults          0       0
root@maga:/media/maga/rootfs# 
root@maga:/media/maga/rootfs# cd boot/
root@maga:/media/maga/rootfs/boot# cp -a zImage-5.13.6-kirkwood-tld-1  zImage.fdt
root@maga:/media/maga/rootfs/boot# cat dts/kirkwood-netgear_stora_ms2000.dtb  >> zImage.fdt
root@maga:/media/maga/rootfs/boot# mv uImage uImage.orig
root@maga:/media/maga/rootfs/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.13.6-kirkwood-tld-1 -d zImage.fdt  uImage
Image Name:   Linux-5.13.6-kirkwood-tld-1
Created:      Sat Jan 21 10:50:02 2023
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    5447331 Bytes = 5319.66 KiB = 5.19 MiB
Load Address: 00008000
Entry Point:  00008000
root@maga:/media/maga/rootfs/boot# sync
root@maga:/media/maga/rootfs/boot#

3) I finally put the USB stick in the nas and started it with these commands

setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
setenv bootcmd 'usb reset; run usb_bootcmd; usb stop; reset'

printenv
boot

4) then it gave me the error that I sent you earlier.

Many thanks

Alberto

Alberto ,

> 1) I opened a terminal as root (su -)
>
> maga@maga:~$ su -
> Password:
> root@maga:~# fdisk -l
> ...
> Disk /dev/sdc: 7,51 GiB, 8053063680 bytes,
> 15728640 sectors
> Disk model: Flash Disk
> 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: 0x8993836e
>
> Dispositivo Avvio Start Fine Settori Size Id
> Tipo
> /dev/sdc1 2048 15728639 15726592 7,5G 83
> Linux

Ok. So after you used fdisk as above to create the partition. How did you format the Ext3 partition? and what Linux system you were using ?

Below the lsblk command does show the Ext3 partition. But I like to see how the format was done. Was it done using mkfs.ext3 command or with a GUI?

> root@maga:~# sudo lsblk -o
> NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL
> NAME FSTYPE SIZE MOUNTPOINT
> LABEL
> ...
> sdc 7,5G
>
> └─sdc1 ext3 7,5G /media/maga/rootfs
> rootfs
>
> [/code]

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

So, to create the partition I used gparted, as distribution I used CSI Linux once and last time Ubuntu Mate 20.04. Now I bought a new USB stick because I suspect that the one I used was not in very good condition.
Do you have a suggestion on how to prepare the USB flash drive from the command line?

Thanks

Alberto

Alberto,

Using GUI on Ubuntu sometime is problematic, as some users have reported the default values caused problem booting.

So just use the fdisk command, wipe it clean (o command) and create new partition (n command), and take default for everything.

fdisk /dev/sdc

And format it

mkfs.ext3 -L rootfs /dev/sdc1

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

Hi Bodhi,
the problem was definitely my USB drive, in any case the new one I prepared from the command line and everything went well.
Is it possible to make booting from USB permanent at this point?
Finally, when I am in root mode in Debian can I proceed to install openmediavault, do I have to do any other steps first?

Thank you very much!

Password:

Linux debian 5.13.6-kirkwood-tld-1 #1.0 PREEMPT Sat Jul 31 22:10:39 PDT 2021 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: Sat Sep 25 19:53:59 PDT 2021 from 192.168.0.100 on pts/0

debian

192.168.1.62

NETGEAR MS2000 / MS2110 aka Stora

Linux version 5.13.6-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1.0 PREEMPT Sat Jul 31 22:10:39 PDT 2021

Debian 11.0
Sat Jan 21 07:30:08 PST 2023 up 1 minute
root@debian:~#

Cool!

> Is it possible to make booting from USB permanent
> at this point?

After you have rebooted the system a few times with this set of envs like you did:

setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
setenv bootcmd 'usb reset; run usb_bootcmd; usb stop; reset'

printenv
boot

And satisfied that everything works. The next reboot you would run saveenv command before boot:

printenv
saveenv
boot

And then reboot it once more to see it automatically boots into USB rootfs.


> Finally, when I am in root mode in Debian can I
> proceed to install openmediavault, do I have to do
> any other steps first?

It's a fully functional Debian system. So follow the roofts installation instruction to finish some recommended steps (several Notes after Step 5). Thing such as creating swap file, and upgrading system should be done. And then install other packages.

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

Hi Bodhi, maybe I sang victory too soon, Debian 11 from USB works fine but OMV6 just won't install, I ran into the many errors that I can't solve. I haven't figured out if the hardware in my hand is too limited for OMV6. I would be fine with an earlier version as long as it works. Can you help me again to understand what is wrong?

I followed this guide:
https://docs.openmediavault.org/en/latest/installation/on_debian.html

root@debian:~# apt-get install --yes gnupg

Reading package lists... 0%

Reading package lists... 100%

Reading package lists... Done


Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree... 58%

Building dependency tree... 79%

Building dependency tree... Done


Reading state information... 0% 

Reading state information... 0%

Reading state information... Done

gnupg is already the newest version (2.2.27-2+deb11u2).
The following packages were automatically installed and are no longer required:
  libarchive13 libltdl7 libodbc1
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
7 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up proftpd-core (1.3.7a+dfsg-12+deb11u2) ...
usermod: no changes
Synchronizing state of proftpd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable proftpd
Failed to reload daemon: Refusing to reload, not enough space available on /run/systemd. Currently, 10.4M are free, but a safety buffer of 16.0M is enforced.
Failed to reload daemon: Refusing to reload, not enough space available on /run/systemd. Currently, 10.4M are free, but a safety buffer of 16.0M is enforced.
Failed to reload daemon: Refusing to reload, not enough space available on /run/systemd. Currently, 10.4M are free, but a safety buffer of 16.0M is enforced.
dpkg: error processing package proftpd-core (--configure):
 installed proftpd-core package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proftpd-dev:
 proftpd-dev depends on proftpd-core (= 1.3.7a+dfsg-12+deb11u2); however:
  Package proftpd-core is not configured yet.

dpkg: error processing package proftpd-dev (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proftpd-mod-vroot:
 proftpd-mod-vroot depends on proftpd-abi-1.3.7a; however:
  Package proftpd-abi-1.3.7a is not installed.
  Package proftpd-core which provides proftpd-abi-1.3.7a is not configured yet.

dpkg: error processing package proftpd-mod-vroot (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openmediavault:
 openmediavault depends on proftpd-mod-vroot; however:
  Package proftpd-mod-vroot is not configured yet.

dpkg: error processing package openmediavault (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proftpd-mod-crypto:
 proftpd-mod-crypto depends on proftpd-core (= 1.3.7a+dfsg-12+deb11u2); however:
  Package proftpd-core is not configured yet.

dpkg: error processing package proftpd-mod-crypto (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proftpd-mod-wrap:
 proftpd-mod-wrap depends on proftpd-core (= 1.3.7a+dfsg-12+deb11u2); however:
  Package proftpd-core is not configured yet.

dpkg: error processing package proftpd-mod-wrap (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proftpd-basic:
 proftpd-basic depends on proftpd-core; however:
  Package proftpd-core is not configured yet.
 proftpd-basic depends on proftpd-mod-wrap; however:
  Package proftpd-mod-wrap is not configured yet.
 proftpd-basic depends on proftpd-mod-crypto; however:
  Package proftpd-mod-crypto is not configured yet.

dpkg: error processing package proftpd-basic (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proftpd-core
 proftpd-dev
 proftpd-mod-vroot
 openmediavault
 proftpd-mod-crypto
 proftpd-mod-wrap
 proftpd-basic
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:~# wget -O "/etc/apt/trusted.gpg.d/openmediavault-archive-keyring.asc" https://packages.openmediavault.org/public/archive.key
--2023-01-23 16:18:29--  https://packages.openmediavault.org/public/archive.key
Resolving packages.openmediavault.org (packages.openmediavault.org)... 178.254.11.33
Connecting to packages.openmediavault.org (packages.openmediavault.org)|178.254.11.33|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3134 (3.1K) [application/pgp-keys]
Saving to: '/etc/apt/trusted.gpg.d/openmediavault-archive-keyring.asc'


          /etc/apt/   0%[                    ]       0  --.-KB/s               
/etc/apt/trusted.gp 100%[===================>]   3.06K  --.-KB/s    in 0.002s  

2023-01-23 16:18:30 (1.85 MB/s) - '/etc/apt/trusted.gpg.d/openmediavault-archive-keyring.asc' saved [3134/3134]

root@debian:~# apt-key add "/etc/apt/trusted.gpg.d/openmediavault-archive-keyring.asc"
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK
root@debian:~# export LANG=C.UTF-8
root@debian:~# export DEBIAN_FRONTEND=noninteractive
root@debian:~# export APT_LISTCHANGES_FRONTEND=none
root@debian:~# apt-get --yes --auto-remove --show-upgraded --allow-downgrades --allow-change-held-packages --no-install-recommends --option DPkg::Options::="--force-confdef" --option DPkg::Options::="--force-confold" install openmediavault-keyring openmediavaultapt-get --yes --auto-remove --show-upgraded --allow-downgrades --allow-change-held-packages --no-install-recommends --option DPkg::Options::="--force-confdef" --option DPkg::Options::="--force-confold" install openmediavault-keyring openmediavault
[?2004l

Reading package lists... 0%

Reading package lists... 100%

Reading package lists... Done


Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree... 55%

Building dependency tree... 76%

Building dependency tree... 97%

Building dependency tree... Done


Reading state information... 0% 

Reading state information... 0%

Reading state information... Done

openmediavault is already the newest version (6.1.7-1).
openmediavault-keyring is already the newest version (1.0).
The following packages will be REMOVED:
  libarchive13 libltdl7 libodbc1
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
7 not fully installed or removed.
After this operation, 1744 kB disk space will be freed.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 31697 files and directories currently installed.)
Removing libarchive13:armel (3.4.3-2+deb11u1) ...
Removing libodbc1:armel (2.3.6-0.1+b1) ...
Removing libltdl7:armel (2.4.6-15) ...
Setting up proftpd-core (1.3.7a+dfsg-12+deb11u2) ...
usermod: no changes
Synchronizing state of proftpd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable proftpd
Failed to reload daemon: Refusing to reload, not enough space available on /run/systemd. Currently, 10.4M are free, but a safety buffer of 16.0M is enforced.
Failed to reload daemon: Refusing to reload, not enough space available on /run/systemd. Currently, 10.4M are free, but a safety buffer of 16.0M is enforced.
Failed to reload daemon: Refusing to reload, not enough space available on /run/systemd. Currently, 10.4M are free, but a safety buffer of 16.0M is enforced.
dpkg: error processing package proftpd-core (--configure):
 installed proftpd-core package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proftpd-dev:
 proftpd-dev depends on proftpd-core (= 1.3.7a+dfsg-12+deb11u2); however:
  Package proftpd-core is not configured yet.

dpkg: error processing package proftpd-dev (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proftpd-mod-vroot:
 proftpd-mod-vroot depends on proftpd-abi-1.3.7a; however:
  Package proftpd-abi-1.3.7a is not installed.
  Package proftpd-core which provides proftpd-abi-1.3.7a is not configured yet.

dpkg: error processing package proftpd-mod-vroot (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openmediavault:
 openmediavault depends on proftpd-mod-vroot; however:
  Package proftpd-mod-vroot is not configured yet.

dpkg: error processing package openmediavault (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proftpd-mod-crypto:
 proftpd-mod-crypto depends on proftpd-core (= 1.3.7a+dfsg-12+deb11u2); however:
  Package proftpd-core is not configured yet.

dpkg: error processing package proftpd-mod-crypto (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proftpd-mod-wrap:
 proftpd-mod-wrap depends on proftpd-core (= 1.3.7a+dfsg-12+deb11u2); however:
  Package proftpd-core is not configured yet.

dpkg: error processing package proftpd-mod-wrap (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proftpd-basic:
 proftpd-basic depends on proftpd-core; however:
  Package proftpd-core is not configured yet.
 proftpd-basic depends on proftpd-mod-wrap; however:
  Package proftpd-mod-wrap is not configured yet.
 proftpd-basic depends on proftpd-mod-crypto; however:
  Package proftpd-mod-crypto is not configured yet.

dpkg: error processing package proftpd-basic (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.31-13+deb11u5) ...
Errors were encountered while processing:
 proftpd-core
 proftpd-dev
 proftpd-mod-vroot
 openmediavault
 proftpd-mod-crypto
 proftpd-mod-wrap
 proftpd-basic
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:~# omv-confdbadm populate
/usr/share/openmediavault/confdb/populate.d/40interfaces.sh: 24: .: cannot open /etc/default/openmediavault: No such file
Traceback (most recent call last):
  File "/usr/sbin/omv-confdbadm", line 76, in <module>
    sys.exit(main())
  File "/usr/sbin/omv-confdbadm", line 72, in main
    return cmd_inst.execute(*sys.argv)
  File "/usr/share/openmediavault/confdbadm/commands.d/populate.py", line 50, in execute
    openmediavault.procutils.check_call([script_path])
  File "/usr/lib/python3/dist-packages/openmediavault/procutils.py", line 58, in check_call
    return subprocess.check_call(*popenargs, **kwargs)
  File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/share/openmediavault/confdb/populate.d/40interfaces.sh']' returned non-zero exit status 2.
root@debian:~#

Edited 2 time(s). Last edit at 01/23/2023 09:56AM by demonside.

May be these tutorial in the Wiki thread will help

Quote

Media Streaming

OpenMediaVault
Debian Stretch and OMV4

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

demonside Wrote:
-------------------------------------------------------
> Failed to reload daemon: Refusing to reload, not
> enough space available on /run/systemd. Currently,
> 10.4M are free, but a safety buffer of 16.0M is
> enforced.
> Failed to reload daemon: Refusing to reload, not
> enough space available on /run/systemd. Currently,
> 10.4M are free, but a safety buffer of 16.0M is
> enforced.

The above errors are because the default behavior of linux systemd is to use a set proportion of ram for the /run partition. This ends up being to small on devices with only 128M of RAM. The least troublesome prevention of this issue is to add the following line to the /etc/fstab file:

none /run tmpfs defaults,size=32M 0 0

Then mount /run again:

#    mount -o remount /run

Now check run with df:

#    df -h /run

After future reboots you should then always have sufficient space for the /run partition.

Ray

Hi, thank you all for your help, it was really valuable!!! I have finally reached the end of my goal. I installed Debian 9 + OMV4 on NETGEAR STORA leaving the original boot unchanged. The only thing I replaced was my USB flash drive with a USB hard drive for speed reasons. Since I am a very tenacious person, I asked myself a question. Is it possible to make the USB hard drive boot by attaching it directly to the SATA of the NAS and put it in RAID 1 mode so that I can free up the USB port and the clutter of the external drive? I read this post about it: https://forum.doozan.com/read.php?2,94014 but I am not clear on the steps and whether I can ultimately boot from SATA into RAID 1. Can you guys help me with this?

Alberto

Alberto,

Yes it is possible.

The USB HDD drive was formatted as Ext3. So you can put it in the SATA slot and boot it. No RAID involved, just a SATA Ext3 rootfs..

Howver, since you are booting with stock uboot, the envs mut be adjusted to boot SATA (with the new uboot it is not necessary to do this).

I will be back and write those adjustment for you.

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

Alberto,

Put the HDD from USB HDD drive into the 1st SATA slot. Power up, interrupt serial console. Some USB HDD controller is old and might cause some weird problem when you format it in the enclosure. So to see if everything is normal, run these to test the spin up.

ide reset
ide part

If you see the HDD is initialzed OK and the partition show what you expect, then do

setenv sata_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv load_uimage_sata 'ext2load ide 0:1 0x800000 /boot/uImage'
setenv load_uinitrd_sata 'ext2load ide 0:1 0x2100000 /boot/uInitrd'
setenv sata_boot 'mw 0x800000 0 1; run load_uimage_sata; run load_uinitrd_sata; bootm 0x800000 0x2100000'
setenv sata_bootcmd 'run sata_set_bootargs; run sata_boot'
setenv bootcmd 'ide reset; run sata_bootcmd; reset'

and then

boot

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