Posts by JackElliott

    Thank you.


    For ACL I find on the drive's root:

    Code
    $ getfacl /srv/dev-disk-by-uuid-1d4d5a04-39e8-4c30-8518-15271f3d1f43
    getfacl: Removing leading '/' from absolute path names
    # file: srv/dev-disk-by-uuid-1d4d5a04-39e8-4c30-8518-15271f3d1f43
    # owner: root
    # group: root
    user::rwx
    group::r-x
    other::r-x

    For the shared folder I find:

    I'm not used to dealing with ACLs. I see "-s-" in the "flags" line. Set SETUID is set, deeper reading than I have time for right now.

    Code
    $ sudo setfacl -b -R /srv/dev-disk-by-uuid-1d4d5a04-39e8-4c30-8518-15271f3d1f43
    [sudo] password for jack:
    $ client_loop: send disconnect: Connection reset

    I got kicked off. So ssh back in and,

    Code
    $ sudo chmod -R 775 /srv/dev-disk-by-uuid-1d4d5a04-39e8-4c30-8518-15271f3d1f43/BMP

    Nothing has changed, so I'm not quite sure what, if anything, setfacl did. Moving on,

    Code
    $ sudo chmod -R 775 /srv/dev-disk-by-uuid-1d4d5a04-39e8-4c30-8518-15271f3d1f43/BMP
    $ ls -la /srv/dev-disk-by-uuid-1d4d5a04-39e8-4c30-8518-15271f3d1f43/BMP
    total 2112704

    Then,


    Well, do I now have write permissions as non-sudo/root? Let's test:

    Code
    $ touch temp2
    $ ls
    '00 KPOV'      DS_Homes_Backup                        'My Books'                    inMotrion.xgeq
    0_Household  'Desktop - Shortcut.lnk'                'Plex Media'                  linuxmint-20.2-cinnamon-64bit.iso
    Audio_Tools  'KPOV FB TSC masked and stickered.png'  'System Volume Information'   temp
    Classics      LinXPS_Home_Jack                       'VST Plugins'                 temp2
    $


    Couldn't do that before without sudo, AND it works from within Windows File Explorer: I can now copy/paste to the share.


    I think you folk have cracked the case here.


    I canse anyone is wondering how I got myself into this pickle, I let OMV wipe, mount a new disk, and copied all my files from an NTFS disk (created on a Linux machine) temporarily mounted on /media to the OMV share with cp -R


    Probably not the cleanest way to do it, but I'm no wizard at these things.


    Thank you! :) (How do I mark this as "solved"?)

    Thank you -- here is what I see:


    The root folder is bmp, it is the shared folder

    Code
    $ ls -la
    total 44
    drwxr-xr-x   4 root root   4096 Nov 26 11:31 .
    drwxr-xr-x   6 root root   4096 Nov 26 11:19 ..
    drwxrwsrwx+ 12 root users  4096 Nov 27 13:06 BMP
    -rw-------   1 root root   6144 Nov 26 11:20 aquota.group
    -rw-------   1 root root   7168 Nov 26 11:20 aquota.user
    drwx------   2 root root  16384 Nov 26 11:06 lost+found

    Dipping down into /bmp is this:


    "temp" (above) is the file I tried to write as user "jack" then had to sudo to do it. See my OP.


    Thank you for looking at this.

    This is a new OMV installation that I built following this guide: https://wiki.omv-extras.org/do…talling_omv5_raspberry_pi


    I am experiencing a problem where I cannot write to the shared folder (or subfolders) from Windows 10 File Explorer from ssh'd Terminal as my username.


    From Terminal I see this:

    Code
    $ touch temp
    touch: cannot touch 'temp': Permission denied
    $ sudo touch temp
    [sudo] password for jack:
    $

    My OMV user "jack" is a member of Groups _crony, adm, root, ssh, sudo and users.


    The same problem when attempting to write using Windows File Explorer. I mapped my drive Z: to the OMV shared folder, and connected using my OMV username ("jack") and password. But cannot write.


    How can I set the OMV permissions for the shared folder and subfolders to gain read/write priviledges for any member of the Group users?


    Let me know if you need screenshots or whatever. Thank you!

    Hi, I just installed OMV on a Raspberry Pi 3B+ and configured it with shared drives and it was working beautifully. I closed the WebGUI browser window (doing a little housekeeping) and reopened it and all I see is a sky-blue background. I had an open ssh connection and it was fine, so I used it to reboot the OMV and after it rebooted it came up again with a plain sky-blue background. I reconnected with ssh and from the terminal it doesn't look like there is any problem. The network shares are available, just no way to get to the WebGUI Dashboard. I'm stumped.

    Hi,


    Raspberry Pi 3+B, OMV 6.0.4-2 (Shaitan), Linux 5.10.63-v7+, single HDD: WD My Passport 25E2


    I just installed OMV per the instructions here: https://www.techradar.com/how-…-raspberry-pi-nas-1315968 and the installation went in smooth as silk.


    I can log into my user share in File Explorer on my Windows 10 laptop. There's nothing to see because there are no files or folders on the HDD yet. But I can't put any there (copy/paste), it seems to be acting read-only. There is a shared folder on the HDD, and my user permissions under User Management > Users > Privileges are read/write, read-only, no access (in that order, left-to-right), and my Group memberships are openmediavault, sudo, users.


    How can I get write privileges?


    Thank you.

    Code
    $ sudo echo 'exit 0' >> /etc/cron.daily/monitor-raspi-health                                                                                
    -dash: 44: cannot create /etc/cron.daily/monitor-raspi-health: Permission denied                                                            
    $ ls -l /etc/cron.daily/monitor-raspi-health                                                                                                
    -rwxr-xr-x 1 root staff 273 Jul 14 04:32 /etc/cron.daily/monitor-raspi-health
    Code
    $ cat /etc/cron.daily/monitor-raspi-health                                                                                                  
    #!/bin/bash                                                                                                                                 
    export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin                                                                    
    sleep 10                                                                                                                                    
    Health=$(perl -e "printf \"%19b\n\", $(vcgencmd get_throttled | cut -f2 -d=)")                                                              
    grep -q 1 <<<${Health} && echo -e "$(date)\t$(printf "%019d" ${Health})" >>/var/log/raspihealth.log

    Indeed, my apologies. Yes, a Raspberry Pi; yes, we are talking about USB-attached drives; and yes there exists sda and sdb. Scary that I didn't think to provide that information, or a scary configuration?


    Anyway, thank you for persevering. In response to your suggestions:


    Code
    $ sudo armbianmonitor -u                                                                                                                    
    [sudo] password for jack:                                                                                                                   
    /var/log/armhwinfo.log has been uploaded to http://sprunge.us/cCKe                                                                          
    Please post the URL in the Armbian forum where you've been asked for.


    For your suggested smartctl loop, the forum isn't letting me post the output, "the message is too long, must be under 10,000 characters". This from posting the output into a Code box. Can I p-mail the output to you?



    PS. Apology for the double-post of the original post. I received a "fatal error" message in the browser from the forum when I first posted the topic. And it didn't appear, so I re-posted. Received the fatal error msg again, shrugged and crossed fingers.

    "I'm getting this emailed alert:

    In the webgui, under Storage > S.M.A.R.T. > Devices, dev/sdc has a red dot in its Status column.


    The Information > Attributes tab for that device shows "Raw_Read_Error_Rate," and "Seek_Error_Rate," and "Spin_Retry_Count" all with green Status dots, "Reallocated_Sector_Ct" with a red status dot, and all of the other attributes are grayed out.


    So it appears that at least some SMART attributes are being monitored (should I be worried about the Reallocated_Sector_Ct status?).


    The Self-Test Logs show only "Completed without error" statuses. I can't read all the data in the log because there doesn't appear to be a way to make some of the columns labeled "Rem..." and "Life..." wide enough to read the full strings.


    So . . . what's going on? Is SMART working or not? The Extended Information says "SMART support is: Available - device has SMART capability.
    SMART support is: Enabled."


    So I don't know why I am getting an email saying the drive doesn't support SMART, and I am wondering whether the drive is failing.


    Any insight would be appreciated! Thank you.