Jump to content
theone

Server Layout Plugin for unRAID v6

292 posts in this topic Last Reply

Recommended Posts

Yep, it was read only, got a pushbullet alert stating just that, but this has happened twice on different USB devices whilst using this plugin, back up and running now (Have a backup USB Key)

 

Any ideas why it happens though?

Doesn't happen to me with this plugin.

Share this post


Link to post

Yep, it was read only, got a pushbullet alert stating just that, but this has happened twice on different USB devices whilst using this plugin, back up and running now (Have a backup USB Key)

 

Any ideas why it happens though?

Doesn't happen to me with this plugin.

 

All I do is read and write to the configurration file /boot/config/plugins/serverlayout and run shell information commands.

I don't see how it can effect the write protection of the flash drive.

 

Share this post


Link to post

Yep, it was read only, got a pushbullet alert stating just that, but this has happened twice on different USB devices whilst using this plugin, back up and running now (Have a backup USB Key)

 

Any ideas why it happens though?

Doesn't happen to me with this plugin.

 

All I do is read and write to the configurration file /boot/config/plugins/serverlayout and run shell information commands.

I don't see how it can effect the write protection of the flash drive.

There isn't any write protection involved. It is file system corruption which causes unRAID to set the device to read-only. No clear evidence this plugin is involved though.

Share this post


Link to post

I'm not saying the plugin is responsible, my hypothesis was that I was initiating a powerdown -r when the smartmon update was occurring and I did wonder whether that was the cause as that is the exact thing I did both times.

 

I understand that would qualify as user error and accept full responsibility for the consequences, my question is, could this be a recognised complication of this kind of user error, and, if so, would it be prudent to warn others not to do the same thing I did?

Share this post


Link to post

I'm not saying the plugin is responsible, my hypothesis was that I was initiating a powerdown -r when the smartmon update was occurring and I did wonder whether that was the cause as that is the exact thing I did both times.

 

I understand that would qualify as user error and accept full responsibility for the consequences, my question is, could this be a recognised complication of this kind of user error, and, if so, would it be prudent to warn others not to do the same thing I did?

Trying to think with you...

 

The smartmontools update, as far as I kow, changes a database file (sungle file) in the system files located in RAM and does not touch the USB or any other device for that matter.

I don't know how it could have caused a corruption or hold up the devices for a clean powerdown.

 

Share this post


Link to post

I'm up for trying to reproduce it if you think it would help. 

 

I'll remove all my other plugins and stop the docker and VM services first.

 

I guess it could be any of the above or a cocktail of factors or even a hardware problem but I'm up for it.

 

How long does a smartmontools update take? Both times I have thought it has made the webui hang, but it may be my impatience.

 

See, got me admitting to all my faults now lol!

Share this post


Link to post

New Release:

 

2015.06.01

- Added transform (rotation and translate) support for other browsers (-webkit, -ms)

- Added Tooltip Disk information for each tray on "Layout" tab and settings for each field in "Settings" tab

- Compacted data and settings tables rows

- Added "User Utilities" icon

 

In the next version (rc4) "User Utilities" will be built-in, and developpers don't need to include it in their plugins anymore.

 

Share this post


Link to post

This is great. Got it up and running with no issues. will make life a ton easier in the future when I need to replace a drive. Easier since I am literately building the box now. Will take some time to setup on my rig at home as I don't know the location of any of the drives. I sued the notes section to type in what sata port on the mobo or raid card each drive is plugged into. Thank you a ton!

Share this post


Link to post

Now got it all set up and working beautifully, I love it, easy record of where I bought the disk, when  I bought the disk and where it is on my server.

 

Worked out what was going wrong, it was my USB disk - both of them!  Unlucky I guess but both my usual Sandisk UnRAID and my back Sandisk UnRAID gave errors when trying to use.  Migrated to new USB keys and errors gone.

 

For the record I had formatted both the failed USB keys and set them up from scratch and hadn't had any problems in the syslog or with any other plugins at all. 

 

Here's my syslog showing what was going on.

 

In my syslog

