theone Posted September 27, 2015 Author Share Posted September 27, 2015 As you can see there is no manufacturer information listed. Quote Link to comment
bonienl Posted September 27, 2015 Share Posted September 27, 2015 Run /usr/sbin/update-smart-drivedb This will update your smart database to the latest version, might help! Quote Link to comment
theone Posted September 27, 2015 Author Share Posted September 27, 2015 Run /usr/sbin/update-smart-drivedb This will update your smart database to the latest version, might help! That's what the update button in the plugin does. Quote Link to comment
opentoe Posted October 4, 2015 Share Posted October 4, 2015 So how does a WD drive have a missing "Manufacturer" field? Strange, right? Quote Link to comment
theone Posted October 4, 2015 Author Share Posted October 4, 2015 So how does a WD drive have a missing "Manufacturer" field? Strange, right? This series WD4003FZEX is probably not in the database. Maybe it can be requested/added. Quote Link to comment
opentoe Posted October 4, 2015 Share Posted October 4, 2015 So how does a WD drive have a missing "Manufacturer" field? Strange, right? This series WD4003FZEX is probably not in the database. Maybe it can be requested/added. Correct. I just looked and that model is not in the database. I guess not a very popular model. I'll see if I can make the request. Quote Link to comment
bondoo0 Posted October 5, 2015 Share Posted October 5, 2015 I installed the plugin and tried to use it but it doesn't seem to save the information. There is also a bunch of php errors when the plugin first loads up the layout page: Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 111 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 111 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 111 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 142 I am using Unraid 6.1.2 and Firefox 40.0.3. I'm getting the same error. Was there ever any resolution for this? All of my drives show up on the data tab. No changes are saved either on the layout page (for the elements displayed, however the number of rows does save), or the data page. And after the first time, I get the listed error on the layout page. Quote Link to comment
theone Posted October 5, 2015 Author Share Posted October 5, 2015 The problem was a u3 usb drive that was recognized as a usb and a cdrom drive. It needed to be formated and the cdrom partition removed. Quote Link to comment
bondoo0 Posted October 5, 2015 Share Posted October 5, 2015 The problem was a u3 usb drive that was recognized as a usb and a cdrom drive. It needed to be formated and the cdrom partition removed. Any other thoughts (in my case the USB is showing up correctly) or things to try? Quote Link to comment
theone Posted October 5, 2015 Author Share Posted October 5, 2015 Please post output of "ls - las /dev/disk/by-id". Quote Link to comment
bondoo0 Posted October 5, 2015 Share Posted October 5, 2015 root@unraid-server1:~# ls -las /dev/disk/by-id total 0 0 drwxr-xr-x 2 root root 920 Oct 5 11:38 ./ 0 drwxr-xr-x 7 root root 140 Oct 3 08:48 ../ 0 lrwxrwxrwx 1 root root 9 Oct 5 11:38 ata-ST3000DM001-1CH166_W1F21S82 -> ../../sdf 0 lrwxrwxrwx 1 root root 10 Oct 5 11:38 ata-ST3000DM001-1CH166_W1F21S82-part1 -> ../../sdf1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 ata-ST3000DM001-1CH166_W1F446BM -> ../../sdc 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 ata-ST3000DM001-1CH166_W1F446BM-part1 -> ../../sdc1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 ata-ST3000DM001-1ER166_Z5005QA3 -> ../../sda 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 ata-ST3000DM001-1ER166_Z5005QA3-part1 -> ../../sda1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 ata-ST3000DM001-1ER166_Z5005R6J -> ../../sdb 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 ata-ST3000DM001-1ER166_Z5005R6J-part1 -> ../../sdb1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 ata-WDC_WD20EADS-00R6B0_WD-WCAVY1805337 -> ../../sdi 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 ata-WDC_WD20EADS-00R6B0_WD-WCAVY1805337-part1 -> ../../sdi1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 ata-WDC_WD20EARX-00PASB0_WD-WMAZA8335536 -> ../../sdg 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 ata-WDC_WD20EARX-00PASB0_WD-WMAZA8335536-part1 -> ../../sdg1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 ata-WDC_WD20EARX-32PASB0_WD-WCAZAF670682 -> ../../sdk 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 ata-WDC_WD20EARX-32PASB0_WD-WCAZAF670682-part1 -> ../../sdk1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 ata-WDC_WD20EZRX-00D8PB0_WD-WMC4N1605008 -> ../../sdj 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 ata-WDC_WD20EZRX-00D8PB0_WD-WMC4N1605008-part1 -> ../../sdj1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T3332087 -> ../../sde 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 ata-WDC_WD30EFRX-68AX9N0_WD-WMC1T3332087-part1 -> ../../sde1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 ata-WDC_WD5003ABYX-01WERA2_WD-WMAYP6969876 -> ../../sdh 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 ata-WDC_WD5003ABYX-01WERA2_WD-WMAYP6969876-part1 -> ../../sdh1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 usb-PepperC_Virtual_Disc_1_0416c9019f482b9c2DFD5493FE193F22-0:0 -> ../../sr0 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 usb-PepperC_Virtual_Disc_2_0416c9019f482b9c2DFD5493FE193F22-0:0 -> ../../sr1 0 lrwxrwxrwx 1 root root 9 Oct 5 11:00 usb-SanDisk_Cruzer_Fit_4C532000060111120183-0:0 -> ../../sdd 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 usb-SanDisk_Cruzer_Fit_4C532000060111120183-0:0-part1 -> ../../sdd1 0 lrwxrwxrwx 1 root root 9 Oct 5 11:38 wwn-0x5000c5005e01e72a -> ../../sdf 0 lrwxrwxrwx 1 root root 10 Oct 5 11:38 wwn-0x5000c5005e01e72a-part1 -> ../../sdf1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 wwn-0x5000c500674c06b4 -> ../../sdb 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 wwn-0x5000c500674c06b4-part1 -> ../../sdb1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 wwn-0x5000c500674e6723 -> ../../sda 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 wwn-0x5000c500674e6723-part1 -> ../../sda1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 wwn-0x5000c5006e3c7497 -> ../../sdc 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 wwn-0x5000c5006e3c7497-part1 -> ../../sdc1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 wwn-0x50014ee059048fea -> ../../sdh 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 wwn-0x50014ee059048fea-part1 -> ../../sdh1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 wwn-0x50014ee0590beb21 -> ../../sdj 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 wwn-0x50014ee0590beb21-part1 -> ../../sdj1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 wwn-0x50014ee206dfc066 -> ../../sdg 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 wwn-0x50014ee206dfc066-part1 -> ../../sdg1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 wwn-0x50014ee2ae7dd4fb -> ../../sdi 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 wwn-0x50014ee2ae7dd4fb-part1 -> ../../sdi1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 wwn-0x50014ee2b1e0cacc -> ../../sdk 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 wwn-0x50014ee2b1e0cacc-part1 -> ../../sdk1 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 wwn-0x50014ee6adde336a -> ../../sde 0 lrwxrwxrwx 1 root root 10 Oct 3 08:48 wwn-0x50014ee6adde336a-part1 -> ../../sde1 Quote Link to comment
theone Posted October 6, 2015 Author Share Posted October 6, 2015 root@unraid-server1:~# ls -las /dev/disk/by-id 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 usb-PepperC_Virtual_Disc_1_0416c9019f482b9c2DFD5493FE193F22-0:0 -> ../../sr0 0 lrwxrwxrwx 1 root root 9 Oct 3 08:48 usb-PepperC_Virtual_Disc_2_0416c9019f482b9c2DFD5493FE193F22-0:0 -> ../../sr1 What are these ? They seem to have the same serial number Quote Link to comment
bondoo0 Posted October 6, 2015 Share Posted October 6, 2015 Not sure. I believe some sort of virtual drive on the system. It's one of the TAMS servers with a super micro h8dme-2 motherboard if that helps. When I did a quick search it looks like it might be something used during boot on the server, and I did see a reference to it showing up as a usb floppy or cd drive, which might be causing the problem. I'm not aware of a way to disable them, or if that would cause other issues. I did find this so it coud be related to kvm on the ipmi card. After receiving your IP KVM information from Dacentec and mounting your ISO as virtual media, you are clear to modify the boot order in your BIOS. If you have a Latronix Spider KVM, the virtual media may be recognized as a USB CD-ROM device called "PepperC Virtual Disk #". Quote Link to comment
theone Posted October 6, 2015 Author Share Posted October 6, 2015 Can you post the output of " smartctl --all /dev/sr0"? Quote Link to comment
bondoo0 Posted October 6, 2015 Share Posted October 6, 2015 FYI, I did some additional research, and the 2 virtual drives are indeed a floppy and CD virtual drive through Super Micro's IPMI. Right now they aren't pointing to anything (which I think is why there is a no medium present message). I don't see a way to disable them in the IPMI tool. Here is the output of the command: root@unraid-server1:~# smartctl --all /dev/sr0 smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.7-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: PepperC Product: Virtual Disc 1 Revision: 0.01 Serial number: 0 Device type: CD/DVD Local Time is: Tue Oct 6 09:04:49 2015 MDT NO MEDIUM present on device A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. Quote Link to comment
papnikol Posted December 2, 2015 Share Posted December 2, 2015 Hi, I am tryin to install the plugin through the unRAID Plugin Manager I get the following: plugin: installing: https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz plugin: downloading https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz plugin: downloading: https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz ... done Warning: simplexml_load_file(): /tmp/plugins/serverlayout-package-2015.09.25.tar.gz:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ??V in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 plugin: xml parse error Can someone help? Quote Link to comment
Squid Posted December 2, 2015 Share Posted December 2, 2015 Hi, I am tryin to install the plugin through the unRAID Plugin Manager I get the following: plugin: installing: https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz plugin: downloading https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz plugin: downloading: https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz ... done Warning: simplexml_load_file(): /tmp/plugins/serverlayout-package-2015.09.25.tar.gz:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ??V in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 plugin: xml parse error Can someone help? In network settings, try setting a static DNS addresses of 8.8.8.8 and 8.8.4.4 and try again Quote Link to comment
papnikol Posted December 2, 2015 Share Posted December 2, 2015 Hi, I am tryin to install the plugin through the unRAID Plugin Manager I get the following: plugin: installing: https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz plugin: downloading https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz plugin: downloading: https://raw.githubusercontent.com/theone11/serverlayout_plugin/master/serverlayout-package-2015.09.25.tar.gz ... done Warning: simplexml_load_file(): /tmp/plugins/serverlayout-package-2015.09.25.tar.gz:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ??V in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 plugin: xml parse error Can someone help? In network settings, try setting a static DNS addresses of 8.8.8.8 and 8.8.4.4 and try again thanks, that solved the problem, although I do not understand why Google's DNS is helping Quote Link to comment
NateCCIE Posted December 7, 2015 Share Posted December 7, 2015 Sorry if this has already been asked, but is there a reason the server layout plugin spins up all un-assigned drives. It does not seep to spin up array drives. Thanks, -Nate Quote Link to comment
opentoe Posted January 9, 2016 Share Posted January 9, 2016 Couple of questions. Anyone else submit a drive to smartmontools.org? I've submitted a few times for a drive that is not in the database and it never gets added. I've given them all the proper information they have asked for. I've seen many drives being added since I'm on the email distro but just not the drive I've asked to add. You'll see below the "manufacture" is missing. You'd think most Western Digital drives would be in there already. Also, another questions. What does the PATH mean? What's the difference between FIRST install and RECENT install? Thanks. [WD-WCC130966733] => Array ( [TRAY_NUM] => 10 [TYPE] => SATA [DEVICE] => sdd [PATH] => 0:0:2:0 [uNRAID] => disk9 [MANUFACTURER] => [MODEL] => WDC WD4003FZEX-00Z4SA0 [sN] => WD-WCC130966733 [FW] => 01.01A01 [CAPACITY] => 4.00 TB [POWER_ON_HOURS] => 17391 [LOAD_CYCLE_COUNT] => 33 [FIRST_INSTALL_DATE] => 2015/09/18 [RECENT_INSTALL_DATE] => 2015/09/18 [LAST_SEEN_DATE] => 2016/01/09 [PURCHASE_DATE] => [NOTES] => [sTATUS] => INSTALLED [FOUND] => YES => green-on Quote Link to comment
theone Posted January 10, 2016 Author Share Posted January 10, 2016 FIRST_INSTALL_DATE is the 1st time the drive was seen in the array. RECENT_INSTALL_DATE is the last (most recent) time the drive was added to the array after it was not seen. For example, you add a drive then after some time yo remove it for some reason then decide to return it again - that will be the RECENT_INSTALL_DATE. If you install a drive but never take it out then these 2 dates will be the same. Quote Link to comment
opentoe Posted January 10, 2016 Share Posted January 10, 2016 Thanks for the explanation. I finally got my lazy ass to map where are the drives are in the bays. Since one of my Western Digital drives is not in the smartdatabase, is there a way I can add it manually to the code/file where the info is saved on the USB stick? It is just missing the manufacture. I have submitted it several times but I guess they don't want to add it. Quote Link to comment
itimpi Posted January 16, 2016 Share Posted January 16, 2016 I was wondering whether there was any way to get this plugin to automatically show the ataX type numbers associated with a drive as many kernel error messages refer to a drive in this way? If not then I guess I can go through adding the information manually, but I thought that it would be better if the plugin derived it automatically so that it followed any drive being physically moved in the machine. It could then be displayed as part of the device information.e.g. Device: sdX (ataY). The ata type information is useful as it relates directly to the physical port that a drive is plugged into and is invariant across boots (unlike the sdX information that can change). Quote Link to comment
RobJ Posted January 16, 2016 Share Posted January 16, 2016 I was wondering whether there was any way to get this plugin to automatically show the ataX type numbers associated with a drive as many kernel error messages refer to a drive in this way? If not then I guess I can go through adding the information manually, but I thought that it would be better if the plugin derived it automatically so that it followed any drive being physically moved in the machine. It could then be displayed as part of the device information.e.g. Device: sdX (ataY). The ata type information is useful as it relates directly to the physical port that a drive is plugged into and is invariant across boots (unlike the sdX information that can change). I've previously requested ata info here. Unfortunately, it's not invariant, it can change as much as the sdX assignments. However, in a small system with few controllers it can be consistent enough to appear invariant. The more controllers you have, the more the order of loading them can be different. Quote Link to comment
itimpi Posted January 16, 2016 Share Posted January 16, 2016 I was wondering whether there was any way to get this plugin to automatically show the ataX type numbers associated with a drive as many kernel error messages refer to a drive in this way? If not then I guess I can go through adding the information manually, but I thought that it would be better if the plugin derived it automatically so that it followed any drive being physically moved in the machine. It could then be displayed as part of the device information.e.g. Device: sdX (ataY). The ata type information is useful as it relates directly to the physical port that a drive is plugged into and is invariant across boots (unlike the sdX information that can change). I've previously requested ata info here. Unfortunately, it's not invariant, it can change as much as the sdX assignments. However, in a small system with few controllers it can be consistent enough to appear invariant. The more controllers you have, the more the order of loading them can be different. I had always thought the ata values were invariant, bit if they are not then I would have thought there was even more reason for the plugin to display them automatically. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.