December 13, 201015 yr I've hit several small issues that are very elementary I'm sure but they are all about things that I'm having trouble finding via forum search. Any input would be greatly appreciated! 1. Why isn't there a v4.6 section of the forums? 2. How can I go about auto-mounting and sharing a formatted single-partition drive that is not within the parity-check array. I set an old 200G drive as the cache drive so that I could format it. I then removed it from the cache drive position and am hoping to use it outside of the array. How can I set the drive to mount and share automatically at startup? I added the mount command that is shown when mounting from the unMenu disk management page to the config/go script but it doesn't seem to work. 3. Subsonic web app customization - I've got subsonic working really well thanks to some very helpful posts on this forum. The problem is that I'm trying to customize some of the html within the subsonic web app and every time I restart, it's getting wiped out. Does anyone know how to persist changes like that? I think a general description of how most applications like subsonic would be deployed at startup and how to alter that process if necessary would go a long way. 4. Transfers disconnecting - I'm having a problem when transferring data to my new server. I've successfully transferred as much as 500G at a time (let it run overnight) without issue. It seems like with a new drive that I recently added to the array is causing transfers to fail after 5 or 10 minutes of transfer. HDParam Info is below - any ideas? HDParm Info for /dev/sdc ST32000542AS_5XW191X2 /dev/sdc: ATA device, with non-removable media Model Number: ST32000542AS Serial Number: 5XW191X2 Firmware Revision: CC34 Transport: Serial Standards: Used: unknown (minor revision code 0x0029) Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 3907029168 device size with M = 1024*1024: 1907729 MBytes device size with M = 1000*1000: 2000398 MBytes (2000 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Advanced power management level: 192 Recommended acoustic management value: 254, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * DOWNLOAD_MICROCODE * Advanced Power Management feature set Power-Up In Standby feature set SET_FEATURES required to spinup after power up SET_MAX security extension * Automatic Acoustic Management feature set * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * WRITE_{DMA|MULTIPLE}_FUA_EXT * 64-bit World wide name Write-Read-Verify feature set * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * SATA-I signaling speed (1.5Gb/s) * SATA-II signaling speed (3.0Gb/s) * Native Command Queueing (NCQ) * Phy event counters Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Long Sector Access (AC1) * SCT LBA Segment Access (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count supported: enhanced erase 372min for SECURITY ERASE UNIT. 372min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 5000c5002a7136aa NAA : 5 IEEE OUI : c50 Unique ID : 02a7136aa Checksum: correct
December 13, 201015 yr I've hit several small issues that are very elementary I'm sure but they are all about things that I'm having trouble finding via forum search. Any input would be greatly appreciated! 2. How can I go about auto-mounting and sharing a formatted single-partition drive that is not within the parity-check array. I set an old 200G drive as the cache drive so that I could format it. I then removed it from the cache drive position and am hoping to use it outside of the array. How can I set the drive to mount and share automatically at startup? I added the mount command that is shown when mounting from the unMenu disk management page to the config/go script but it doesn't seem to work. SNAP.
December 13, 201015 yr Author thankyou! SNAP was something I heard talk of but never connected the dots. Got that set up and sharing great now! Thanks for helping, mbryanr - #2 is solved!
December 13, 201015 yr 1. Why isn't there a v4.6 section of the forums? Good question, but only LimeTech can answer that. Unfortunately, this is pretty normal for these forums. The 4.6 forum will probably go up around the time that 5.0 comes out of beta... 2. How can I go about auto-mounting and sharing a formatted single-partition drive that is not within the parity-check array. I set an old 200G drive as the cache drive so that I could format it. I then removed it from the cache drive position and am hoping to use it outside of the array. How can I set the drive to mount and share automatically at startup? I added the mount command that is shown when mounting from the unMenu disk management page to the config/go script but it doesn't seem to work. SNAP will definitely work, but what you are describing is the normal, default operation of the cache drive. When you start the array, the cache drive will be mounted as it's own share named 'cache'. Any files on that drive will be outside the parity-protected array. If that's all you want to accomplish, you don't need SNAP at all. This is normal unRAID behavior. If you are looking to have a second drive mounted outside the array in addition to a cache drive, then SNAP is the answer. 3. Subsonic web app customization - I've got subsonic working really well thanks to some very helpful posts on this forum. The problem is that I'm trying to customize some of the html within the subsonic web app and every time I restart, it's getting wiped out. Does anyone know how to persist changes like that? I think a general description of how most applications like subsonic would be deployed at startup and how to alter that process if necessary would go a long way. Don't know the answer to this, sorry. 4. Transfers disconnecting - I'm having a problem when transferring data to my new server. I've successfully transferred as much as 500G at a time (let it run overnight) without issue. It seems like with a new drive that I recently added to the array is causing transfers to fail after 5 or 10 minutes of transfer. HDParam Info is below - any ideas? Did you preclear the new drive? If so, did it pass preclear? The only time I've seen behavior like you describe is when I attempted to use a known-dodgy drive. As soon as I removed the bad drive the behavior went back to normal. Another theory is that your PSU isn't powerful enough, so the new drive pushed it over the edge. Normally this would cause the server to restart, though, not just for a transfer to fail.
December 13, 201015 yr 3. Subsonic web app customization - I've got subsonic working really well thanks to some very helpful posts on this forum. The problem is that I'm trying to customize some of the html within the subsonic web app and every time I restart, it's getting wiped out. Does anyone know how to persist changes like that? I think a general description of how most applications like subsonic would be deployed at startup and how to alter that process if necessary would go a long way. Any customizations you make will have to be added to the go script (in the config folder of the flash drive) so that they are redone when the server is booted again.
December 14, 201015 yr Author 4. Transfers disconnecting - I'm having a problem when transferring data to my new server. I've successfully transferred as much as 500G at a time (let it run overnight) without issue. It seems like with a new drive that I recently added to the array is causing transfers to fail after 5 or 10 minutes of transfer. HDParam Info is below - any ideas? Did you preclear the new drive? If so, did it pass preclear? The only time I've seen behavior like you describe is when I attempted to use a known-dodgy drive. As soon as I removed the bad drive the behavior went back to normal. Another theory is that your PSU isn't powerful enough, so the new drive pushed it over the edge. Normally this would cause the server to restart, though, not just for a transfer to fail. OK - just finished 2 cycles of preclear and posted in the results thread - hopefully it's just a bad drive and I can ditch it and move on the the next one. Just a followup - is it fairly safe to say that one cycle should be sufficient to identify problems with a drive and the only benefit to multiple cycles is to burn in the drive?
December 14, 201015 yr is it fairly safe to say that one cycle should be sufficient to identify problems with a drive and the only benefit to multiple cycles is to burn in the drive?True.
December 14, 201015 yr Author 3. Subsonic web app customization - I've got subsonic working really well thanks to some very helpful posts on this forum. The problem is that I'm trying to customize some of the html within the subsonic web app and every time I restart, it's getting wiped out. Does anyone know how to persist changes like that? I think a general description of how most applications like subsonic would be deployed at startup and how to alter that process if necessary would go a long way. Any customizations you make will have to be added to the go script (in the config folder of the flash drive) so that they are redone when the server is booted again. OK - so the best way to do that for subsonic would be to modify the subsonic_start.sh script and copy the edited files into the deployed web app from somewhere on the flash boot device? I was thinking of going down that road, but I wasn't sure if when the subsonic war got deployed at startup and wasn't sure if I could rely on the files always being there under /var/subsonic/data/jetty/####/webapp/. Do I need to worry about that?
December 14, 201015 yr Author is it fairly safe to say that one cycle should be sufficient to identify problems with a drive and the only benefit to multiple cycles is to burn in the drive?True. Thanks Joe -your involvement in these forums is much appreciated - even by us bumbling idiots ;0
Archived
This topic is now archived and is closed to further replies.