I shutdown one of my NAS (7.1.4) servers, it simply shutdown without any issue with much spare time in the "graceful shutdown" timer, yet when i boot the NAS again it wants to scan parity? I have attached the syslog:

Nov 1 09:55:56 NAS3 shutdown[909383]: shutting down for system halt

Nov 1 09:55:56 NAS3 init: Switching to runlevel: 0

Nov 1 09:55:56 NAS3 rc.0: Running shutdown script /etc/rc.d/rc.0:

Nov 1 09:55:56 NAS3 init: Trying to re-exec init

Nov 1 09:55:56 NAS3 rc.0: Saving system time to the hardware clock (UTC).

Nov 1 09:55:56 NAS3 rc.0: Creating system time correction file /etc/adjtime.

Nov 1 09:55:56 NAS3 rc.0: /sbin/hwclock --utc --systohc

Nov 1 09:55:58 NAS3 rc.local_shutdown: Waiting up to 200 seconds for graceful shutdown...

Nov 1 09:55:58 NAS3 kernel: mdcmd (36): nocheck cancel

Nov 1 09:55:59 NAS3 emhttpd: Spinning up all drives...

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdm

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdj

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdk

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdh

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdg

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdd

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sde

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdb

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdf

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdc

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdn

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdq

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdo

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdl

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdi

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sdp

Nov 1 09:55:59 NAS3 emhttpd: read SMART /dev/sda

Nov 1 09:55:59 NAS3 emhttpd: Stopping services...

Nov 1 09:55:59 NAS3 recycle.bin: Stopping Recycle Bin

Nov 1 09:56:01 NAS3 emhttpd: shcmd (209): /etc/rc.d/rc.samba stop

Nov 1 09:56:01 NAS3 rc.samba: Stopping Samba server daemon...

Nov 1 09:56:01 NAS3 rc.samba: killall --ns 909564 smbd nmbd wsdd2 winbindd

Nov 1 09:56:01 NAS3 winbindd[2611]: [2025/11/01 09:56:01.961232, 0, traceid=1] ../../source3/winbindd/winbindd_dual.c:1982(winbindd_sig_term_handler)

Nov 1 09:56:01 NAS3 winbindd[2611]: Got sig[15] terminate (is_parent=1)

Nov 1 09:56:02 NAS3 rc.samba: Samba server daemon... Stopped.

Nov 1 09:56:02 NAS3 emhttpd: shcmd (210): rm -f /etc/avahi/services/smb.service

Nov 1 09:56:02 NAS3 avahi-daemon[2561]: Files changed, reloading.

Nov 1 09:56:02 NAS3 avahi-daemon[2561]: Service group file /services/smb.service vanished, removing services.

Nov 1 09:56:02 NAS3 emhttpd: Stopping mover...

Nov 1 09:56:02 NAS3 emhttpd: shcmd (212): /usr/local/sbin/mover stop

Nov 1 09:56:02 NAS3 root: mover: not running

Nov 1 09:56:02 NAS3 emhttpd: Sync filesystems...

Nov 1 09:56:02 NAS3 emhttpd: shcmd (213): sync

Nov 1 09:56:02 NAS3 emhttpd: shcmd (214): /usr/sbin/zfs unmount -a

Nov 1 09:56:02 NAS3 emhttpd: shcmd (215): umount /mnt/user0

Nov 1 09:56:02 NAS3 emhttpd: shcmd (216): rmdir /mnt/user0

Nov 1 09:56:02 NAS3 emhttpd: shcmd (217): umount /mnt/user

Nov 1 09:56:03 NAS3 emhttpd: shcmd (218): rmdir /mnt/user

Nov 1 09:56:03 NAS3 emhttpd: shcmd (220): rm -f /boot/config/plugins/dynamix/mover.cron

Nov 1 09:56:03 NAS3 emhttpd: shcmd (221): /usr/local/sbin/update_cron

Nov 1 09:56:03 NAS3 emhttpd: Unmounting disks...

Nov 1 09:56:03 NAS3 emhttpd: shcmd (222): umount /mnt/disk1

