New Trial Install- Slow starting services


Maz

Recommended Posts

Hi, Need advise please-  few questions- I'm new here so please go easy on me.... New Install.

 

I did a fresh UNRAID install with trial key, built an array with 2 data drives and 1 parity drive and created some shares. No dockers containers and only 3 plugins.

 

Q1- when I go to start the array, it says "starting Services" and it takes approximately 4 to 5 minutes time before it switches over to "array started"

Is it normal for the array to take 5 minutes to start? I only have 2 data drives. and 5 shares so far...  Will it take longer to start if I have 10 drives instead of 2?

 

My Parity drive is an 8TB WD RED and 2 data drives are each 4TB... no errors reported on any drives once the array finally starts. I am using version 6.7.0RC5 since I am running on an AMD RYZEN 1700 platform which seems stable after disabling C6 states and adding the following "rcu_nocbs=0-15" command in the SYSLINUX configuration:

 

kernel /bzimage
append initrd=/bzroot rcu_nocbs=0-15

 

And

kernel /bzimage
append initrd=/bzroot,/bzroot-gui
rcu_nocbs=0-15

 

I am left with an UN-easy feeling  being that the services takes 5 minutes to start, and am worried in the future it will hang and not start at all.  Before purchasing a license I need to feel confidant this is not going to become something to always worry about moving forwards over the coming years... appreciate the feedback..

 

 

Diagnostic log attached. thank you. appreciate the advise.....by The way, Stopping services seems to take around a minute or less to complete.

 

Q2- I also am confused since adding 2nd disk to array, having the default disk file system format set to BTRFS under disk settings, but after clearing the drive it shows the disk defaulting to "auto"  ... I seem to be forced to switch it to BTRFS which obviously requests to format the drive once the array is once again started....  is that normal?

 

Thank you!!

unraid-diagnostics-20190326-1205.zip

Edited by Maz
Link to comment
18 hours ago, Maz said:

Q1- when I go to start the array, it says "starting Services" and it takes approximately 4 to 5 minutes time before it switches over to "array started"

Is it normal for the array to take 5 minutes to start? I only have 2 data drives. and 5 shares so far...  Will it take longer to start if I have 10 drives instead of 2?

You can see in your logs the time stamps for when each event occurs.  When you started the array:

 

Mar 26 07:57:58 UNRAID emhttpd: Mounting disks...
Mar 26 07:57:58 UNRAID emhttpd: shcmd (37): /sbin/btrfs device scan
Mar 26 07:57:58 UNRAID root: Scanning for Btrfs filesystems
Mar 26 07:57:58 UNRAID emhttpd: shcmd (38): mkdir -p /mnt/disk1
Mar 26 07:57:58 UNRAID emhttpd: shcmd (39): mount -t btrfs -o noatime,nodiratime /dev/md1 /mnt/disk1
Mar 26 07:57:58 UNRAID kernel: BTRFS info (device md1): disk space caching is enabled
Mar 26 07:57:58 UNRAID kernel: BTRFS info (device md1): has skinny extents
Mar 26 07:57:58 UNRAID avahi-daemon[2539]: Service "UNRAID" (/services/ssh.service) successfully established.
Mar 26 07:57:58 UNRAID avahi-daemon[2539]: Service "UNRAID" (/services/smb.service) successfully established.
Mar 26 07:57:58 UNRAID avahi-daemon[2539]: Service "UNRAID" (/services/sftp-ssh.service) successfully established.
Mar 26 07:57:58 UNRAID avahi-daemon[2539]: Service "UNRAID-AFP" (/services/afp.service) successfully established.
Mar 26 07:57:58 UNRAID ntpd[2012]: receive: Unexpected origin timestamp 0xe0449247.322158e8 does not match aorg 0000000000.00000000 from [email protected] xmt 0xe0449246.df2ec879
Mar 26 07:57:58 UNRAID ntpd[2012]: receive: Unexpected origin timestamp 0xe0449247.32239fe0 does not match aorg 0000000000.00000000 from [email protected] xmt 0xe0449246.e01d315a
Mar 26 07:57:59 UNRAID emhttpd: shcmd (40): btrfs filesystem resize max /mnt/disk1
Mar 26 07:57:59 UNRAID root: Resize '/mnt/disk1' of 'max'
Mar 26 07:57:59 UNRAID kernel: BTRFS info (device md1): new size for /dev/md1 is 4000786976768
Mar 26 07:57:59 UNRAID emhttpd: shcmd (41): mkdir -p /mnt/disk2
Mar 26 07:57:59 UNRAID emhttpd: /mnt/disk2 mount error: Unsupported partition layout
Mar 26 07:57:59 UNRAID emhttpd: shcmd (42): umount /mnt/disk2
Mar 26 07:57:59 UNRAID root: umount: /mnt/disk2: not mounted.
Mar 26 07:57:59 UNRAID emhttpd: shcmd (42): exit status: 32
Mar 26 07:57:59 UNRAID emhttpd: shcmd (43): rmdir /mnt/disk2
Mar 26 07:57:59 UNRAID emhttpd: shcmd (44): sync
Mar 26 07:58:00 UNRAID emhttpd: shcmd (45): mkdir /mnt/user
Mar 26 07:58:00 UNRAID emhttpd: shcmd (46): /usr/local/sbin/shfs /mnt/user -disks 6 -o noatime,big_writes,allow_other -o direct_io -o remember=0  |& logger
Mar 26 07:58:00 UNRAID shfs: stderr redirected to syslog
Mar 26 07:58:00 UNRAID emhttpd: shcmd (48): /usr/local/sbin/update_cron
Mar 26 07:58:00 UNRAID root: Delaying execution of fix common problems scan for 10 minutes

