Jump to content

youcrew

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About youcrew

  • Rank
    Newbie

Recent Profile Visitors

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

  1. youcrew

    Parity Drive Question

    Thank you guys for your replay. I knew I wasn't putting the question together well. I think I understand it doesn't work like a RAID setup. The parity unraid uses is a bit out of my comprehension. So U guess a better way to put my question is: Is there an array size limit where the parity needs the second drive? Aside from having more drives in the array means more of a chance of having one fail, simply by having more. Feel free to tell me to just shut up and just have parity drives set up ( I do)
  2. youcrew

    Parity Drive Question

    Just a quick question about parity drives. When creating an array there are slots for parity drive selection. So I can put in two 12tb drives, giving me 24tb of parity. So should I keep my array 24tb? Or am I missing an option somewhere? Sorry I had a hard time trying to explain my question when typing I hope it makes sense.
  3. youcrew

    Unmountable No File System

    @johnnie.black Thank you, sorry for not responding sooner. I just bought and move the drives from the onboard SATA to an LSI PCI card and bing bang boom. You were correct, thank you a lot for your direction.
  4. youcrew

    Unmountable No File System

    I have followed the steps found here: https://lime-technology.com/wiki/Check_Disk_Filesystems#xfs_repair Phase 1 - find and verify superblock... - block cache size set to 761168 entries sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap ino pointer to 97 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary ino pointer to 98 Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) empty log check failed zero_log: cannot find log head/tail (xlog_find_tail=5) ERROR: The log head and/or tail cannot be discovered. Attempt to mount the filesystem to replay the log or use the -L option to destroy the log and attempt a repair. Then the -L give me this and I am lost of my next step: Phase 1 - find and verify superblock... sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap ino pointer to 97 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary ino pointer to 98 Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) empty log check failed zero_log: cannot find log head/tail (xlog_find_tail=5)