jaybee Posted October 16, 2015 Posted October 16, 2015 I just installed the latest Unraid 6.1.3 onto a server and I've noticed: 1: It takes a longtime to start up (5-10 minutes) 2: Sometimes it is impossible to navigate to the webgui. When I can, navigation around the pages is very slow or it never completes. 3: Within a few hours the syslog grew to 130MB 4: There are many errors and a lot of repeated logs So far all I have managed to do is install 1 x plugin (preclear http) and the preclear script. I just wanted to preclear some disks and I have not done any other config yet or additions. I went to do a preclear but the server hung up. I won't attach the 130MB sys log but towards the end of that period that the server was on just before it locked up, the last messages logged were as below, the same line repeated hundreds of times: Oct 16 15:16:58 Tower kernel: sd 0:0:0:0: rejecting I/O to offline device And at the time I got a top output of: 0k total, 0k used, 0k free, 515164k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 13647 root 20 0 9796 1628 1380 R 100 0.1 26:37.11 dd 13648 root 20 0 8760 1608 1372 S 38 0.1 11:44.55 sed 1178 root 20 0 228m 3160 2016 S 25 0.2 6:05.31 rsyslogd 874 root 20 0 0 0 0 S 0 0.0 0:03.87 kworker/3:2 1377 root 20 0 188m 4756 3452 S 0 0.2 0:03.36 nmbd 19895 root 20 0 13284 2220 1912 R 0 0.1 0:00.10 top 1 root 20 0 4368 1552 1456 S 0 0.1 0:11.50 init 2 root 20 0 0 0 0 S 0 0.0 0:00.01 kthreadd 3 root 20 0 0 0 0 S 0 0.0 0:00.24 ksoftirqd/0 5 root 0 -20 0 0 0 S 0 0.0 0:00.00 kworker/0:0H 7 root 20 0 0 0 0 S 0 0.0 0:06.94 rcu_preempt 8 root 20 0 0 0 0 S 0 0.0 0:00.00 rcu_sched 9 root 20 0 0 0 0 S 0 0.0 0:00.00 rcu_bh 10 root RT 0 0 0 0 S 0 0.0 0:00.35 migration/0 11 root RT 0 0 0 0 S 0 0.0 0:00.34 migration/1 12 root 20 0 0 0 0 S 0 0.0 0:00.21 ksoftirqd/1 13 root 20 0 0 0 0 S 0 0.0 0:00.00 kworker/1:0 14 root 0 -20 0 0 0 S 0 0.0 0:00.00 kworker/1:0H 15 root RT 0 0 0 0 S 0 0.0 0:00.35 migration/2 16 root 20 0 0 0 0 S 0 0.0 0:00.28 ksoftirqd/2 17 root 20 0 0 0 0 S 0 0.0 0:00.00 kworker/2:0 18 root 0 -20 0 0 0 S 0 0.0 0:00.00 kworker/2:0H 19 root RT 0 0 0 0 S 0 0.0 0:00.34 migration/3 20 root 20 0 0 0 0 S 0 0.0 0:00.28 ksoftirqd/3 22 root 0 -20 0 0 0 S 0 0.0 0:00.00 kworker/3:0H 23 root 0 -20 0 0 0 S 0 0.0 0:00.00 khelper 24 root 20 0 0 0 0 S 0 0.0 0:00.00 kdevtmpfs 25 root 0 -20 0 0 0 S 0 0.0 0:00.00 netns 28 root 0 -20 0 0 0 S 0 0.0 0:00.00 perf 262 root 0 -20 0 0 0 S 0 0.0 0:00.00 writeback 264 root 25 5 0 0 0 S 0 0.0 0:00.00 ksmd 265 root 39 19 0 0 0 S 0 0.0 0:00.11 khugepaged 266 root 0 -20 0 0 0 S 0 0.0 0:00.00 crypto 267 root 0 -20 0 0 0 S 0 0.0 0:00.00 kintegrityd 268 root 0 -20 0 0 0 S 0 0.0 0:00.00 bioset 270 root 0 -20 0 0 0 S 0 0.0 0:00.00 kblockd Attached should be the smaller syslog (inside a diagnostics dump zip) where the server was started up for a shorter time. I managed to get onto the webgui once and change the page once then I gave up. Notice the same log repeating a lot: Oct 16 16:14:06 Tower kernel: blk_update_request: I/O error, dev sdn, sector 0 Oct 16 16:14:06 Tower kernel: Buffer I/O error on dev sdn, logical block 0, async page read Oct 16 16:14:10 Tower kernel: sd 0:0:13:0: [sdn] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Oct 16 16:14:10 Tower kernel: sd 0:0:13:0: [sdn] Sense Key : 0x3 [current] Oct 16 16:14:10 Tower kernel: sd 0:0:13:0: [sdn] ASC=0x11 ASCQ=0x0 Oct 16 16:14:10 Tower kernel: sd 0:0:13:0: [sdn] CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00 tower-diagnostics-20151016-1614.zip
itimpi Posted October 16, 2015 Posted October 16, 2015 The syslog shows that /dev/sdn (a 750GB) disk has got some sort of major issue as it is reporting repeating failures to read sector 0. Either that disk is failing or the cabling to it is suspect
jaybee Posted October 16, 2015 Author Posted October 16, 2015 There are 16 disks in there and they all appear in the logs in the same way. So it complains about all disks I think. They can't all be failing so is this some problem with the RAID Card they all connect to? In the BIOS the card functions fine and I can go in and view disk info and perform actions as normal. Could it be that it is not compatible with unraid? The motherboard is a supermicro and the RAID card is an Adaptec PCI-X one I believe. The disks are not in a RAID array and have just been configured to be JBOD. EDIT: Not in the log I attached actually. Hmm...yes it does only complain about /dev/sdn Would a bad disk cause the entire GUI to lock up though?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.