strance4

Members
  • Posts

    28
  • Joined

  • Last visited

Everything posted by strance4

  1. I am working on a backup server but i only have 3 drives i it will be up in maybe 30 days i need get a couple more drives i have 36TB on 2 Drives and 90TB of total data so i got to get like 6-8 more 18tb drives so before i bring it online.
  2. yea sorry for the confusion i dont want to remove the diable disk until i copy the data just in case i cant get the data back. i will do a rebuild with 2 new drives. thanks for all the help i send you a beer Trurl.
  3. Ok once i finish copying the files i will use my spares and do a parity check.
  4. on disk 15 there is a lost and found folder with my files in it on DISK 10 the files are just there no lost and found folder. how do i get the drive to become enable again the are still disable.
  5. root@Brain:~# du -h -d 1 /mnt/user/lost+found 1.8T /mnt/user/lost+found/131 1.8T /mnt/user/lost+found
  6. Updated Diagnostics. brain-diagnostics-20240206-1044.zip
  7. Update. I restart the server and the drive is mounted now but still disabled but i can see the contents. i plan on moving the 18TB from both drives on to another drive then i plan on reformatting them and give it a try again if not i will relace them with my back up drives. this should take 2-3 days to move all that data. Do you guys think this is a good plan or should i do something else? i dont want to restart and the data goes away again. Thank you guys so much you help out alot.
  8. drive 10 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 bad CRC for inode 131 bad CRC for inode 135 bad CRC for inode 131, will rewrite cleared inode 131 bad CRC for inode 135, will rewrite cleared inode 135 - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 12 - agno = 13 - agno = 4 - agno = 8 - agno = 7 - agno = 6 - agno = 11 - agno = 10 - agno = 14 - agno = 15 - agno = 9 - agno = 16 - 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:443386) is ahead of log (1:2). Format log to cycle 4. done
  9. ok running drive 10 test will post then restart server and let you know.
  10. drive 15 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata - 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 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 10 - agno = 13 - agno = 9 - agno = 8 - agno = 4 - agno = 11 - agno = 6 - agno = 12 - agno = 14 - agno = 15 - agno = 16 - agno = 5 - agno = 7 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:130825) is ahead of log (1:2). Format log to cycle 4. done
  11. i dont know how to look for drive 10 and 15 in terminal if some one could let me know the command. After i reboot i am seeing disk unmountable until format bit i think if i format i will loose all that data.
  12. Good Morning, looking for some assistance i woke up to my drive 10 and 15 saying "Unmountable unsupported or no filesystem" they are not in the unassigned devices section. i restart the server and nothing changed. my data from those drive are not there unraid wants me to format those drive before i can reconnect it back to server. brain-diagnostics-20240206-0921.zip
  13. So i restarted in safe mode and everything looks ok then i restarted and it started parity check but everything is working so thanks.
  14. is there a terminal key for that i dont have any buttons to use.
  15. Hi guy Request some help. I went to work and came home and i cant see anything no matter what i do. Everything works Dockers and SMB folders. I have listed below what i have done request assistance i dont want to restart through terminal and then it wont work. I swapped from chrome to edge to firefox no change. I try clicking on DASHBORD MIAN SHARE USERS and there is no change on display. I tried login with other User no change. I reset the WEB Ui using the code from space invader video. Any assistance much appreciated.
  16. ok i will choose that one thanks. I will let you know if it comes back.
  17. I changed the spindown for all my disc under each disk individually to 9 hours each because i didn't see any disable button so i just choose the longest time, dont know if I'm doing this right? The errors went away. i am going to run new SMART test on all my drives will update after.
  18. I dont see drive error all the drive smart is as far as i can see but not an expert at it i only get the log error as warning nothing else.
  19. I am look for some help with this problem. I keep getting this warning that log file is full and i cant find or figure out what is going on. I request some assistance if anyone has any time. brain-diagnostics-20200106-2116.zip
  20. the 90% went away when i delete the docker image.
  21. No smarts warnings on any drives.