Jun  3 18:20:52 Server kernel: usb 4-1.5: reset high-speed USB device number 3 using ehci-pci
Jun  3 18:20:56 Server emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1
Jun  3 18:21:07 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:21:22 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:21:22 Server kernel: usb 4-1.5: reset high-speed USB device number 3 using ehci-pci
Jun  3 18:21:37 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:21:52 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:21:53 Server kernel: usb 4-1.5: reset high-speed USB device number 3 using ehci-pci
Jun  3 18:21:58 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:22:03 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:22:03 Server kernel: usb 4-1.5: reset high-speed USB device number 3 using ehci-pci
Jun  3 18:22:08 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:22:13 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:22:13 Server kernel: usb 4-1.5: USB disconnect, device number 3
Jun  3 18:22:13 Server kernel: sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
Jun  3 18:22:13 Server kernel: sd 0:0:0:0: [sda] CDB: opcode=0x2a 2a 00 00 13 c4 a7 00 00 14 00
Jun  3 18:22:13 Server kernel: blk_update_request: I/O error, dev sda, sector 1295527
Jun  3 18:22:13 Server kernel: sd 0:0:0:0: [sda] UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
Jun  3 18:22:13 Server kernel: sd 0:0:0:0: [sda] CDB: opcode=0x2a 2a 00 00 00 09 74 00 00 01 00
Jun  3 18:22:13 Server kernel: blk_update_request: I/O error, dev sda, sector 2420
Jun  3 18:22:13 Server kernel: Buffer I/O error on dev sda1, logical block 2357, lost async page write
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): FAT read failed (blocknr 2357)
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): FAT read failed (blocknr 2357)
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): Directory bread(block 41968) failed
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): Directory bread(block 41969) failed
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): Directory bread(block 41970) failed
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): Directory bread(block 41971) failed
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): Directory bread(block 41972) failed
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): Directory bread(block 41973) failed
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): Directory bread(block 41974) failed
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): Directory bread(block 41975) failed
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): Directory bread(block 41968) failed
Jun  3 18:22:13 Server kernel: FAT-fs (sda1): Directory bread(block 41969) failed
Jun  3 18:22:13 Server kernel: usb 4-1.5: new high-speed USB device number 4 using ehci-pci
Jun  3 18:22:28 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:22:43 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:22:44 Server kernel: usb 4-1.5: new high-speed USB device number 5 using ehci-pci
Jun  3 18:22:59 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:23:14 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:23:14 Server kernel: usb 4-1.5: new high-speed USB device number 6 using ehci-pci
Jun  3 18:23:19 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:23:24 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:23:24 Server kernel: usb 4-1.5: new high-speed USB device number 7 using ehci-pci
Jun  3 18:23:29 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:23:34 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:23:35 Server kernel: usb 4-1-port5: unable to enumerate USB device
Jun  3 18:23:35 Server kernel: usb 4-1.5: new high-speed USB device number 8 using ehci-pci
Jun  3 18:23:50 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:24:05 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:24:05 Server kernel: usb 4-1.5: new high-speed USB device number 9 using ehci-pci
Jun  3 18:24:20 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:24:31 Server kernel: fat__get_entry: 46 callbacks suppressed
Jun  3 18:24:31 Server kernel: FAT-fs (sda1): Directory bread(block 41968) failed
Jun  3 18:24:31 Server kernel: FAT-fs (sda1): Directory bread(block 41969) failed
Jun  3 18:24:31 Server kernel: FAT-fs (sda1): Directory bread(block 41970) failed
Jun  3 18:24:31 Server kernel: FAT-fs (sda1): Directory bread(block 41971) failed
Jun  3 18:24:31 Server kernel: FAT-fs (sda1): Directory bread(block 41972) failed
Jun  3 18:24:31 Server kernel: FAT-fs (sda1): Directory bread(block 41973) failed
Jun  3 18:24:31 Server kernel: FAT-fs (sda1): Directory bread(block 41974) failed
Jun  3 18:24:31 Server kernel: FAT-fs (sda1): Directory bread(block 41975) failed
Jun  3 18:24:35 Server kernel: usb 4-1.5: device descriptor read/64, error -110
Jun  3 18:24:36 Server kernel: usb 4-1.5: new high-speed USB device number 10 using ehci-pci
Jun  3 18:24:41 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:24:46 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:24:46 Server kernel: usb 4-1.5: new high-speed USB device number 11 using ehci-pci
Jun  3 18:24:51 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:24:56 Server kernel: usb 4-1.5: device descriptor read/8, error -110
Jun  3 18:24:56 Server kernel: usb 4-1-port5: unable to enumerate USB device
Jun  3 18:24:57 Server kernel: FAT-fs (sda1): Directory bread(block 42976) failed
Jun  3 18:24:57 Server kernel: FAT-fs (sda1): Directory bread(block 42977) failed
Jun  3 18:24:57 Server kernel: FAT-fs (sda1): Directory bread(block 42978) failed
Jun  3 18:24:57 Server kernel: FAT-fs (sda1): Directory bread(block 42979) failed
Jun  3 18:24:57 Server kernel: FAT-fs (sda1): Directory bread(block 42980) failed
Jun  3 18:24:57 Server kernel: FAT-fs (sda1): Directory bread(block 42981) failed
Jun  3 18:24:57 Server kernel: FAT-fs (sda1): Directory bread(block 42982) failed
Jun  3 18:24:57 Server kernel: FAT-fs (sda1): Directory bread(block 42983) failed
Jun  3 18:24:57 Server emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1
Jun  3 18:24:57 Server kernel: FAT-fs (sda1): Directory bread(block 42976) failed
Jun  3 18:24:57 Server kernel: FAT-fs (sda1): Directory bread(block 42977) failed
Jun  3 18:24:57 Server emhttp: sendOutput: write
Jun  3 18:25:18 Server emhttp: sendOutput: write
Jun  3 18:25:19 Server kernel: fat__get_entry: 142 callbacks suppressed
Jun  3 18:25:19 Server kernel: FAT-fs (sda1): Directory bread(block 16384) failed
Jun  3 18:25:19 Server kernel: FAT-fs (sda1): Directory bread(block 16385) failed
Jun  3 18:25:19 Server kernel: FAT-fs (sda1): Directory bread(block 16386) failed
Jun  3 18:25:19 Server kernel: FAT-fs (sda1): Directory bread(block 16387) failed
Jun  3 18:25:19 Server kernel: FAT-fs (sda1): Directory bread(block 16388) failed
Jun  3 18:25:19 Server kernel: FAT-fs (sda1): Directory bread(block 16389) failed
Jun  3 18:25:19 Server kernel: FAT-fs (sda1): Directory bread(block 16390) failed
Jun  3 18:25:19 Server kernel: FAT-fs (sda1): Directory bread(block 16391) failed
Jun  3 18:25:24 Server emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1

