cholzer

Members
 View Profile  See their activity

  • Posts

    164

  • Joined

  • Last visited

 Content Type 

Posts posted by cholzer

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted · Edited by cholzer

    Is it possible to ssh into unraid and then remotely call UD to unmount or mount a disk?
     

    I did take a look at the scripts in the first post but these dont seem to hold the answer. 😅

     

    Reason for my question is that as it truns out I run into several issues with the SMB share creation/destruction when I remotely SSH into unraid and then just mount/unmount the disk.

    These problems do not exists when I use the "mount" button in the UD gui, so I guess the solution would be to call UD remotelly via SSH and let it do the mount/umount. But how?

    Thanks in advance!

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    3 hours ago, dlandon said:

    Your script can do an unmount when it is done, or you can unmount the disk with a User Script on a cron.  Go to the UD page and click on the help icon and read about using the UD script to mount and unmount the disk.  The problem with the cron is that you'd also need to confirm it got unmounted or you'll be back in the same pickle.

     

    I noticed that it can sometimes take 60 seconds or more for the SMB share to get accessible after the disk has been mounted.

    Is that.... normal? 😅

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    44 minutes ago, dlandon said:

    You can't get Linux to unforget the disk.  If it's properly unmounted, there is no problem.  Don't remove it until it is unmounted.  If it's not unmounted before removal, you risk data loss/corruption.

    Thx!

    I found a way to have Veeam Backup & Replication remotely mount the disk via ssh before the backup starts
    then then unmount it once the backup is done. :)

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    21 minutes ago, dlandon said:

    Your script can do an unmount when it is done, or you can unmount the disk with a User Script on a cron. 

    thx!

    Ideally I would have Veeam Backup & Replication SSH into unraid, ensure that the disk is mounted before the backup and unmount it when its done.
    But I need to see if I can execute that pre/post backup job. (ESXi is on a different machine - Unraid is 'only' used to store onsite backups and as 'provider' for the offsite backup media)

     

    As a quick solution I have now created a userscript to unmount the disk - scheduled to run ~2hours after the backup task is always finished. This worked nicely in my test! :)

    I assume there is no way how I could have a cron job run sometime at night to let Unraid/Linux forget that a disk was safely removed - in case that this would happen at some point - so that a reboot isnt required.
     

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    2 minutes ago, dlandon said:

    This happens when the disk is removed without being unmounted first.  When it is re-installed, Linux assigns a new sdX designation.  Unraid does not see the new disk as an Unassigned DIsk and UD thinks it's a disk that fell out of the array.

     

    You'll need to reboot to clear it up.


    Thank you! I will reboot and see what happens.

    Is there a way to have a cron job unmount the disk?

    I'd like to have this offsite-backup as "end-user" proof as possible. Which means I do not want to unmount it manually every Monday evening before it gets unplugged. 😅

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted · Edited by cholzer

    I'm building a new NAS and I have a reeeeeeally funky issue.

    Unraid 6.9.2
    The Array consists out of 3x 4TB Seagate Ironwolf's and a 120GB Plextor SSD Cache. But that has nothing to do with the funky stuff.

     

    I have 2x 2TB Seagate Compute drives, these are used for off-site backups.

    The usecase is this:

    1. Monday morning 2TB Seagate Compute "A" is plugged in, auto mounted and SMB shared by UD
    2. later that day a backup is executed on a different system which stores the backup on that disk/share
    3. Monday night 2TB Seagate Compute "A" is disconnected and stored off site
    4. Next week on Monday morning 2TB Seagate Compute "B" is plugged in, auto mounted and SMB shared shared by UD
    5. later that day a backup is executed on a different system which stores the backup on that disk/share
    6. Monday night 2TB Seagate Compute "B" is disconnected and stored off site
    7. etc.....

    Now here is the funky part:

    1. I connected 2TB Seagate Compute "A", configured auto mount and auto share in UD
    2. disconnected 2TB Seagate Compute "A"
    3. I connected 2TB Seagate Compute "B", configured auto mount and auto share in UD
    4. disconnected 2TB Seagate Compute "B"

    Whenever I now connect either 2TB Seagate Compute "A" or "B" I get this greyed out "ARRAY" button in UD and the disk is not shared 😬🙃🤪

     

     

    Array.jpg

     

    I connected the drives to a different machine and deleted the partition. Yet they still show up with that greyed out "ARRAY" button in UD.

    Below is the log taken when I connected one of the drives while it had no partition anymore. It complains about a mismatch in line 4 as if it does not like that different disks get connected to that sata port.

      

    Mar 31 13:56:32 NAS kernel: ata6: SATA link down (SStatus 0 SControl 300)
