Hello,

 

I'm running into an issue with my rootfs, where the output of "df /" is 0 across the board.

 

root@Prime:~# df /
Filesystem     1K-blocks  Used Available Use% Mounted on
rootfs                 0     0         0    - /

 

The issue came up when I tried to preclear disks with the unassigned.devices.preclear plugin. At one point it checks for free space on '/' and there was wrong behavior due to my issue. I posted on Support Thread and the plugin was updated, and it correctly aborts the whole script now with 'Low memory...' message.

Since this issue is unrelated to the plugin, I post here in General Support, I hope that's right

 

I do not know where to look to find out whats scrambling the rootfs.

I restarted in safe mode, but this does not change the output of "df /"

Running current stable [6.11.5]. Array autostart disabled.
attaching Diagnostics from normal boot and safe mode.

 

Thanks in advance!

normal_prime-diagnostics-20230524-0721.zip safemode_prime-diagnostics-20230524-0733.zip

should there be a mount in fstab for /  ? 
on my arch machine there is but afaik unraid runs differently from ram and stuff.

 

root@Prime:~# cat /etc/fstab 
/dev/sda1                  /boot         vfat      rw,flush,noatime,nodiratime,dmask=77,fmask=177,shortname=mixed
/boot/bzmodules            /lib/modules  squashfs  ro,defaults
/boot/bzfirmware           /lib/firmware squashfs  ro,defaults
tmpfs                      /dev/shm      tmpfs     defaults
hugetlbfs                  /hugetlbfs    hugetlbfs defaults

 

A reboot should fix any issues, unless you have something on a script or the go file making changes.

I rebooted several times with no effect unfortunatly.

i had a look into the go file but there are only energy saving functions as far as i can tell.
 

Spoiler

root@Prime:/boot/config# cat go
#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &

# -------------------------------------------------
# Set power-efficient CPU governor
# -------------------------------------------------
/etc/rc.d/rc.cpufreq powersave

# -------------------------------------------------
# Enable power-efficient ethernet
# -------------------------------------------------

# enable IEEE 802.3az (Energy Efficient Ethernet): Could be incompatible to LACP bonds!
for i in /sys/class/net/eth?; do dev=$(basename $i); [[ $(echo $(ethtool --show-eee $dev 2> /dev/null) | grep -c "Supported EEE link modes: 1") -eq 1 ]] && ethtool --set-eee $dev eee on; done

# Disable wake on lan
for i in /sys/class/net/eth?; do ethtool -s  $(basename $i) wol d; done

# -------------------------------------------------
# powertop tweaks
# -------------------------------------------------

# Enable SATA link power management
echo med_power_with_dipm | tee /sys/class/scsi_host/host*/link_power_management_policy

# Runtime PM for I2C Adapter (i915 gmbus dpb)
echo auto | tee /sys/bus/i2c/devices/i2c-*/device/power/control

# Autosuspend for USB device
echo auto | tee /sys/bus/usb/devices/*/power/control

# Runtime PM for disk
echo auto | tee /sys/block/sd*/device/power/control

# Runtime PM for PCI devices
echo auto | tee /sys/bus/pci/devices/????:??:??.?/power/control

# Runtime PM for ATA devices
echo auto | tee /sys/bus/pci/devices/????:??:??.?/ata*/power/control

 

i looked at cron and it seems also nothing out of the ordinary.

 

I restarted (also in safe mode) and the issue persists with started and stopped array.

where else could I search for a script or something?

1 hour ago, MrTee said:

had a look into the go file

That is a lot of extra stuff. What happens if you just boot with the "stock" go file?

i did not change the go files manually. I think this is from tips and tweaks plugin.

I downloaded the unraid install files and used the go file from there
 

Spoiler

root@Prime:/boot/config# cat go
#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &

 

restarted. still the same
 

root@Prime:~# df /
Filesystem     1K-blocks  Used Available Use% Mounted on
rootfs                 0     0         0    - /

any other suggestions?

 

/boot/extra
total 18808
-rw------- 1 root root 2174744 Nov 17  2022 powertop-2.15-x86_64-1.txz
-rw------- 1 root root 8472744 Dec  9 20:26 vim-9.0.0623-x86_64-1_nerdtools.txz
-rw------- 1 root root 8601288 May 17 18:11 vim-9.0.1493-x86_64-1_nerdtools.txz

Get rid of this stuff in /extra on the flash drive.

30 minutes ago, Squid said:

/boot/extra
total 18808
-rw------- 1 root root 2174744 Nov 17  2022 powertop-2.15-x86_64-1.txz
-rw------- 1 root root 8472744 Dec  9 20:26 vim-9.0.0623-x86_64-1_nerdtools.txz
-rw------- 1 root root 8601288 May 17 18:11 vim-9.0.1493-x86_64-1_nerdtools.txz

Get rid of this stuff in /extra on the flash drive.

did that. rebooted. no change.

where else might i look?
 

prime-diagnostics-20230524-1749.zip

Edit config/docker.cfg to disable Docker. Do the same for config/domain.cfg to disable VM Manager. Boot in SAFE mode (no plugins). If that doesn't work something wrong with your flash install.

I disabled docker and vm already was.
I rebooted in safe mode again and the same issue.

So my flash install seams to be bugged. I am clueless where to look.

So what are my options?
reinstall? what would i loose?

 

Backup current flash, re-create with a stock install, then restore the bare minimum from the current config, like the key, super.dat and pools folder, docker templates, there are a few cfg files that should be safe to restore, like network, shares, etc, you can then re-configure the server or restore the rest a few tiles at a time to see if you find the culprit.

46 minutes ago, JorgeB said:

Backup current flash, re-create with a stock install, then restore the bare minimum from the current config, like the key, super.dat and pools folder, docker templates, there are a few cfg files that should be safe to restore, like network, shares, etc, you can then re-configure the server or restore the rest a few tiles at a time to see if you find the culprit.

Wow that issue impact more than i thought.
so to backup i go to Main > Flash   and then "Flash Backup"

 

>>  Creation error  "Insufficient free disk space available"

EDIT:

what  other options do i have to backup?  plain copy?

 

Edited May 24, 20233 yr by MrTee

Just copy the /config folder somewhere, everything you need is there.

alright. will do and report back if i find anything conclusive

4 hours ago, JorgeB said:

Backup current flash, re-create with a stock install, then restore the bare minimum from the current config, like the key, super.dat and pools folder, docker templates, there are a few cfg files that should be safe to restore, like network, shares, etc, you can then re-configure the server or restore the rest a few tiles at a time to see if you find the culprit.

 

So that worked. I had an issue with stale config after reboots but a quick look in the forum gave me steps to do. After re assign that works
I kept my shares and docker containers and that's what i cared about.
Getting plugins again is no hassle.

So i figured that the culprit was a product of an old stick/config. I ran this one since 2018 and just updated, changed hardware...

Thanks for all of your help everybody.
I appreciate it!