fr05ty

@khaneliman thanks for this, just setup a win11 pc and couldn't figure out where I was going wrong

thanks for having a look, that error block was right after I installed netdata and it started up, I have export on the flash drive and just browsed to \flash in windows and it shows the plugin folder, to check the usb is there any particular program to use, I have a win and a linux pc if you have a fav program I don't think the system would be to busy its a 3900x and most of the time sits at around 5-10% usage and looking at glances iowait is around 1-5%

hello all hopefully someone much smarter than me can tell me why I'm getting this error in my syslogs and if there is a way to fix it unassigned.devices: Warning: shell_exec(/usr/bin/cat /proc/mounts | awk '{print $1 ',' $2}') took longer than 1s! been having a few random lockup lately trying to narrow down causes iceberg-diagnostics-20220816-1456.zip

I have been using plex with the trakt tv plugin for the longest time and never knew why my appdata backups were taking 2Hrs to complete so i installed the QDirStat docker and let it scan all my appdata folders and found mnt/user/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Plug-in Support/Data/com.plexapp.plugins.trakttv/Backups was nearly 100GB am i safe to delete this dir and let it start fresh. I have just added it to my excluded folders for back ups and will let it do a backup tomorrow so i know how much time i will save not backing it up

@neow scroll back to page 11 for screen fix info and you may need to change your network adapter to 'e1000-82545em' to get appleid working

@Leoyzen Sorry I got distracted last night was going to post a pic of the -v , but I will have a look tonight at the log method you suggested, where will I find the log after I try to boot?

@Leoyzen i added the agdpmod=pikera and the AppleMCEReporterDisabler.kext and changed id to iMacPro1,1 but i still get stuck with the loading bar half way, in the vm logs i see this: 2020-03-25T07:33:28.814709Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2020-03-25T07:33:28.820691Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3

hello i have a 5700xt that i would like to pass through to Mac Catalina i have setup macinabox and the vnc works but when i tried to pass through my gfx card it gets to the apple logo the loading bar gets halfway and stops, i have dl'd WG/LILU latest versions and added them to the K/O dir, do i have to add some other boot args to get it working/loading the 5700xt if i change the id to iMacPro1,1 I would also have to add AppleMCEReporterDisabler.kext if i have read this sub correct i also came across an opencore page that says to add agdpmod=pikera for a navi 10 cards is this added in the Clover Configurator somewhere?

i have been having a small problem every 7-18ish days where plex locks up (i think just after a transcode starts) and i need to press the reset button on the system or ssh and send reboot command, i can't do a clean shutdown/reboot, i also tried to disable docker and plex wont shutdown. i have included the diagnostics from the last episode it had. i am using a p2000 and i was using 6.8rc7 at the time it happened but it has also done the same for previous versions of unraid iceberg-diagnostics-20191228-1024.zip

Congrats on 100k users, this has to be one of the hardest contests 1. Toss up between the community and the ease of use to get up and running and expand later. 2. Again would be either native Nvidia driver support (thanks to the linuxserver.io guys) or multi-pools

@srfnmnk you could use a sas expander card like the intel res2sv240 it has pcie x4 pins for power or 4 pin molex if you want to keep a slot free, it can be configured for 1 or 2 8087 from a HBA card and breaks out to 4 or 5 8087 (depending on how you config the input side ), so you can have 16 - 20 drives hanging off this thing, i use one of these in my rig it's just plug and play, I think HP make one that is about upto 24 or 28 drives capable, so if you want it set up for speed use 2 input 4 output and if you can use the m/b sata plugs for the rest or a second HBA card for upto 8 more drives or option 2 you could setup 1 input 5 output for 20 drives and still have another 4 off the second port of your HBA card

i know when i had the error 43 i had to change my bios booting the unraid usb from the "uefi: sandisk" to just "sandisk" and the just reinstall the drivers again

Aug 5 11:31:54 iceberg kernel: md: sync done. time=109225sec Aug 5 11:31:54 iceberg kernel: md: recovery thread: exit status: 0 14tb dives suck 30Hrs for the scrub, but they were on sale for a good price at the time so i just finished the correcting yesterday and the non-correcting today, fixed over 101K errors in first pass and had 0 after the N.C check, so why would i have had so many errors to fix? could it be because parity disk 2 was dying after i rebuilt disk 1? also should a monthly scrub be as a correcting or non-correcting?

it might have filled the internal cache size limit of the ssd, ,it then slows down and writes it to the flash storage itself, same goes for reading, tech deals showed off this in a nvme comparison video recently @ about the 17min mark

last week i had both of my parity drives go red, 1 died replaced it done a rebuild then the second died, done the next rebuild and 3 days later i had the scheduled sync run and got a message of over 100k errors fixed, so i stopped the server done a quick memtest (~8hr 1 pass) had no issues i am currntly doing a 3rd p.s. and im at 50% and 68K errors corrected, i have ordered some new 8087 to 4 sata cables just test the cables but they wont arrive until wed. whet should i be looking for in the logs after 1st re-sync and before 2nd hdd crash iceberg-diagnostics-20190727-0936.zip this is where the drive died Jul 27 17:13:28 iceberg kernel: md: sync done. time=87060sec Jul 27 17:13:28 iceberg kernel: md: recovery thread: exit status: 0 Jul 27 19:29:47 iceberg kernel: sd 7:0:0:0: attempting task abort! scmd(000000001dc9c3cc) Jul 27 19:29:47 iceberg kernel: sd 7:0:0:0: [sdd] tag#0 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00 Jul 27 19:29:47 iceberg kernel: scsi target7:0:0: handle(0x000a), sas_address(0x5001e67467de7fec), phy(12) Jul 27 19:29:47 iceberg kernel: scsi target7:0:0: enclosure logical id(0x5001e67467de7fff), slot(12) Jul 27 19:29:47 iceberg kernel: sd 7:0:0:0: device_block, handle(0x000a) Jul 27 19:29:49 iceberg kernel: sd 7:0:0:0: device_unblock and setting to running, handle(0x000a) Jul 27 19:29:49 iceberg kernel: sd 7:0:0:0: [sdd] Synchronizing SCSI cache Jul 27 19:29:49 iceberg rc.diskinfo[7620]: SIGHUP received, forcing refresh of disks info. Jul 27 19:29:49 iceberg rc.diskinfo[7620]: SIGHUP ignored - already refreshing disk info. Jul 27 19:29:51 iceberg kernel: sd 7:0:0:0: task abort: SUCCESS scmd(000000001dc9c3cc) Jul 27 19:29:51 iceberg kernel: md: disk29 read error, sector=4916493968 Jul 27 19:29:51 iceberg kernel: md: disk29 read error, sector=4916493976 after scheduled parity check iceberg-diagnostics-20190801-2003.zip