Adrian

Members
  • Posts

    187
  • Joined

  • Last visited

1 Follower

Converted

  • Gender
    Male
  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Adrian's Achievements

Explorer

Explorer (4/14)

2

Reputation

  1. Worked perfectly, thank you again!
  2. Great, thanks again. Parity2 building now.
  3. Current system has 2 Parity and 17 disks. I want to physically re-arrange the disks and want to confirm the steps. Stop Array New Config -> Preserve Current assignments = None? Configure Parity and Disk 1 - 17 in Array Devices When do I state that Parity #1 is valid? When do I set Parity 2 so that it rebuilds only the 2nd parity? Thank you, Adrian
  4. Disregard everything I said about the folders and names being difference. I was looking in the wrong place, my fault. It's all good. Thank you trurl and everyone else for your help and guidance, I really appreciate it!
  5. The old repairs that I ran were the ones previously instructed to run. I was told that was only on the emulated disks. Recently I just put the drive in the available slot and mounted it as an unassigned drive. I used the Web UI to browse the contents.
  6. Yea that part I understood. It's just 2-3 other folders in their normal location that were not named correctly. The folders had some videos and were named with the event (concert) name, but I renamed them to include the date and city/state as the concerts are part of a tour. It's the date and city/state of the folder name that was missing.
  7. Former disk 14. Disk 15 was always unassigned, it's where I would preclear from. At some point I want to rearrange the disks so I don't have a disk id being skipped, adds to the confusion.
  8. Well this is odd, the original drive looks same. I recall the repair saying something about logs being discarded. May the folder renames were in the logs that were discarded? Any recommended tools\scripts to run to compare the drives?
  9. Rebuild completed. I quickly looked at disk 14 which is the one that had the lost+found folder and looking at some files I know I saved recently, the folders names are different. I put 3 folders with files in each and the I renamed the folder with the City\State, but I see them now with the original folder name. I recall seeing them correctly when the drive was emulated. What would I do next to get the original drive mounted so I can compare the contents? I've attached the latest diagnostics after the rebuild. mediaserver-diagnostics-20220721-1411.zip
  10. Alrighty, both drives replaced and rebuilding now. Will see what happens tomorrow.
  11. So all my bays except 1 (where Disk 15 is) are full. So would I shutdown, pull disk 1 and 14 and insert the new drives in each and rebuild both at the same time?
  12. Just 1 folder that has 3 recent files from 7/13/2022. So what's next? mediaserver-diagnostics-20220720-1214.zip
  13. I think so. Still shows disabled\emulated. But I can access them through their direct share. One of the disks has a lost+found folder which I assume is from the repair? So would I next set these aside and rebuild onto new drives and then I can compare the rebuilt drives to the repaired ones?
  14. Ran it with -L option Disk 1 Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 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... clearing needsrepair flag and regenerating metadata sb_icount 0, counted 63776 sb_ifree 0, counted 179 sb_fdblocks 1952984865, counted 929448093 - 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 = 3 - agno = 5 - agno = 6 - agno = 7 - agno = 1 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:141778) is ahead of log (1:2). Format log to cycle 4. done Disk 14 Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 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... clearing needsrepair flag and regenerating metadata sb_icount 0, counted 14784 sb_ifree 0, counted 254 sb_fdblocks 1952984865, counted 936669596 - 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 = 7 - agno = 4 - agno = 1 - agno = 3 - agno = 6 - agno = 5 - agno = 2 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 ... disconnected dir inode 11307331946, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 191 nlinks from 2 to 3 Maximum metadata LSN (1:93159) is ahead of log (1:2). Format log to cycle 4. done