May 1, 201313 yr I ran a parity check last night/this morning, and after it completed I noticed right away that only the parity had spun down after 15 minutes. I made sure all access to the array from various clients was stopped, stopped the array, rebooted the server, and am still seeing the same issue. Disks 1-6 are supposed to spin full time, but the rest should spin down after 15 minutes. The log shows parity spinning down exactly 15 minutes after boot up; 10:50 am. Thanks. v4.7 CPU: AMD Sempron 140 Motherboard: BIOSTAR A760G M2+ Micro ATX RAM: Kingston 2GB Case: AZZA Helios 910 Drive Cage(s): Icy Dock 5 in 3 Drive Cage(s): 2x SUPERMICRO CSE-M35T 5 in 3 Power Supply: Corsair TX650 SATA Expansion Card(s): SUPERMICRO AOC-SASLP-MV8 PCI Express x4 SAS RAID Controller Cables: 18 inch Fans: Stock fans Flash Drive: 2GB SanDisk Cruzer Micro syslog-2013-05-01.zip
May 3, 201313 yr I guess this is a difficult issue to resolve. Whatever will I do? If you have no other disk activity occurring, you can sometimes get an idea of what is accessing the disks by running inotifywait or turning on disk buffer cache messages. Either one will show you the disk activity and name the files involved. Once you know what is being accessed, it is usually easy to figure out which program is doing it. See the two links in this post: http://lime-technology.com/forum/index.php?topic=27162.msg238578#msg238578
Archived
This topic is now archived and is closed to further replies.