Arandomdood
-
Posts
35 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Arandomdood
-
-
Stupid question but where are case icons stored? I used to have one of the generic case icons that I really liked in 6.7.2. I upgraded and boom it's gone. Kinda miss it ow lol. I have the 6.7.2 USB and system backups if needed to dig thru em!
-
[979160.434112] ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen [979160.434116] ata6.00: irq_stat 0x00400041, connection status changed [979160.434119] ata6: SError: { PHYRdyChg 10B8B DevExch } [979160.434123] ata6.00: failed command: WRITE DMA [979160.434131] ata6.00: cmd ca/00:18:40:00:00/00:00:00:00:00/e0 tag 5 dma 12288 out res 50/00:00:57:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) [979160.434133] ata6.00: status: { DRDY } [979160.434141] ata6: hard resetting link [979166.285124] ata6: link is slow to respond, please be patient (ready=0) [979170.444985] ata6: COMRESET failed (errno=-16) [979170.444991] ata6: hard resetting link [979171.216017] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [979171.224074] ata6.00: supports DRM functions and may not be fully accessible [979171.529181] ata6.00: supports DRM functions and may not be fully accessible [979172.321785] ata6.00: configured for UDMA/133 [979172.321806] ata6: EH completeSaw this in dmesg log today, what does this mean?
Board is Supermicro X8SIL-F
________________________________________
EDIT1: Okay so I investigated which device is ata6 and it's my Parity disk. I did notice randomly increasing parity errors for no reason every few checks.
Here's disk SMART data screenshot, seems fine, no?
=== START OF INFORMATION SECTION === Model Family: WDC HGST Ultrastar He10 Device Model: WDC WD80EZAZ-11TDBA0 LU WWN Device Id: 5 000cca 267e5d200 Firmware Version: 83.H0A83 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Jun 1 15:24:58 2023 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Disabled Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 93) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 991) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 100 100 016 - 0 2 Throughput_Performance --S--- 128 128 054 - 116 3 Spin_Up_Time POS--- 215 215 024 - 168 (Average 443) 4 Start_Stop_Count -O--C- 100 100 000 - 57 5 Reallocated_Sector_Ct PO--CK 100 100 005 - 0 7 Seek_Error_Rate -O-R-- 100 100 067 - 0 8 Seek_Time_Performance --S--- 128 128 020 - 18 9 Power_On_Hours -O--C- 096 096 000 - 31245 10 Spin_Retry_Count -O--C- 100 100 060 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 57 22 Helium_Level PO---K 100 100 025 - 100 192 Power-Off_Retract_Count -O--CK 048 048 000 - 62452 193 Load_Cycle_Count -O--C- 048 048 000 - 62452 194 Temperature_Celsius -O---- 166 166 000 - 39 (Min/Max 17/50) 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 197 Current_Pending_Sector -O---K 100 100 000 - 0 198 Offline_Uncorrectable ---R-- 100 100 000 - 0 199 UDMA_CRC_Error_Count -O-R-- 200 200 000 - 0 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning SMART Extended Comprehensive Error Log Version: 1 (1 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 31245 - # 2 Short offline Completed without error 00% 26872 - # 3 Short offline Completed without error 00% 20047 - # 4 Short offline Completed without error 00% 12133 - # 5 Short offline Completed without error 00% 8154 - # 6 Short offline Completed without error 00% 0 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 256 (0x0100) Device State: Active (0) Current Temperature: 39 Celsius Power Cycle Min/Max Temperature: 38/39 Celsius Lifetime Min/Max Temperature: 17/50 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/65 Celsius Min/Max Temperature Limit: -40/70 Celsius Temperature History Size (Index): 128 (90) Index Estimated Time Temperature Celsius 91 2023-06-01 13:17 39 ******************** ... ..( 35 skipped). .. ******************** 127 2023-06-01 13:53 39 ******************** 0 2023-06-01 13:54 38 ******************* ... ..( 12 skipped). .. ******************* 13 2023-06-01 14:07 38 ******************* 14 2023-06-01 14:08 39 ******************** ... ..( 11 skipped). .. ******************** 26 2023-06-01 14:20 39 ******************** 27 2023-06-01 14:21 38 ******************* ... ..( 19 skipped). .. ******************* 47 2023-06-01 14:41 38 ******************* 48 2023-06-01 14:42 39 ******************** ... ..( 7 skipped). .. ******************** 56 2023-06-01 14:50 39 ******************** 57 2023-06-01 14:51 38 ******************* ... ..( 19 skipped). .. ******************* 77 2023-06-01 15:11 38 ******************* 78 2023-06-01 15:12 39 ******************** ... ..( 11 skipped). .. ******************** 90 2023-06-01 15:24 39 ******************** SCT Error Recovery Control: Read: Disabled Write: Disabled Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 57 --- Lifetime Power-On Resets 0x01 0x010 4 31245 --- Power-on Hours 0x01 0x018 6 85746489895 --- Logical Sectors Written 0x01 0x020 6 80012707 --- Number of Write Commands 0x01 0x028 6 415639400659 --- Logical Sectors Read 0x01 0x030 6 412639083 --- Number of Read Commands 0x01 0x038 6 112484917450 --- Date and Time TimeStamp 0x03 ===== = = === == Rotating Media Statistics (rev 1) == 0x03 0x008 4 21134 --- Spindle Motor Power-on Hours 0x03 0x010 4 21134 --- Head Flying Hours 0x03 0x018 4 62452 --- Head Load Events 0x03 0x020 4 0 --- Number of Reallocated Logical Sectors 0x03 0x028 4 1272 --- Read Recovery Attempts 0x03 0x030 4 0 --- Number of Mechanical Start Failures 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 39 --- Current Temperature 0x05 0x010 1 37 N-- Average Short Term Temperature 0x05 0x018 1 35 N-- Average Long Term Temperature 0x05 0x020 1 50 --- Highest Temperature 0x05 0x028 1 17 --- Lowest Temperature 0x05 0x030 1 46 N-- Highest Average Short Term Temperature 0x05 0x038 1 20 N-- Lowest Average Short Term Temperature 0x05 0x040 1 43 N-- Highest Average Long Term Temperature 0x05 0x048 1 25 N-- Lowest Average Long Term Temperature 0x05 0x050 4 0 --- Time in Over-Temperature 0x05 0x058 1 65 --- Specified Maximum Operating Temperature 0x05 0x060 4 0 --- Time in Under-Temperature 0x05 0x068 1 0 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 1 --- Number of Hardware Resets 0x06 0x010 4 58 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors 0xff ===== = = === == Vendor Specific Statistics (rev 1) == |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) No Defects Logged SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 1 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 1 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FISAlso ran a SMART short-self test, it passed without error.
-
Update & Solution; after trying many things, reading up on udev and drivers I found the answer:
I created an udev rule with:
nano /etc/udev/rules.d/99-usb-printer.rules
In the file is written:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="1d17", ATTR{serial}=="yourSerialNumb", SYMLINK+="hpusbprinter"(yourSerialNumb,idVendor and idProduct can be found in lsusb and then lsusb -d device_vendor:device_productID (you'll see what I mean as soon as you run lsmod alone)
Then I reloaded and triggered:
udevadm control --reload-rules udevadm trigger
And voila! It was working.
You can also use the followingg command to aid you with debugging:
udevadm info -q path -n /dev/bus/XXX/XXX/XXX #This is to find the device udevadm monitor --property #This is to observe adds, removes, changes, binds and unbinds udevadm test /devices/XXXXXX/XXXX/XXXXX/XXXX (this refers to the 1st command above in this code that finds the device via info -q path, it will basically look for an udev rule that applies to this device and trigger it alone so you can observe "log" what happens.
My last todo and I will edit later with solution is how to make this device get automatically written & added upon system boot since Unraid boots from USB. If we had a persistent OS you wouldn't need to do this (if you're on Debian or whatever), but since we run live from ram that's not the case.
Then since this is all for a CUPS container in my case, I added the ydkn/cups from @José Coelho - maintained here
and I removed the Printer argument, and added an extra argument via advanced options within docker in unraid the following argument:
--device=$(readlink -f /dev/hpusbprinter)
This was needed because you need an absolute path and udev only creates relative ones.
------------------
WHY DO THIS? WHAT'S MY REASON?
My printer has some flaw that it reconnects usb every 30 mintues, so this way I am keeping it symlinked to a specific /dev/ non stop so that I don't have to reset my container. So far it seems to work. Hopefully the rising bus number won't pose to be a problem someday.
EDIT2: Yeah.. this wasn't worth doing. Udev rule worked but it this only works for devices that read directly from /dev/. CUPS container that I was using requires actual device to initialize within the container so yeah..
-
Why does this work with /dev/bus/usb/001/005 (where my printer resides) but not with /dev/usb/lp0?
Edit: Oh okay I figured it out, since the contaienr itself creates a lp0 internally, it needs raw device. Got it
-
Hiya. Long story short my printer seems to have some fault and it randomly reconnects (disconnects and connects again) every 30 minutes.
Bus 001 Device 005: ID 03f0:1d17 Hewlett-Packard LaserJet 1320
So I made this udev rule
SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="1d17", SYMLINK+="hpusbprinter"However it doesn't seem to work. I also tried adding the group "lp", but that was to no avail either.
Problem is every time it reconnects my device number goes up, so after 3 days I'd have like device number 87, and also I'm passing the /dev/bus/usb/XXX/XXX to my CUPS docker container, which stops working as soon as the bus device changes.
Do you people have any ideas how to get this going?
-
This is really interesting
Quotebattery.charge: 96
battery.charge.low: 20
battery.charge.warning: 20
battery.runtime: 2334
battery.temperature: 42.9
battery.type: PbAc
battery.voltage: 26.4
battery.voltage.nominal: 27.0
device.mfr: Hewlett-Packard
device.model: HP T1000 G3 UPS
device.part: 502535-001
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4.1
driver.version.data: TrippLite HID 0.82
driver.version.internal: 0.53
driver.version.usb: libusb-1.0.22 (API: 0x1000106)
input.frequency: 50.0
input.transfer.high: 266.0
input.transfer.low: 194.0
input.voltage: 234.0
input.voltage.nominal: 230
output.current: 0.0
output.frequency: 50.0
output.frequency.nominal: 50
output.voltage: 234.0
output.voltage.nominal: 230
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.firmware: 264
ups.load: 10
ups.load.nominal: 80
ups.mfr: Hewlett-Packard
ups.model: HP T1000 G3 UPS
ups.power: 67.0
ups.power.nominal: 1000
ups.productid: 1fe2
ups.status: OL CHRG
ups.test.result: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.timer.start: -1
ups.vendorid: 03f0When I first hooked everything up the voltage was 27.1V. Now 3 days later it's dropped. No idea what's wrong, interesting. I kinda want to run a self test and discharge test and see if UPS will recharge batteries.
-
5 minutes ago, SimonF said:
Nut will just report values passed via usb from the device. There may be HP software that may provide more info have you looked at firmware downloads on hp site for update info?
I have indeed. I guess I could shut down NUT and hook up the UPS to a windows laptop real quick to avoid passthru VM within unraid since I'm lazy, but I didn't want to break the NUT connection if not needed yet as I'm not sure if it will be successfully reestablished without a machine restart heh. Never tried it before
-
Is it possible to check UPS firmware a bit more in depth with usbhid-ups? Mine says "ups.firmware = 264" and that doesn't really tell me anything heh. UPS is HP T1000 G3. It has a reccomended firmware upgrade to bypass false fan fault that randomly can occur and enable faster switching on undervoltage.
-
2 hours ago, JorgeB said:
Click on the flash drive on main then "Flash Backup ", parity check can be done before upgrading.
Thank you Jorge. Sorry for being annoying, this is the last question, I promise.
Should I reboot before the parity check?
-
4 hours ago, JorgeB said:
Don't remember if 6.7 supports updating via the GUI (Tools -> Update OS), but you can always do a manual update.
There indeed is Tools -> Update OS. 6.11.5 is the current stable.
Can I anyhow create a full backup for reverting to 6.7.2 in case some big issue arises? Then I'd do a fresh install instead.
Edit: Ah I see: "Before upgrading, we highly recommend making a complete backup of your USB flash device. You can do this by copying the entire contents of the "flash" share to a separate computer."
What would be the best approach to make this copy without shutting down the server?
Also, would you recommend running a correcting parity check first before upgrade? And, should I reboot before correcting parity check and run a noncorrecting one just to see if it still persists? (Rule out software glitch, but it probably isn't a glitch).
-
8 hours ago, JorgeB said:
That's normal.
Run another non correcting check to compare the errors, if they are the exact same sectors you should then run a correcting check.
You should also update Unraid, that's a very old release.
Hello JorgeB, thank you for your reply.
I see, so it's normal then. I wonder why this happened. It seems that it's 1.7MB of data that got ruined on it's own. I did run two checks, errors are exact same.
Oh well, I'll sync it and get that file integrity plugin running, since I have backups anyway so I have no issues restoring from them.
By the way, what's the best way to go upgrading the server? I agree 6.7.2 is old, I think I would benefit from newer kernel and everything.
-
Hello people!
I've been running Unraind since 2019 with no issues, no disk failures, no nothing except great performance, knock on wood.
Anyway, the first issue ever arose a few days ago. It ran it's standard parity check, the only difference was that I changed it in config from every 1mo to every 2mo.
And bam.. Notification - Notice [NAS] - Parity check finished (3360 errors).
So I did some reading, I got the diagnostics file downloaded and attached, I also ran another parity check and same result, same sectors got marked, same amount (3360 errors). So it's probably not ram related and also shouldn't be cabling related (sata in my case).
Also some other important facts:
- 355 day uptime, no issues
- runs on a very good UPS, very stable voltage, no fluctuations
- no sudden shutdowns recently or ever... UPS always gracefully shuts it down
- no any weird changes to settings or modifications except changing scheduler from 1mo to 2mo
- it runs 32MB ECC ram
- parity was always clean (0 errors before) since the server's first startup
SMART data seems to be clean and I don't notice anything else weird.
I DO NOTICE ONE VERY WEIRD THING Sorry for caps, but this is very important.
Pay attention to the sector numbers:
Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737232 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737240 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737248 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737256 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737264 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737272 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737280 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737288 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737296 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737304 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737312 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737320 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737328 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737336 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737344 Feb 5 04:40:09 NAS kernel: md: recovery thread: P incorrect, sector=1056737352They're incremented by 8 non stop. 32, 40, 48, 56, 64, 72, 80, 88, 96, 04, 12, 20, 28.
There is something very wrong. I don't think parity is actually bad, I think there's something wack with the parity checker.
So what do I do now?
Should I reboot?
Thank you.
______________
p.s. I had two questions on my mind for some time:
1. Should I add the checksum plugin?
2. I'm on 6.7.2 atm, is it safe for me to update? since I'm on a really old version I'm not sure if it can update directly without issues, thanks
-
Hi. My DuckDNS docker stopped updating my machine's IP all out of a sudden. I already tried restarting. What are my go to steps for fixing this?
Edit: fixed, was using improper Subdomain keys. Should've only used the subdomain name, eg:
myserver
instead of
myserver.duckdns.org
-
What's the root password for the MinecraftBasicServer docker? I need to change the server.properties file.
-
39 minutes ago, Squid said:
IDK. It works no problems for me under those same circumstances. Only suggestion I have is that an addon to your browser is interfering (ie: MEW CX)
Just tried safe mode with no addons and the latest Mozilla - same thing. Perhaps I could try reinstalling? Is it safe to reinstall CA with a lot of Dockers and Plugins running alongside it.
-
9 minutes ago, Squid said:
What version of CA is showing on the left? What browser are you using?
Chrome 79 on Windows 10, CA version 2020.01.11a
-
After reboot mine still doesn't show search tips. CA is the latest version. Any ideas?
-
17 minutes ago, Squid said:
Fixed
Just updated. Still the same thing. Do I perhaps need to restart my machine?
-
Newest CA update isn't showing hints for me in search. Is it just me?
-
Good luck to everyone!!
The best thing is definetely the community, it's so easy to deploy a good and usable NAS thanks to unRAID. The only thing I'd really like to see is an ability to limit max size of shares
So that you can include multiple disks, but make sure they don't get filled up fully.
-
3 hours ago, trurl said:
You really shouldn't base shutdown on battery level anyway. You don't want your server running on batteries until they are almost dead. You want it to shutdown after only a short period of time without power.
Oh okay. Yes it is the same UPS. There's also an opton called "time on battery", it's basically a timer for how long the server has been without power.
I'm worried to put that one as a setting because, can this happen?:
I set it up to use 10 minutes as a shutdown time if running on battery.
Power goes down->
>5 minutes pass,
>power comes back for 2 seconds and goes down again,
-> server starts 10 minute countdown again -> battery runs down to 0%, server loses power because it restarted its counting down, while the batteries weren't at 100%. So it wasn't a proper countdown.
EDIT: Solved, got it running on blazer_usb.
-
Kinda solved it, I just installed a new UPS with NUT, however I don't see the battery level being reported, can you people please help me diagnose what could be the problem?
How would I tell the server to shut down itself when its running on UPS without battery level?
-
Hello! I just installed a new UPS with NUT, however I don't see the battery level being reported, can you please help me diagnose what could be the problem?
How would I tell the server to shut down itself when its running on UPS without battery level?
EDIT: Solved, got it running on blazer_usb.
I just don't see runtime left now. Any way to make that avalible?
-
It's a PowerMust 1000 NetGuard RM, supported by NUT and blazer_ser driver. How does unRAID manage UPSes? I can also connect it with serial if that helps?
Upgraded from 6.7.2 to 6.11.5 - SMB has become extremely slow in creating files
in General Support
Posted
Example:
Right click, create new folder. *Takes 2 seconds*. Rename it *also takes 2 seconds*.
Tested on multiple devices, same both on 3 Windows machines and one Ubuntu machine. I also captured packets with Wireshark to see what happens and it hangs on "status_pending" packet.