lurkio

Members
  • Posts

    32
  • Joined

Posts posted by lurkio

  1. I had a failure that caused me to rebuild my array on new disks. I noticed that I have two user folders, /mnt/user and /mnt/user0. It's more confusing to me that neither is really identical to /mnt/disk1 (the only data drive). Can someone help me understand better what /mnt/user is meant to represent? Thanks

     

    root@Unraid:/# ls -lah /mnt/user
    total 12K
    drwxrwxrwx  1 nobody users  273 May 17 04:40 ./
    drwxr-xr-x 10 root   root   200 May 11 22:42 ../
    drwxr-xr-x  1 nobody users  184 May 11 10:36 3d_printing/
    drwxr-xr-x  1 nobody users 4.0K Apr 27 15:35 appdata/
    drwxr-xr-x  1 nobody users 4.0K May 11 11:07 audio_books/
    drwxr-xr-x  1 nobody users  289 May 11 12:40 backups/
    drwxr-xr-x  1 nobody users 4.0K May 11 14:47 ebooks/
    drwxr-xr-x  1 nobody users  316 Mar 31  2022 isos/
    drwxr-xr-x  1 nobody users   47 Aug 25  2022 kiwix-zims/
    drwxrwxrwx  1 nobody users   19 May  8 21:14 paperless/
    drwxr-xr-x  1 nobody users   76 May 25  2021 personal_storage/
    drwxr-xr-x  1 nobody users   29 May 11 16:18 plex/
    drwxr-xr-x  1 nobody users   35 May 10 21:26 system/
    drwxr-xr-x  1 nobody users   54 May 12 12:27 temp/
    drwxr-xr-x  1 nobody users    6 Jun  8  2021 unassigned/
    drwxr-xr-x  1 nobody users  184 Jun 14  2022 win_tools/
    root@Unraid:/# ls -lah /mnt/user0
    total 8.0K
    drwxrwxrwx  1 nobody users  273 May 17 04:40 ./
    drwxr-xr-x 10 root   root   200 May 11 22:42 ../
    drwxr-xr-x  1 nobody users  184 May 11 10:36 3d_printing/
    drwxr-xr-x  1 nobody users 4.0K May 11 11:07 audio_books/
    drwxr-xr-x  1 nobody users  289 May 11 12:40 backups/
    drwxr-xr-x  1 nobody users 4.0K May 11 14:47 ebooks/
    drwxr-xr-x  1 nobody users  316 Mar 31  2022 isos/
    drwxr-xr-x  1 nobody users   47 Aug 25  2022 kiwix-zims/
    drwxr-xr-x  1 nobody users   64 May  8 21:14 paperless/
    drwxr-xr-x  1 nobody users   76 May 25  2021 personal_storage/
    drwxr-xr-x  1 nobody users   29 May 11 16:18 plex/
    drwxr-xr-x  1 nobody users   21 May 10 21:26 system/
    drwxr-xr-x  1 nobody users   54 May 12 12:27 temp/
    drwxr-xr-x  1 nobody users    6 Jun  8  2021 unassigned/
    drwxr-xr-x  1 nobody users  184 Jun 14  2022 win_tools/
    root@Unraid:/# ls -lah /mnt/disk1/
    total 8.0K
    drwxrwxrwx 15 nobody users  273 May 17 04:40 ./
    drwxr-xr-x 10 root   root   200 May 11 22:42 ../
    drwxr-xr-x  5 nobody users  184 May 11 10:36 3d_printing/
    drwxr-xr-x 20 nobody users 4.0K May 11 11:07 audio_books/
    drwxr-xr-x 14 nobody users  289 May 11 12:40 backups/
    drwxr-xr-x 22 nobody users 4.0K May 11 14:47 ebooks/
    drwxr-xr-x  2 nobody users  316 Mar 31  2022 isos/
    drwxr-xr-x  2 nobody users   47 Aug 25  2022 kiwix-zims/
    drwxr-xr-x  5 nobody users   64 May  8 21:14 paperless/
    drwxr-xr-x  4 nobody users   76 May 25  2021 personal_storage/
    drwxr-xr-x  3 nobody users   29 May 11 16:18 plex/
    drwxr-xr-x  3 nobody users   21 May 10 21:26 system/
    drwxr-xr-x  5 nobody users   54 May 12 12:27 temp/
    drwxr-xr-x  2 nobody users    6 Jun  8  2021 unassigned/
    drwxr-xr-x  5 nobody users  184 Jun 14  2022 win_tools/

     

  2. I have the two shucked drives back in their enclosures and the broken sata connector appears to be working for the moment. However, when I attach them to unraid via usb neither of them appear to be the XFS formatted data drive. That seems strange, right? I have done nothing to these besides moved them. They were removed from a working installation, I saw the data drive had the broken connector and set them both aside, deciding instead to replace them and fix the array later if I could. 

    Screenshot 2023-05-09 194750.jpg

  3. This array consisted of only two drives, 1 parity 1 data. I still have both drives, but I've created a new array config with two new drives with that thumb drive.

    The question becomes; if I use a fresh unraid usb stick and add "only" the parity drive can I start an array (zero data drives present). I think the answer is no. I have run fully on parity before, with the sole data drive dead (in a past array, not part of the failed one I am talking about here), unraid was able to emulate what the data should be from parity.

  4. I was migrating towers and realized I broke the sata connector OFF my 8TB data drive. To complicate the situation these are shucked drives and dont power up with the newer power supply (known issue with shucked drives). I still have the parity drive, sound and healthy, but I'm in a pickle now. Because I have folks that use my VM's and dockers for services like Bitwarden (and as the data runs off the cache drive) I went ahead and ordered two new 8TB drives off amazon same day so I could get the rest of it back online. So, unraid is up, without my old data.

    I "think" I can take the board off my parity drive, put it on the data drive (they are identical, from the same batch), then attach that drive to any linux system and copy the data to the new array as it's XFS. I think. I havent tried that yet because I dont want to make this worse. I've tried to glue the connector back on, because the pins appear to be fine, but it's just not working.

     

    If I make another temporary unraid usb and use the working parity drive in the old tower as a new array would I still be able to copy the data off? Can you start the array without a data drive, I assume the answer is no? Help
     

  5. It's an old gen 3 i7. My experience is the same as yours, works better before you slice the model. It is definitely still usable. Sounds like I'd need to add a GPU which may not be worth it for that box, I'm using Plex on another system so it really doesnt need it otherwise.

  6. About every 18 seconds two 10-12 second processes kick off, and they cause 25-35% cpu utilization. I have disabled docker, removed plugins, and watched processes, etc. There have been a few red herrings, like file activity viewer that was enabled. So far I see only one culprit that matches the timing but I can't figure out what's triggering it. Anyone recognize this process and know what it's linked to? Thanks all.
     

    ps auxf |grep leaf |grep -v grep  
    root      4508  0.0  0.0   2648   792 ?        S    14:46   0:00  |   \_ /bin/timeout 30 find /mnt/disk1/backups -noleaf
    root      4510  0.0  0.0   4480  2740 ?        R    14:46   0:00  |       \_ find /mnt/disk1/backups -noleaf
    root      4509  0.0  0.0   2648   724 ?        S    14:46   0:00      \_ /bin/timeout 30 find /mnt/cache/appdata -noleaf
    root      4511  0.0  0.0   4280  2576 ?        R    14:46   0:00          \_ find /mnt/cache/appdata -noleaf

    (I know in this output the cpu is zero, it goes up immediately after, but only one process at a time. I chose this because it shows both processes and what they are "finding" hoping it will give a better clue.)

  7. Decided to install and just manually add all my docs from paperless back. I'm getting a strange error on about half of them and google is zero help. 

    [2021-03-04 16:55:26,100] [ERROR] [paperless.consumer] Error while consuming document 2021-01-30-0104240000-none-20180222_175754-0000124.jpg: ExifOrientationError: Invalid rotation (0)

    The documents in question are absolutely oriented correctly. Has anyone seen this or know of a work around? Thanks!