Bigzy Posted February 12 Share Posted February 12 (edited) 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 Edited February 12 by Bigzy Quote Link to comment
JorgeB Posted February 12 Share Posted February 12 Enable the syslog server and post that after a crash, in the meantime check filesystem for disk1, run it without -n. Quote Link to comment
Bigzy Posted February 12 Author Share Posted February 12 got these hamilton-diagnostics-20240129-0841.zip hamilton-diagnostics-20240131-0159.zip syslog Quote Link to comment
JorgeB Posted February 12 Share Posted February 12 That appears to be the same syslog, not the persistent one form the syslog server. Quote Link to comment
Bigzy Posted February 12 Author Share Posted February 12 (edited) why is my date wrong? hamilton-syslog-20240212-1612.zip hamilton-syslog-20240212-1618.zip Edited February 12 by Bigzy Quote Link to comment
JorgeB Posted February 12 Share Posted February 12 That's still the same syslog. 2 hours ago, JorgeB said: Enable the syslog server and post that after a crash, in the meantime check filesystem for disk1, run it without -n. Quote Link to comment
Bigzy Posted February 12 Author Share Posted February 12 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 Quote Link to comment
Bigzy Posted February 12 Author Share Posted February 12 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 Quote Link to comment
Bigzy Posted February 12 Author Share Posted February 12 hamilton-syslog-20240212-1612.zip hamilton-syslog-20240212-1618.zip Quote Link to comment
itimpi Posted February 12 Share Posted February 12 17 minutes ago, Bigzy said: how do i do that Restart you array in normal mode Quote Link to comment
Bigzy Posted February 12 Author Share Posted February 12 just got locked out again Quote Link to comment
Bigzy Posted February 12 Author Share Posted February 12 hamilton-syslog-20240212-1929.zip Quote Link to comment
trurl Posted February 12 Share Posted February 12 Two of the posts above were split from another user's thread this user hijacked. @Bigzy why did you think you should post to that other user's thread? Please don't hijack. Quote Link to comment
Bigzy Posted February 12 Author Share Posted February 12 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 Quote Link to comment
trurl Posted February 12 Share Posted February 12 Almost everyone you encounter on the forum, including moderators, are your fellow Unraid users, just trying to help each other. Free support is on the forum from your fellow Unraid users. Paid support is available but not included in the purchase of Unraid. And, you already have multiple people on this thread, some of the most knowledgeable people on the forum. Also, if you post about the same thing in multiple places, it makes it impossible to coordinate responses. Not hijacking and not crossposting has been basic etiquette in internet discussions since before the World Wide Web. Please cooperate. Quote Link to comment
trurl Posted February 12 Share Posted February 12 1 hour ago, itimpi said: Restart you array in normal mode And post new diagnostics Quote Link to comment
Bigzy Posted February 12 Author Share Posted February 12 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 Quote Link to comment
trurl Posted February 12 Share Posted February 12 Please help us help you. Start the array in normal (not maintenance) mode and post new diagnostics. Quote Link to comment
Bigzy Posted February 12 Author Share Posted February 12 hamilton-diagnostics-20240212-1534.zip Quote Link to comment
trurl Posted February 12 Share Posted February 12 Disk1 is mounted and has plenty of data. Also, filesystem repair didn't result in any lost+found. Disk2 appears to be empty, or nearly so. Is that expected? Quote Link to comment
trurl Posted February 12 Share Posted February 12 Unrelated, your system share has files on the array. We can deal with that later. 4 hours ago, Bigzy said: why is my date wrong? The timestamp on these latest diagnostics says 20240212-1534 Last syslog entry about 30 seconds before that. Feb 12 15:15:04 Is that not the correct time for you? Quote Link to comment
trurl Posted February 12 Share Posted February 12 1 hour ago, Bigzy said: just got locked out again Do you have a syslog from syslog server? Quote Link to comment
Bigzy Posted February 12 Author Share Posted February 12 hamilton-syslog-20240212-2110.zip Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.