Beiträge von akovia

  • libc6 stuck

    Zitat von ryecoaaron

    if dpkg --configure -a causes a reboot, you likely have file corruption. that will be hard to fix on a running system and assuming the SD card isn't bad. If you have another arm64 linux system that you can chroot to the sd card, that would be the best bet.

    Ok thanks. Was afraid of that.

    Ordering a new card right now.

  • libc6 stuck

    ODroid HC4

    Code
    ~#cat /etc/debian_version
12.5

~#dpkg -l | grep openmediavault
ii  openmediavault                 7.0.5-1                                    all          openmediavault - The open network attached storage solution
ii  openmediavault-flashmemory     7.0                                        all          folder2ram plugin for openmediavault
ii  openmediavault-keyring         1.0.2-2                                    all          GnuPG archive keys of the openmediavault archive
ii  openmediavault-omvextrasorg    7.0                                        all          OMV-Extras.org Package Repositorie

    Not sure when or what exactly happened, but somehow the DNS setting got wiped and I couldn't reach the internet without an ip address.

    After identifying the issue and fixing it, I also found errors in the log about rrdcached records marked in the future. (forgot the exact error) I used omv-firstaid to fix those.

    Then I decided to do updates, but I kept getting 500: internal error messages stating I needed to do a dpkg --configure -a to fix the issue.

    What happens after issuing that command it that it forces a reboot and I'm right back where I started.

    I then have to remove the file locks and temp packages to try the next fix that doesn't work.


    Code
    dpkg --configure -a <-- REBOOTS --> "Setting up libc6:arm64 (2.36-9+deb12u7) ..."
apt-get install -f <-- REBOOTS --> "....1 not fully installed or removed. ....Setting up libc6:arm64 (2.36-9+deb12u7)"
apt-get clean <-- runs, no issues
apt-get update <-- runs, no issues
apt-get autoremove <-- REBOOTS --> "....1 not fully installed or removed. ....Setting up libc6:arm64 (2.36-9+deb12u7)"
apt-get upgrade <-- REBOOTS --> "....1 not fully installed or removed. ....Setting up libc6:arm64 (2.36-9+deb12u7)"
omv-upgrade <-- REBOOTS --> "....1 not fully installed or removed. ....Setting up libc6:arm64 (2.36-9+deb12u7)"
apt-get --fix-broken install <-- REBOOTS "....1 not fully installed or removed. ....Setting up libc6:arm64 (2.36-9+deb12u7)"

    Something went sideways somewhere, but I hadn't been working on anything at all which I don't think is a good sign.

    Is there no other way to get around this broken package?


    Thanks!

  • Incorrect date in OMV?!

    Zitat von SaladCesar

    Update :

    So I've fixed my problem. For an unknown reason, pool.ntp.org isn't working correctly at all for me. I changed to another server, I searched for the closest I could find. If you're in France, you can pick from this list : https://services.renater.fr/ntp/serveurs_francais . time.windows.com also works well. That's strange because pool.ntp.org is supposed to include all those french servers. So I've you're having the same issue, try some other servers.

    Nice!

    That's incredibly odd indeed how it affects different logs differently. Seemingly at random.

    I'll find a another server near me, but I think they might want to think about a different default since this problem has been going on for quite some time now.

    Cheers

  • OMV Syslog wrong time and date

    Any luck MarcS or VaryingLegwarmer?

    I have the same here on two separate installs.


    On my OMV6 install, I've found that the Boot.log and Rsync - Jobs logs report the correct time, but all others are reporting a couple months in the future.

    On my freshly installed OMV7, only Boot & Kernel logs appear to be wrong, and they are a few months in the past.


    Definitely some weirdness going on.

  • Show more results

    Searching didn't return anything meaningful, but I would think this has been asked before.


    Is there any way to return more than 15 results per page? Especially for system logs.

    If I need to do any serious work I'd ssh in, but even looking up some casual information in the system logs requires going through multiple pages of results.


    I was hoping there might be a userscript or some other hack that could increase the number of results.


    Thanks!

  • Upgraded OMV5: Now -> No such file or directory

    Some more info:


    Code
    # cat /etc/exports

# NFSv4 - pseudo filesystem root
/export 192.168.1.0/24(ro,fsid=0,root_squash,no_subtree_check,hide)

# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
/export/MEDIA2 192.168.1.0/24(fsid=b174c796-4f41-4a79-8577-8e56f7b2c296,rw,subtree_check,insecure)
    Code
    # showmount -e localhost

Export list for localhost:
/export        192.168.1.0/24
/export/MEDIA2 192.168.1.0/24




    I haven't used Ubuntu for a decade, but can I roll all of this back?


    Please help.

  • Upgraded OMV5: Now -> No such file or directory

    As it says, I just ran my updates for OMV5 and now I don't have any access to my shares.

    Code
    $ sudo mount -t nfs4 192.168.1.107:/export/MEDIA2 /mnt/NAS/