Mar 31 13:56:42 NAS kernel: ata6: link is slow to respond, please be patient (ready=0)
Mar 31 13:56:44 NAS kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 31 13:56:44 NAS kernel: ata6.00: serial number mismatch ' WFL3RRLV' != ' WFL2P4XZ'
Mar 31 13:56:44 NAS kernel: ata6.00: revalidation failed (errno=-19)
Mar 31 13:56:44 NAS kernel: ata6: limiting SATA link speed to 1.5 Gbps
Mar 31 13:56:49 NAS kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Mar 31 13:56:49 NAS kernel: ata6.00: serial number mismatch ' WFL3RRLV' != ' WFL2P4XZ'
Mar 31 13:56:49 NAS kernel: ata6.00: revalidation failed (errno=-19)
Mar 31 13:56:49 NAS kernel: ata6.00: disabled
Mar 31 13:56:55 NAS kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 31 13:56:55 NAS kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Mar 31 13:56:55 NAS kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Mar 31 13:56:55 NAS kernel: ata6.00: ATA-10: ST2000DM008-2FR102, WFL2P4XZ, 0001, max UDMA/133
Mar 31 13:56:55 NAS kernel: ata6.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Mar 31 13:56:55 NAS kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20200925/psargs-330)
Mar 31 13:56:55 NAS kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Mar 31 13:56:55 NAS kernel: ata6.00: configured for UDMA/133
Mar 31 13:56:55 NAS kernel: ata6.00: detaching (SCSI 7:0:0:0)
Mar 31 13:56:55 NAS kernel: sd 7:0:0:0: [sdl] Synchronizing SCSI cache
Mar 31 13:56:55 NAS kernel: sd 7:0:0:0: [sdl] Stopping disk
Mar 31 13:56:55 NAS unassigned.devices: Reload: A udev 'remove disk' initiated a reload of udev info.
Mar 31 13:56:55 NAS unassigned.devices: Updating udev information...
Mar 31 13:56:55 NAS unassigned.devices: Udev: Update udev info for /dev/disk/by-id/ata-ST2000DM008-2FR102_WFL3RRLV.
Mar 31 13:56:55 NAS unassigned.devices: Udev: Update udev info for /dev/disk/by-id/wwn-0x5000c500cf867c17.
Mar 31 13:56:55 NAS kernel: scsi 7:0:0:0: Direct-Access ATA ST2000DM008-2FR1 0001 PQ: 0 ANSI: 5
Mar 31 13:56:55 NAS kernel: sd 7:0:0:0: Attached scsi generic sg6 type 0
Mar 31 13:56:55 NAS kernel: sd 7:0:0:0: [sdl] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Mar 31 13:56:55 NAS kernel: sd 7:0:0:0: [sdl] 4096-byte physical blocks
Mar 31 13:56:55 NAS kernel: sd 7:0:0:0: [sdl] Write Protect is off
Mar 31 13:56:55 NAS kernel: sd 7:0:0:0: [sdl] Mode Sense: 00 3a 00 00
Mar 31 13:56:55 NAS kernel: sd 7:0:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 31 13:56:56 NAS kernel: sdl:
Mar 31 13:56:56 NAS kernel: sd 7:0:0:0: [sdl] Attached SCSI disk
Mar 31 13:56:56 NAS unassigned.devices: Hotplug: A udev 'add disk' initiated a Hotplug event.
Mar 31 13:56:56 NAS unassigned.devices: Updating udev information...
Mar 31 13:56:56 NAS unassigned.devices: Udev: Update udev info for /dev/disk/by-id/ata-ST2000DM008-2FR102_WFL2P4XZ.
Mar 31 13:56:56 NAS unassigned.devices: Udev: Update udev info for /dev/disk/by-id/wwn-0x5000c500cf6a8b34.
Mar 31 13:56:59 NAS unassigned.devices: Processing Hotplug event...

     


    but even when I connect one of the drives to a different SATA port now it still shows up with that greyed out "array" button and shows that "mismatch" error in the log.
      

    Mar 31 14:01:33 NAS kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 31 14:01:33 NAS kernel: ata3.00: serial number mismatch ' WFL2P4XZ' != ' WFL3RRLV'
Mar 31 14:01:33 NAS kernel: ata3.00: revalidation failed (errno=-19)

     

    EDIT!

    Now it gets even funky'er!!! 🤣

    If I do the exact same thing with these 2 disks:

    • HGST_HDS724040ALE640
    • dev3HGST_HDS724040ALE640

    Then it works just fine!

    Only with the 2 ST2000DM008-2FR102 it does not work and I run into this greyed out "ARRAY" button. :)

    [Notification Settings] expose 'chatid' in Telegram agent configuration

    in Feature Requests

    Posted

    The Telegram agent is extremely useful!
    However if you'd like to have the agent send messages to a telegram group then the agent needs to know the ChatID of that telegram group.

     

    Currently you have to use the terminal for that. 

    cd /boot/config/plugins/dynamix/telegram
