hope I'm not too annoying and can help you find the error.
You found a bug. That is not annoying and is helpful.
hope I'm not too annoying and can help you find the error.
You found a bug. That is not annoying and is helpful.
Hi heute habe ich ein neues problem mit der neuen Version von Snapraid. Ich habe ein paar "Data error in file" bekommen und wollte dies wie früher immmer möglich in der konsole mit:
Use 'snapraid status' to list the bad blocks.Use 'snapraid -e fix' to recover them.Use 'snapraid -p bad scrub' to recheck after fixing.[tt]
[/tt]
beheben. leider geht das in der neuen Snapraidversion nicht mehr
evtl muss hier die ausgabe der Mail gleich mit den passenden Befehlen angepasst werden.
Gruß
Markus
On OMV 7.x, snapraid supports multiple arrays. When you run a command from the command (there is a status button in the plugin), you need to specify the config file for that array from /etc/snapraid/.
As an example:
sudo snapraid -c /etc/snapraid/omv-snapraid-193819d0-f5b1-4926-9ccc-d56c877a4335.conf status
Do you have to use the -c /path/to/conf for all commands? Like diff, sync, scrub? Otherwise snapraid wouldn't know which array it's working with, right?
Do you have to use the -c /path/to/conf for all commands?
Yes. snapraid without the -c argument will look for /etc/snapraid.conf which the plugin is not creating/maintaining anymore.
Otherwise snapraid wouldn't know which array it's working with, right?
Yes.
I use the command line exclusively for managing snapraid. To make things easier, can I link the conf to a more friendly filename?
I use the command line exclusively for managing snapraid.
Why use the plugin?
To make things easier, can I link the conf to a more friendly filename?
Sure, I don't think snapraid cares. If you only have one array, you could symlink it back to /etc/snapraid.conf to eliminate needing to pass the -c parameter at all (I think but I didn't test).
I use the plugin for configuring the array. Daily tasks like diff, sync, scrub, status I find easier to do via ssh terminal.
I just added code that will create a symlink to each array's config file using the array's name. I tested using the symlink from the command line and it works as expected.
Was bedeutet das jetzt? Ich weiß leider nicht was ein Symlink ist oder ob ich jetzt etwas zu tun habe?
Gruß & Vielen Dank
Markus
Was bedeutet das jetzt? Ich weiß leider nicht was ein Symlink ist oder ob ich jetzt etwas zu tun habe?
There is nothing you need to do. It is just an additional way to access the array's config file.
A symlink is:
QuoteA symbolic link, or symlink, creates a name that references another file, directory, or other Linux file system object. Using symlinks minimizes the necessity of having multiple copies of a file within a system. Any changes can be made in one place, instead of modifying many copies.
I just added code that will create a symlink to each array's config file using the array's name. I tested using the symlink from the command line and it works as expected.
I just migrated my omv 6 systems to 7. I noticed that after migrating /etc/snapraid.conf still exists and snapraid commands work the same as before. I assume this is because I haven't made any configuration changes to the array? If I do, the plugin will update /etc/snapraid/array1.conf, correct? Maybe I should delete /etc/snapraid.conf...
I just migrated my omv 6 systems to 7. I noticed that after migrating /etc/snapraid.conf still exists and snapraid commands work the same as before. I assume this is because I haven't made any configuration changes to the array? If I do, the plugin will update /etc/snapraid/array1.conf, correct? Maybe I should delete /etc/snapraid.conf...
The plugin being upgraded to v7 upgrades the database and runs the saltstack code. So, the config file in /etc/snapraid/ should already exist.
I would delete /etc/snapraid.conf because it won't be maintained anymore. But I don't know what you do outside the plugin to know if something else will break.
The plugin being upgraded to v7 upgrades the database and runs the saltstack code. So, the config file in /etc/snapraid/ should already exist.
I would delete /etc/snapraid.conf because it won't be maintained anymore. But I don't know what you do outside the plugin to know if something else will break.
Yep the .conf files exist in /etc/snapraid/
Just letting you know that /etc/snapraid.conf was not removed and I don't know if the upgrade was supposed to do that. I think i'll remove it and start using "-c array1.conf" in my commands.
Just letting you know that /etc/snapraid.conf was not removed and I don't know if the upgrade was supposed to do that.
There is nothing in the code that removes it.
There is nothing in the code that removes it.
OK. I guess it would only be an issue if people run snapraid from the terminal like me. People running it from the web interface should have no issue. And for me it's not an issue until I would make a change to the array.
OK. I guess it would only be an issue if people run snapraid from the terminal like me. People running it from the web interface should have no issue. And for me it's not an issue until I would make a change to the array.
Why not change your command line commands to use -c and the path to the new config file?
Why not change your command line commands to use -c and the path to the new config file?
Yep, I'm doing that once I became aware of the situation. I'll probably just mv snapraid.conf snapraid.conf.deprecated or something like that to prevent accidental usage. Just wanted to make you aware of the potential for folks to use the wrong snapraid conf after upgrading. (only nerds like me that use terminal a lot though)
Don’t have an account yet? Register yourself now and be a part of our community!