ArdNsc
-
Posts
29 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by ArdNsc
-
-
3 hours ago, JorgeB said:
when you reconnect it, do you use a different USB port?
Yes. Next time I can try using the same port.
-
4 hours ago, JorgeB said:
Could still be a board/USB problem, but it can also be a device problem, do you have another NIC you could try with?
I don't have another USB-NIC. Before I buy a new one, I would at least like to understand what the log is telling me: For some unknown reason the USB disconnetcs. (But) it gets recognized after I replug it manually, but then nothing happens. Is that expected behaviour? My assumption would be, that if it was a problem with the NIC itself unplugging and replugging the USB device should solve the issue? (While booting the log says
usbcore: registered new interface driver r8152
, this does not happen after replugging.)
-
On 4/3/2024 at 2:40 PM, JorgeB said:
USB device getting disconnect should not be a drive issue, try a different USB port.
Hi JorgeB, unfortunately this did not help resolve the issue. Had the bug again just a few minutes ago:
Apr 10 16:33:04 Server kernel: r8152-cfgselector 2-3: USB disconnect, device number 2 Apr 10 16:33:04 Server kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. Apr 10 16:33:04 Server avahi-daemon[15003]: Interface eth0.IPv4 no longer relevant for mDNS. Apr 10 16:33:04 Server avahi-daemon[15003]: Leaving mDNS multicast group on interface eth0.IPv4 with address yyy.yyy.y.yyy. Apr 10 16:33:04 Server avahi-daemon[15003]: Withdrawing address record for yyy.yyy.y.yyy on eth0. Apr 10 16:33:04 Server kernel: usb 2-3: new SuperSpeed USB device number 4 using xhci_hcd Apr 10 16:33:04 Server kernel: r8152-cfgselector 2-3: reset SuperSpeed USB device number 4 using xhci_hcd Apr 10 16:33:04 Server kernel: r8152 2-3:1.0 eth0: v2.17.1 (2023/06/13) Apr 10 16:33:04 Server kernel: r8152 2-3:1.0 eth0: This product is covered by one or more of the following patents: Apr 10 16:33:04 Server kernel: US6,570,884, US6,115,776, and US6,327,625. Apr 10 16:33:04 Server kernel: Apr 10 16:33:06 Server ntpd[1444]: Deleting interface #1 *multiple*, yyy.yyy.y.yyy#123, interface stats: received=1807, sent=1807, dropped=0, active_time=431332 secs Apr 10 16:33:06 Server ntpd[1444]: xxx.xxx.xx.0 local addr yyy.yyy.y.yyy -> <null> Apr 10 16:33:06 Server ntpd[1444]: xxx.xxx.xx.12 local addr yyy.yyy.y.yyy -> <null> Apr 10 16:33:06 Server ntpd[1444]: xxx.xxx.xx.8 local addr yyy.yyy.y.yyy -> <null> Apr 10 16:33:06 Server ntpd[1444]: xxx.xxx.xx.4 local addr yyy.yyy.y.yyy -> <null> Apr 10 16:35:08 Server emhttpd: read SMART /dev/sdk Apr 10 16:35:08 Server emhttpd: read SMART /dev/sdl Apr 10 16:35:11 Server kernel: r8152-cfgselector 2-3: USB disconnect, device number 4 Apr 10 16:35:13 Server emhttpd: read SMART /dev/sdj Apr 10 16:35:36 Server kernel: usb 1-4: new high-speed USB device number 4 using xhci_hcd Apr 10 16:35:36 Server kernel: r8152-cfgselector 1-4: reset high-speed USB device number 4 using xhci_hcd Apr 10 16:35:37 Server kernel: r8152 1-4:1.0 (unnamed net_device) (uninitialized): get_registers -19 Apr 10 16:35:37 Server kernel: r8152 1-4:1.0 (unnamed net_device) (uninitialized): Get ether addr fail Apr 10 16:35:37 Server kernel: r8152 1-4:1.0 eth0: v2.17.1 (2023/06/13) Apr 10 16:35:37 Server kernel: r8152 1-4:1.0 eth0: This product is covered by one or more of the following patents: Apr 10 16:35:37 Server kernel: US6,570,884, US6,115,776, and US6,327,625. Apr 10 16:35:37 Server kernel: Apr 10 16:35:37 Server kernel: r8152-cfgselector 1-4: USB disconnect, device number 4 Apr 10 16:35:37 Server kernel: usb 2-4: new SuperSpeed USB device number 5 using xhci_hcd Apr 10 16:35:37 Server kernel: r8152-cfgselector 2-4: reset SuperSpeed USB device number 5 using xhci_hcd Apr 10 16:35:37 Server kernel: r8152 2-4:1.0 eth0: v2.17.1 (2023/06/13) Apr 10 16:35:37 Server kernel: r8152 2-4:1.0 eth0: This product is covered by one or more of the following patents: Apr 10 16:35:37 Server kernel: US6,570,884, US6,115,776, and US6,327,625. Apr 10 16:35:37 Server kernel: Apr 10 16:38:26 Server emhttpd: spinning down /dev/sde Apr 10 16:38:26 Server emhttpd: spinning down /dev/sdf Apr 10 16:41:14 Server elogind-daemon[1344]: Power key pressed. Apr 10 16:41:14 Server elogind-daemon[1344]: Powering Off...
Note that at 16:35 i manually detached the USB device and plugged it into another USB port. I try this every time this bug occures, but it does not help.
-
My server becomes unresponsive from time to time and i have to reboot it. Looking at the log (previous) seems to tell me that there is some problem with my USB-Ethernet device.
Apr 3 11:36:28 Server kernel: r8152-cfgselector 2-2: USB disconnect, device number 2 Apr 3 11:36:28 Server kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. Apr 3 11:36:28 Server kernel: r8152 2-2:1.0 eth0: Tx status -108 Apr 3 11:36:28 Server kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. Apr 3 11:36:28 Server dhcpcd[1281]: eth0: carrier lost Apr 3 11:36:28 Server dhcpcd[1281]: eth0: deleting route to yy.yy.yy.0/24 Apr 3 11:36:28 Server dhcpcd[1281]: eth0: deleting default route via yy.yy.yy.1 Apr 3 11:36:28 Server dhcpcd[1281]: eth0: removing interface Apr 3 11:36:28 Server avahi-daemon[21299]: Interface eth0.IPv4 no longer relevant for mDNS. Apr 3 11:36:28 Server avahi-daemon[21299]: Leaving mDNS multicast group on interface eth0.IPv4 with address yy.yy.yy.120. Apr 3 11:36:28 Server avahi-daemon[21299]: Withdrawing address record for yy.yy.yy.120 on eth0. Apr 3 11:36:29 Server kernel: usb 2-2: new SuperSpeed USB device number 5 using xhci_hcd Apr 3 11:36:29 Server kernel: r8152-cfgselector 2-2: reset SuperSpeed USB device number 5 using xhci_hcd Apr 3 11:36:29 Server kernel: r8152 2-2:1.0 eth0: v2.17.1 (2023/06/13) Apr 3 11:36:29 Server kernel: r8152 2-2:1.0 eth0: This product is covered by one or more of the following patents: Apr 3 11:36:29 Server kernel: US6,570,884, US6,115,776, and US6,327,625. Apr 3 11:36:29 Server kernel: Apr 3 11:36:31 Server ntpd[1525]: Deleting interface #1 *multiple*, yy.yy.yy.120#123, interface stats: received=775, sent=775, dropped=0, active_time=135907 secs Apr 3 11:36:31 Server ntpd[1525]: xx.xx.xx.8 local addr yy.yy.yy.120 -> <null> Apr 3 11:36:31 Server ntpd[1525]: xx.xx.xx.4 local addr yy.yy.yy.120 -> <null> Apr 3 11:36:31 Server ntpd[1525]: xx.xx.xx.0 local addr yy.yy.yy.120 -> <null> Apr 3 11:36:31 Server ntpd[1525]: xx.xx.xx.12 local addr yy.yy.yy.120 -> <null> Apr 3 11:41:35 Server ntpd[1525]: no peer for too long, server running free now
I am not sure what is going on here. Am I using the wrong driver (the installed plugin seems to be RTL8152 Drivers, while under system devices it says: Bus 002 Device 002 Port 2-2 ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G LAN) Or is it some kind of power state problem, where USB gets deactivated?
Can you point me into the right direction? As I don't have physical access to my server right now (only vpn via unraid wireguard) I am too afraid to just delete the network driver and reboot.
-
I downgraded back to 6.11.5 and everything is woring again. Will not upgrade to 6.12.x any time soon.
Too bad that there seems to be no answer to the plugin-problem. And the fact that macvlan/ipvlan suddenly is messing everything up is not acceptable for me. Adding a second network-card/cable is no solution for me.
-
Since the Upgrade to 6.12.x i ran into several problems of which I don't know if they are connected in any way:
-
I cannot install new plugins. I always get this message
Quote
Installation already in progress
Another plugin installation or update is already in progress, and this one cannot start. Wait until the current installation or update is completed and try again
(I am trying to install the new appdata backup plugin, since the old one is deprecated). I am running the latest CA (2023.07.03) and rebooting the system does NOT solve the issue.
-
Fix Common Problems is complaining about
Quotemacvlan call traces found
but when I change in the docker setting to ipvlan as anyone here is recommending to do, my Pihole container stops working properly (I can still access the container, but all queries seem to get blocked).
-
I don't get internet access on my clients when I route my devices through VPN (running on unraid) any longer.
I think I did not change any settings (at least knowingly) and had none of these issues with 6.11.5. Any idea what might go wrong? Or how to fix these problems one at a time?
-
I cannot install new plugins. I always get this message
-
I ran into the same problem. I cannot install any new plugins, I always get this message:
QuoteInstallation already in progress
Another plugin installation or update is already in progress, and this one cannot start. Wait until the current installation or update is completed and try again
I am running Unraid 6.12.2, CA is version 2023.07.03. Reboot did not fix the problem for me. Any suggestions?
-
I get this error since today/since last container update:
QuoteThis version of Nextcloud is not compatible with PHP>=8.2.
You are currently running 8.2.6.How to proceed?
-
Just to let you know in case anyone reads this later: I switched out the faulty drive by now; but I had to use a backup to rebuild the contents of my cache pool -- which is all my fault.
I started with a btrfs raid5 (5 drives) and I wanted to remove 2 drives (the faulty one and another small old SSD, only one at a time, of course) and replace it by a newer, bigger one.
This is how not to do it: I think I messed things up when I replaced the small healthy drive by the larger SSD (insted of getting rid of the faulty one first). I performed a balance operation (I think it started automatically, the UI does not tell you what Unraid is doing at this point!) and then a scub, which threw a few hundred of errors on me. I performed a second, error correcting scrub operation which left around 100 errors uncorrected. Then I removed the faulty SSD (which just was involved In a full balance operation with lots of data not only read off it, but rewritten to it...), perfomed balance again. I was at my desired config now (4-Drive-Raid5). The next scrub check threw over 9.000.000 errors at me, all uncorrectable. In the logs I found only around 300 faulty files, but even after deleting them, I still got around 5-6million errors. Then I decided that I seriously have fucked things up and started from scratch.
Now my new 4-disk-raid5-pool is fine (no more smart errors, no scrub errors) and thanks to full backups I did not suffer any dataloss. (I would not have tried that procedure otherwise.)
-
Okay. Thanks for clearing that up.
And in case I ever decide to switch to dual parity I just build up a (new) "Parity" (1) and keep the "Parity 2", right?
-
I just want to double check if I am doing everything right.
What I want do achive: I have an array with single parity (10TB). I got a new drive (12TB) recently and I want to end up with an array with single parity (the new 12TB drive), containing the ex-parity drive (10TB) as an additional data disk.
I dont want to lose parity during any step of the process, so removing the parity device from the array and rebuilding it on the new drive was no option for me. Instead I planned the following steps:
1. Preclear the new 12TB drive (to test if it's good, succeeded)
2. Add the 12TB drive as Parity 2 and build parity on it (currently running, around 50% done)
3. Removing "Parity" 1 device (10TB drive)
4. Assign the old parity drive (10TB) as a new data drive, clear it.
5. Ending up with 10TB additional storage space in the array - and single parity.
Currently I am in the middle of step 2. I am getting some mixed feelings because the nomenclatura/terms/descriptions of the UI do not seem to be totally idiot proof/consistant; at least not to me: On the Main page under "Parity" it says "Data-Rebuild in progress... Completed: xx%". (I am not rebuilding any data? I am building up a second parity?) Under "Array" I have a green dot next to the "Parity" device and a yellow dot ("invalid") next to the "Parity 2" device. In The array Tab under "Array Devices" I have a green dot next to "Parity" and a yellow triangle next to "Parity 2" stating: "Parity is invalid". (All devices exept "Parity 2" are reading; "Parity 2" is writing. Seems right to me. The parity is considered "invalid" because it's still "building up"?) Under array operation I read: "Parity-Sync in progress." I am assuming that I am still having single parity at the moment and that I am currently building up dual parity. Right?
Also I want to make sure that it is okay to perform Step 3: When I remove Parity 1 and start the array, will "Parity 2" automatically become "Parity" (1) without the need to rebuild the parity again? This is what I am assuming.
And: When perfoming step 4 (adding new data drive) I also do not have to rebuild parity, it will remain valid. Right?
Tl;dr: Can I switch from dual parity to single parity just by removing the "Parity" device and keeping the "Parity 2" device? Will it become "Parity" (1) then?
Sorry for the redundant questions, I just don't want to mess things up.
-
If this is the wrong Sub-Forum, please just hint me into the right direction. Over a year ago Unraid reported a SMART-Error for one of my SSDs in my cache-pool. I confirmed the warning and since then no new errors where reported. Now I realised that I cannot run manual short or extended SMART-tests anymore (when I click, just nothing happens).
There is no really important data on my Cache-Pool, which is running as a btrfs raid5. Anyway I wanted to know if I should replace that drive. I was planning to upgrade my cache soon.
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.17-Unraid] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Crucial/Micron RealSSD m4/C400/P400 Device Model: M4-CT256M4SSD2 Serial Number: 0000000013010925333F LU WWN Device Id: 5 00a075 10925333f Firmware Version: 040H User Capacity: 256,060,514,304 bytes [256 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches TRIM Command: Available, deterministic Device is: In smartctl database 7.3/5417 ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Dec 26 16:19:15 2022 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM level is: 254 (maximum performance) 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. General SMART Values: Offline data collection status: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. Self-test execution status: ( 64) The previous self-test completed having a test element that failed and the test element that failed is not known. Total time to complete Offline data collection: ( 1190) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 19) minutes. Conveyance self-test routine recommended polling time: ( 3) 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 POSR-K 001 001 050 NOW 310 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 12288 9 Power_On_Hours -O--CK 100 100 001 - 38257 12 Power_Cycle_Count -O--CK 100 100 001 - 3089 170 Grown_Failing_Block_Ct PO--CK 100 100 010 - 3 171 Program_Fail_Count -O--CK 100 100 001 - 78 172 Erase_Fail_Count -O--CK 100 100 001 - 0 173 Wear_Leveling_Count PO--CK 082 082 010 - 563 174 Unexpect_Power_Loss_Ct -O--CK 100 100 001 - 76 181 Non4k_Aligned_Access -O---K 100 100 001 - 1477 1182 295 183 SATA_Iface_Downshift -O--CK 100 100 001 - 0 184 End-to-End_Error PO--CK 100 100 050 - 0 187 Reported_Uncorrect -O--CK 100 100 001 - 0 188 Command_Timeout -O--CK 100 100 001 - 0 189 Factory_Bad_Block_Ct -OSR-- 100 100 001 - 82 194 Temperature_Celsius -O---K 100 100 000 - 0 195 Hardware_ECC_Recovered -O-RCK 100 100 001 - 93333 196 Reallocated_Event_Count -O--CK 100 100 001 - 3 197 Current_Pending_Sector -O--CK 100 100 001 - 0 198 Offline_Uncorrectable ----CK 100 100 001 - 0 199 UDMA_CRC_Error_Count -O--CK 100 100 001 - 0 202 Perc_Rated_Life_Used ---RC- 082 082 001 - 18 206 Write_Error_Rate -OSR-- 100 100 001 - 78 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 51 Comprehensive SMART error log 0x03 GPL R/O 16383 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 255 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 3449 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0 GPL VS 2000 Device vendor specific log 0xa0 SL VS 208 Device vendor specific log 0xa1-0xbf GPL,SL VS 1 Device vendor specific log 0xc0 GPL VS 80 Device vendor specific log 0xc1-0xdf GPL,SL VS 1 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (16383 sectors) No Errors Logged SMART Extended Self-test Log size 3449 not supported SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 38257 - # 2 Short offline Completed without error 00% 37923 - # 3 Short offline Completed without error 00% 37923 - # 4 Short offline Completed without error 00% 37923 - # 5 Extended offline Completed without error 00% 37898 - # 6 Extended offline Completed without error 00% 37897 - # 7 Extended offline Completed without error 00% 37897 - # 8 Extended offline Completed without error 00% 37897 - # 9 Short offline Completed without error 00% 37897 - #10 Extended offline Completed without error 00% 33020 - #11 Short offline Completed without error 00% 33016 - #12 Extended offline Completed without error 00% 33016 - #13 Extended offline Completed without error 00% 33016 - #14 Short offline Completed without error 00% 29870 - #15 Vendor (0xff) Completed without error 00% 27430 - #16 Short offline Completed without error 00% 26310 - #17 Vendor (0xff) Completed without error 00% 26284 - 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): 1 (0x0001) Device State: Active (0) Current Temperature: 0 Celsius Power Cycle Min/Max Temperature: --/ 0 Celsius Lifetime Min/Max Temperature: --/ 0 Celsius SCT Temperature History Version: 2 Temperature Sampling Period: 10 minutes Temperature Logging Interval: 10 minutes Min/Max recommended Temperature: 0/70 Celsius Min/Max Temperature Limit: -5/75 Celsius Temperature History Size (Index): 478 (73) Index Estimated Time Temperature Celsius 74 2022-12-23 08:40 0 - ... ..(476 skipped). .. - 73 2022-12-26 16:10 0 - SCT Error Recovery Control: Read: 40 (4.0 seconds) Write: 40 (4.0 seconds) Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 2) == 0x01 0x008 4 3089 --- Lifetime Power-On Resets 0x01 0x010 4 38257 --- Power-on Hours 0x01 0x018 6 104764793610 --- Logical Sectors Written 0x01 0x020 6 930655381 --- Number of Write Commands 0x01 0x028 6 186135985241 --- Logical Sectors Read 0x01 0x030 6 1119502745 --- Number of Read Commands 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 0 --- Current Temperature 0x05 0x010 1 0 --- Average Short Term Temperature 0x05 0x018 1 0 --- Average Long Term Temperature 0x05 0x020 1 0 --- Highest Temperature 0x05 0x028 1 0 --- Lowest Temperature 0x05 0x030 1 0 --- Highest Average Short Term Temperature 0x05 0x038 1 0 --- Lowest Average Short Term Temperature 0x05 0x040 1 0 --- Highest Average Long Term Temperature 0x05 0x048 1 0 --- Lowest Average Long Term Temperature 0x05 0x050 4 - --- Time in Over-Temperature 0x05 0x058 1 70 --- Specified Maximum Operating Temperature 0x05 0x060 4 - --- Time in Under-Temperature 0x05 0x068 1 0 --- Specified Minimum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 0 --- Number of Hardware Resets 0x06 0x010 4 0 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors 0x07 ===== = = === == Solid State Device Statistics (rev 1) == 0x07 0x008 1 2 N-- Percentage Used Endurance Indicator |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 4 0 Command failed due to ICRC error 0x000a 4 22 Device-to-host register FISes sent due to a COMRESET -
Damn. I am hesitating to buy another PCIe->NVMe Bifurcation card that fits my needs when I can't even get a single NVMe drive running. Are there any (stupid) mistakes that come to your mind what I could be missing here? Any wrong Bios-settings?
-
-
So: For testing I am running the PCIe port in [1x16] default mode with one NVMe-Drive installed on the Expansion Card. The NVMe-Drive is detected in Bios:
Seg:Bus:Dev:Func 00:01:00:00
Model Number CT500P5SSD8
Total Size 500.1 GB
Vendor ID 1344
Device ID 5405
Namespace: 1 Size: 500.1 GB
But I can't see it in unRAID. When I try to add Disks to my Cache Pool or create a new one, the drive is not there.
What am I missing here? -
16GB DDR4 ECC
-
Ist aus Deinem Projekt etwas geworden? Ich habe das gleiche Board und habe bis vorhin gedacht, ich könne einfach eine PCIe x8 Adapterkarte auf 2x NVMe M.2 daran betreiben. Offenbar funktioniert das aber nicht, weil ich als Modus dann 4x4x4x4 bräuchte. Siehst du noch andere Möglichkeiten, an dem Board mehrere M.2 SSDs zu betreiben? Der M.2-Slot auf dem Board ist bei mir (wie bei dir) durch einen 5-Port-Sata-Adapter belegt.
-
Okay. Thanks so far. I will check a few things and get back in touch later.
-
The board has just one PCIe-Slot. Can you tell if the adapter card is getting recognized?
-
-
Damn. But should'nt I be able to at least see/use one of the two drives right now? The notes of the PCIe-Card say "Without PCIe bifurcation only the first M.2 slot of the card can be used." I just want to rule out other possible errors before I send the new hardware back and start over from scratch...
-
I am trying to set up a new cache pool with two NVMe drives (Crucial P5 500GB).
I have this Mainboard https://www.gigabyte.com/Motherboard/C246N-WU2-rev-10#kf and got this PCIe-Card https://www.delock.de/produkte/G_89045/merkmale.html?setLanguage=en . Long story short: It does not work, Unraid does not show me the new drives when I want to assign them to the new cache pool. I already changed the bios setting "CPU PCIE x16 Switch" ("Allows you to determine how the bandwidth of the PCIEX16 slot is divided. (Default: 1x16)") from [1x16] to [2x8] as well as [1x8 & 2x4], which does not make any difference.
What am I doing wrong here? Please tell me if you need any more information. And I hope, i put this into the right category. If not, don't hesitate to tell me. Thanks.
-
On 2/22/2020 at 2:48 PM, Squid said:
That setting sets Sab to be the absolute lowest priority of any given docker container. Such that every container has priority over it (default cpu shares setting is 512)
I have been experimenting with "--cpu-shares" and it does not what I am intending to do. I read everywhere that the default value is 1024, are you sure it's 512? Is this some kind of special setting in unRaid or just a typo?
-
I have not yet started the moving project (moving Internet-exposed Nextcloud from Raspi to Server) I explained in my opening post. I wanted to do it in the next couple of days, but now I red some horror stories of users losing all their data because they exposed their Unraid-machines to the internet.
Am I getting this right, that exposing a single docker container (nextcloud) with its own fixed IP-Adress by forwarding port 443 (thats what I was planning to do) is not the kind of thing everyone is warning users about (they are exposing the Unraid-UI)? Would you say that what I am planning to do is "okay"?
Sorry for asking again, I just want to make sure I am not messing things up.
[Plugin] Realtek R8125 R8168 and R8152\6 drivers
in Plugin Support
Posted
I had the chance to test it: It does not make any difference if I switch to a different USB port or use the same one as before.
Yeah, it seems like it. So this is a dead end I guess. Can I make a feature request anywhere?
Besides that I am still trying to find out what makes the USB NIC drop out in the first place. Any Ideas how to proceed?