Share this post


Link to post

Now got it all set up and working beautifully, I love it, easy record of where I bought the disk, when  I bought the disk and where it is on my server.

Good to see you got it going OK.

 

Do you think I should add more columns or are you using the NOTES as for everything else?

 

Share this post


Link to post

Now got it all set up and working beautifully, I love it, easy record of where I bought the disk, when  I bought the disk and where it is on my server.

Good to see you got it going OK.

 

Do you think I should add more columns or are you using the NOTES as for everything else?

 

I use the notes column for my purchase place, I haven't thought of any other info I really need at the moment.  The only other thing I did think of was a interface tab, so I can put in which driver controller the drive is connected to.  May really help troubleshooting if problems arise.

 

A massive innovation would be the ability to customise the server layout more with some sort of block based building.  I have sixteen drive bays in my system

 

At the top a horizontal 5.25" Drive bay to 3.5" hot swappable bay

Then all my other drives are vertical with three, 5 in 3 hot swappable bays.  The ability to define that would be epic but I can see how that would be tricky.

 

Maybe a USB port section so you can allocate which USB drive is plugged in where.

 

But these are all just ideas....

Share this post


Link to post

New Release:

 

2015.06.08

- Added support for HIDDEN TRAYS - click on preview tray to show/hide it - don't forget to save settings

