Squid

Community Developer
  • Content count

    9255
  • Joined

  • Last visited

  • Days Won

    18

Squid last won the day on April 17

Squid had the most liked content!

Community Reputation

161 Very Good

5 Followers

About Squid

Converted

  • Gender
    Male
  • Personal Text
    Don Juan Prawn

Recent Profile Visitors

927 profile views
  1. Download http://www.hdsentinel.com/hdslin/hdsentinel-016-x64.tar.gz, and extract the file and store it on your flash drive. Then from the command prompt, /boot/HDSentinel to run and analyze. BUT, if you ask me, the program is a POS, and smartctl (which unRaid's UI leverages and notifies you about problems with the drives is better.) Consider this drive. Output from smartctl: root@Server_A:/tmp/GitHub# smartctl -A /dev/sdm smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.19-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 099 099 006 Pre-fail Always - 2553328 3 Spin_Up_Time 0x0003 094 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 091 091 020 Old_age Always - 10097 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 053 048 030 Pre-fail Always - 953529061048 9 Power_On_Hours 0x0032 068 068 000 Old_age Always - 28724 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 295 183 Runtime_Bad_Block 0x0032 092 092 000 Old_age Always - 8 184 End-to-End_Error 0x0032 088 088 099 Old_age Always FAILING_NOW 12 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 077 063 045 Old_age Always - 23 (Min/Max 17/30) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 87 193 Load_Cycle_Count 0x0032 043 043 000 Old_age Always - 115443 194 Temperature_Celsius 0x0022 023 040 000 Old_age Always - 23 (0 16 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 198 000 Old_age Always - 51 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 4161h+19m+20.345s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 45739743333 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 765808399191 And the output from HDSentinel HDSentinel makes a big argument on their website about how the manufacturers set the thresholds such that they cannot be hit, and how their method of analysis is far better, and yet according to smartctl which is reading the threshholds set by Seagate, and reporting the values, and the drive itself says that it is in a failing state, and yet HDSentinel states Yeah, there's no problem, don't worry about it.... By the way, the end to end error that HDSentinel is saying "12 errors occured during transfer" is one way of putting it, albeit the wrong way. The proper way of putting it is that there was a communication error between the drive head and the sata interface on the drive (ie: an actual physical failure), which is why Seagate sets a single failure as "FAILING NOW"... Outside of this rather large error on their analysis, it is interesting in that it attempts to put into english what is shown on the drive's SMART reports. BTW, you can RMA a drive before any attribute is in failing status.
  2. I think this one is ok to ignore. I believe its informative more than anything else, as it looks like a request to eth1 timed out Apr 23 10:33:46 JARVIS kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:316 dev_watchdog+0x181/0x1dc Apr 23 10:33:46 JARVIS kernel: NETDEV WATCHDOG: eth1 (e1000e): transmit queue 0 timed out Apr 23 10:33:46 JARVIS kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod e1000e ptp pps_core fbcon bitblit fbcon_rotate ast fbcon_ccw fbcon_ud fbcon_cw softcursor ttm font i2c_algo_bit drm_kms_helper x86_pkg_temp_thermal cfbfillrect cfbimgblt cfbcopyarea coretemp drm kvm_intel agpgart syscopyarea sysfillrect sysimgblt ahci i2c_i801 fb_sys_fops fb i2c_smbus kvm i2c_core fbdev libahci wmi ipmi_si [last unloaded: pps_core] Apr 23 10:33:46 JARVIS kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.19-unRAID #1 Apr 23 10:33:46 JARVIS kernel: Hardware name: ASUSTeK COMPUTER INC. Z9PA-D8 Series/Z9PA-D8 Series, BIOS 5602 06/11/2015 Apr 23 10:33:46 JARVIS kernel: ffff88046fa03db0 ffffffff813a3bf2 ffff88046fa03e00 ffffffff819a9d54 Apr 23 10:33:46 JARVIS kernel: ffff88046fa03df0 ffffffff8104d04c 0000013c6fa03e68 ffff88046c578000 Apr 23 10:33:46 JARVIS kernel: ffff88045ec8e400 ffff88046c5783a0 0000000000000000 0000000000000001 Apr 23 10:33:46 JARVIS kernel: Call Trace: Apr 23 10:33:46 JARVIS kernel: <IRQ>
  3. Far from a network guy, but is the static IP you're attempting to use already in use?
  4. Docker compose support would be a huge bonus for unRaid. But, there are some workarounds... One would be the docker autostart manager which will start / restart the containers in the order which you specify, and optionally either wait a set delay before starting the next one, or wait for a local or remote port to be available prior to continuing)
  5. My 2 cents on this... Depending upon what's going on with the server and the downloads / VMs / etc, it is possible for me to actually fill the cache drive (rare, but it has happened to me). For this reason, I prefer to use /mnt/user/.... for my downloads and appdata, and have the share settings to be prefer. That way if it does fill up, excess files will get written to the array until I free up space, at which point the mover script will put everything back on the cache drive where it belongs. /mnt/cache/appdata vs /mnt/user/appdata: The primary reason to use /mnt/cache/... instead of /mnt/user/... is to outright force the system to put the items onto the cache drive regardless of the share's settings. But, with a setting of prefer or only, then its effectively the same thing. That being said, a small minority of users have issues with certain apps' appdata being referenced by /mnt/user/appdata/..., and switching it to /mnt/cache/appdata/... fixes the problems for them....(and I am not one of those users, and have thus far been unable to replicate any of their supposed issues) Net result is that if you have a large enough cache drive that you don't need to worry about it ever possibly filling up, for the most trouble free experience, reference your appdata (and download) shares by /mnt/cache/appdata/.... If you think space might be at a premium for whatever reason on your cache drive, then reference the appdata paths (and download paths) as /mnt/user/appdata with a setting of prefer...
  6. Apr 24 04:51:03 Tower kernel: FAT-fs (sda1): Directory bread(block 32774) failed Apr 24 04:51:03 Tower kernel: FAT-fs (sda1): Directory bread(block 32775) failed Apr 24 04:51:03 Tower kernel: FAT-fs (sda1): Directory bread(block 32776) failed Your flash drive dropped off line... Could be either a flash problem or controller (if in USB3, try it in USB2 and vice versa), or you pulled the stick. You will have to reboot, and the system will want to do a parity check...
  7. Is this expander compatible with marvel based controllers. AOC-SAS2LP?
  8. Did you download the virtio drivers on the VM settings page. And did you enter in that information when you created the VM?
  9. Yeah, you're good on that one...
  10. XFS is the default file system for 6.x+ ReiserFS is slowly being deprecated, as its no longer being maintained and the odd issue with it surfaces for some users. Under ideal circumstances, it is recommended to redo all your drives as XFS (which means copying from the reiser disks to the xfs disk, reformatting the now empty reiser disk as xfs, and continuing. There a whole sticky for converting to xfs
  11. That is if you were trying to recover a disk. In your case, the disk was indeed unmountable because it had no filesystem, and needed to be formatted... So long as the only disk the unRaid notified you it was going to be formatted was indeed the new disk, then all is good
  12. As have I (actually 2 weeks) as you can tell from this quick snap of my workspace: - Removed the legacy UI. Now instead of it looking like it was from the 80's, we're up to it looking like its from the 90's - New UI will now work on pre 6.3.3. Introduced my very first dependency for pre-6.3.3 - Lost track of the minor little changes/fixes, so I'm unable to iterate them here. (or in CA's changelog itself) UI Changes: Sections Navigate the sections via hovering over or clicking on the "briefcase" icon (ie: Available apps, Installed Apps, Previously Installed, Pinned, CA Modules) Views Change the view modes available by hovering over or clicking on the "binoculars" icon. Categories Change the category displayed by hovering over or clicking on the "Folder" icon SubCategories Change the subcategory displayed by hovering over or clicking on the "Sub Folders" icon Installing / Editing / Settings / etc Table mode is largely unaffected, and still has the separate buttons for Add / Install / Edit (don't want to annoy @sparklyballs too much ) Icon / Icon Details (default) mode, the Add / Install / Edit / Settings / Changelog Icons are now completely removed. To install / edit / go to the plugin settings (or newly added, go to a docker app's webUI), simply hover over the app's icon (or click on it if you're on a mobile device) and icons will appear within the popup that will allow you to do everything you want to do. All Icons everywhere are dynamic, and will either be disabled (grey background) or not appear depending upon what section you are in. Change logs are now incorporated automatically when displaying the full details (ie: hovering or clicking on the app's icon) I'll get around to updating the help file / manual / OP for CA later today / tomorrow for these changes (no update to CA required for this) Thanks go out to @gfjardim for spearheading getting tooltipster included in unRaid 6.3.3+ (which is my dependency on pre 6.3.3) which makes all of the UI changes possible, and @bonienl for creating the CSS for it.... Personally, I think the new UI is more intuitive, and is largely language agnostic, but since it is a departure from what you're used to, it may take some getting used to.
  13. Best guess is this: Apr 24 22:18:51 Tower emhttp: err: get_limetech_time: -2 (7) 0 Followed by Apr 24 22:18:51 Tower kernel: mdcmd (28): import 27 Apr 24 22:18:51 Tower kernel: mdcmd (29): import 28 Apr 24 22:18:51 Tower kernel: mdcmd (30): import 29 Apr 24 22:18:51 Tower kernel: md: import_slot: 29 empty Apr 24 22:18:51 Tower emhttp: import flash device: sda Apr 24 22:18:51 Tower emhttp: shcmd (13): /etc/rc.d/rc.nfsd start |& logger Apr 24 22:18:51 Tower root: Starting NFS server daemons: Apr 24 22:18:51 Tower root: /usr/sbin/exportfs -r Apr 24 22:18:51 Tower root: /usr/sbin/rpc.nfsd 8 Apr 24 22:18:51 Tower dhcpcd[1669]: br0: offered 192.168.1.100 from 192.168.1.1 your server didn't get a valid IP until after emhttp started...., and internet access is required for Trial. Since it didn't have it when emhttp loaded, emhttp wouldn't autostart the array. Won't be an issue if/when you purchase. (But, setting a static IP either in unRaid or in your router would probably fix that) No real good answer as to the continual usb hubs being found. A work around would be to disable one at a time the ports in your bios until your find the offending controller and then disable it. As an aside, I had a KVM that also did the exact same thing... While by itself the continual disconnects / reconnects won't cause any issue, the logging spam will...
  14. Try escaping the spaces. Use Folder\ 1 instead of "Folder 1"
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.