leeknight1981

Cheers john i am on a flight back home in 4 weeks so no more Tough-book and Satphone frantically trying to sort it,

OK Disk is Now mounted is this because never repaired ? I have attached logs 😊 r720xd-diagnostics-20210418-2040.zip

XD 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... Metadata CRC error detected at 0x43cfad, xfs_bnobt block 0x80002038/0x1000 btree block 1/1032 is suspect, error -74 bad magic # 0x3d1cede3 in btbno block 1/1032 Metadata CRC error detected at 0x43cfad, xfs_bnobt block 0x800026b8/0x1000 btree block 1/1240 is suspect, error -74 bad magic # 0x241a9c92 in btbno block 1/1240 Metadata CRC error detected at 0x43cfad, xfs_cntbt block 0x28c0bf890/0x1000 btree block 5/25263895 is suspect, error -74 bad magic # 0x241a9c92 in btcnt block 5/25263895 agf_freeblks 219408396, counted 219359283 in ag 5 agf_btreeblks 67, counted 66 in ag 5 agi unlinked bucket 8 is 1608 in ag 5 (inode=10737419848) agf_btreeblks 87, counted 85 in ag 1 sb_ifree 3509, counted 3576 sb_fdblocks 2402598327, counted 2427541432 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 Metadata CRC error detected at 0x44d87d, xfs_bmbt block 0x80002030/0x1000 - agno = 1 Metadata CRC error detected at 0x44d87d, xfs_bmbt block 0x80002030/0x1000 btree block 1/1031 is suspect, error -74 bad magic # 0x241a9c92 in inode 2147492304 (data fork) bmbt block 268436487 bad data fork in inode 2147492304 cleared inode 2147492304 - 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 = 1 - agno = 4 - agno = 8 - agno = 2 - agno = 3 - agno = 6 - agno = 7 - agno = 10 - agno = 9 - agno = 5 entry "2147492304" at block 0 offset 752 in directory inode 296 references free inode 2147492304 clearing inode number in entry at offset 752... Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... bad hash table for directory inode 296 (no data entry): rebuilding rebuilding directory inode 296 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 10737419848, moving to lost+found Phase 7 - verify and correct link counts... Metadata corruption detected at 0x44d778, xfs_bmbt block 0x80002030/0x1000 libxfs_bwrite: write verifier failed on xfs_bmbt bno 0x80002030/0x1000 Maximum metadata LSN (1984442616:371148) is ahead of log (1:2). Format log to cycle 1984442619. xfs_repair: Releasing dirty buffer to free list! xfs_repair: Refusing to write a corrupt buffer to the data device! xfs_repair: Lost a write to the data device! fatal error -- File system metadata writeout failed, err=117. Re-run xfs_repair. NO Flag 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 - 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 = 1 - agno = 3 - agno = 10 - agno = 4 - agno = 2 - agno = 5 - agno = 7 - agno = 6 - agno = 9 - agno = 8 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

No i havent didn’t realise i needed too, Do i start the Array in Maintance mode and do it i have no idea anymore its just messing with my brain too much! i just need a working stable server its been fine past 8 years now one thing after another.

So the iffy disk 7 was an 8TB it has been replaced with a 12TB WD, Parity / Data rebuild took 24 ish hours with 0 errors! when i click the folder it says "No listing: Too many files" also in MC cannot read directory contents. some of my shares keep dissapering but re apppear after a re start isos and system 2 off hand. is there anyway to get help with all this cos its doing my nut in and im going to smash the lot. my Deluge now says error where they was downloading fine there is some really weird shit going on and i cant get to the bottom of it from here Cheers Lee

Cheers John! Many thanks i have ordered a 12TB WD to Replace the 8TB as i am slowly replacing the Seagates with WD! that 8TB is the newest of the seagates i have 3 x 4TB Seagates left in there that are like 5 years old so they was going to be swapped out anyway but in oldest date order, See how i get on after Replacing the Disk

Just as an update Disk 7 has now got the Red X and says emulated, logs 22:28 before i shut down and 22:42 on reboot shall i order a 12TB to replace it with? or will the corrupted move onto a New Drive Regards Lee r720xd-diagnostics-20210414-2242.zip r720xd-diagnostics-20210414-2227.zip