The entire mounting of the disks took less than 2 seconds.  After that, it starts services:

Mar 26 07:58:00 UNRAID emhttpd: Starting services...
Mar 26 07:58:00 UNRAID emhttpd: shcmd (51): /etc/rc.d/rc.samba restart
Mar 26 07:58:02 UNRAID root: Starting Samba:  /usr/sbin/nmbd -D
Mar 26 07:58:02 UNRAID root:                  /usr/sbin/smbd -D
Mar 26 07:58:02 UNRAID root:                  /usr/sbin/winbindd -D
Mar 26 07:58:02 UNRAID emhttpd: shcmd (67): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20
Mar 26 07:58:02 UNRAID kernel: BTRFS: device fsid 4735afec-9878-471a-aea9-3472810d93c0 devid 1 transid 87 /dev/loop2
Mar 26 07:58:02 UNRAID kernel: BTRFS info (device loop2): disk space caching is enabled
Mar 26 07:58:02 UNRAID kernel: BTRFS info (device loop2): has skinny extents
Mar 26 07:58:02 UNRAID root: Resize '/var/lib/docker' of 'max'
Mar 26 07:58:02 UNRAID kernel: BTRFS info (device loop2): new size for /dev/loop2 is 21474836480
Mar 26 07:58:02 UNRAID emhttpd: shcmd (69): /etc/rc.d/rc.docker start
Mar 26 07:58:02 UNRAID root: starting dockerd ...
Mar 26 07:58:02 UNRAID dbus-daemon[2971]: [session uid=0 pid=2968] Activating service name='org.a11y.Bus' requested by ':1.0' (uid=0 pid=2964 comm="firefox --profile /usr/share/mozilla/firefox/9n35r")
Mar 26 07:58:02 UNRAID dbus-daemon[2971]: [session uid=0 pid=2968] Successfully activated service 'org.a11y.Bus'
Mar 26 07:58:45 UNRAID kernel: logitech-hidpp-device 0003:046D:101B.0007: HID++ 1.0 device connected.
Mar 26 07:58:49 UNRAID avahi-daemon[2539]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Mar 26 07:58:49 UNRAID avahi-daemon[2539]: New relevant interface docker0.IPv4 for mDNS.
Mar 26 07:58:49 UNRAID avahi-daemon[2539]: Registering new address record for 172.17.0.1 on docker0.IPv4.
Mar 26 07:58:49 UNRAID kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
Mar 26 08:00:01 UNRAID crond[2038]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null
Mar 26 08:01:34 UNRAID emhttpd: shcmd (83): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1
Mar 26 08:01:34 UNRAID kernel: BTRFS: device fsid b8382bc5-1fba-4181-9b43-f4d0e8bbc7f4 devid 1 transid 23 /dev/loop3
Mar 26 08:01:34 UNRAID kernel: BTRFS info (device loop3): disk space caching is enabled
Mar 26 08:01:34 UNRAID kernel: BTRFS info (device loop3): has skinny extents
Mar 26 08:01:34 UNRAID root: Resize '/etc/libvirt' of 'max'
Mar 26 08:01:34 UNRAID kernel: BTRFS info (device loop3): new size for /dev/loop3 is 1073741824
Mar 26 08:01:34 UNRAID emhttpd: shcmd (85): /etc/rc.d/rc.libvirt start
Mar 26 08:01:34 UNRAID root: Starting virtlockd...
Mar 26 08:01:34 UNRAID root: Starting virtlogd...
Mar 26 08:01:34 UNRAID root: Starting libvirtd...

Looks like all services came up in about 3 and a half minutes.  Now if this was the first time you started the array and you are using all spinning drives (no SSDs), and no cache drive, this is typical behavior.  You are getting minimal performance at this point.  The best solution is to configure a cache drive or better yet, a cache pool, and this way you can improve your performance of services because they won't be bound by the write speed limits of the array with dedicated parity.  In addition, the first time you start the array, you are also formatting disks, which will slow down the performance of the system until the formats are complete.

 

I don't see any real issues here, so maybe consider adding a cache drive and seeing if that improves things a bit.

Link to comment

Thanks, your feedback was much appreciated- I've since added an SSD cache drive to my configuration and also switched the default file system for the Data drives back to XFS....  My array with valid parity drive starts much quicker now... more like in under 10 seconds where as before it was taking minutes.  I am very impressed with UNRAID. Will likely purchase more than one license. 

 

That being said, not sure why it was taking 3 1/2 minutes before since it was not the first time the array was started - all that changed for me was adding an SSD cache drive, changing back to XFS for data drives and updating to 6.7.0RC6....... Starts right up now... all good!!!

Edited by Maz
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.