Nov 1 09:56:03 NAS3 kernel: XFS (dm-0): Unmounting Filesystem b2f74f02-923d-444d-8412-e81e735367aa

Nov 1 09:56:03 NAS3 emhttpd: shcmd (223): rmdir /mnt/disk1

Nov 1 09:56:03 NAS3 emhttpd: shcmd (224): umount /mnt/disk2

Nov 1 09:56:03 NAS3 kernel: XFS (dm-1): Unmounting Filesystem a5958af1-b349-45d3-8b61-fd4ba5f40a5a

Nov 1 09:56:03 NAS3 emhttpd: shcmd (225): rmdir /mnt/disk2

Nov 1 09:56:03 NAS3 emhttpd: shcmd (226): umount /mnt/disk3

Nov 1 09:56:03 NAS3 kernel: XFS (dm-2): Unmounting Filesystem 80a7d11d-c2ee-41ee-9449-fdee750aa33a

Nov 1 09:56:03 NAS3 emhttpd: shcmd (227): rmdir /mnt/disk3

Nov 1 09:56:03 NAS3 emhttpd: shcmd (228): umount /mnt/disk4

Nov 1 09:56:03 NAS3 kernel: XFS (dm-3): Unmounting Filesystem 0caf6f9a-9bf3-4875-90ea-87c256430c49

Nov 1 09:56:03 NAS3 emhttpd: shcmd (229): rmdir /mnt/disk4

Nov 1 09:56:03 NAS3 emhttpd: shcmd (230): umount /mnt/disk5

Nov 1 09:56:03 NAS3 kernel: XFS (dm-4): Unmounting Filesystem a247a353-39e0-4b43-b770-960d781ea748

Nov 1 09:56:03 NAS3 emhttpd: shcmd (231): rmdir /mnt/disk5

Nov 1 09:56:03 NAS3 emhttpd: shcmd (232): umount /mnt/disk6

Nov 1 09:56:04 NAS3 kernel: XFS (dm-5): Unmounting Filesystem 25cc2ce3-38ac-45eb-8b9b-ad7ff4e5bfd5

Nov 1 09:56:04 NAS3 emhttpd: shcmd (233): rmdir /mnt/disk6

Nov 1 09:56:04 NAS3 emhttpd: shcmd (234): umount /mnt/disk7

Nov 1 09:56:04 NAS3 kernel: XFS (dm-6): Unmounting Filesystem e94eae6b-d61f-4a8a-bffc-7a59e715f17b

Nov 1 09:56:04 NAS3 emhttpd: shcmd (235): rmdir /mnt/disk7

Nov 1 09:56:04 NAS3 emhttpd: shcmd (236): umount /mnt/disk8

Nov 1 09:56:04 NAS3 kernel: XFS (dm-7): Unmounting Filesystem 440129b6-4f6a-4382-9949-5e9df5318123

Nov 1 09:56:04 NAS3 emhttpd: shcmd (237): rmdir /mnt/disk8

Nov 1 09:56:04 NAS3 emhttpd: shcmd (238): umount /mnt/disk9

Nov 1 09:56:04 NAS3 kernel: XFS (dm-8): Unmounting Filesystem 99155c60-42a8-4015-bc0e-da0421d37a6e

Nov 1 09:56:04 NAS3 emhttpd: shcmd (239): rmdir /mnt/disk9

Nov 1 09:56:04 NAS3 emhttpd: shcmd (240): umount /mnt/disk10

Nov 1 09:56:04 NAS3 kernel: XFS (dm-9): Unmounting Filesystem 7f4acdad-e6e6-41f9-ba9b-f903b4085c35

Nov 1 09:56:04 NAS3 emhttpd: shcmd (241): rmdir /mnt/disk10

Nov 1 09:56:04 NAS3 emhttpd: shcmd (242): umount /mnt/disk11

Nov 1 09:56:04 NAS3 kernel: XFS (dm-10): Unmounting Filesystem 25b586b2-bc3e-46c9-9ccf-208111c5b97a