I had to restore app data for emby, Im using deluge to re get the lost data. With that deluge is rigting to the array disk 1 & 7 i think and then both parity disks, So i am going to try figure out the best setting for deluge IE move the folders to the cache pool only not the array so it downloads to cache and then when i used filebot to rename i can move them from the cache to the media folder which is along the lines of /mnt/R720XD/Array Share/Plex/Tv Shows (Sourced). Not sure if thats the correct way or not i was concerned about all the extra Read/Writes on the aray and or parity's as i have almost 8TB of stuff to re download. So do i leave deluge set to mnt/user/deluge and cache Yes or do i move it to say mnt/cache/deluge and onec downloded move it to Tv Shows (Sourced) folder using krusader Cheers Lee

Will pay in Gold

Yup this is prior to shutdown r720xd-diagnostics-20210413-1304.zip

r720xd-diagnostics-20210413-1315.zip

Yes this is the Disk i formatted i tried the suggested software but all the video files were like FML99877667 FHG9877676 00021547 so i would never know what they was so i took the loss and got a list of missing data. Stuck the drive back in and the data rebuild completed without error. Iv since downloaded some of the losat data still lots to go. But today the drive did the same thing - Unmountable Disk! The Disks are in a Dell R720XD secured in Drive Trays and the Server is in a cupboard at home 8k miles away and never touched. So im wonderinging why that Disk for a second time has gone to unmountable when the server is not touched. I did as you said "ran the file system repair with the default -n" and restarted the array and it was ok again Disk was mounted fine. Then i did what you advised "try again without the "-n"" psted the result and restarted the array. So id guess im looking to see why its done it again! So checked smart report downloded and posted logs etc, No reason for say the backpaine to randomly start playing up i guess. I think i seen somewhere a recent issue with unraid 6.9.1 and seagate disks but i may be wrong. I Guess im just looking to identify why im having such issues when the server is not touched as we have 3 UnRaid servers and dont ever have any issues. This R720XD is my Emby Server and has a lot of media on thats taken me many many years to Rip and Encode my discs plus the downloads. If it was say the Disk that was at fault id get the wife to swap it out. Im no UnRaid expert so i look here for help being Deployed in Afghanistan the internet here's not the best and i have to use Remote Desktop to an imac to get onto the R720XD to get diagnostics - logs etc So it can be frustrating and the thought of loosing that amount of data / years work is devistating and when home i will setup a backup machine elsewhere to replicate anything i add / remove Cheers Lee

ok Done 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 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 4 - agno = 7 - agno = 6 - agno = 3 - 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... done Does that Help, i cant see anythign in the smart report for the disk to say swap it out! or its on its way out I Dont understand all the logs tbh but would be helpful to understand why the disk 7 goes to unmountable TIA Lee

Hiya So today i had the Same issue with that disk, iv added the smart report, logs before i shut it down logs after i shut it down and the repair status report it spat out. Re started the array and Boom disk 7 is back, Any ideas as to whats going on? and iv upgarded to 6.9.2 Thanks Again Lee Disk 7 xfs_repair status-.rtf r720xd-smart-20210413-1330.zip r720xd-diagnostics-20210413-1315.zip r720xd-diagnostics-20210413-1304.zip

Hiya is this something to be massively concerned about if so what do i need to do? Regards Lee The following files : folders may not be accessible to the users allowed via each Share's SMB settings.rtf

Im Not trying to argue i am telling you What UnRaid Told me to Do, It told me that the disk needed to be formatted so i did, it said start and rebuild So i did. Yes it warned me about formatting My bad for thinking i could loose a disk and re build and preserve.

I did that i tried repair file system in the disk 7 dropdown. Sorry i am just so Pissed off iv lost that data i cant run two 64TB servers its not cost effective i was under the dilution if a disk failed id be kinda protected against data loss Obviously not as i have lost 8TB of Media and don't even know whats missing. SO is that it my Valid Parity is now missing the failed 8TB Gone Forever. Sorry i cant even think straight let alone express what i mean properly all these years of using unraid never lost a disk and never lost data not once