nano chatid


    Please expose a 'chatid' field in the Configuration of the Telegram Agent to make this process more user friendly. :)

    @limetech

    • Like 1
    • Upvote 1

    Telegram Bot GROUP notification

    in General Support

    Posted

    Hey everyone!

     

    I just got the Telegram Agent to work.
    However we are 2 admins and we'd both like to get notifications via telegram from UNRAID.
    Is it possible to have the telegram Agent send messages to a telegram group? I could not figure it out. 😅

    Thanks in advance!

    USB creator not seeing USB drive.

    in General Support

    Posted · Edited by cholzer

    How can this still be am issue?

    I am about to setup an UnRAID machine for a friend and I ran into the exact same problem that this garbage USB creator does not detect ANY of the 10 different drives I tried.

    The manual method created a working USB drive that this UnRAID machine now runs on (so my sandisk usb drive is okay) but c'mon @limetech !!!
    Fix that USB creator!!!!

    This is a HORRIBLE first impression for anyone who considers trying UnRAID!!!

    What HBA to choose these days?

    in Hardware

    Posted · Edited by cholzer

    On 1/15/2021 at 3:32 PM, JorgeB said:

     

    9300-8i is IT mode only, and a good option, though SSD needs to support deterministic read after trim or it won't be trimmed.


    Ah so if I would not have bought an LSI SAS 3008 and instead went straight for an 9300-8i then I would not have had to flash the IT BIOS?

    Cool, great to know!

    So you would still go for an 9300-8i in 2021, right?

    What HBA to choose these days?

    in Hardware

    Posted · Edited by cholzer

    I am building an Unraid system for a friend and I was wondering which HBA to choose.

    It has to support (up to) 7 HDD's and 1 SSD (cache)

    If possible I'd like to avoid the stressful experience I had with switching/flashing my SAS 9300-8i to IT-Mode 😅

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted · Edited by cholzer

    4 minutes ago, dlandon said:

    Look at the log.  The disk is probably being mounted read only.  This can happen with some NTFS formatted disks.

     

    That only applies to XFS formatted disks.

    Thank you!
    I was only looking at the log next to the disk in UD which did not show anything. Looking at the correct log I guess there is indeed something wrong with that partition. I did shutdown the PC as usual though before I removed it. Well... lets investigate. O.o
      

    Dec 30 22:17:36 NAS unassigned.devices: Mount warning: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Falling back to read-only mount because the NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting.)

     

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    RC2 with 2020.12.19

    For a long time I used UD to share a 6TB drive, which was previosuly used in a Windows PC and only contains a single NTFS partition.
    That drive/smb share still works nicely! 👍

    However today I added a 512GB SSD (using the same settings in UD as the 6TB drive).
    When I access that share from a Windows PC it tells me that it is "write proteced"!?!?
    Even though "read only" is not enabled in UD.
    The settings are identical to the 6TB drive and the same SMB user is used as for the 6TB drive. O.o

    Another thing I just noticed is that the "Change Disk UUID" dropdown list in the UD settings is empty.

    ReadOnly.jpg

    write protected.jpg

    Dynamix - V6 Plugins

    in Plugin Support

    Posted · Edited by cholzer

    Cache Plugin

    Seems like the "include folders" feature does not support folders that use a &

     

    Fotoalbum Anita & Chris

    Software & Resources 

    Dec 15 07:37:52 NAS cache_dirs: ERROR: included directory 'Fotoalbum\ Anita\ &\ Chris' does not exist.
Dec 15 07:37:52 NAS cache_dirs: ERROR: included directory 'Software\ &\ Resources' does not exist.

    Could the plugin support that in the near future? :)

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    Hi there! :)

    My "unassigned devices" hdd does not spin down automatically while the array devices spin down nicely (see attached image).

    • Cache Dir Plugin uses "include" folders as recommended.
    • Updated all plugins to the latest version.
    • All drives connected to the same HBA

    you can spin down/up the array devices by clicking on the dot left to the disk#, could that functionality be added to the unassigned devices plugin where clicking on the icon does nothing. :)

     

    1536981479_unassigneddevices.thumb.jpg.792a69e4141379a56a07538a8eef239b.jpg

     

    how to transfer unraid array to a new PC?

    in General Support

    Posted

    Hi guys!

    I have a rather scary task ahead of me. 😬

    My current config:
    - core i5 system on an Asus mainboard, 8GB
    - LSI 9200-8i (IT-Mode)
    --- 1x 8GB Ironwolf Parity
    --- 4x 6GB Ironwolf Data

    - 1x 120GB SSD Cache (no dockers, no VM)

    Now I want to only move my Ironwolf HDD's and the unraid USB stick to a new system:
    - Xeon E5-2620, Supermicro X10SRi-F, 32GB
    - LSI 9300-8i (IT-Mode)
    - 1x 500GB SSD Cache

    Am I correct that this should basically be "plug and play"?
    unraid should boot up and the array should be present (minus the cache SSD which I will replace with a new one)

    Anything special that I have to pay attention to? 😅

    Thanks in advance!