Jump to content

ryan8382

Members
  • Content Count

    37
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ryan8382

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm seeing the same things after getting the warning from fix common problems. I tried the above commands and see the same outputs. I think those are the right commands. Mobo is Supermicro - H8SGL AMD Opteron™ 6212 @ 2600 tower-diagnostics-20180930-1841.zip
  2. ryan8382

    Wrong number of disks?

    So I have found some interesting things. If I plug in a new disk so that I can preclear it on the server. My cache drive drops. I have to stop the array reboot unplug the drive then plug back in then it comes back. This is no matter which SATA port i choose. I'm only using 10 drive out of my 12. I was seeing I think that was related to the USB being used on my Mac when I set it up. I moved that file and that error went away. Not sure why it was trying to read the _.Plus.key. As for when I try and add a disk to preclear I have no clue what is happening. I don't have any other issues. I do see this error ata1.00: failed command: WRITE FPDMA QUEUED. Only thing I can find when searching is related to bad PSU. tower-diagnostics-20180313-1649.zip
  3. ryan8382

    Wrong number of disks?

    I was just replacing one of my cache drives when I ran into a weird issue. First I noticed that one of the drives was missing. I assumed it had died. So i plugged in the new drive but it wasn't detected. I checked the logs and saw the line below shfs: error: get_key_info, 584: Invalid argument (22): get_message: /boot/config/._Plus.key (-3) I forgot I had a drive space set for an HD that wasn't there. Once I removed that it saw the new SSD. I then went back and counted my drives. I have 9 HD and 2 SSD. That should only be 11 disks right? The drive limit for plus is 12 total? What am I missing? tower-diagnostics-20180306-2037.zip
  4. ryan8382

    Running ESXi on Unraid

    I have a pretty nice UnRaid box and would like do some Vmware lab work. I would like to install some ESX VMs to test setups. I was able to get 6.5 to run but it doesn't detect and network adapters. What are the tips and tricks for getting that to run? Is there a possible OVA import feature coming?
  5. After doing that reboot and deleting the docker.img. Now it came up with docker started. I'm adding a container now to see if it is working and will post the diag later. No clue as to what happened.
  6. Deleted Docker.img and go to reboot and get the following. Oct 19 11:35:35 Tower emhttp: Unmounting disks... Oct 19 11:35:35 Tower emhttp: shcmd (6865): umount /mnt/disk1 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk1: target is busy Oct 19 11:35:35 Tower root: (In some cases useful info about processes that Oct 19 11:35:35 Tower root: use the device is found by lsof( or fuser(1).) Oct 19 11:35:35 Tower emhttp: shcmd (6866): umount /mnt/disk2 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk2: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6867): rmdir /mnt/disk2 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk2': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6868): umount /mnt/disk3 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk3: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6869): rmdir /mnt/disk3 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk3': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6870): umount /mnt/disk4 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk4: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6871): rmdir /mnt/disk4 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk4': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6872): umount /mnt/disk5 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk5: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6873): rmdir /mnt/disk5 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk5': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6874): umount /mnt/disk6 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk6: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6875): rmdir /mnt/disk6 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk6': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6876): umount /mnt/disk7 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk7: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6877): rmdir /mnt/disk7 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk7': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6878): umount /mnt/cache |& logger Oct 19 11:35:35 Tower root: umount: /mnt/cache: target is busy Oct 19 11:35:35 Tower root: (In some cases useful info about processes that Oct 19 11:35:35 Tower root: use the device is found by lsof( or fuser(1).) Oct 19 11:35:35 Tower emhttp: Retry unmounting disk share(s)...[/move][/move][/move] I have had to do a shutdown -r now a few times. Not sure if this is related.
  7. Same error on Disk1 Oct 19 10:46:28 Tower emhttp: shcmd (4941): /etc/rc.d/rc.docker start |& logger Oct 19 10:46:28 Tower root: starting docker ... Oct 19 10:47:01 Tower emhttp: shcmd (4959): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/disk1/docker.img' /var/lib/docker 40 |& logger Oct 19 10:47:01 Tower root: /mnt/disk1/docker.img is in-use, cannot mount Oct 19 10:47:01 Tower emhttp: err: shcmd: shcmd (4959): exit status: 1 I'm gong to guess my next option is to roll back to previous version?
  8. Already did that. No go error didn't change.
  9. After upgrading to 6.2.1 and swapping out a drive Docker won't start. My docker image is directly on cache. So it wasn't associated with the drive being swapped. This is what shows in the logs. Oct 19 09:23:01 Tower emhttp: shcmd (3242): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 40 |& logger Oct 19 09:23:01 Tower root: /mnt/cache/docker.img is in-use, cannot mount Oct 19 09:23:01 Tower emhttp: err: shcmd: shcmd (3242): exit status: 1 Oct 19 09:24:02 Tower emhttp: shcmd (3259): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 40 |& logger Oct 19 09:24:02 Tower root: /mnt/cache/docker.img is in-use, cannot mount Oct 19 09:24:02 Tower emhttp: err: shcmd: shcmd (3259): exit status: 1 tower-diagnostics-20161019-0914.zip
  10. ryan8382

    6.2 Beta 21 2nd drive parity disk timeouts

    I have already removed that container. I'm going to work on that one. I have a limit setup on my cache pool if that is what it is referring to. I think it is hitting the limit on the pool. I would assume the mover would kick it. Going to look at that this weekend I hope. I have a AOC-SAS2LP-MV8 card in there I'm not sure if those drives are on there. I will check everything on the system. Thanks for pointing that out. This tends to indicate a remnant of an older version still there, which can cause problems. * At the end of the 6.1.9 syslog, there is a failure of TimeMachine and AFP. With those other issues. I'm thinking of backing up the config related items and basically do a fresh install. I could try 6.2. again and see how it goes. Thanks for the help. I will update the post when i have more detail.
  11. ryan8382

    6.2 Beta 21 2nd drive parity disk timeouts

    It did complete at a reasonable time frame. It was a full rebuild. I did a new config setup thinking that it might have been related. I think I going to hold off for the next release before I try again. Wife didn't like server being down. Sent from my iPhone using Tapatalk
  12. ryan8382

    6.2 Beta 21 2nd drive parity disk timeouts

    Yes it finally finished. Sent from my iPhone using Tapatalk
  13. ryan8382

    6.2 Beta 21 2nd drive parity disk timeouts

    Figured I would update this. My server is now working running 6.1.9. I hope you guys can figure out what the bug is in the beta. Sent from my iPhone using Tapatalk
  14. ryan8382

    Unraid 6 and server freezes

    I was seeing mine stay up from about 40min to 2hrs. It responds to pings but webUI is sluggish and docker doesn't work. VM also just stops. One time I was using it when it quit. Sent from my iPhone using Tapatalk
  15. ryan8382

    Unraid 6 and server freezes

    Try downgrading from the beta to 6.1.9. My server appears to be working again at that level. I hope they find something in the logs something isn't right.