sevenz
-
Posts
56 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by sevenz
-
-
1 hour ago, trurl said:
How is starting from scratch going to help your hardware issues?
Are you saying Disk 6,5 and 1 possibly hardware failure? Because I just bought it recently, the oldest one is Disk6, around 4 months ago, Disk5 2 months ago. Disk 1 just bought it last week. Or seagate I bought is just shit?
-
10 hours ago, trurl said:
Fixing connections won't necessarily make disks mountable again. They might still need filesystem repair.
You can see the connection issues in syslog. Until they are fixed no point in trying to fix anything else, including repairing filesystems or rebuilding disks.
Thanks, that's what I thought too, probably a lot easier to start from scratch, and install everything again from there. Any guidance on what I can do now?
I'm not sure how to wipe clean and restart unraid after backing up.
-
22 minutes ago, trurl said:
Still having connection problems with disk5. Check connections, both ends, power and SATA, including splitters.
You must always have another copy of everything important and irreplaceable. There are many ways to lose data that parity can't help with.
I will try again tomorrow, I have some cables somewhere in office and will try that. I have swapped the sata cables but still unmountable. I havent tried to change the molex to sata adapter to power the HDD.
13 minutes ago, trurl said:Can't tell what may be on disk5 or disk1 since they aren't mountable.
You have a lost+found share where repair would have put anything it couldn't figure out from repair, but that share would only contain lost+found from disk6 currently, which has few if any files on it. Unless you have done repair at some time on another disk that is currently mounted.
I see numbers and most of it are empty. So it's good to say that disk6 is empty and I cant recover anything?
EDIT:
Side note, now the error is gone, just that 2 disks are unmountable
-
Just now, trurl said:
Do you have backups of everything important and irreplaceable?
Unfortunately this is my best backup
unraid has been reliable protecting my files.
Should I try to back up whatever's left?
-
1 minute ago, trurl said:
Did you ever push the format button?
nope never.
-
I changed the cable, changed the sata slot on disk5, still unmountable.
-
It all started with Disk 1 died, so for a few days while waiting new disk comes, content is emulated. Now that it has come, opened up the case, swap the disk, suddenly Disk 1 becomes unmountable: not mounted. Weird it's a new disk, so I swapped the cables for it, somehow disk 5 and 6 follows, becomes unmountable.
So I read up here https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
I did the xfs-repair. Not sure how I did it, suddenly disk 5 and 6 loss all data, if you see screenshot above that disks 6 has 56gb used. originally both disk 5 and 6 has almost full disk. Is there anyway to recover those files?
Panicked, I try to upgrade UNRAID to the latest RC version, only to kill my USB. I changed my USB to a new one, and copied the config to the new USB. Screenshot are all from the new USB.Anyway, I dare not do anything else as of now, here I seek guidance on how should I proceed. I noticed photos from 2008 are gone, probably because they're on disk 5 or 6.
Right now the system is doing parity rebuild, but the speed is horrible.
mynas-diagnostics-20210913-2001.zip
here is the diagnostics, not sure if it any helps. Weird part that I notice is that all these happens to Seagate IronWolf disks.
-
Sorry for the late reply, yes I do but only 1 file.
-
Got it. Thank you for the explanation!
-
I did it via GUI terminal. It looks for secondary block and all it does is giving dots ....................... and never stops. I canceled it via ctrl + z. I hope I'm not making any mistake there?
-
-
Quote
Phase 1 - find and verify superblock...
- reporting progress in intervals of 15 minutes
- block cache size set to 1859624 entries
Phase 2 - using internal log
- zero log...
zero_log: head block 452803 tail block 451456
ALERT: The filesystem has valuable metadata changes in a log which is being
destroyed because the -L option was used.
- 20:48:25: zeroing log - 59617 of 59617 blocks done
- scan filesystem freespace and inode maps...
agi_freecount 11571, counted 11570 in ag 31
agi unlinked bucket 37 is 33999013 in ag 31 (inode=8355498149)
block (34,321655-321910) multiply claimed by cnt space tree, state - 2
agf_freeblks 15995487, counted 15995828 in ag 34
sb_ifree 172202, counted 173174
sb_fdblocks 938740953, counted 941210108
- 20:48:28: scanning filesystem freespace - 64 of 64 allocation groups done
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- 20:48:28: scanning agi unlinked lists - 64 of 64 allocation groups done
- process known inodes and perform inode discovery...
- agno = 0
- agno = 30
- agno = 15
- agno = 60
- agno = 45
- agno = 61
- agno = 62
- agno = 63
- agno = 31
- agno = 16
- agno = 46
- agno = 47
imap claims a free inode 8355498174 is in use, correcting imap and clearing inode
cleared inode 8355498174
- agno = 32
- agno = 17
- agno = 48
- agno = 49
- agno = 50
- agno = 51
- agno = 52
- agno = 53
- agno = 54
- agno = 55
- agno = 56
- agno = 57
- agno = 58
- agno = 59
- agno = 33
- agno = 34
- agno = 35
- agno = 18
- agno = 36
- agno = 1
- agno = 19
- agno = 2
- agno = 37
- agno = 38
- agno = 39
- agno = 40
- agno = 41
- agno = 3
- agno = 4
- agno = 20
- agno = 5
- agno = 21
- agno = 42
- agno = 22
- agno = 6
- agno = 23
- agno = 24
- agno = 7
- agno = 25
- agno = 8
- agno = 26
- agno = 9
- agno = 27
- agno = 28
- agno = 43
- agno = 44
- agno = 10
- agno = 11
- agno = 29
- agno = 12
- agno = 13
- agno = 14
- 20:49:30: process known inodes and inode discovery - 612864 of 612864 inodes done
- process newly discovered inodes...
- 20:49:30: process newly discovered inodes - 64 of 64 allocation groups done
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- 20:49:30: setting up duplicate extent list - 64 of 64 allocation groups done
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 4
- agno = 9
- agno = 10
- agno = 3
- agno = 6
- agno = 7
- agno = 8
- agno = 2
- agno = 11
- agno = 5
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- agno = 24
- agno = 25
- agno = 26
- agno = 27
- agno = 28
- agno = 29
- agno = 30
- agno = 31
- agno = 32
- agno = 33
- agno = 34
- agno = 35
- agno = 36
- agno = 37
- agno = 38
- agno = 39
- agno = 40
- agno = 41
- agno = 42
- agno = 43
- agno = 44
- agno = 45
- agno = 46
- agno = 47
- agno = 48
- agno = 49
- agno = 50
- agno = 51
- agno = 52
- agno = 53
- agno = 54
- agno = 55
- agno = 56
- agno = 57
- agno = 58
- agno = 59
- agno = 60
- agno = 61
- agno = 62
- agno = 63
- 20:49:30: check for inodes claiming duplicate blocks - 612864 of 612864 inodes done
Phase 5 - rebuild AG headers and trees...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- agno = 24
- agno = 25
- agno = 26
- agno = 27
- agno = 28
- agno = 29
- agno = 30
- agno = 31
- agno = 32
- agno = 33
- agno = 34
- agno = 35
- agno = 36
- agno = 37
- agno = 38
- agno = 39
- agno = 40
- agno = 41
- agno = 42
- agno = 43
- agno = 44
- agno = 45
- agno = 46
- agno = 47
- agno = 48
- agno = 49
- agno = 50
- agno = 51
- agno = 52
- agno = 53
- agno = 54
- agno = 55
- agno = 56
- agno = 57
- agno = 58
- agno = 59
- agno = 60
- agno = 61
- agno = 62
- agno = 63
- 20:49:43: rebuild AG headers and trees - 64 of 64 allocation groups done
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- agno = 24
- agno = 25
- agno = 26
- agno = 27
- agno = 28
- agno = 29
- agno = 30
- agno = 31
- agno = 32
- agno = 33
- agno = 34
- agno = 35
- agno = 36
- agno = 37
- agno = 38
- agno = 39
- agno = 40
- agno = 41
- agno = 42
- agno = 43
- agno = 44
- agno = 45
- agno = 46
- agno = 47
- agno = 48
- agno = 49
- agno = 50
- agno = 51
- agno = 52
- agno = 53
- agno = 54
- agno = 55
- agno = 56
- agno = 57
- agno = 58
- agno = 59
- agno = 60
- agno = 61
- agno = 62
- agno = 63
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 8355498149, moving to lost+found
Phase 7 - verify and correct link counts...
- 20:50:13: verify and correct link counts - 64 of 64 allocation groups done
Maximum metadata LSN (62:452259) is ahead of log (1:2).
Format log to cycle 65.XFS_REPAIR Summary Tue Mar 9 20:50:27 2021
Phase Start End Duration
Phase 1: 03/09 20:48:21 03/09 20:48:21
Phase 2: 03/09 20:48:21 03/09 20:48:28 7 seconds
Phase 3: 03/09 20:48:28 03/09 20:49:30 1 minute, 2 seconds
Phase 4: 03/09 20:49:30 03/09 20:49:30
Phase 5: 03/09 20:49:30 03/09 20:49:43 13 seconds
Phase 6: 03/09 20:49:43 03/09 20:50:13 30 seconds
Phase 7: 03/09 20:50:13 03/09 20:50:13Total run time: 1 minute, 52 seconds
doneAhh alright, it does it's thing now. I used the option -vL there. What should I do next?
-
Quote
Phase 1 - find and verify superblock...
- reporting progress in intervals of 15 minutes
- block cache size set to 1859624 entries
Phase 2 - using internal log
- zero log...
zero_log: head block 452803 tail block 451456
ALERT: The filesystem has valuable metadata changes in a log which is being
ignored because the -n option was used. Expect spurious inconsistencies
which may be resolved by first mounting the filesystem to replay the log.
- 19:14:06: zeroing log - 59617 of 59617 blocks done
- scan filesystem freespace and inode maps...
agi_freecount 11571, counted 11570 in ag 31
agi unlinked bucket 37 is 33999013 in ag 31 (inode=8355498149)
block (34,321655-321910) multiply claimed by cnt space tree, state - 2
agf_freeblks 15995487, counted 15995828 in ag 34
sb_ifree 172202, counted 173174
sb_fdblocks 938740953, counted 941210108
- 19:14:08: scanning filesystem freespace - 64 of 64 allocation groups done
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- 19:14:08: scanning agi unlinked lists - 64 of 64 allocation groups done
- process known inodes and perform inode discovery...
- agno = 45
- agno = 30
- agno = 15
- agno = 0
- agno = 60
- agno = 61
- agno = 62
- agno = 63
- agno = 46
- agno = 47
- agno = 16
- agno = 31
- agno = 17
- agno = 48
- agno = 49
- agno = 50
- agno = 51
- agno = 52
- agno = 53
- agno = 54
- agno = 55
- agno = 56
- agno = 57
- agno = 58
- agno = 59
imap claims a free inode 8355498174 is in use, would correct imap and clear inode
- agno = 32
- agno = 33
- agno = 34
- agno = 18
- agno = 35
- agno = 19
- agno = 36
- agno = 1
- agno = 2
- agno = 37
- agno = 38
- agno = 39
- agno = 40
- agno = 41
- agno = 3
- agno = 20
- agno = 4
- agno = 21
- agno = 42
- agno = 5
- agno = 22
- agno = 6
- agno = 23
- agno = 24
- agno = 25
- agno = 7
- agno = 26
- agno = 8
- agno = 27
- agno = 9
- agno = 28
- agno = 43
- agno = 44
- agno = 29
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- 19:15:10: process known inodes and inode discovery - 612864 of 612864 inodes done
- process newly discovered inodes...
- 19:15:10: process newly discovered inodes - 64 of 64 allocation groups done
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
free space (34,321911-321995) only seen by one free space btree
- 19:15:10: setting up duplicate extent list - 64 of 64 allocation groups done
- check for inodes claiming duplicate blocks...
- agno = 1
- agno = 2
- agno = 11
- agno = 0
- agno = 3
- agno = 4
- agno = 5
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 6
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- agno = 24
- agno = 25
- agno = 26
- agno = 27
- agno = 28
- agno = 29
- agno = 30
- agno = 31
- agno = 32
- agno = 33
- agno = 34
- agno = 35
- agno = 36
- agno = 37
- agno = 38
- agno = 39
- agno = 40
- agno = 41
- agno = 42
- agno = 43
- agno = 44
- agno = 45
- agno = 46
- agno = 47
- agno = 48
- agno = 49
- agno = 50
- agno = 51
- agno = 52
- agno = 53
- agno = 54
- agno = 55
- agno = 56
- agno = 57
- agno = 58
- agno = 59
- agno = 60
- agno = 61
- agno = 62
- agno = 63
- 19:15:10: check for inodes claiming duplicate blocks - 612864 of 612864 inodes done
No modify flag set, skipping phase 5
Inode allocation btrees are too corrupted, skipping phases 6 and 7
No modify flag set, skipping filesystem flush and exiting.XFS_REPAIR Summary Tue Mar 9 19:15:10 2021
Phase Start End Duration
Phase 1: 03/09 19:14:05 03/09 19:14:05
Phase 2: 03/09 19:14:05 03/09 19:14:08 3 seconds
Phase 3: 03/09 19:14:08 03/09 19:15:10 1 minute, 2 seconds
Phase 4: 03/09 19:15:10 03/09 19:15:10
Phase 5: Skipped
Phase 6: Skipped
Phase 7: SkippedTotal run time: 1 minute, 5 seconds
So this is what I got from the first checkup. Doesnt look so good.
Trying to do xfs_repair -nv /dev/sdb now -
Yep as other people who have similar issues I dare not touch until I know what I need to do.
mynas-diagnostics-20210309-1800.zip
After a restart this is what happened to sdb
I tried changing the cable but still the same. I wonder how should I proceed from here?
Do I need to xfs_repair -v /dev/ something?
It's been few days because I didnt have the time (work) to fix this immediately.I wonder what would happen to my data?
Anyone can fill me here?
Thanks!
-
Hello, I`m trying to passthrough the whole front panel USB controller (4 of them) so that I can hot swap my USBs. Steps that I used is:
Quote
root@MyNAS:~# lspci | grep USB
00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller (rev 05)
00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 (rev 05)
00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 (rev 05)
0c:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
Then I tested
Quote
root@MyNAS:~# lsusb
Bus 002 Device 002: ID 8087:8002 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 0951:1642 Kingston Technology DT101 G2
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:800a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 1532:0204 Razer USA, Ltd
Bus 003 Device 003: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 002: ID 0b05:180a ASUSTek Computer, Inc.
Bus 003 Device 008: ID 1043:8012 iCreate Technologies Corp. Flash Disk 256 MB
Bus 003 Device 006: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 003 Device 004: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 003 Device 008 is one of the USB I tried plugging onto the front panel.
Quote
root@MyNAS:~# readlink /sys/bus/usb/devices/usb3
../../../devices/pci0000:00/0000:00:14.0/usb3So by this its on 0000:00:14.0 right?
Using step 11.b, I wrote to my XML this just above the </devices> line
Quote
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x00' slot='0x14' function='0x0'/>
</source>
</hostdev>
Here is my IOMMU groups
QuoteIOMMU group 0
[8086:6f81] ff:0b.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01)
[8086:6f36] ff:0b.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01)
[8086:6f37] ff:0b.2 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01)
[8086:6f76] ff:0b.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link Debug (rev 01)
IOMMU group 1
[8086:6fe0] ff:0c.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
[8086:6fe1] ff:0c.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
[8086:6fe2] ff:0c.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
[8086:6fe3] ff:0c.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
[8086:6fe4] ff:0c.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
[8086:6fe5] ff:0c.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
IOMMU group 2
[8086:6ff8] ff:0f.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
[8086:6ff9] ff:0f.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
[8086:6ffc] ff:0f.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
[8086:6ffd] ff:0f.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
[8086:6ffe] ff:0f.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01)
IOMMU group 3
[8086:6f1d] ff:10.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent (rev 01)
[8086:6f34] ff:10.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent (rev 01)
[8086:6f1e] ff:10.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01)
[8086:6f7d] ff:10.6 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01)
[8086:6f1f] ff:10.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01)
IOMMU group 4
[8086:6fa0] ff:12.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 (rev 01)
[8086:6f30] ff:12.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 (rev 01)
IOMMU group 5
[8086:6fa8] ff:13.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS (rev 01)
[8086:6f71] ff:13.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS (rev 01)
[8086:6faa] ff:13.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01)
[8086:6fab] ff:13.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01)
[8086:6fac] ff:13.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01)
[8086:6fad] ff:13.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01)
[8086:6fae] ff:13.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Broadcast (rev 01)
[8086:6faf] ff:13.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast (rev 01)
IOMMU group 6
[8086:6fb0] ff:14.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Thermal Control (rev 01)
[8086:6fb1] ff:14.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Thermal Control (rev 01)
[8086:6fb2] ff:14.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Error (rev 01)
[8086:6fb3] ff:14.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Error (rev 01)
[8086:6fbc] ff:14.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01)
[8086:6fbd] ff:14.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01)
[8086:6fbe] ff:14.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01)
[8086:6fbf] ff:14.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01)
IOMMU group 7
[8086:6fb4] ff:15.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Thermal Control (rev 01)
[8086:6fb5] ff:15.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Thermal Control (rev 01)
[8086:6fb6] ff:15.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Error (rev 01)
[8086:6fb7] ff:15.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Error (rev 01)
IOMMU group 8
[8086:6f68] ff:16.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Target Address/Thermal/RAS (rev 01)
[8086:6f6e] ff:16.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Broadcast (rev 01)
[8086:6f6f] ff:16.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast (rev 01)
IOMMU group 9
[8086:6fd0] ff:17.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 0 Thermal Control (rev 01)
[8086:6fb8] ff:17.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01)
[8086:6fb9] ff:17.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01)
[8086:6fba] ff:17.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01)
[8086:6fbb] ff:17.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01)
IOMMU group 10
[8086:6f98] ff:1e.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
[8086:6f99] ff:1e.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
[8086:6f9a] ff:1e.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
[8086:6fc0] ff:1e.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
[8086:6f9c] ff:1e.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
IOMMU group 11
[8086:6f88] ff:1f.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
[8086:6f8a] ff:1f.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01)
IOMMU group 12
[8086:6f00] 00:00.0 Host bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 (rev 01)
IOMMU group 13
[8086:6f02] 00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01)
IOMMU group 14
[8086:6f03] 00:01.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01)
IOMMU group 15
[8086:6f08] 00:03.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 01)
IOMMU group 16
[8086:6f28] 00:05.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management (rev 01)
[8086:6f29] 00:05.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug (rev 01)
[8086:6f2a] 00:05.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors (rev 01)
[8086:6f2c] 00:05.4 PIC: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC (rev 01)
IOMMU group 17
[8086:8d7c] 00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR (rev 05)
[8086:8d62] 00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] (rev 05)
IOMMU group 18
[8086:8d31] 00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller (rev 05)
IOMMU group 19
[8086:8d3a] 00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI Controller #1 (rev 05)
IOMMU group 20
[8086:15a1] 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V (rev 05)
IOMMU group 21
[8086:8d2d] 00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 (rev 05)
IOMMU group 22
[8086:8d20] 00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio Controller (rev 05)
IOMMU group 23
[8086:8d10] 00:1c.0 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #1 (rev d5)
IOMMU group 24
[8086:8d16] 00:1c.3 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #4 (rev d5)
IOMMU group 25
[8086:8d18] 00:1c.4 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #5 (rev d5)
IOMMU group 26
[8086:8d1c] 00:1c.6 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #7 (rev d5)
IOMMU group 27
[8086:8d26] 00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 (rev 05)
IOMMU group 28
[8086:8d47] 00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller (rev 05)
[8086:8d02] 00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] (rev 05)
[8086:8d22] 00:1f.3 SMBus: Intel Corporation C610/X99 series chipset SMBus Controller (rev 05)
IOMMU group 29
[1002:699f] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon RX 550] (rev c7)
[1002:aae0] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0
IOMMU group 30
[1b21:118f] 05:00.0 PCI bridge: ASMedia Technology Inc. Device 118f
IOMMU group 31
[1b21:118f] 06:01.0 PCI bridge: ASMedia Technology Inc. Device 118f
IOMMU group 32
[1b21:118f] 06:02.0 PCI bridge: ASMedia Technology Inc. Device 118f
IOMMU group 33
[1b21:118f] 06:03.0 PCI bridge: ASMedia Technology Inc. Device 118f
IOMMU group 34
[1b21:118f] 06:04.0 PCI bridge: ASMedia Technology Inc. Device 118f
IOMMU group 35
[8086:1539] 07:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
IOMMU group 36
[14e4:43a0] 08:00.0 Network controller: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter (rev 03)
IOMMU group 37
[10de:1b82] 09:00.0 VGA compatible controller: NVIDIA Corporation GP104 (rev a1)
[10de:10f0] 09:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
IOMMU group 38
[1b21:0612] 0b:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
IOMMU group 39
[1b21:1142] 0c:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
But when I want to start my VM, I get this
I wonder which step I did wrong? I tried redoing again and googling, but I'm not sure which part should I fix.
Any help would be nice. Thanks!
-
10 minutes ago, pwm said:
TX-100 and TX-1000 uses the wires differently, which means TX-100 can work where TX-1000 doesn't.
TX-100 only needs two of the pairs, while TX-1000 needs all four pairs.
Besides that, TX-1000 uses a higher bandwidth through each pair making it more sensitive to a bad connection.
Ah got it! Guess if it does happen again I`ll try to get a new cable. Didn't know the cable is very sensitive.
-
11 hours ago, Squid said:
Bad or loose cable?
Loose cable seems like it. I just changed it like a month ago because of the same problem. I plugged it out and back and now it's green light with 1000mbps speed.
But how can loose cable still get connection? I thought it's supposed to just lose connection?
-
Hello, I tried searching the forum, but found nothing, either my keyword sucks or no such problem ever posted.
NIC Link is up 100Mbps instead of 1000Mbps. Any idea what caused it? I'm not sure what that exceed max 2 second means. Is it a problem with the router or my setting in NAS?
Here is my setup.
I have a VM that is passthrough as well, would that cause it?
-
Ahh alright, thanks for the TL;DR! I will read back again a couple post behind when I got home from work.
EDIT: I remote to my VM to do it and it works now!
38 minutes ago, [email protected] said:exact same problem here too, after updating the letsencrypt container.
the solution is posted a couple posts below.
tl:dr = letsencrypt changed something (auth method over port 443 disabled)
1. you have to make sure now that tcp port 80 is forwarded on your router (internet gateway) to your unraid server (be aware that unraid uses default tcp 80 for its webinterface, so map tcp port 80 extern to something else intern like tcp 81)
2. edit/update the container settings > edit letsencrypt in the unraid docker tab and set the http port to 81 or whatever to used for your portmapping on your router.
3. also change the variable HTTPVAL from false to true, its found in " show more settings"
HTTPVAL: true Flag to switch validation method to HTTP (over port 80) if set to 'true' -
Hello guys, Letsencrypt goes down on me suddenly, I don't recall on making changes on UnRaid (only adding new HDD and SSD) and I haven't upgraded to 6.4.0 yet.
Browsing through the thread, I don't see anyone with similar log to mine (or I missed it).
Here is the log.
I notice because Nextcloud stopped working this morning. Everything was working before then.
-
Ahh sorry, should I post in Letsencrypt instead?
EDIT: Nevermind I got it working! Turns out I need to port letsencrypt to 443 and nextcloud to 444, not the other way around!
-
Hello, not sure if I should post it here or the letsencrypt forum, but I followed the guide here and almost got all the steps except getting letsencrypt to work.
This is the log file shown in the letsencrypt.
Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,
it will attempt to use a webserver both for obtaining and installing the
cert.
certbot: error: argument --cert-path: No such file or directory
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
tls-sni-01 challenge for www.nextcloud.sevenz.id
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. www.nextcloud.sevenz.id (tls-sni-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Incorrect validation certificate for tls-sni-01 challenge. Requested 649cc8da09ee4b25e364c0cfb83940c9.39736846123211ed6c97ba1fdcec0678.acme.invalid from 66.96.235.118:443. Received 1 certificate(s), first certificate had names "*"
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: www.nextcloud.sevenz.id
Type: unauthorized
Detail: Incorrect validation certificate for tls-sni-01 challenge.
Requested
649cc8da09ee4b25e364c0cfb83940c9.39736846123211ed6c97ba1fdcec0678.acme.invalid
from 66.96.235.118:443. Received 1 certificate(s), first
certificate had names "*"
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address.
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.Anything I should do to fix this?
-
@ken-ji ah right, that will comment out the command. Alright I added it! Will report back if anything doesn't work properly.
-
On 10/26/2017 at 7:18 AM, ken-ji said:
You are running out of file descriptors.... this is usually solved by running some commands before the docker is started
# sysctl -w fs.file-max=1616812
You can place this in the go file. I don't know if the Tips and Tweaks Plugin can set that for you.
Caveat: The number is the default max on my system and I never had to override it and I run Transmission with a bunch of seeds.
Tou can get the current value with
# sysctl fs.file-max
Got it! I used ssh for this, I can't find the Tips and Tweaks Plugin while...
On 10/26/2017 at 11:47 PM, trurl said:The go file is in config folder of your flash drive. It is sometimes used to run code at boot since most things won't survive a reboot.
You could also do this with the User Scripts plugin.
I managed to get the User Scripts, but I'm not sure if I set it up correctly.
unraid has been reliable protecting my files. 
Content is emulated, unmountable - device not mounted.
in General Support
Posted
ah ok, thank you for your guidance, I`ll try to backup everything and re-check everything.