To add a new disk to the existing array, it would need to be formatted. But you were not adding it. You were replacing a failed disk. If you add a disk the total number increases. If you replace a disk the total number remains the same. It's a completely different process - like adding a second disk to your PC would be different from replacing one that had failed. OK i put the formated drive in and it said ReBuild so thats what i did, Unraid also said Unmountable disk present so i clicked on it and it Said it had to be formatted so thats what i did. So if UnRaid see's an 8TB formatted disk and asks to rebuild why has the data that was on the failed disk not gone back. Why did unraid tell me that the disk had to be formated if thats Not what had to be done? I may have been naive here but i just assumed as i have dual parity it would Not loose any data.

Sorry i don't mean to be frustrated here But I Understand what formatting A disk does, But isn't some of the point to UnRaid that you can loose a disk without loosing data? i also have dual parity so if that 8TB totally died DEAD DEAD and i had to put a new drive in it should re build with NO Data loss! Unraid said the Drive Had to be formatted to be added to the array, Unmountable disk so i clicked on it and it said it had to be formatted! Yes i got a warning but i assumed i was Parity Protected so whats the difference in the disk just completely failing and me formatting it? Surely with Dual Parity and Parity Being VALID i shouldn't loose data Regards Lee

Hiya had a weird issue the other day Disk 7 smart health (198) offline uncorrectable 8, then later that day returned nor Normal as telegram says. Then i got Disk 7 Unmountable disk present after a reboot, took the drive out checked it reseated booted back up and did the same Disk 7 Unmountable disk present. So i ran the Check Filesystem Status checked the smart report etc so i stopped the array again rebooted same Disk 7 Unmountable disk present and it said i had to format the drive which i did and started a re build. i appear to have LOST everything on that disk 7.85TB worth of Emby media i have dual Parity 2 x 12TB WD Disk's so why have i lost so much data? I was under the assumption i wont loose data if a disk dies and i re build as parity was Valid and i have dual parity. Have i missed something here? the share is set as High-water and i have 2 x 1TB SSD's as cache-pool for app data. can someone please explain to a thick person Why iv lost all that media buy loosing a disk TIA Lee

Hiya had a weird issue the other day Disk 7 smart health (198) offline uncorrectable 8, then later that day returned nor Normal as telegram says. Then i got Disk 7 Unmountable disk present after a reboot, took the drive out checked it reseated booted back up and did the same Disk 7 Unmountable disk present. So i ran the Check Filesystem Status checked the smart report etc so i stopped the array again rebooted same Disk 7 Unmountable disk present and it said i had to format the drive which i did and started a re build. i appear to have LOST everything on that disk 7.85TB worth of Emby media i have dual Parity 2 x 12TB WD Disk's so why have i lost so much data? I was under the assumption i wont loose data if a disk dies and i re build as parity was Valid and i have dual parity. Have i missed something here? the share is set as High-water and i have 2 x 1TB SSD's as cache-pool for app data. can someone please explain to a thick person Why iv lost all that media buy loosing a disk TIA Lee

Ok thats returned 0 sync errors So is the way forward if i run it every 3 months and it shows sync errors Do i simply run it again error correcting with no reboot? Was there actual errors and now showing 0 as its corrected then or did it think they was errors and is now happy there isn't. Many Thanks for your help with this i just do not Get the time to sort stuff out research stuff i am always working and rarely at home with the server and when i am at home its family time XD r720xd-diagnostics-20210320-0854.zip

Sorry didn’t mean to be short with you there’s years of my life on there like 10 years and currently it’s my only copy due to COVID. Where or what am I looking for in the logs? I’d like to be able to understand instead of trying to sort it during work and hectic life. I started another at 1950 so I guess have to wait another 24 ish hours and prey a drive doesn’t fail but hey ho of it fails I’ll swap it with a 12 cheers

i am just concerned about running so many parity scans in a week iv done 4 already is it safe? seems a lot of stress on the drives, ok ill start another scan now

Iv ran 4 in the past week there all above each giving a different amount of errors with re booting without re booting. So not really sure what to do next!