Thank you very much. I feel like I've been trying to solve a problem for hours that was an intended feature. If I'd have read the changelog I'd have saved myself hours of time since I couldn't find the mounted drives at first
Beiträge von ezkialrage
-
-
I recently reinstalled omv and my hdd references went from uiud=xxx media/xxx
To being this below
Srv/media-by-label srv/media-by-labelI liked having then by uiud and I tried to change them back in fstab but that borked omv. My question is why did this happen? Why did the reference/mount point change?
-
Alles anzeigen
Hello, I would first like to apologize for my bad English.
I encountered a problem when using docker, to make it simple I want to install a bitorrent client that must go through a VPN without all the traffic of the machine going through the VPN.
So I had the idea to turn to docker and especially to the image haugene / transmission-openvpn.
My problem is that the storage does this in the volume of the container and I would like him to do it directly in a local directory that does not change as soon as a change is made to the container and do not have a name like "002ef0c61d59f744f2416c3153cc3308ba6efd5ac991ca5fea0d1950fb887948"
If ever you have advice when setting up transmission, to download torrents and seed them behind
thank you in advance
The last part referring to storage I find it hard to understand. Can you try and explain again what's the issue ?
I know exactly what your problem is and i know how to solve it. I was having the same issue myself and i didn't know what the problem was. I ended up just trial and erroring things and then eventually i was the options in the omv docker-container gui i needed to edit to make this work. I will try to explain the problem and then how i fixed it.
the issue is that your docker download directory, and your 'omv/transmission/nas' doanload directory are not bound.
I spent hours changing the ENV variable TRANSMISSION_FINISHED_DOWNLOAD to my nas directory but my nas drive wouldnt get the file. transmission would spend time downloading the file and then poof it was just no where to be found. Then i got to digging into the docker container file system and after a lot of digging 'usr/var/lib/docker/???' something like that, i found the transmission downloads. at the directory i specified in the EVN variable.
so then after a few more hours, i realized below the ENV variables section in the container start dialogue, there is a bind directory field. Thats what you need to edit. your Nas download directory is the first field, and the docker container download directory is the second field. (if you changed this in the ENV variables, you have to put that directory here). but there is a GOTCHA. i put my NAS directory as /jack/sparrow/ and my docker downloads were /docker/downloads/. If you are using Sonarr, and you set up transmission to download into /jack/sparrow, your downloads will fail because your docker container does not have the folder /jack/sparrow and transmission will not know where to put the file. this is because docker is running transmission and not OMV so it does not have immediate access to your root file structure. it only have access to the internal folders (e.g /docker/downloads) and they get bound to external folders (e.g. /jack/sparrow). The solution to this problem is simple. you need to make your docker downloads directory the same ad your NAS downloads directory. so your docker ENV variable for transmission downloads should also be /jack/sparrow/.
I know this is long, but i wanted to explain why it wasn't working vs just giving a solution.
Tl:Dr;
1. set your Docker downloads ENV variable path to be the same as your NAS download dir path
2. in the docker container start dialogue, BIND the nas doanload path to your docker download path. (this means they should say the same thing on each line e.g. /my/download/folder).
3. this also applies to incomplete downloads, and a watch folder.hope this helps.
-
yup thats what i ended up setting up. so now its only accessible from ovpn port and ftp. easy peasy.
-
just wanted to chime in here again and close this thread out. I think i was right in thinking it was the bruteforce attacks killing the box overnight. i shut off access from the net and its been running great.
-
so the nasbox has been running great the last two days. i closed off access from the internet to the box. now its only accessible from the local network and through openvpn and ftp. i think my issue was that i was getting Dos'ed. i combed through the authentication logs and the timeframes of the hundreds of login attempts match the timeframe of the last log in the syslog everytime it crashed.
today i am going to replace my os drive with an ssd and my old media drives with 1 red drive. hopefully this will fix up all issues. Ill report back and close this thread out after a few days. i appreciate the help so far.
-
heres the smart command of my OS drive..
Code
Alles anzeigenLinux ServerRage 3.16-0.bpo.2-amd64 #1 SMP Debian 3.16.3-2~bpo70+1 (2014-09-21) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Wed Oct 29 19:42:12 2014 from 216.155.129.27 root@ServerRage:~# smartctl -a /dev/sda smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.16-0.bpo.2-amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint T166 Device Model: SAMSUNG HD501LJ Serial Number: S0MUJ1BQB04955 LU WWN Device Id: 5 0000f0 01bb04955 Firmware Version: CR100-13 User Capacity: 500,106,780,160 bytes [500 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Thu Oct 30 12:51:56 2014 CDT SMART support is: Available - device has SMART capability. SMART support is: 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: ( 9069) 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: ( 155) minutes. SCT capabilities: (0x003f) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 6 3 Spin_Up_Time 0x0007 100 100 015 Pre-fail Always - 7744 4 Start_Stop_Count 0x0032 088 088 000 Old_age Always - 12965 5 Reallocated_Sector_Ct 0x0033 099 099 010 Pre-fail Always - 11 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 253 253 015 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 19802 10 Spin_Retry_Count 0x0033 253 253 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 253 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 280 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 176159608 187 Reported_Uncorrect 0x0032 097 097 000 Old_age Always - 327684 188 Command_Timeout 0x0032 253 253 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 077 053 000 Old_age Always - 23 194 Temperature_Celsius 0x0022 169 094 000 Old_age Always - 23 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 176159608 196 Reallocated_Event_Count 0x0032 099 099 000 Old_age Always - 11 197 Total_Pending_Sectors 0x0012 253 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 253 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 202 Data_Address_Mark_Errs 0x0032 253 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run 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. -
interesting. people are attempting to break into my server. thought kernel logs were pretty anonymous.
edit: apparently people have been trying to bruteforce their way in since sunday
just went through the authentication logs. no idea how my server got out there. -
heres the 2nd one. post was too long
Code
Alles anzeigensmartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.16-0.bpo.2-amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 Device Model: ST3500630A Serial Number: 9QG6BDJ1 Firmware Version: 3.AAF User Capacity: 500,106,780,672 bytes [500 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed Oct 29 19:43:27 2014 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. 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: ( 430) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 163) minutes. 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 112 081 006 Pre-fail Always - 46725742 3 Spin_Up_Time 0x0003 097 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 090 090 020 Old_age Always - 10409 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 056 041 030 Pre-fail Always - 11485726963523 9 Power_On_Hours 0x0032 053 053 000 Old_age Always - 41629 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 566 187 Reported_Uncorrect 0x0032 076 076 000 Old_age Always - 24 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 066 039 045 Old_age Always In_the_past 34 (Min/Max 25/34) 194 Temperature_Celsius 0x0022 034 061 000 Old_age Always - 34 (0 18 0 0) 195 Hardware_ECC_Recovered 0x001a 069 052 000 Old_age Always - 234332903 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 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 24 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 24 occurred at disk power-on lifetime: 14218 hours (592 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 c6 0a 05 f0 Error: UNC at LBA = 0x00050ac6 = 330438 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 bf 0a 05 f0 00 00:02:55.200 READ DMA EXT 25 00 08 bf 0a 05 f0 00 00:02:55.199 READ DMA EXT 25 00 08 bf 0a 05 f0 00 00:02:55.175 READ DMA EXT 25 00 08 bf 0a 05 f0 00 00:02:55.170 READ DMA EXT 25 00 00 7f 1a 05 f0 00 00:02:55.163 READ DMA EXT Error 23 occurred at disk power-on lifetime: 14218 hours (592 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 c6 0a 05 f0 Error: UNC at LBA = 0x00050ac6 = 330438 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 bf 0a 05 f0 00 00:02:55.200 READ DMA EXT 25 00 08 bf 0a 05 f0 00 00:02:55.199 READ DMA EXT 25 00 08 bf 0a 05 f0 00 00:02:55.175 READ DMA EXT 25 00 00 7f 1a 05 f0 00 00:02:55.170 READ DMA EXT 25 00 00 7f 19 05 f0 00 00:02:55.163 READ DMA EXT Error 22 occurred at disk power-on lifetime: 14218 hours (592 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 c6 0a 05 f0 Error: UNC at LBA = 0x00050ac6 = 330438 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 bf 0a 05 f0 00 00:02:55.200 READ DMA EXT 25 00 08 bf 0a 05 f0 00 00:02:55.199 READ DMA EXT 25 00 00 7f 1a 05 f0 00 00:02:55.175 READ DMA EXT 25 00 00 7f 19 05 f0 00 00:02:55.170 READ DMA EXT 25 00 00 7f 18 05 f0 00 00:02:55.163 READ DMA EXT Error 21 occurred at disk power-on lifetime: 14218 hours (592 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 c6 0a 05 f0 Error: UNC at LBA = 0x00050ac6 = 330438 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 bf 0a 05 f0 00 00:02:55.200 READ DMA EXT 25 00 00 7f 1a 05 f0 00 00:02:55.199 READ DMA EXT 25 00 00 7f 19 05 f0 00 00:02:55.175 READ DMA EXT 25 00 00 7f 18 05 f0 00 00:02:55.170 READ DMA EXT 25 00 00 7f 17 05 f0 00 00:02:55.163 READ DMA EXT Error 20 occurred at disk power-on lifetime: 14218 hours (592 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 c6 0a 05 f0 Error: UNC at LBA = 0x00050ac6 = 330438 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 bf 0a 05 f0 00 00:02:41.651 READ DMA EXT 25 00 38 47 0b 05 f0 00 00:02:41.643 READ DMA EXT 25 00 08 bf 0a 05 f0 00 00:02:53.150 READ DMA EXT 25 00 80 c7 0a 05 f0 00 00:02:53.137 READ DMA EXT 25 00 08 b7 0a 05 f0 00 00:02:51.222 READ DMA EXT SMART Self-test log structure revision number 1 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. -
Here is the smart command for my two oldest hard drives. the other two are wd reds i just bought so im sure they arnt bad. these two however are pretty old. my kern.log is too big to attach (2.6mb) so here is a dropbox link if your interested, would my messages.txt or deamon.log be useful to put up?. https://dl.dropboxusercontent.com/u/7059664/files/kern.log
ive combed through it, but at the time of the crash, it does not log anything. you can see the time jump multiple hours for when it stopped logging, to when i rebooted it.
Code
Alles anzeigensmartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.16-0.bpo.2-amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint T166 Device Model: SAMSUNG HD501LJ Serial Number: S0MUJ1BQB04955 LU WWN Device Id: 5 0000f0 01bb04955 Firmware Version: CR100-13 User Capacity: 500,106,780,160 bytes [500 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Wed Oct 29 19:42:33 2014 CDT SMART support is: Available - device has SMART capability. SMART support is: 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: ( 9069) 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: ( 155) minutes. SCT capabilities: (0x003f) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 100 100 015 Pre-fail Always - 7744 4 Start_Stop_Count 0x0032 088 088 000 Old_age Always - 12965 5 Reallocated_Sector_Ct 0x0033 099 099 010 Pre-fail Always - 11 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 253 253 015 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 19785 10 Spin_Retry_Count 0x0033 253 253 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 253 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 280 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 339432 187 Reported_Uncorrect 0x0032 097 097 000 Old_age Always - 327684 188 Command_Timeout 0x0032 253 253 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 076 053 000 Old_age Always - 24 194 Temperature_Celsius 0x0022 166 094 000 Old_age Always - 24 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 339432 196 Reallocated_Event_Count 0x0032 099 099 000 Old_age Always - 11 197 Total_Pending_Sectors 0x0012 253 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 253 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 253 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 253 100 000 Old_age Always - 0 202 Data_Address_Mark_Errs 0x0032 253 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run 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. -
ok will do a bit later. i also just remembered on bootup it hangs on "checking quotas". i dont have quotas enabled and it hasn't normally done this.
-
thanx for the reply. the system drive is a repurposed WD passport 2.5inch 320gb sata drive i had laying around unused. i do not have smart enabled, is this something i should do? i wasn't sure if it was important or not. I will look for and check the kern.log tonight. Thanks for helping me out
-
hey guys,
I’m having an issue either with OMV(software) or my system(hardware), and I’m hoping i can describe my issues here and get some help if its OMV. I’ve reinstalled OMV about a week ago and everything was running great until about 4 days ago. after a reboot the system wouldn’t finish booting and threw out a lot of errors.
usb 2-2 device descriptor read/64, error -71
xhci_hcd 00:0:0:0 setup error: setup context command for slot 1
usb 2-2 hub failed to enable device
i figured after a few hours that it was the keyboard that i had plugged into the usb3.0 terminal and when i plugged it into the 2.0 terminal system booted no errors no problem. this was using the new kernel so i was surprised that usb 3.0 wasn’t working especially since i enabled usb 3.0 in the mobo bios.
the next morning i woke up and my Nasbox was hard locked up; unreachable by smb/ssh/ftp etc, so i had to hold down the power and start it up. I thought it was a fluke until the next morning I woke up and found the nasbox unresponsive yet again.
at this point i started looking up potential issues. The system logs didn’t show anything out of the ordinary other than the timestamp of a “flushall” was 7 hours before the rebooting logging started. So to me it seemed as though whatever happened wasn’t being logged.
full disclosure, I’m still new to linux and couldn’t find an error log so i was only going off of the syslog in the GUI.
steps I’ve taken 2 nights ago.
I thought the drives might be overheating so i separated my 4 drives from 1 bay into 2 x 2 bays.
I plugged the sata cables into different terminals on my motherboard after checking for faulty cabling.
i uninstalled all plugins except for plex.
after a few reboots, i started watching some vids and during playback the nasbox froze yet again after about 30 min of video watching. I rebooted once and all seemed fine for the night.
then this morning i woke up to a frozen box again so i held down power to reboot again. this time when i rebooted, I received a few errors on the startup screen which lead me to believe a hard drive is failing.
33.888139 ata2.00 failed command: read dma
43.295999 ata2.00 revalidation failed (errno=-5
end_request i/0 error, dev sad sect 8
ect…
I let the machine boot all the way up and one of my raids was offline so i rebooted, and this time i used the old 3.2.0 kernel vs the 3.16 kernel. The machine booted all the way in and the raid was there so i started backing up the media on that drive to another drive and during the transfer the box locked up frozen again. Im not sure if a bad drive would totally freeze the machine especially if its just been sitting for hours. and thats where I’m at right now.
so I think there are a few issues i could possibly be facing.
Maybe my OMV installation got borked.
maybe my HDD is borked causing system lockups
maybe my cpu is overheating, although I’ve got a serious fan on it and around 6 case fans with serious airflow.
maybe ram is borked?
so many variables i don’t know where to start. I can’t find an error log to point me in the right direction. Ill post logs (if i can figure out how) when i get home from work later, i just wanted to get this down before i forgot everything I’ve done.
anybody have any ideas? what other information do you need from me?
-
thanx for the reply. I actually did do
apt-get --purge remove plexmediaserver
apt-get --purge remove openmediavault-plexmediaserver
userdel plexbefore every reinstall of plex and OMV. I saw that you mentioned these commands in another thread so i added them to things to try. whats strange is that i would thing that doing this purge would delete all user permissions and metadata. but still everytime i reinstalled OMV and plex i would still get the "service isnt running" red dot in services gui.
maybe i was reinstalling in the wrong order? does a fresh reinstall of OMV totally delete plugin data/users or is there a chance of permission remnants staying?
this was one of the more hair pulling issues ive had but still im glad its solved for me at least for now.
-
xpost from plex.tv forums...
I'm writing this to document the steps i took to resolve an issue i had with PMS where no matter what i did the service wouldn't start. I somehow borked my PMS installation and decided i needed to reinstall it and start fresh. I had installed from the plugins menu so i uninstalled from there. proceeded to purge all pms assets in the command line and rebooted. I reinstalled pms from the gui again and this time the server wouldnt start.
I went through multiple uninstalls and reinstalls, changed the pms database directory multiple times and still no go. so then i reinstalled from a .deb in the command line. no matter what i did the plexmediaservice would show a red dot in the OMV gui services tab and the command line would output "it seems the service isnt running".
welp time to start over completely and totally reinstall OMV. so i reinstalled OMV went through all of the updates, installed the new kernal from the omv-extras repo and then i reinstalled plex. rebooted. I went to the services tab and the plexmediaservice still had a red dot! reinstalled OMV multiple times using default kernel, changing database folders. I searched all over the forums, here and omv.org, tried all manner of purge this, grep that, apt update/upgrade ect. I tried changing ownership of the database folder to root:nogroup, then to plex:users, then to fuck:this. nothing worked. the errors still plagued me.
reading a forum late at night i read an off-comment about manually creating the plex user. I tried to create the plex user but it wasn't showing up in the gui. I read that this was because when you install plex it creates a user "silently". I uninstalled plex, rebooted, created the plex user manually and gave it access to all the shares. When i reinstalled plex lo and behold, works like a charm and somewhat faster than before!
sorry for the rambling, but i wanted to give people the solution that worked for me after days of searching. maybe i can help save people time.
TL;DR
if you're at wits end, try uninstalling plex, create a user with the name "plex" manually and give it access to all your shares and then reinstall plex.
-
ok thank you. was wondering if i was going crazy. by chance, is there a way that i can check if a repo is down myself? like a ping command or something? I'm still new to linux & i like knowing how to do things and figuring out issues so i don't have to keep asking for help.
-
i was having issues with my plex media server after i moved my nasbox to a different place in the house. it has a static ip, and everything is the same, from when it was working, but somehow moving it has caused the plex server to no longer work. in the services tab it was showing as enabled, but with a red dot instead of a blue dot. so after a few hours of searching and enabling reenabling and reinstalling the plunging, i decided to start anew.
i completely reinstalled OMV and this time i updated all of the updates/installed the extras repo and then am trying to install plex. instead of installing, it is just sitting on the install screen with..
Reading package lists...
Building dependency tree...no matter how long i let it sit, it will not continue. every other plugin i try to install works fine. after an apt-get update, these errors were thrown out at the end...
CodeW: Failed to fetch http://shell.ninthgate.se/packages/debian/dists/squeeze/Release.gpg Could not connect to shell.ninthgate.se:80 (195.22.88.165). - connect (111: Connection refused)W: Failed to fetch http://shell.ninthgate.se/packages/debian/dists/wheezy/Release.gpg Unable to connect to shell.ninthgate.se:http:W: Some index files failed to download. They have been ignored, or old ones used instead.is the plex server down or have i screwed something royally? appreciate the help
-
Where it says server you should only put the ip address. The remote share below the ip address field
my good man. thank you for this. i can not believe how difficult i was making it. you've saved me a few grey hairs. i really appreciate it.
-
hi,
im hoping maybe i could get a little assistance with the remoteshare plugin. im a complete noob in linux but building this omv box has been a great learning experience for me. ive got everything set up the way i want for a plex server, but i would like to use the remoteshare plugin to mount a static ip'd servers smb shared drive for plex to access.
ive run into a few issues trying this, and i fully believe its because i have no idea how to format the "server address" line in the plugin. i will try to attach photos but basically what ive tried in the server address field is
//server_name/shared_folder
server_name/shared_folder//192.168.xxx.xxx/shared_folder
192.168.xxx.xxx/shared_folderive even tried options with the forward slashes instead of backslashes and each with single quotes around them as well. each one of those lines returns an error when i hit "apply" in omv. sometimes its "cant resolve host" or one was "bad unc" i think. id appreciate if someone would help with the correct way to format/use this plugin, or point me to a a remoteshare manual. ive honestly looked everywhere for a readme or something to help me figure out how to use the plugin.
again, sorry if this is a completely easy rudimentary thing, but ive only just gotten into linux and omv in the last week. everything else ive figured out with extensive googlage, but this issue has taken me about 3 days and now id just rather ask someone.
-
double-post