Nov 1 09:56:04 NAS3 emhttpd: shcmd (243): rmdir /mnt/disk11

Nov 1 09:56:04 NAS3 emhttpd: shcmd (244): umount /mnt/disk12

Nov 1 09:56:05 NAS3 kernel: XFS (dm-11): Unmounting Filesystem f5f041be-8d85-4669-a731-34daac225324

Nov 1 09:56:05 NAS3 emhttpd: shcmd (245): rmdir /mnt/disk12

Nov 1 09:56:05 NAS3 emhttpd: shcmd (246): umount /mnt/disk13

Nov 1 09:56:05 NAS3 kernel: XFS (dm-12): Unmounting Filesystem 24eb13a7-4cb4-43b1-aab3-f16ef29bef25

Nov 1 09:56:05 NAS3 emhttpd: shcmd (247): rmdir /mnt/disk13

Nov 1 09:56:05 NAS3 emhttpd: shcmd (248): umount /mnt/disk14

Nov 1 09:56:05 NAS3 kernel: XFS (dm-13): Unmounting Filesystem 2c81ddd7-24bb-48dd-8937-30aeaad9bcb9

Nov 1 09:56:05 NAS3 emhttpd: shcmd (249): rmdir /mnt/disk14

Nov 1 09:56:05 NAS3 emhttpd: shcmd (250): umount /mnt/disk15

Nov 1 09:56:40 NAS3 kernel: md: md_notify_reboot

Nov 1 09:56:40 NAS3 kernel: md: stopping all md devices

Nov 1 09:56:40 NAS3 kernel: md: 15 devices still in use.

Nov 1 09:56:40 NAS3 kernel: sd 12:0:7:0: [sdq] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 12:0:6:0: [sdp] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 12:0:5:0: [sdo] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 12:0:4:0: [sdn] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 12:0:3:0: [sdm] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 12:0:2:0: [sdl] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 12:0:1:0: [sdk] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 12:0:0:0: [sdj] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 10:0:7:0: [sdi] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 10:0:6:0: [sdh] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 10:0:5:0: [sdg] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 10:0:4:0: [sdf] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 10:0:3:0: [sde] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 10:0:2:0: [sdd] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 10:0:1:0: [sdc] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: sd 10:0:0:0: [sdb] Synchronizing SCSI cache

Nov 1 09:56:40 NAS3 kernel: mpt3sas_cm1: sending message unit reset !!

Nov 1 09:56:40 NAS3 kernel: mpt3sas_cm1: message unit reset: SUCCESS

Nov 1 09:56:40 NAS3 kernel: mpt3sas_cm0: sending message unit reset !!

Nov 1 09:56:40 NAS3 kernel: mpt3sas_cm0: message unit reset: SUCCESS

Edited November 1, 2025Nov 1 by je82

for now i installed tips & tweaks to have the shutdown bash/ssh on shutdown, i think that might have caused it but i still don't understand why it would shutdown before the 200 seconds has passed if it couldn't do a graceful shutdown

The log snippet is incomplete, but it does show issues with the HBA.

46 minutes ago, JorgeB said:

The log snippet is incomplete, but it does show issues with the HBA.

I had been transfering files to disk 15 via smb but i checked so the files were written and the disk was not reading/writing before i pressed shutdown

AI tells me this

Why SMB Seems to Block Shutdown Unraid's shutdown script does this:

1. Stop Samba → kills smbd
2. sync
3. unmount /mnt/user, /mnt/disk*
4. stop MD array

But if a client reconnects during step 1, or Samba doesn't fully release handles, then:

• /mnt/user may fail to unmount

• Or shfs keeps /dev/mdX open

This is rare, but happens with:

• Windows 10/11 aggressive SMB caching

• macOS Finder with "recent items"

• NFS hard mounts

that sounds plausible? as ive never seen it happen before, could potentially a timed smb connection cause shutdown event to end not gracefully? i cannot see any issues with the server now and ive been using it for years, this just happened once so it threw me off.

You need to see the full syslog to possibly have an idea of what caused the issue.