Hello,

 

Just a quick one I think about something that happened this evening.

 

Over the last couple weeks I've been doing upgrades and tinkering with my Unraid server. I've been shutting it down and rebooting it many times - and every time it has done so without issue.  Tonight was different. I followed what I thought was my usual procedure when I'm shutting down:

 

1. Stop all docker containers (not the service though).

2. Stop my 1 running Linux VM (not the VM service though).

3. Press the shutdown buttons from Dashboard or "main". 

 

Once I get the "shutting down" web page, I close that page down and just wait for the server to shut off.  I left it around 10 minutes tonight, and when I went into the room where the server is, it was still running.  I went back onto the Unraid UI and everything was still accessible - array looked started etc - and I honestly thought that instead of confirming the shutdown command, I pressed "cancel" instead; so I just selected the shutdown button again - it asked if i wanted to shut down, and the server pretty much shut off immediately.

 

When I booted it up again next time, everything was fine - I started the array - and then after a few minutes realised there was a parity check running.  Because I assumed everything was hunky-dorry - I decided not to let the parity check continue - but then I noticed that in the few minutes it had been running - it actually found 17 sync errors - something that has never happened before after a parity check from unclean shutdown.

 

I am obviously running another parity check right now (with the errors correcting) and it at 17% it has found another 9 errors.

 

Oct 10 01:36:20 serverName kernel: md: recovery thread: P corrected, sector=2147483640
Oct 10 01:36:20 serverName kernel: md: recovery thread: P corrected, sector=2147483648
Oct 10 01:36:20 serverName kernel: md: recovery thread: P corrected, sector=2147483656
Oct 10 01:36:20 serverName kernel: md: recovery thread: P corrected, sector=2147483664
Oct 10 01:36:20 serverName kernel: md: recovery thread: P corrected, sector=2147483672
Oct 10 01:36:20 serverName kernel: md: recovery thread: P corrected, sector=2147483680
Oct 10 01:36:20 serverName kernel: md: recovery thread: P corrected, sector=2147483688
Oct 10 01:36:20 serverName kernel: md: recovery thread: P corrected, sector=2147483696
Oct 10 01:36:20 serverName kernel: md: recovery thread: P corrected, sector=2147483704

 

This was the last bit of log before it shutdown:

Oct  9 22:24:47 serverName kernel: BTRFS info (device loop3): last unmount of filesystem 3f2f815a-d996-4e63-86a0-5c3b4d62cf4e
Oct  9 22:24:47 serverName kernel: docker0: port 2(veth6baaa8b) entered disabled state
Oct  9 22:24:47 serverName kernel: veth174b5d9: renamed from eth0
Oct  9 22:24:47 serverName kernel: docker0: port 2(veth6baaa8b) entered disabled state
Oct  9 22:24:47 serverName kernel: device veth6baaa8b left promiscuous mode
Oct  9 22:24:47 serverName kernel: docker0: port 2(veth6baaa8b) entered disabled state
Oct  9 22:24:48 serverName root: stopping dockerd ...
Oct  9 22:24:49 serverName root: ... Waiting to die.
Oct  9 22:24:50 serverName root: ... Waiting to die.
Oct  9 22:24:51 serverName root: ... Waiting to die.
Oct  9 22:24:52 serverName root: ... Waiting to die.
Oct  9 22:24:52 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:24:53 serverName root: ... Waiting to die.
Oct  9 22:24:54 serverName root: ... Waiting to die.
Oct  9 22:24:55 serverName emhttpd: shcmd (616435): umount --lazy /var/lib/docker
Oct  9 22:24:58 serverName kernel: BTRFS info (device loop2): last unmount of filesystem c9cff771-8d35-4df3-8c1c-9171fbb3d9d8
Oct  9 22:24:58 serverName Recycle Bin: Stopping Recycle Bin
Oct  9 22:24:58 serverName emhttpd: Stopping Recycle Bin...
Oct  9 22:24:58 serverName unassigned.devices: Unmounting All Devices...
Oct  9 22:25:03 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:25:14 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:25:25 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:25:37 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:25:48 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:25:59 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:26:10 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:26:21 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:26:32 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:26:43 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:26:54 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:27:06 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:27:17 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:27:28 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:27:39 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:27:50 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:28:01 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:28:12 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:28:24 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:28:27 serverName root: Status of all loop devices
Oct  9 22:28:27 serverName root: /dev/loop1: [2049]:12 (/boot/bzfirmware)
Oct  9 22:28:27 serverName root: /dev/loop0: [2049]:10 (/boot/bzmodules)
Oct  9 22:28:27 serverName root: Active pids left on /mnt/*
Oct  9 22:28:35 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:28:46 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:28:57 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:29:08 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:29:19 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:29:30 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:29:41 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:29:53 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:30:04 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:30:15 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:30:26 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:30:37 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:30:48 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:30:59 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:31:11 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:31:22 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:31:33 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:31:44 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:31:55 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:32:06 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:32:17 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:32:29 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:32:40 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:32:51 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:33:02 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:33:13 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:33:24 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:33:35 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:33:47 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:33:58 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:34:09 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:34:20 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:34:31 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:34:42 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:34:53 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:35:04 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:35:16 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:35:27 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name
Oct  9 22:35:38 serverName key.dns_resolver: QNAP.LOCAL: No address associated with name

 

"QNAP" is another NAS that I use UD to connect to - I shut that off before the Unraid server, but I have always done that.

 

The only line that stood out to me was the "root: Active pids left on /mnt/*" - that could have been something hanging it?  

 

My disk settings shutdown time-out is 240s.

 

Like I say, I have done this loads of times and it has never been an issue.

 

I have a theory: I maybe thought more time had passed since my first telling the server to shutdown - and if I had just left it a little longer it would have shut down normally.  Does Unraid force shutdown the server if you press the shutdown buttons in the GUI a second time?

 

Anyway - re: the "sync errors".  These are basically just bits on the parity drive that are not what they should be for what is on the array disks, right?  It's not a case of any data loss/corruption or anything?

 

Thanks. Apologies for the long-winded-ness 🙂

A few sync errors after an unclean shutdown are normal, just run a correcting check.