July 6, 20178 yr It's been a long time all, sorry to come back with a request for help...but ya know....that's life. I installed a new 8TB drive on Tuesday, ran the pre-clear successfully and all is good on that front. (Damn they are fast!) Today while preparing to swap it in for my Parity drive, I was using unBALANCE to move some files around when the copy abruptly died...don't worry, I'm not going to ask about the plugin. In investigating the issue I looked in the syslog and found scrolling errors from sda: Jul 6 05:14:07 Storage kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jul 6 05:14:07 Storage kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x6 [current] Jul 6 05:14:07 Storage kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x28 ASCQ=0x0 Jul 6 05:14:07 Storage kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 10 00 00 00 08 00 Jul 6 05:14:07 Storage kernel: blk_update_request: I/O error, dev sda, sector 4096 Jul 6 05:14:07 Storage rc.diskinfo[26060]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 668 Jul 6 05:14:07 Storage rc.diskinfo[26060]: SIGHUP received, forcing refresh of disks info. Jul 6 05:14:07 Storage rc.diskinfo[26060]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 668 Jul 6 05:14:07 Storage rc.diskinfo[26060]: SIGHUP ignored - already refreshing disk info. Jul 6 05:14:08 Storage rc.diskinfo[26060]: PHP Warning: in_array() expects parameter 2 to be array, null given in /etc/rc.d/rc.diskinfo on line 364 Jul 6 05:14:08 Storage rc.diskinfo[26060]: PHP Warning: in_array() expects parameter 2 to be array, null given in /etc/rc.d/rc.diskinfo on line 364 Now my UI shows all disks as innactive even though they seem to be spinning from the CLI, and serving media files to my devices. I have a the syslog file and can post it, but I'm not sure it will be useful. Anyone with a clue out there?
July 6, 20178 yr Author I'm holding off rebooting, I've never had a situation like this before and I'm not sure it would be wise to cast that hail mary until I know more about what is happening. Espically as I just noticed that this is sda, so my flash drive...Egads. Update: Removed the Stats plugin just on the off chance that was impacting. No change storage-diagnostics-20170706-1323.zip Edited July 6, 20178 yr by Tybio
July 6, 20178 yr Author Ok, I finally just rebooted and the error seems to have cleared. However, /mnt/disk6 is totally empty (No files at all) but the UI shows it at 3.06G used. Is something out of sync? I was preparing to remove a few old disks and shrink the array, should I worry that this isn't reporting proper usage before I extract and rebuild parity?
July 6, 20178 yr Depending on file system type and total size, 3GB probably isn't too far out of line for an empty formatted disk. The file system bookkeeping area itself takes up space. Have you already emptied all the disks you want to remove? Was this one of the drives you planned on removing?
July 6, 20178 yr Author I'm emptying the last drive now, yes..this is one that I'm pulling. I guess I normally see them go down to 33M or so, it makes sense that it's not a big deal...but I thought I'd ask the wise ones before actually doing the new config ;).
July 6, 20178 yr 5 hours ago, Tybio said: It's been a long time all, sorry to come back with a request for help...but ya know....that's life. I installed a new 8TB drive on Tuesday, ran the pre-clear successfully and all is good on that front. (Damn they are fast!) Today while preparing to swap it in for my Parity drive, I was using unBALANCE to move some files around when the copy abruptly died...don't worry, I'm not going to ask about the plugin. In investigating the issue I looked in the syslog and found scrolling errors from sda: Jul 6 05:14:07 Storage kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jul 6 05:14:07 Storage kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x6 [current] Jul 6 05:14:07 Storage kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x28 ASCQ=0x0 Jul 6 05:14:07 Storage kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 10 00 00 00 08 00 Jul 6 05:14:07 Storage kernel: blk_update_request: I/O error, dev sda, sector 4096 Jul 6 05:14:07 Storage rc.diskinfo[26060]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 668 Jul 6 05:14:07 Storage rc.diskinfo[26060]: SIGHUP received, forcing refresh of disks info. Jul 6 05:14:07 Storage rc.diskinfo[26060]: PHP Warning: Missing argument 2 for force_reload() in /etc/rc.d/rc.diskinfo on line 668 Jul 6 05:14:07 Storage rc.diskinfo[26060]: SIGHUP ignored - already refreshing disk info. Jul 6 05:14:08 Storage rc.diskinfo[26060]: PHP Warning: in_array() expects parameter 2 to be array, null given in /etc/rc.d/rc.diskinfo on line 364 Jul 6 05:14:08 Storage rc.diskinfo[26060]: PHP Warning: in_array() expects parameter 2 to be array, null given in /etc/rc.d/rc.diskinfo on line 364 Now my UI shows all disks as innactive even though they seem to be spinning from the CLI, and serving media files to my devices. I have a the syslog file and can post it, but I'm not sure it will be useful. Anyone with a clue out there? rc.diskinfo is a script in the preclear plugin. Be sure you have the latest version of preclear installed.
Archived
This topic is now archived and is closed to further replies.