mount.nfs4: mounting 192.168.1.107:/export/MEDIA2 failed, reason given by server: No such file or directory


    I ssh'd in and my files are there.


    Right after the update my file manager, (thunar) reported stale file handles so I rebooted. This didn't help. I can still mount my other NAS, (OMV4) so I'm pretty sure it's nothing with my machine.


    Here is the email notification I got before upgrading.


    Not sure where to go from here.

  • Can no longer log in to web interface

    This and a reboot seems to have fixed things for now. *crosses fingers*


    I live on an island and power goes out a lot. I'm thinking this was the result of an unclean shutdown due to a power outage where the UPS ran out. It's the only thing that makes sense. Hoping this might help the next person.



    Thanks macom & Soma

  • Can no longer log in to web interface

    So it appears to be corruption.

    Not sure how to fix it yet.


    from dmesg

    Code
    481009.015244] hid-generic 0003:0463:FFFF.0008: hiddev96,hidraw0: USB HID v10.10 Device [EATON Eaton 3S] on usb-xhci-hcd.0.auto-2.1/input0
[548006.693398] EXT4-fs error (device mmcblk0p2): ext4_validate_block_bitmap:390: comm fstrim: bg 5: bad block bitmap checksum
[548006.693540] Aborting journal on device mmcblk0p2-8.
[548006.698797] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[637806.941488] EXT4-fs (mmcblk0p2): error count since last fsck: 1
[637806.941524] EXT4-fs (mmcblk0p2): initial error at time 1630900801: ext4_validate_block_bitmap:390
[637806.941537] EXT4-fs (mmcblk0p2): last error at time 1630900801: ext4_validate_block_bitmap:390

  • Can no longer log in to web interface

    Zitat von Soma

    Doesn't line 61 say Read only OS?

    Seems we posted at the same time.


    I never set anything as read-only. It's just an odroid-hc4 with an micro sdcard in it. The card was perfectly writable before.


    I'm really scratching my head here.


    edit: I see the ro statements now, but I have no recollection of ever explicitly setting them that way, or how to fix this.

  • Can no longer log in to web interface

    I'm also confused about all the messages about being a Read-only file system


    I wanted to try this fix, but it won't allow me.


    Code
    root@ODROID-HC4:~# cp /var/cache/salt/minion/roots/mtime_map /var/cache/salt/minion/roots/mtime_map-OLD
cp: cannot create regular file '/var/cache/salt/minion/roots/mtime_map-OLD': Read-only file system
root@ODROID-HC4:~# cp /var/cache/salt/minion/roots/mtime_map /var/tmp/mtime_map-OLD
root@ODROID-HC4:~# rm /var/cache/salt/minion/roots/mtime_map
rm: cannot remove '/var/cache/salt/minion/roots/mtime_map': Read-only file system

  • Can no longer log in to web interface

    Wasn't sure if I should continue so I'll wait till you say so.

  • Can no longer log in to web interface

    Well it wasn't happy about that.


    Code
    Updating web control panel settings. Please wait ...
{'response': None, 'error': {'code': 0, 'message': '', 'trace': "OMV\\Config\\DatabaseException in /usr/share/php/openmediavault/config/databasebackend.inc:450\nStack trace:\n#0 /usr/share/php/openmediavault/config/databasebackend.inc(230): OMV\\Config\\DatabaseBackend->commit()\n#1 /usr/share/php/openmediavault/config/database.inc(259): OMV\\Config\\DatabaseBackend->replace('//webadmin', Array)\n#2 /usr/share/openmediavault/engined/rpc/webgui.inc(75): OMV\\Config\\Database->set(Object(OMV\\Config\\ConfigObject))\n#3 [internal function]: Engined\\Rpc\\WebGui->setSettings(Array, Array)\n#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)\n#5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\\Rpc\\ServiceAbstract->callMethod('setSettings', Array, Array)\n#6 /usr/sbin/omv-engined(537): OMV\\Rpc\\Rpc::call('WebGui', 'setSettings', Array, Array, 1)\n#7 {main}", 'http_status_code': 500}}
ERROR:

  • Can no longer log in to web interface

    Zitat von macom

    Maybe this helps:

    [How-To] Fix full OS filesystem - GUI login loop

    Thanks for the link, but neither of the solutions work for me.


    I have plenty of space.

    and neither a hard refresh or private window seemed to have any effect.


    any other thoughts?

  • Can no longer log in to web interface

    I am trying to connect a windows machine to map a drive to my nas, but when I went to log into my OMV5 WebGUI, it just takes my credentials and realods the page.


    Thinking I entered the wrong credentials, if I tried anything else I would get an error message stating the wrong user/password.


    I haven't updated anything since my last login, so I really don't know what this could be. I also tried from other machines on the network and I get the same result.


    I get still access via SSH though.


    Please help