starfox101
Occasional Visitor
I have posted this on the qnap forum, but you guy's seem to be on top of things. I ran this program qnap supplies to check the system when the drives will not spend down:
kjournald(1218): WRITE block 3312 on md13
md13_raid1(1104): WRITE block 160512 on sda4
md13_raid1(1104): WRITE block 160512 on sdc4
md13_raid1(1104): WRITE block 160512 on sdd4
md13_raid1(1104): WRITE block 160512 on sdb4
md9_raid1(1030): WRITE block 1060096 on sda1
md9_raid1(1030): WRITE block 1060096 on sdd1
md9_raid1(1030): WRITE block 1060096 on sdc1
seems kjournald is keeping the drives active. I have updated firmware for the drives last week. Maybe this is causing the problem?
I'm not sure what to do. I am running the bad block scan, and check disk, on the admin web pages. Looks like around 4 hr per drive with bad block scan.
Just looking for information, something I need to do, am I using the right scans?
Thanks for the help
kjournald(1218): WRITE block 3312 on md13
md13_raid1(1104): WRITE block 160512 on sda4
md13_raid1(1104): WRITE block 160512 on sdc4
md13_raid1(1104): WRITE block 160512 on sdd4
md13_raid1(1104): WRITE block 160512 on sdb4
md9_raid1(1030): WRITE block 1060096 on sda1
md9_raid1(1030): WRITE block 1060096 on sdd1
md9_raid1(1030): WRITE block 1060096 on sdc1
seems kjournald is keeping the drives active. I have updated firmware for the drives last week. Maybe this is causing the problem?
I'm not sure what to do. I am running the bad block scan, and check disk, on the admin web pages. Looks like around 4 hr per drive with bad block scan.
Just looking for information, something I need to do, am I using the right scans?
Thanks for the help