Jump to content

gavin_UK

Members
  • Content Count

    75
  • Joined

  • Last visited

Community Reputation

0 Neutral

About gavin_UK

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Hi guys and girls can I get some basic advice a friend of mine is looking to build a basic Unraid Server he mainly wants it for Plex and a Nass storage he’s also going to be adding a P2000 video card to handle any transcode and in codes for friends and family apart from that I know hes not really looking to use it with VM’s or loads of apps and I think he’s looking at the ballpark figure of about £600 that’s with the GPU I kind of feel a bit out of the game regarding hardware intell or AMD as my personal unraid server is an old X58 that suits me fine any recommendations welcome
  2. The thing I like most is the community to help me learn this great OS I would like to see Multiple array’s
  3. thanks for all your help i just have to now go step by step and hope for the best if you guys dont mind me reporting back at each stage lol
  4. so what would be the best way after ive done a parity rebuild onto the 1st parity disk should i then replace my disk 1 and rebuild that and as for disk 7 should i Stop the array unassign the drive start the array to commit the current assignments (and ‘forget’ the drive just unassigned) Stop the array assign the drive start the array to rebuild the drive can i just say thank you guys for all your help with this im just panicking about losing my data as i was in the process of upload my most important files to the cloud
  5. i know that sorry if that sounds like im being sarcastic i was just asking what would be the best order to do things in
  6. wouldn't it just be replaced from a parity sync ?
  7. ok its doing a parity sync on to the 1st parity dive only 26 hours togo disk 7 was able to stay as it was would you say after that i should replace my disk one with the new RMA'ed one and the do a parity sync to just that or format disk 7 and replace disk one and do both at the same time
  8. This is what im worried about when i get the replacement disk for disk 1 and go to start the array its going to say do a parity sync to copy data back over to the new disk would it also force Disk 7 (discarding all data currently on those disks) to format as thats what i keep getting on the Array Operation panel ive only got one parity drive working with a 2nd faild hdd being emulated with a 3rd hdd Unmountable: Unsupported partition layout it dont say it's disabled or being emulated does that just mean the files are not being seen
  9. disk one is being emulated i guess from the 2nd parity disk the drive was dead its been taking out sent back for a RMA which i should be getting today should i replace this before i try To re-enable the 1st parity disk (Using the same disk) do the following: Stop the array unassign the drive start the array to commit the current assignments (and ‘forget’ the drive just unassigned) Stop the array assign the drive start the array to rebuild the drive (either parity or data as appropriate).
  10. the model of the drive which is a RMAed is to replace disk 1 which is a 6TB WD Red pro ive done the Rerun without the -n this is the log 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 - agno = 11 - agno = 12 - agno = 13 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 4 - agno = 6 - agno = 1 - agno = 3 - agno = 5 - agno = 7 - agno = 8 - agno = 9 - agno = 2 - agno = 10 - agno = 11 - agno = 12 - agno = 13 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 done a restart of the array and disk 7 is Unmountable: Unsupported partition layout also as i have 2 parity drives ok parity 1 is disabled for some reason im sure that was from crc errors parity2 i hope is standing in for disk 1 which im waiting for my RMA today at some point what is the best thing to day about disk 7 ? as it looks like ive only got 1 parity drive running
  11. thanks for your reply this is the log 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 (but don't 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 - 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 = 4 - agno = 3 - agno = 5 - agno = 9 - agno = 6 - agno = 8 - agno = 7 - agno = 11 - agno = 10 - agno = 12 - agno = 13 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.
  12. sorry i gave you the wrong diagnostic i had the hdd out of the bay this is the correct oneabyss-diagnostics-20190916-2339.zip
  13. abyss-diagnostics-20190916-2308.zip thanks