FreeMan Posted January 27, 2017 Share Posted January 27, 2017 I've been having issues with my server locking up over the last several days, but I'll make a separate post about that soon. In keeping an eye on that, I discovered this line in my syslog: Jan 26 18:40:15 NAS preclear.disk: Resuming preclear of disk 'sdp' Not only am I not currently running a preclear (nor was I before the system locked up), but I don't have a device 'sdp' as can be seen in the output of lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT md1 9:1 0 931.5G 0 md /mnt/disk1 md2 9:2 0 1.8T 0 md /mnt/disk2 md3 9:3 0 931.5G 0 md /mnt/disk3 md4 9:4 0 1.8T 0 md /mnt/disk4 md5 9:5 0 3.7T 0 md /mnt/disk5 md6 9:6 0 1.8T 0 md /mnt/disk6 md7 9:7 0 1.8T 0 md /mnt/disk7 md8 9:8 0 1.8T 0 md /mnt/disk8 md9 9:9 0 931.5G 0 md /mnt/disk9 sda 8:0 1 3.8G 0 disk ??sda1 8:1 1 3.8G 0 part /boot sdb 8:16 0 931.5G 0 disk ??sdb1 8:17 0 931.5G 0 part sdc 8:32 0 232.9G 0 disk ??sdc1 8:33 0 232.9G 0 part /mnt/cache sdd 8:48 0 3.7T 0 disk ??sdd1 8:49 0 3.7T 0 part sde 8:64 0 1.8T 0 disk ??sde1 8:65 0 1.8T 0 part sdf 8:80 0 3.7T 0 disk ??sdf1 8:81 0 3.7T 0 part sdg 8:96 0 1.8T 0 disk ??sdg1 8:97 0 1.8T 0 part sdh 8:112 0 3.7T 0 disk ??sdh1 8:113 0 3.7T 0 part sdi 8:128 0 2.7T 0 disk ??sdi1 8:129 0 2.7T 0 part sdj 8:144 0 1.8T 0 disk ??sdj1 8:145 0 1.8T 0 part sdk 8:160 0 3.7T 0 disk ??sdk1 8:161 0 3.7T 0 part sdl 8:176 1 1.8T 0 disk ??sdl1 8:177 1 1.8T 0 part sdm 8:192 1 931.5G 0 disk ??sdm1 8:193 1 931.5G 0 part sdn 8:208 1 931.5G 0 disk ??sdn1 8:209 1 931.5G 0 part sdo 8:224 1 1.8T 0 disk ??sdo1 8:225 1 1.8T 0 part md10 9:10 0 2.7T 0 md /mnt/disk10 md11 9:11 0 3.7T 0 md /mnt/disk11 md12 9:12 0 3.7T 0 md /mnt/disk12 loop0 7:0 0 30G 0 loop /var/lib/docker I just rebooted my server a few minutes prior to this point in the syslog, and I've attached the complete diagnostics.zip in case anyone can find anything interesting in there. Why is my server claiming it's resuming a never started preclear on a nonexistent drive? nas-diagnostics-20170126-1903.zip Quote Link to comment
FreeMan Posted January 28, 2017 Author Share Posted January 28, 2017 Any thoughts or suggestions? Quote Link to comment
RobJ Posted January 28, 2017 Share Posted January 28, 2017 I would guess that sdp was assigned in a *previous* session. Is the lsblk report after a reboot of a session with a Preclear? I would post this in the Preclear plugin support thread, for gfjardim to see. Quote Link to comment
FreeMan Posted January 28, 2017 Author Share Posted January 28, 2017 Nope. Haven't precleared a disk since... October? I did have some issues during the preclear related to other parts of the system, and the server crashed a couple of times then, too. It's has OS updates since then, and I shut it down to put all the drives in 5x3 cages since then, too, so it's had a couple of clean reboots, as well. The current number of drives is the max I've ever had in the box, so there should have never been a drive mounted as sdp. Weird... I presume you saw nothing else that would cause any concern? If not, I'll just mosey along and pretend this didn't happen. Quote Link to comment
Recommended Posts
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.