Beiträge von karnasw

    Ok, wrong docs.

    In salt.states.file (saltproject.io) it's name instead o path. Now deploy works.

    But drive still have Bad health status (with -i or -I parameter):

    Code
    # This file is auto-generated by openmediavault (https://www.openmediavault.org)
    # WARNING: Do not edit this file, your changes will get lost.
    
    DEFAULT -a -o on -S on -T permissive -W 0,0,0 -n never,q
    /dev/disk/by-id/ata-Micron_1100_SATA_256GB_18061B0FF865 -a -i 195

    I created 30micronparameters.sls file:

    Code
    micron_parameters_replace:
      file.replace:
        - path: "/etc/smartd.conf"
        - pattern: "/dev/disk/by-id/ata-Micron_1100_SATA_256GB_18061B0FF865"
        - repl: "/dev/disk/by-id/ata-Micron_1100_SATA_256GB_18061B0FF865 -a -I 195"
        - count: 1
        - backslash_literal: True

    but when I try to deploy I got error:

    In docs I can see that path is a valid argument:

    Code
    salt.modules.file.replace(path, pattern, repl, count=0, flags=8, bufsize=1, append_if_not_found=False, prepend_if_not_found=False, not_found_content=None, backup='.bak', dry_run=False, search_only=False, show_changes=True, ignore_if_missing=False, preserve_inode=True, backslash_literal=False)

    I tried add -i flag for parameter 195 in /usr/local/etc/smartd.conf and this doesn't make diefference.


    I see openmediavault auto generate /etc/smartd.conf, so adding this flag there is pointless.


    # This file is auto-generated by openmediavault (https://www.openmediavault.org)

    # WARNING: Do not edit this file, your changes will get lost.


    DEFAULT -a -o on -S on -T permissive -W 0,0,0 -n never,q

    /dev/disk/by-id/ata-Micron_1100_SATA_256GB_18061B0FF865

    Hi, I have Wyse 5070 and Micron 1100 SSD. Drive is tested on many application including one from drive manufacturer and everything is OK.

    How can I exclude attribute with false positive error from smartctl? Attribute is 195 Cumulativ_Corrected_ECC

    Hi, I have weird problem. I have Raspberry Pi 64-bit installed on USB SSD. For "NAS" data I attached 2 USB drives (2.5 HDD and 3.5 HDD (BTRFS both) with external power supply). When I don't open Web Control Panel everything is ok, after sudo reboot command in SSH Pi reboots in few seconds, but when I open Web Control Panel and view Dashboard with drives status or just view filesystems in menu, after sudo reboot command it hangs on A stop job is running /srv/dev-disk-by-uuid ... after few minutes it turns into BTRFS: error (device sdc1) in write_all_supers:3878: errno=-5 IO failure(errors while submitting device barriers.). What can be wrong?

    Hi, I moved from OMV5 to OMV6. Installed Docker, created user which belongs to group (adm, root, users, sudo) and its PID = 1001 and GID = 100 (users).

    Containers have mapped volumes to my old containers config, but containers don't read them. Also haven't access to write files on drive. "chown -R user:group" didn't helped. Owner and group have r/w rights.

    Hi, I have problem with my HDD mounted in ASM1153 enclosure on my Pi 4B. It freezes after random time. I can't check S.M.A.R.T. in OMV or read any file in SMB or mount point in OS. I have to reboot Pi and then it works for a while and then again freezes. How can I check where is the problem? Because of that my OS shuts down and turns on few minutes.


    I tried to change firmware (ASMT-2115) in enclosure, but I always get fail status in ASMedia MP Tool. Should I try another enclosure? Which one?

    HDD have no sector errors.

    Hi, earlier I had pihole setup like on first post. Now I tried solution with macvlan, it's working but I haven't access to WebGui from Raspberry itself (it's working on other devices in network). What should I change?


    My macvlan configuration:

    IPV4 Subnet - 192.168.162.0/24 IPV4 Gateway - 192.168.162.1

    IPV4 IP range - 192.168.162.11/28 IPV4 Excluded Ips


    and connection to container

    Container Name IPv4 Address

    pihole 192.168.162.11/24