- Increased number of maximum trays to 99 (from 26) - Supports better usage of HIDDEN TRAYS

- Removed "User Utilities" icon - part of unRAID v6 RC4

- Add Enable/Disable for Tooltips

- Fixed "UNRAID" functionality recognition for USB devices

 

2015.06.08-2

- Fixed bug - introduced by new parameter array "TRAY_SHOW"

- Fixed bug - introduced by new parameter array "GENERAL"

 

Main change/addition - Hidden Trays - as requested by phenomeus: http://lime-technology.com/forum/index.php?topic=40223.msg378962#msg378962

 

Click on the trays in the preview table no the "Data" tab and the tray will become hidden/visible. Save your changes and see it on the "Layout" tab.

If a tray is already assigned to a device and then it is hidden then the device that was assigned to it will become unassigned.

 

See attached screenshots

Hidden_Trays_-_Layout_tab.gif.a13040f1f7de014bdc092a0d83d4f555.gif

Hidden_Trays_-_Data_tab.gif.6644bc8740d45de45bbcae435a85c6d0.gif

Share this post


Link to post

New Release:

 

2015.06.08

- Added support for HIDDEN TRAYS - click on preview tray to show/hide it - don't forget to save settings

- Increased number of maximum trays to 99 (from 26) - Supports better usage of HIDDEN TRAYS

- Removed "User Utilities" icon - part of unRAID v6 RC4

- Add Enable/Disable for Tooltips

- Fixed "UNRAID" functionality recognition for USB devices

 

2015.06.08-2

- Fixed bug - introduced by new parameter array "TRAY_SHOW"

- Fixed bug - introduced by new parameter array "GENERAL"

 

Main change/addition - Hidden Trays - as requested by phenomeus: http://lime-technology.com/forum/index.php?topic=40223.msg378962#msg378962

 

Click on the trays in the preview table no the "Data" tab and the tray will become hidden/visible. Save your changes and see it on the "Layout" tab.

If a tray is already assigned to a device and then it is hidden then the device that was assigned to it will become unassigned.

 

See attached screenshots

 

Hidden trays are great, just added another row to my server config, hid four of them and it's now a pretty good representation of the actual drive arrangements.  Loving it.

Share this post


Link to post

I use lsusb to list all usb devices.

then I do lsusb -D to get each devices information and if it is a mass storage device.

 

This takes most of the time in the webui loading and there are many devices which are not mass storage devices.

 

How can I know in advance which are storage devices and query only these with lsusb -D (I will need to know the bus and device numbers).

 

For starters I will filter out all that have "root hub" in the description, but how do I filter out the rest?

 

How do I get the Device and Bus numbers for using in lsusb -D by knowing the device node (sda,sdb,etc...)?

 

 

Share this post


Link to post

Now got it all set up and working beautifully, I love it, easy record of where I bought the disk, when  I bought the disk and where it is on my server.

Good to see you got it going OK.

 

Do you think I should add more columns or are you using the NOTES as for everything else?

 

I use the notes column for my purchase place, I haven't thought of any other info I really need at the moment.  The only other thing I did think of was a interface tab, so I can put in which driver controller the drive is connected to.  May really help troubleshooting if problems arise.

 

A massive innovation would be the ability to customise the server layout more with some sort of block based building.  I have sixteen drive bays in my system

 

At the top a horizontal 5.25" Drive bay to 3.5" hot swappable bay

Then all my other drives are vertical with three, 5 in 3 hot swappable bays.  The ability to define that would be epic but I can see how that would be tricky.

 

Maybe a USB port section so you can allocate which USB drive is plugged in where.

 

But these are all just ideas....

 

There was a addin for Windows Home Server v1.0 Called WHS Disk Management.  It supported custom case layouts.  Users created wire lists for many different cases.  Using the addon was clunky, but it was a cool concept.

Share this post


Link to post

Wow,mjust found out about this plugin and i love the idea of it! I'm gonna install it as soon as i get home.

 

