-
-
[Support] Goobaroo - Modded Minecraft Java Servers
So is there a guide for N00Bs? I tried to install SkyFactoryOne and i dont know what im doing wrong but i cant connect to the server I just need some kind of skyblock server and when i lunch ver 1.12.2 MC dosnt work when i lunch 1.16.5 it cant connect to server i get this error: https://prnt.sc/HHuJVGDlfX2O also this is how the server show when i want to connect: https://prnt.sc/2xa0ZnwfpawR I whent and installed this https://files.minecraftforge.net/net/minecraftforge/forge/index_1.16.5.html what am i doing wrong?
-
Drives - What is recommended & what is overkill
Thank you for your thoughts and input I love the great help you can get here even if some questions are very n00b
-
Drives - What is recommended & what is overkill
Thank you for your input My data is mostly stuff i can get again if all fail so no company info or family photo that is one of a kind. So in my case if i wanna downgrade to 1 Parity drive can i just take the array off-line power down and then remove the drive and start up again?
-
Drives - What is recommended & what is overkill
Hi I cant fint a thread like this so im trying to post if there is a thread i have missed please let me know. I have been a happy user of Unraid for around 1 year now and most of the time it work (when i dont fuck up my self). I had some problems with my drives where someone commented that it was overkill with 2 Parity drives when i have 2 normal drives so this thread. My setup is: 2 x Exos 14 TB Parity 2 x Ironwolf 12 TB Disk 2 x EVO 850 500G Cache Now when is it overkill and when is it just right? Both Exos are bought from same seller at same time and Ironwolf are also bought together from an other seller. I know some will say that you should ever buy from same batch but well i prob did. So in case some fail is my Parity over kill? If yes can i remove one of my Parity and reuse for other use? Looking forward to hear your thoughts on this.
-
HDD problems wont mount after shutdown
So its done all looks fine i have had to shutdown due to move but now it have up time of almost 48 hrs no problems with error. Thank you all for now
-
HDD problems wont mount after shutdown
Found this and tried now it say "Parity-Sync/Data-Rebuild in progress." Does this mean that all shoud be okay now?
-
HDD problems wont mount after shutdown
Holy hell >_> I had 4 drive and 12 fans on same power cable with 3 splitter.... I have now changed this to 2 HDD for each cable and Fans on its own cable. Now it say my Parity drive is disable (maybe there were befor i changed around on cables i didnt notic) so how do i re-enable them?
-
HDD problems wont mount after shutdown
so i need new power cabel?
-
HDD problems wont mount after shutdown
Now i have problems again multiple drives is getting error. Can this be a cable problem? I have removed the SATA controller and all are connected to MB. tower-diagnostics-20220214-1217.zip
-
HDD problems wont mount after shutdown
Ah i knew i had been there befor just forgot where to look >_< No new folders in there so all is good?
-
HDD problems wont mount after shutdown
How do i see that?
-
HDD problems wont mount after shutdown
I ran the -L and this is what i got back Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - 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 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 7 - agno = 2 - agno = 8 - agno = 4 - agno = 3 - agno = 6 - agno = 9 - agno = 10 - agno = 1 - agno = 5 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... Maximum metadata LSN (1:2869553) is ahead of log (1:2). Format log to cycle 4. done Stoped the system after and started it again and all seem fine But is it fine? If not please let me know what i need to if yes then... Thank you very much for you help.
-
HDD problems wont mount after shutdown
Will my date be gone if that fails?
-
HDD problems wont mount after shutdown
Also for some reason i have 1 drive in xfs and 1 btrfs im pretty sure they should be the same but im 100% i didnt change anything like filesystem
-
HDD problems wont mount after shutdown
So i ran a check as the guide said and this is what i got but i dont know what it mean about "mount the filesystem" Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.
Ira
Members
-
Joined
-
Last visited