• Disk wont stay spun down - i am 99.9 % sure its SMART - not a plugin, docker or vm


    Michael H
    • Solved Annoyance
    Quote

    before you read the whole thing let me get to the point: can somebody tell me how to disable smart readings completely? i know the risks and its only to check my theory for peace of mind. i have commented out the DEVICESCAN line in /etc/smartd.conf but i cant seem to restart the smart reading service - partly because i dont know what the service is called and partly because neither systemctl nor service seem to be implemented in unraid.

     

    so here goes the long version why i want to know that:

     

     

    I have read many bug reports of this, but nothing ever came of it in any thread. its always the plugins, the vms, a docker container etc. Well, as with so many people not for me, it could not be pinned to any of those culprits.

     

    I have booted in safe mode, i have manually disabled docker and vm service, no mover, no script, my appdata and system shares are on cache only and i have made sure not a single computer on my network is connected to a share and still, the data disks keep spinning up again and again.

     

    the funny thing is i have tried so many hours to find out why and nothing came of it. i checked with open streams plugin - nothing. i checked with disk activity plugin - nothing. i have even made a new config just to be sure... even unraids own gui did not increase read or write counts for 2 consecutive spindown/spinup cycles.

     

    i am completely lost with this and i still dont think anybody can help me, but i refuse to let this one go without at least opening up another bug report as so many have done before me with no help.

     

    here are my diagnostics, although they wont help you im afraid. i know i know, smart only reads when the disk is active and so on... every bug report was full of it. well as i have detailed above, NOTHING accessed the disks when they spun up. so either its a bug or something with smart does not work. i am convinced its smart because it also had trouble displaying the drive temps correctly with my raid controller (in hba mode).

     

    what makes me believe its not an issue with my raid card or other hardware is that parity stays spun down.

     

    please just let me disable smart reading and see if the disks keep spun down.

     

     

     

     

    hp-diagnostics-20220911-2334.zip




    User Feedback

    Recommended Comments



    There have been cases where a combination of certain hardware and disks have caused this spin up issue.  Both your data disks are WD, You said in the thread that the parity disk does spin down.  I think your parity disk is a Seagate disk.  Do you have another disk you could add to the array that is a different manufacturer just as a test?  It can be any size.

    Link to comment

    yes i should be able to do that, i have a few disks lying around. however they are not the kind that i would entrust with my data on the long run, so is there any way to remove a disk from the array afterwards? i guess it should have data on it just to create a real world scenario.

    Link to comment
    40 minutes ago, Michael H said:

    yes i should be able to do that, i have a few disks lying around. however they are not the kind that i would entrust with my data on the long run, so is there any way to remove a disk from the array afterwards? i guess it should have data on it just to create a real world scenario.

    You can remove the disk later.  The idea is to see if there is a disk and controller combination here that is the problem.

    Link to comment

    i added a seagate disk like the parity drive, but there is data on it so i wanted to erase it with your preclear plugin. however it does not show the option to do so, as i understood from your support thread thats because there is a partition and data on the disk. so how do i clear it before adding it to the array?

     

    but for now, even just sitting there in unassigned devices i can spin it down and it spins back up at will... so can we call it a failure already?

    Edited by Michael H
    Link to comment

    If it's already spinning up, then that tells us what we need to know.  What disk controller are you using?

     

    Post another diagnostics file before you do anything else.

     

    To clear a disk, you need to enable "Destructive Mode" in UD settings.  You can clear the disk by clicking on the red X next to the disk seral.

    Link to comment

    Not necessary to preclear a disk unless you just want to test it. The only time a clear disk is required is when adding it to a new slot in an array that already has parity, and Unraid itself will clear the disk in that case.

    Link to comment

    new discovery to pass along:

     

    hdparm -C /dev/sdg
    
    /dev/sdg:
     drive state is:  unknown

     

    for the new seagate disk. strange, isnt it? maybe thats why it spinss up even sooner than the wd red

    Link to comment
    30 minutes ago, Michael H said:

    new discovery to pass along:

     

    hdparm -C /dev/sdg
    
    /dev/sdg:
     drive state is:  unknown

     

    for the new seagate disk. strange, isnt it? maybe thats why it spinss up even sooner than the wd red

    Do you have another disk you could try?

    Link to comment

    all others report correctly. the new seagate also does when it is active, just in standby it does not. adding it to the array now to see if that makes a difference - preclear will finish in 11 hours.

    Link to comment

    as part of the array, the new seagate now reports correctly.

     

    however it spins up like the wd's do still, so its not a disk/controller-specific problem as the same disk as parity stays down.

     

    also although its empty removing it would need me to recalculate parity again which i dont want to do. wish i had known that sooner :)

    Edited by Michael H
    Link to comment

    I've got some more information for you.  In the change log for 6.11-rc3: "Quit trying to spin down devices which do not support standby mode.".

     

    What this means is on 6.11-rc3 and later, Unraid will not spin down disks that don't support standby mode.  If you run the array and Unraid spins down the disk, it should not spin back up.  If you manually spin down a disk and it doesn't support standby mode, it will probably spin back up.

     

    See if this doesn;t explain some of your issues.

    Link to comment

    i dont think thats the issue, because i would think both the seagates and the reds do support spindown. at least for the seagate we can be sure because it does stay down (parity). also, this issue is there since the server was set up on 6.8.x. but nevertheless, i set the spindown timer to 15 minutes for all disks - had it set to never for the reds because it would spin up again anyhow so if i cant save on energy costs why strain the disks with the countless spin down and ups.

     

    what is weird is after setting the timer to 15 minutes, unraid spins it down and 5 seconds later smart read and up:

     

    Quote

    Sep 22 20:07:25 hp kernel: mdcmd (44): set md_num_stripes 1280
    Sep 22 20:07:25 hp kernel: mdcmd (45): set md_queue_limit 80
    Sep 22 20:07:25 hp kernel: mdcmd (46): set md_sync_limit 5
    Sep 22 20:07:25 hp kernel: mdcmd (47): set md_write_method 1
    Sep 22 20:07:31 hp kernel: mdcmd (48): set md_num_stripes 1280
    Sep 22 20:07:31 hp kernel: mdcmd (49): set md_queue_limit 80
    Sep 22 20:07:31 hp kernel: mdcmd (50): set md_sync_limit 5
    Sep 22 20:07:31 hp kernel: mdcmd (51): set md_write_method 1
    Sep 22 20:07:31 hp  emhttpd: spinning down /dev/sdd
    Sep 22 20:07:36 hp  emhttpd: read SMART /dev/sdd
    Sep 22 20:07:36 hp kernel: sdd: sdd1
    Sep 22 20:07:38 hp kernel: mdcmd (52): set md_num_stripes 1280
    Sep 22 20:07:38 hp kernel: mdcmd (53): set md_queue_limit 80
    Sep 22 20:07:38 hp kernel: mdcmd (54): set md_sync_limit 5
    Sep 22 20:07:38 hp kernel: mdcmd (55): set md_write_method 1
    Sep 22 20:07:38 hp  emhttpd: spinning down /dev/sdb
    Sep 22 20:07:44 hp  emhttpd: read SMART /dev/sdb
    Sep 22 20:07:44 hp kernel: sdb: sdb1
    Sep 22 20:07:47 hp kernel: mdcmd (56): set md_num_stripes 1280
    Sep 22 20:07:47 hp kernel: mdcmd (57): set md_queue_limit 80
    Sep 22 20:07:47 hp kernel: mdcmd (58): set md_sync_limit 5
    Sep 22 20:07:47 hp kernel: mdcmd (59): set md_write_method 1
    Sep 22 20:07:47 hp  emhttpd: spinning down /dev/sdg
    Sep 22 20:07:52 hp  emhttpd: read SMART /dev/sdg

     

    also can you tell me why the kernel loves to print out the disks all the time... especially for the passed through unassigned device:

     

    Quote

    Sep 22 20:08:48 hp kernel: sdb: sdb1
    Sep 22 20:08:48 hp kernel: sdd: sdd1
    Sep 22 20:08:48 hp kernel: sdg: sdg1
    Sep 22 20:08:48 hp kernel: sdc: sdc1
    Sep 22 20:08:49 hp kernel: sdf: sdf1 sdf2
    Sep 22 20:08:49 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS' is set as passed through.
    Sep 22 20:08:49 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 20:09:20 hp kernel: sdd: sdd1
    Sep 22 20:09:20 hp kernel: sdb: sdb1
    Sep 22 20:09:20 hp kernel: sdg: sdg1
    Sep 22 20:09:20 hp kernel: sdc: sdc1
    Sep 22 20:09:21 hp kernel: sdf: sdf1 sdf2
    Sep 22 20:09:21 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS' is set as passed through.
    Sep 22 20:09:22 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 20:09:52 hp kernel: sdb: sdb1
    Sep 22 20:09:52 hp kernel: sdd: sdd1
    Sep 22 20:09:52 hp kernel: sdc: sdc1
    Sep 22 20:09:52 hp kernel: sdg: sdg1
    Sep 22 20:09:53 hp kernel: sdf: sdf1 sdf2
    Sep 22 20:09:54 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS-part1' is set as passed through.
    Sep 22 20:09:54 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 20:10:24 hp kernel: sdd: sdd1
    Sep 22 20:10:24 hp kernel: sdb: sdb1
    Sep 22 20:10:24 hp kernel: sdg: sdg1
    Sep 22 20:10:24 hp kernel: sdc: sdc1
    Sep 22 20:10:25 hp kernel: sdf: sdf1 sdf2
    Sep 22 20:10:26 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS-part1' is set as passed through.
    Sep 22 20:10:26 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 20:10:57 hp kernel: sdd: sdd1
    Sep 22 20:10:57 hp kernel: sdg: sdg1
    Sep 22 20:10:57 hp kernel: sdb: sdb1
    Sep 22 20:10:57 hp kernel: sdc: sdc1
    Sep 22 20:10:58 hp kernel: sdf: sdf1 sdf2
    Sep 22 20:10:58 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS-part1' is set as passed through.
    Sep 22 20:10:58 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 20:11:29 hp kernel: sdd: sdd1
    Sep 22 20:11:29 hp kernel: sdb: sdb1
    Sep 22 20:11:29 hp kernel: sdg: sdg1
    Sep 22 20:11:29 hp kernel: sdc: sdc1
    Sep 22 20:11:30 hp kernel: sdf: sdf1 sdf2
    Sep 22 20:11:30 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS' is set as passed through.
    Sep 22 20:11:30 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 20:

     

    pollutes the log quite a bit. maybe this is the issue?

    Edited by Michael H
    Link to comment

    so unraid spun them down on its own and then back up about a minute later. really not ideal...

     

    Quote

    Sep 22 20:22:34 hp  emhttpd: spinning down /dev/sdd
    Sep 22 20:22:42 hp  emhttpd: spinning down /dev/sdb
    Sep 22 20:22:48 hp kernel: sdc: sdc1
    Sep 22 20:22:48 hp kernel: sdg: sdg1
    Sep 22 20:22:49 hp kernel: sdf: sdf1 sdf2
    Sep 22 20:22:49 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS' is set as passed through.
    Sep 22 20:22:49 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 20:22:50 hp  emhttpd: spinning down /dev/sdg
    Sep 22 20:23:08 hp  emhttpd: spinning down /dev/sdc
    Sep 22 20:23:23 hp kernel: sdf: sdf1 sdf2
    Sep 22 20:23:24 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS' is set as passed through.
    Sep 22 20:23:24 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 20:23:57 hp kernel: sdf: sdf1 sdf2
    Sep 22 20:23:57 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS' is set as passed through.
    Sep 22 20:23:57 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 20:24:31 hp kernel: sdf: sdf1 sdf2
    Sep 22 20:24:31 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS' is set as passed through.
    Sep 22 20:24:31 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 20:25:04 hp kernel: sdf: sdf1 sdf2
    Sep 22 20:25:05 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS' is set as passed through.
    Sep 22 20:25:05 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 20:25:33 hp  emhttpd: read SMART /dev/sdb
    Sep 22 20:25:34 hp kernel: sdb: sdb1
    Sep 22 20:25:47 hp  emhttpd: read SMART /dev/sdd
    Sep 22 20:25:47 hp kernel: sdd: sdd1
    Sep 22 20:26:00 hp  emhttpd: read SMART /dev/sdg
    Sep 22 20:26:00 hp kernel: sdg: sdg1

     

    Link to comment
    1 hour ago, Michael H said:

    also can you tell me why the kernel loves to print out the disks all the time... especially for the passed through unassigned device:

    Go to the UD settings and set the "Debug Log Level" to "Udev and Hotplug".  Let it run for a few minutes and then post diagnostics so I can see why you are getting those messages.  This should not be happening.  I think you are getting constant udev events.  Be sure to turn off the "Debug Log Level".  It can be very chatty.

     

     

    • Thanks 1
    Link to comment

    Here are the diagnostics and a snippet of the relevant part of the log, which repeats over and over :

     

    Quote

    Sep 22 21:42:50 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 21:43:21 hp kernel: sdd: sdd1
    Sep 22 21:43:21 hp kernel: sdb: sdb1
    Sep 22 21:43:21 hp kernel: sdg: sdg1
    Sep 22 21:43:21 hp kernel: sdc: sdc1
    Sep 22 21:43:21 hp unassigned.devices: Reload: A udev 'change partition' initiated a reload of udev info.
    Sep 22 21:43:21 hp unassigned.devices: Updating udev information...
    Sep 22 21:43:21 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-id/ata-SanDisk_SSD_PLUS_1000GB_2022JN458902-part1.
    Sep 22 21:43:21 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-id/wwn-0x5001b444a775ef36-part1.
    Sep 22 21:43:21 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-path/pci-0000:08:00.0-sas-0x3001438037d9568a-lun-0-part1.
    Sep 22 21:43:21 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-uuid/1e4e331f-b2e1-4395-970e-df01e96d64b6.
    Sep 22 21:43:21 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 21:43:21 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 21:43:21 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 21:43:21 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 21:43:22 hp kernel: sdf: sdf1 sdf2
    Sep 22 21:43:22 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-id/scsi-35000c500262e13f3-part1.
    Sep 22 21:43:22 hp unassigned.devices: Partition found with the following attributes: serial_short='9WK3NR0J0000C1299VJ0', device='/dev/sdf1', serial='ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', uuid='', part='1', disk='/dev/sdf', label='IBM-ESXS ST31000424SS', disk_label='', fstype='', mountpoint='/mnt/disks/IBM-ESXS_ST31000424SS', luks='', mounted='', not_unmounted='', pool='', pass_through='1', disable_mount='1', target='', size='0', used='0', avail='0', owner='udev', automount='', read_only='', shared='', command='', user_command='', command_bg='', prog_name='', logfile=''
    Sep 22 21:43:22 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'IBM-ESXS_ST31000424SS' is set as passed through.
    Sep 22 21:43:22 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 21:43:22 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-id/scsi-35000c500262e13f3-part2.
    Sep 22 21:43:22 hp unassigned.devices: Partition found with the following attributes: serial_short='9WK3NR0J0000C1299VJ0', device='/dev/sdf2', serial='ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', uuid='7876DE2776DDE642', part='2', disk='/dev/sdf', label='DVR', disk_label='DVR', fstype='ntfs', mountpoint='/mnt/disks/DVR', luks='', mounted='', not_unmounted='', pool='', pass_through='1', disable_mount='1', target='', size='0', used='0', avail='0', owner='udev', automount='', read_only='', shared='', command='', user_command='', command_bg='', prog_name='', logfile=''
    Sep 22 21:43:22 hp unassigned.devices: Disk with serial 'ST31000424SS_9WK3NR0J0000C1299VJ0_35000c500262e13f3', mountpoint 'DVR' is set as passed through.
    Sep 22 21:43:22 hp unassigned.devices: Mount: Received a udev 'add partition'.

     

    hp-diagnostics-20220922-2145.zip

    Link to comment

    That UD disk is continually being re-discovered by udev and triggering a udev event.  How is it attached to your server?  I'd say you have a cable or power supply problem to that disk.

    Link to comment

    that ud disk is the sas disk. as all disks are attached via a backplane i would doubt that its a cable or power supply issue otherwise it would affect all disks wouldnt it? anyway i put it in a different slot same result. so i removed it from the server, still it spams:

     

    Quote

    Sep 22 22:19:45 hp  ool www[2548]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'save'
    Sep 22 22:20:01 hp kernel: sdd: sdd1
    Sep 22 22:20:01 hp kernel: sdb: sdb1
    Sep 22 22:20:01 hp kernel: sdg: sdg1
    Sep 22 22:20:01 hp kernel: sdc: sdc1
    Sep 22 22:20:01 hp unassigned.devices: Reload: A udev 'change partition' initiated a reload of udev info.
    Sep 22 22:20:01 hp unassigned.devices: Updating udev information...
    Sep 22 22:20:01 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-id/ata-SanDisk_SSD_PLUS_1000GB_2022JN458902-part1.
    Sep 22 22:20:01 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-id/wwn-0x5001b444a775ef36-part1.
    Sep 22 22:20:01 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-path/pci-0000:08:00.0-sas-0x3001438037d9568a-lun-0-part1.
    Sep 22 22:20:01 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-uuid/1e4e331f-b2e1-4395-970e-df01e96d64b6.
    Sep 22 22:20:01 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:20:01 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:20:01 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:20:01 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:20:32 hp kernel: sdd: sdd1
    Sep 22 22:20:32 hp kernel: sdb: sdb1
    Sep 22 22:20:32 hp kernel: sdg: sdg1
    Sep 22 22:20:32 hp kernel: sdc: sdc1
    Sep 22 22:20:32 hp unassigned.devices: Reload: A udev 'change partition' initiated a reload of udev info.
    Sep 22 22:20:32 hp unassigned.devices: Updating udev information...
    Sep 22 22:20:32 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-id/ata-SanDisk_SSD_PLUS_1000GB_2022JN458902-part1.
    Sep 22 22:20:32 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-id/wwn-0x5001b444a775ef36-part1.
    Sep 22 22:20:32 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-path/pci-0000:08:00.0-sas-0x3001438037d9568a-lun-0-part1.
    Sep 22 22:20:32 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-uuid/1e4e331f-b2e1-4395-970e-df01e96d64b6.
    Sep 22 22:20:32 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:20:32 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:20:32 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:20:32 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:21:03 hp kernel: sdd: sdd1
    Sep 22 22:21:03 hp kernel: sdb: sdb1
    Sep 22 22:21:03 hp kernel: sdc: sdc1
    Sep 22 22:21:03 hp unassigned.devices: Reload: A udev 'change partition' initiated a reload of udev info.
    Sep 22 22:21:03 hp kernel: sdg: sdg1
    Sep 22 22:21:03 hp unassigned.devices: Updating udev information...
    Sep 22 22:21:03 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-id/ata-SanDisk_SSD_PLUS_1000GB_2022JN458902-part1.
    Sep 22 22:21:03 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-id/wwn-0x5001b444a775ef36-part1.
    Sep 22 22:21:03 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-path/pci-0000:08:00.0-sas-0x3001438037d9568a-lun-0-part1.
    Sep 22 22:21:03 hp unassigned.devices: Udev: Update udev info for /dev/disk/by-uuid/1e4e331f-b2e1-4395-970e-df01e96d64b6.
    Sep 22 22:21:03 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:21:04 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:21:04 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:21:04 hp unassigned.devices: Mount: Received a udev 'add partition'.
    Sep 22 22:21:15 hp  ool www[5790]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'save'
    Sep 22 22:21:35 hp kernel: sdd: sdd1
    Sep 22 22:21:35 hp kernel: sdb: sdb1
    Sep 22 22:21:35 hp kernel: sdg: sdg1
    Sep 22 22:21:35 hp kernel: sdc: sdc1

     

    Also opened the machine, reseated every cable, the raid card itself, the disks... still the same...

     

    as that sas disk is directly forwarded to a windows vm, shouldnt i see something there as well? as it is the disk for my surveilance i should get corrupted files or not? i dont see any such issues

     

     

    edit: it gets worse. now even the parity wont stay down. i guess its a hardware issue after all... welp...

    Edited by Michael H
    Link to comment

    Ok, it's probably not related to the UD disk itself, but something is triggering udev to re-discover the disks in your server.  If that's true, then this might be the explanation.  I know you aren't thinking power supply, but take another look.  Whatever it is affects all disks.

    Link to comment
    On 9/12/2022 at 4:58 PM, Michael H said:

    so as i said, its not my raid controller (although i completely agree they can be bothersome)

    Like others mentions, raid controller may be the issue and I also agree that. Seems you only have 3 data disk, could you try connect disks to onboard SATA to bypass the RAID controller for troubleshoot ?

     

    I use Unarid several yrs ( up to 6.10 didn't try 6.11 ), spindown usually work well with onboard SATA or LSI HBA. Below is one of 7x24 Unraid, basically it only spinup once per day. ( Other spinup just because I access it )

     

    image.png.6f9a003f13850b2a65f626d26d706b97.png

    Link to comment

    as mentioned a few replies before, the server does not have sata ports.

     

    i do however have 2 sas ports directly on the motherboard, each supporting 4 drives via my backplate . so i have the 4 array disks on the motherboard now and the cache and the ud-disk still on the raid controller as i only had one fitting sas cable which i borrowed from another server.

     

    the 4 disks stayed down for half an hour (new record) but then spun up almost in sync one after another. i spun dem down, they immedeately spun up again. now they are down and i am monitoring.

     

    server still vomits the udev to logs (probably because of the cache and the ud on the raid controller). so my next step is to buy 2 sas cables to use both ports on the moderboard. i loose 4 slots for disks for now, but if this ends up resolving the issue the energy bill savings alone would fund a new lsi card in about a year.

    Link to comment

    Update for now: Completely removed the RAID card, used the SAS Ports on the motherboard. Disks stay down now, however the logs still spits out

     

    Quote

    Sep 26 22:15:19 hp kernel: sdg: sdg1
    Sep 26 22:15:19 hp unassigned.devices: Disk with serial 'WDC_WD40PURZ-85TTDY0_WD-WCC7K3VU31JT', mountpoint 'WD-WCC7K3VU31JT' is set as passed through.
    Sep 26 22:15:52 hp kernel: sdg: sdg1
    Sep 26 22:15:52 hp unassigned.devices: Disk with serial 'WDC_WD40PURZ-85TTDY0_WD-WCC7K3VU31JT', mountpoint 'WD-WCC7K3VU31JT' is set as passed through.
    Sep 26 22:16:25 hp kernel: sdg: sdg1
    Sep 26 22:16:25 hp unassigned.devices: Disk with serial 'WDC_WD40PURZ-85TTDY0_WD-WCC7K3VU31JT', mountpoint 'WD-WCC7K3VU31JT' is set as passed through.
    Sep 26 22:16:57 hp kernel: sdg: sdg1
    Sep 26 22:16:58 hp unassigned.devices: Disk with serial 'WDC_WD40PURZ-85TTDY0_WD-WCC7K3VU31JT', mountpoint 'WD-WCC7K3VU31JT' is set as passed through.
    Sep 26 22:17:30 hp kernel: sdg: sdg1
    Sep 26 22:17:30 hp unassigned.devices: Disk with serial 'WDC_WD40PURZ-85TTDY0_WD-WCC7K3VU31JT', mountpoint 'WD-WCC7K3VU31JT' is set as passed through.
    Sep 26 22:18:03 hp kernel: sdg: sdg1
    Sep 26 22:18:03 hp unassigned.devices: Disk with serial 'WDC_WD40PURZ-85TTDY0_WD-WCC7K3VU31JT', mountpoint 'WD-WCC7K3VU31JT' is set as passed through.
    Sep 26 22:18:36 hp kernel: sdg: sdg1
    Sep 26 22:18:36 hp unassigned.devices: Disk with serial 'WDC_WD40PURZ-85TTDY0_WD-WCC7K3VU31JT', mountpoint 'WD-WCC7K3VU31JT' is set as passed through.
    Sep 26 22:19:09 hp kernel: sdg: sdg1
    Sep 26 22:19:09 hp unassigned.devices: Disk with serial 'WDC_WD40PURZ-85TTDY0_WD-WCC7K3VU31JT', mountpoint 'WD-WCC7K3VU31JT' is set as passed through.
    Sep 26 22:19:42 hp kernel: sdg: sdg1
    Sep 26 22:19:42 hp unassigned.devices: Disk with serial 'WDC_WD40PURZ-85TTDY0_WD-WCC7K3VU31JT', mountpoint 'WD-WCC7K3VU31JT' is set as passed through.

     

    roughly every 30 seconds. as this is not the sas disk that was doing it before, but a completely different disk usually not present in the server and also not connected via the raid card i guess the ud plugin does not like that it is passed physically to a windows vm (/dev/disk/by-id/xxxxx).

     

    as this is just a nuissance when trying to view the log and not a bug with unraid all that is left is to thank you for sticking with me and giving suggestions and saying sorry for wasting everones time.

    Link to comment

    just while i have @dlandon here... it seems the log-vomit is because of your (awesome!) plugin. when i deinstall it it stops. im not saying your plugin is causing it, but making the issue visible. so that may be something you could take to limetech.

     

    let me know if you need anything from me

    Link to comment
    1 hour ago, Michael H said:

     

    let me know if you need anything from me

    It's something unique to your system.  Can you do the following:

    • Install UD if it is not already installed.
    • Set the "Debug Log Level" in UD settings to "Udev and Hotplug".
    • Let it run for a few minutes and log those udev entries in the log.
    • Post another diagnostics.
    • Turn off the "Debug Log Level".  It can be overly chatty.

     

    Thank you.

    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
    Add a comment...

    ×   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.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.