strance4 Posted February 6 Share Posted February 6 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 Quote Link to comment
strance4 Posted February 6 Author Share Posted February 6 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. Quote Link to comment
JorgeB Posted February 6 Share Posted February 6 Check filesystem on both emulated disks, run it without -n. Quote Link to comment
strance4 Posted February 6 Author Share Posted February 6 (edited) I Ran the test and the results for drive 15 below. Edited February 6 by strance4 Quote Link to comment
strance4 Posted February 6 Author Share Posted February 6 (edited) Drive 10 had the same results. Edited February 6 by strance4 Quote Link to comment
strance4 Posted February 6 Author Share Posted February 6 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 Quote Link to comment
itimpi Posted February 6 Share Posted February 6 When you restart the array in normal mode that disk should now mount. Quote Link to comment
strance4 Posted February 6 Author Share Posted February 6 (edited) ok running drive 10 test will post then restart server and let you know. Edited February 6 by strance4 Quote Link to comment
strance4 Posted February 6 Author Share Posted February 6 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 Quote Link to comment
strance4 Posted February 6 Author Share Posted February 6 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. Quote Link to comment
strance4 Posted February 6 Author Share Posted February 6 Updated Diagnostics. brain-diagnostics-20240206-1044.zip Quote Link to comment
trurl Posted February 6 Share Posted February 6 SMART for disabled disks 10 and 15 look fine, and both emulated disks are mounted with their data. Check your lost+found share (created on both emulated disks) to see what repair couldn't figure out. You still have more work to do. I don't understand the purpose of your plan and can't imagine what reformatting would accomplish. Rebuild is the whole point of parity. Quote Link to comment
trurl Posted February 6 Share Posted February 6 3 minutes ago, trurl said: Check your lost+found share (created on both emulated disks) If it looks like it might be too much of a mess, it might be possible to try to get files from the physical disks, possibly after repairing their filesystem if necessary.. Don't do anything with the physical disks until you decide if emulated contents look good enough. Rebuild to spares would be another option, then you would still have the originals to see if more could be recovered from them. Quote Link to comment
trurl Posted February 6 Share Posted February 6 What do you get from command line with this? du -h -d 1 /mnt/user/lost+found and this? ls -lah /mnt/user/lost+found Quote Link to comment
strance4 Posted February 6 Author Share Posted February 6 root@Brain:~# du -h -d 1 /mnt/user/lost+found 1.8T /mnt/user/lost+found/131 1.8T /mnt/user/lost+found Quote Link to comment
trurl Posted February 6 Share Posted February 6 So there is a total of 1.8T of data in lost+found. Might be worthwhile to see how much is on each disk. What do you get with these? du -h -d 1 /mnt/disk10/lost+found du -h -d 1 /mnt/disk15/lost+found Quote Link to comment
strance4 Posted February 6 Author Share Posted February 6 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. Quote Link to comment
trurl Posted February 6 Share Posted February 6 Sorry, looks like the other disk with lost+found is disk11. You must have repaired it on some other occasion. Take a look at that one. I recommend rebuilding to spares, that way you keep the original disks just as they are, and maybe they will help recover some of the lost+found. Quote Link to comment
trurl Posted February 6 Share Posted February 6 Since disk10 has no lost+found, it should be OK to rebuild on top of that same disk. Quote Link to comment
strance4 Posted February 6 Author Share Posted February 6 Ok once i finish copying the files i will use my spares and do a parity check. Quote Link to comment
trurl Posted February 6 Share Posted February 6 1 minute ago, strance4 said: Ok once i finish copying the files i will use my spares and do a parity check. I don't know what you are thinking now. Why copy anything? If you are concerned about not having a backup of some important and irreplaceable files, then it might make sense to copy those files somewhere off the array. And you can't do a parity check with 2 disabled disks. Quote Link to comment
trurl Posted February 6 Share Posted February 6 3 minutes ago, strance4 said: use my spares and do a parity check Probably just some confusion about terminology. You must mean you will rebuild the disabled disks to your spares, not really a parity check. 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.