Bigzy

i got the NFS share setup on unraid, but when i try to setup the tdarr node for transcode i can't get to the NFS share. It would appreciate any advice, I got the nfs share setup on unraid i can see the file, but i can't acces them from apps

got a whole bunch of errors went and bought new ram running test now, if i still get the issue im done

it passed three times before error, should i stop it?

1st cycle is a pass! gonna let it run for the day till complete. will give report then.

running memtest, will let you know the result

Have you done memtest? actually no i haven't. yeah I think I have ECC. What Else could it be?

hamilton-diagnostics-20240213-0819.zip

syslog-192.168.1.121.log

dont have any special settings

hamilton-syslog-20240212-2110.zip

hamilton-diagnostics-20240212-1534.zip

ok, we shall see! if the etiquette is as you say i'll say nothing else until im spoken too. But like everything else, im keeping records

i'm trying to get a definitive answer to a issue im having, asking more than one person makes sense to me. I would imaging it a few of you working on alot of question, going by how long it takes for an answer. ok just trying to optimize my possibilities. i paid for this program yet im having all these issues first it was AMD issue now i changed to Intel same issue

hamilton-syslog-20240212-1929.zip

just got locked out again

hamilton-syslog-20240212-1612.zip hamilton-syslog-20240212-1618.zip

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 bad CRC for inode 4298927383 bad CRC for inode 4298927383, will rewrite cleared inode 4298927383 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 2 - agno = 1 clearing reflink flag on inodes when possible Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done. same issue

how do i do that

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 bad CRC for inode 4298927383 bad CRC for inode 4298927383, will rewrite cleared inode 4298927383 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 2 - agno = 1 clearing reflink flag on inodes when possible Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done

why is my date wrong? hamilton-syslog-20240212-1612.zip hamilton-syslog-20240212-1618.zip

got these hamilton-diagnostics-20240129-0841.zip hamilton-diagnostics-20240131-0159.zip syslog

switched from AMD to Intel , still having issue where it freezes up and i can't access the web ui. help! hamilton-flash-backup-20240211-2010.ziphamilton-flash-backup-20240211-2010.zip hamilton-syslog-20240212-1254.zip

yes i have a ryzen based server now i think i should have stayed with intel