Btw, just throwing this out there, what about making a mapping for the sata-sas controllers too? It's useful to keep a mapping of the ports/controllers assignment, especially if you use multiple controllers and expanders... In case of troubleshooting and identifying performance bottlenecks.

Share this post


Link to post

Btw, just throwing this out there, what about making a mapping for the sata-sas controllers too? It's useful to keep a mapping of the ports/controllers assignment, especially if you use multiple controllers and expanders... In case of troubleshooting and identifying performance bottlenecks.

 

Please elaborate and give an example if you can.

 

Share this post


Link to post

Just vpn-d home and installed this plugin. Love it!

Will have to wait til I actually get home and check the labels on the server to actually map the drives to the slot location :P

 

Please elaborate and give an example if you can.

 

I'm thinking of additional column in the 'data' table… 'Controller' and 'Port'. I'm not sure if you can derive this from the 'path' field or not?

 

One more question… is 'drive light activity' possible? :D

Share this post


Link to post

I'm thinking of additional column in the 'data' table… 'Controller' and 'Port'. I'm not sure if you can derive this from the 'path' field or not?

 

One more question… is 'drive light activity' possible? :D

 

I will look into these feature requests.

 

Share this post


Link to post

New Release:

 

2015.06.11

- Remove EMPTY row and columns pull-down options in Layout Settings

- HW scan speed optimization - Changed USB path from "lsusb" to "lsscsi -t"

- HW scan speed optimization - Changed USB data gathering from "lsusb -D" to "udevadm" so I can scan only USB storage devices

 

Main change

Reduce plugin load time due to storage device information scanning.

On my server with 8 HDDs and 1 USB storage device (flash) I went from over 10 seconds to under 3 seconds.

 

Share this post


Link to post

New Release:

 

2015.06.12

- Added device status icon (same as unRAID icons) - as requested  :)

- Added option to delete historical devices (per device) from database under "Historical Device" table

 

See attached screenshots

Status_Icons_-_Layout_tab.gif.f61f6c064716fd5f11e37cba43f37798.gif

Delete_Historical_-_Data_tab.gif.74e49302f4b7503d4c960acac9cc5f86.gif

Share this post


Link to post

I experience a problem which I haven't seen reported by anyone else, so I wonder whether I'm the only person affected.

 

On the 'Layout' tab, there's a pop-up (do you call it a tooltip?), which provides detailed info about the drive in the tray over which the mouse pointer is positioned.

 

My problem is that this pop-up is only visible for the right-most trays.  As the mouse pointer moves to the trays further left, the pop-up moves further right - this results in it moving out of the current window and becoming invisible (unless you have a very wide display window/screen).

 

I'm using FF38.0.5 on ArchLinux.  My trays are configured in a 3 row/5 column layout in vertical orientation.

 

As an aside, I do wonder whether this plugin ought to be accessed from the 'Tools' page, rather than the 'Settings' page.

Share this post


Link to post

I experience a problem which I haven't seen reported by anyone else, so I wonder whether I'm the only person affected.

 

On the 'Layout' tab, there's a pop-up (do you call it a tooltip?), which provides detailed info about the drive in the tray over which the mouse pointer is positioned.

 

My problem is that this pop-up is only visible for the right-most trays.  As the mouse pointer moves to the trays further left, the pop-up moves further right - this results in it moving out of the current window and becoming invisible (unless you have a very wide display window/screen).

 

I'm using FF38.0.5 on ArchLinux.  My trays are configured in a 3 row/5 column layout in vertical orientation.

 

I acknowledge this issue (also on MS Internet Explorer) - somehow I missed it - on Chrome it is working flawlessly.

 

On first glance it seems that on FF and MSIE the "hover" is relative to the the whole matrix (right edge of the array) and on Chrome it is relative to each TRAY as it should be.

 

Need to understand why ...  :o:-\  ??? and fix it  :)

Share this post


Link to post

Need to understand why ...  :o:-\  ??? and fix it  :)

 

Okay, thanks!

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now