February 4, 201610 yr I have 10 disks: Parity, 1 through 8 data, and cache. When in the shares>include or exclude disks menu it list disks 1 through 9. There are no descriptions next to the disks. There is no way to know which 9 drives are on the include/exclude UI.
February 4, 201610 yr I will leave this here for a while till we get more information to let us decide whether this belongs in Defect Reports. If not I will move it to General Support. This seems to be working as expected for me. Can you post a screenshot showing exactly what you are seeing?
February 5, 201610 yr Author Here is my screenshot showing 9 disks. I assume either the parity or cache is missing, but which one .
February 5, 201610 yr Here is my screenshot showing 9 disks. I assume either the parity or cache is missing, but which one . Neither parity or cache are meant to show up in that list, so it is not clear what you think is wrong. I assume it is that you only expected to see 8 disks? Perhaps you should post the diagnostics file (Tools->Diagnostics) so we can see what is configured and what is being detected.
February 5, 201610 yr Author Here is my lsscsi.txt showing my 11 storage devices. Top is unRAID flash, one of the ST3000DM001 is parity one CT480BX200SSD1 is cache. Is there another file that would be useful? The whole zip is too large to post ATM. [0:0:0:0] disk SanDisk Ultra Fit 1.00 /dev/sda /dev/sg0 state=running queue_depth=1 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/0:0:0:0 [/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/host0/target0:0:0/0:0:0:0] [1:0:0:0] disk ATA ST1000DX001-1CM1 CC43 /dev/sdb /dev/sg1 state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/1:0:0:0 [/sys/devices/pci0000:00/0000:00:1f.2/ata1/host1/target1:0:0/1:0:0:0] [2:0:0:0] disk ATA ST3000DM001-1CH1 CC43 /dev/sdc /dev/sg2 state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/2:0:0:0 [/sys/devices/pci0000:00/0000:00:1f.2/ata2/host2/target2:0:0/2:0:0:0] [3:0:0:0] disk ATA ST1000DX001-1CM1 CC43 /dev/sdd /dev/sg3 state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/3:0:0:0 [/sys/devices/pci0000:00/0000:00:1f.2/ata3/host3/target3:0:0/3:0:0:0] [4:0:0:0] disk ATA ST1000DX001-1CM1 HP70 /dev/sde /dev/sg4 state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/4:0:0:0 [/sys/devices/pci0000:00/0000:00:1f.2/ata4/host4/target4:0:0/4:0:0:0] [5:0:0:0] disk ATA ST1000DX001-1CM1 CC43 /dev/sdf /dev/sg5 state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/5:0:0:0 [/sys/devices/pci0000:00/0000:00:1f.2/ata5/host5/target5:0:0/5:0:0:0] [6:0:0:0] disk ATA ST1000DX001-1CM1 CC43 /dev/sdg /dev/sg6 state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/6:0:0:0 [/sys/devices/pci0000:00/0000:00:1f.2/ata6/host6/target6:0:0/6:0:0:0] [7:0:0:0] disk ATA CT480BX200SSD1 .4 /dev/sdh /dev/sg7 state=running queue_depth=31 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/7:0:0:0 [/sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata7/host7/target7:0:0/7:0:0:0] [8:0:0:0] disk ATA CT480BX200SSD1 .4 /dev/sdi /dev/sg8 state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/8:0:0:0 [/sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/ata8/host8/target8:0:0/8:0:0:0] [9:0:0:0] disk ATA ST3000DM001-1CH1 CC43 /dev/sdj /dev/sg9 state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/9:0:0:0 [/sys/devices/pci0000:00/0000:00:1c.4/0000:05:00.0/ata9/host9/target9:0:0/9:0:0:0] [10:0:0:0] disk ATA ST3000DM001-1CH1 CC43 /dev/sdk /dev/sg10 state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/10:0:0:0 [/sys/devices/pci0000:00/0000:00:1c.4/0000:05:00.0/ata10/host10/target10:0:0/10:0:0:0]
February 5, 201610 yr I was interested in seeing the various configuration files. The diagnostics.zip file is not normally that large - surprised that yours is and would be interested to know why! Do you have lots of errors being logged? Perhaps you can remove the syslog from it to bring the size down?
February 5, 201610 yr According to disk.cfg, CT480BX200SSD1_1546F010AEA7 is the cache drive. What is CT480BX200SSD1_1545F01050E8?
February 5, 201610 yr Author Initial config had it as a BTRFS cache drive #2. Then it crashed and needed formatted. I read up on the forums and decided to go with XFS and have the extra ssd as a spare performance drive.
February 5, 201610 yr I also notice that the file smart-one.cfg has a mention of disk9! Not sure that that file relates to.
February 5, 201610 yr Initial config had it as a BTRFS cache drive #2. Then it crashed and needed formatted. I read up on the forums and decided to go with XFS and have the extra ssd as a spare performance drive. Do you have Unassigned Devices plugin installed?
February 5, 201610 yr Author Installed now, it lists no drives. "No unassigned disks available." i rebooted, here is an un-doctored diagnostics. Much smaller now, 65KB vs 200KB+ tower-diagnostics-20160205-2031.zip
February 5, 201610 yr Installed now, it lists no drives. "No unassigned disks available." i rebooted, here is an un-doctored diagnostics. Much smaller now, 65KB vs 200KB+ Your disks.cfg shows 8 array disks. That's all that should show in the drop down list for included and excluded disks. Look at the "/usr/local/emhttp/state/disks.ini" file. You will see ["disk1"] through ["disk8"]. If there is a ["disk9"] then you may have found a bug.
February 6, 201610 yr Author This work for you? /usr/local/emhttp/state/disks.ini: line 1: [parity]: command not found /usr/local/emhttp/state/disks.ini: line 25: [disk1]: command not found /usr/local/emhttp/state/disks.ini: line 53: [disk2]: command not found /usr/local/emhttp/state/disks.ini: line 81: [disk3]: command not found /usr/local/emhttp/state/disks.ini: line 109: [disk4]: command not found /usr/local/emhttp/state/disks.ini: line 137: [disk5]: command not found /usr/local/emhttp/state/disks.ini: line 165: [disk6]: command not found /usr/local/emhttp/state/disks.ini: line 193: [disk7]: command not found /usr/local/emhttp/state/disks.ini: line 221: [disk8]: command not found /usr/local/emhttp/state/disks.ini: line 249: [cache]: command not found /usr/local/emhttp/state/disks.ini: line 278: [flash]: command not found
February 6, 201610 yr It looks like the drop down showing disk9 is the issue and not the configuration of the array disks.
February 6, 201610 yr Author Fresh Diagnostics, same issue. Disks 1 through 9 As a feature request, could the disk numbers also come with a size/model identifier here? Not everyone can remember which drive is #7 tower-diagnostics-20160206-2333.zip
June 10, 201610 yr This is old, but it does appear there may be a bug. It was never resolved, so unknown if there's a bug and whether it's been fixed in subsequent releases.
June 18, 201610 yr Author RobJ, Still seeing this in 6.1.9. Did you want updated screenshots or diags? I really do think that adding label info here would help resolve this bug.
June 18, 201610 yr RobJ, Still seeing this in 6.1.9. Did you want updated screenshots or diags? I really do think that adding label info here would help resolve this bug. You need to delete the file /boot/config/smart-one.cfg, it contains a reference to the non-existing disk9. I suppose you did have a disk9 in the past and decided to change the array configuration, which puts the file smart-one.cfg out of sync (if it was existing).
June 18, 201610 yr Perhaps this should be changed to a Feature Request, as harika suggested above, and replace the disk numbers with the drive serial numbers, in the smart-*.cfg files. Sorry bonienl, I think I'm getting pretty good at finding work for you!
July 10, 20169 yr I re-purposed a server to finally start using VMs and I'm having the same issue, there are only 3 arrays disks, but on shares include/exclude I get disks 1 to 4. Deleting /boot/config/smart-one.cfg and rebooting didn't fix it, diagnostics attached. tower7-diagnostics-20160710-1203.zip
July 12, 20169 yr I re-purposed a server to finally start using VMs and I'm having the same issue, there are only 3 arrays disks, but on shares include/exclude I get disks 1 to 4. Deleting /boot/config/smart-one.cfg and rebooting didn't fix it, diagnostics attached. A few things I noticed (nothing particularly unusual) - - In the vars, the array is 3 data drives (1, 2, and 3) and a parity drive, not yet valid. In the vars, there are slots for disk1 through disk4, but only disk1 through disk3 are filled out, fully operational, disk4 is empty. Disk 4 is DISK_NP. - However sec_afp, sec, and sec_nfs are all setup with disk1 through disk4, with completely equivalent settings. - Global and individual share settings do not have any includes or excludes set up, no drives at all listed. - I could find no mentions of Disk 4 anywhere, in any config file. All I can suggest is that the shares dropdown must be including any *potential* drive, from the available slots. I suspect that if you increased the slots higher, you would have additional phantom drive choices! I suppose that *could* be called a feature, allowing a user to plan and configure for the future! The following seems to be another vestige from the past - monitor ( [smart] => Array ( [sde.187] => 18 [sde.199] => 27 [sdc.199] => 1 ) There is an sdc and an sde, but they don't correlate to this. In fact, none of the current drives has a 187, and all of the current drives has a 199 of zero. I was unable to find a single source file for this info, found in the vars. As I understand here, he has deleted the smart persistence var file and rebooted. So where is this info coming from? Also, in my opinion, the usage of sdX drive symbols is a mistake, as they constantly change, even from boot to boot. They are only valid within a single session. I assume the new system path creation has created the double isos shares, both isos and ISOs.
July 12, 20169 yr monitor ( [smart] => Array ( [sde.187] => 18 [sde.199] => 27 [sdc.199] => 1 ) There is an sdc and an sde, but they don't correlate to this. In fact, none of the current drives has a 187, and all of the current drives has a 199 of zero. I was unable to find a single source file for this info, found in the vars. As I understand here, he has deleted the smart persistence var file and rebooted. So where is this info coming from? Also, in my opinion, the usage of sdX drive symbols is a mistake, as they constantly change, even from boot to boot. They are only valid within a single session. I assume the new system path creation has created the double isos shares, both isos and ISOs. The references to sdX are set in /boot/config/plugins/dynamix/monitor.ini. This file keeps SMART errors information after a system reboot. In others words it is used to restore previously recorded SMART errors. sdX references are only used for disks which are unassigned when the array is started. These disks do not have a diskX designation unless they become part of the array or cache pool. Since the assignment of the disks has changed after the SMART errors occurred, the course of action here is to delete the monitor.ini file and reboot the system. Ps. Update has been made to delete disk history files automatically when a new config is performed and avoid situations like these.
Archived
This topic is now archived and is closed to further replies.