Beiträge von tdriver

ok, thank you all. i change this thread to resolved.

should i wait for an update then, or edit zed.rc ?

i found this on another site ,not sure if its legit :

"un-plugging a drive to make it degraded?
zed, for whatever reason percieves the sys-admin removing drives as not a zfs fault and thusly doesnt send emails"

same here:

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

ZED_EMAIL_ADDR=me@mail.gr
ZED_NOTIFY_INTERNAL_SECS=3600

yes, i have. i get other messages ,eg. updates etc.

i reposted the correct one above.

sorry my bad.

fwiw, this install was via omv-regen, a couple of months ago.

deleted

it is installed. openmediavault-zfs 6.0.14.

no i don't have this option.

hello,

a data cable from one hdd of a 2-disk mirror came off (don't ask me how), and the status of my nas was degraded for weeks...... until i found out by accident.

it did not show any alert or mail to fix this early on, so I may have just been lucky to find this before anything serious happened......

why didn't i get any alert ?

how can i include this kind of error to get an email ?

thank you in advance.

Zitat von chente

...

There must be another factor that has made a difference. ..

yes there is, but what....

i just regenerated the old "bad" orb-backup with kernel and it finished correctly.

since the "bad" one worked the first time, i won't bother to test more.

everything works, so all good. if something similar happens in the future, i just retry until it works.

btw,

the apt-tool installed everything there was by itself ! good work chente !

no difference were in config.xml .

Zitat von chente

What makes you think that this backup was corrupt? Just because of the result of regeneration or something else?

yesterdays orb-backup was regenerated 5-6 times, half of them with kernel regeneration. when kernel was included, regen stopped at the known spot ( previous screenshoot ) , without kernel omv-regen finished, but with that error in docker.

todays orb-backup finished successfully with kernel.

i will do both again, multiple times later this evening.

if there is anything else i should do to find the culprit let me know.

Zitat von chente

I still don't understand how a corrupt backup can cause the proxmox kernel to not be installed correctly. This makes no sense.

me too, it's just a txt file, i will regen both ,the bad and the good again, later today, just to be sure it is nothing randomly.....

I copy the backup to the new system via winscp.

contents of ORB_Unamea :

Linux nas 6.2.16-20-bpo11-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-20~bpo11+1 (2023-12-01T14:42Z) x86_64 GNU/Linux

contents of ORB_Dpkg is too long, adding attachment.

ORB_Dpkg.txt

i'm checking the config.xml right now.

first of ,thank you all for your help.

i resolved the issue by creating a new orb-backup. afaik, the old (just yesterday) orb-backup must be corrupted somehow. i did more regenerations (same orb), all with the same error ,so i re-created a new orb-backup ,and voila even with kernel no error or stopping mid way !!

the only thing i have to do usually ,is to reinstall whatever is in apt-tool. (no big deal).

one question though, if i keep a good orb-backup for longer time, and regenerate it, what will the worst case scenario be ? just some newer versions plugins missing?

chente

did another omv-regen, this time with kernel. again it stopped mid way. here is a screenshoot.

to be more precise, and if gpt/mbr is irrelevant, the only thing changed in docker is: i added persistent volumes in /var/lib/docker/volumes (rootfs)

and also did docker backups via schedule on the pool , which btw are not there (in restore) . empty and same error ones opening the page.

(booting with original disk everything works)

Zitat von chente

It would be helpful to see the shell output at the time of the error to know what is happening.

tell me exactly where and what you want and i will send it when this happens again.