luksak

Thank you for your input! I'll try that and report back on my progress.

Hi there once again a drive shows up faulty. Please tell me what steps to take. Attached are the diagnostics. tower-diagnostics-20180724-1412.zip

There you go. The unmountable disk is disk 5. tower-diagnostics-20170125-0948.zip

I started the array after assigning a ne partity disk. here is the syslog: syslog.txt

I finally finished migrating all data, formatting all drives using xfs and started to update parity. Thanks for guiding me trough this! I have a new issue now. The moment I assigned the new parity drive, one of the data drives showed up as unmountable... This one is xfs. What should I do?

My current plan would be formatting the 3TB disk as a xfs drive and then copy back the data from the 4TB drive. Do I have to preclear the drive first? How can I reformat the drive using xfs? Could you give me instructions how to do this please?

oh wow this is looking good i guess: Flushing..finished Objects without names 51 Empty lost dirs removed 2 Dirs linked to /lost+found: 13 Dirs without stat data found 1 Files linked to /lost+found 38 Objects having used objectids: 5 files fixed 3 dirs fixed 2 Pass 4 - finished done 768478, 69 /sec Deleted unreachable items 8 Flushing..finished Syncing..finished ########### reiserfsck finished at Thu Dec 29 15:08:15 2016 ########### i was able to mount the drive. so switching back to my actual unraid installation and testing the array.

It failed this is the end of the output: block 180227787: The number of items (34) is incorrect, should be (1) - corrected block 180227787: The free space (388) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 180227787, item (0): Unknown item type found [285213060 99584 0x1850009 (12)] - deleted ...40%....60%....80%....100% left 0, 31535 /secec /sec/sec /sec9 /secec 334125 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 732536066 Leaves among those 790548 - leaves all contents of which could not be saved and deleted 21 Objectids found 334126 Pass 1 (will try to insert 790527 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....Not enough allocable blocks, checking bitmap...there are 1 allocable blocks, btw out of disk space Aborted

Maybe the --scan-whole-partition would help since we resized the partition?

This was the output: $ reiserfsck --check /dev/sda1 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/sda1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Wed Dec 28 03:25:52 2016 ########### Replaying journal: Done. Reiserfs journal '/dev/sda1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) Aborted Doesn't look too good...

$ resize_reiserfs /dev/sda1 resize_reiserfs 3.6.24 resize_reiserfs: run reiserfsck --check first Running reiserfsck --check /dev/sda1 now.

Ok, this time it went through without any warnings: $ parted /dev/sda resizepart 1 100% Information: You may need to update /etc/fstab. Here is the output of sfdisk /dev/sda: $ sfdisk /dev/sda Welcome to sfdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9C418D6E-79F2-4D4F-B0FF-8E2B17D3E4F7 Old situation: Device Start End Sectors Size Type /dev/sda1 64 7814037134 7814037071 3.7T Linux filesystem Type 'help' to get more information. Should I run reiserfsck again?

Ok, here is what happened: parted /dev/sda resizepart 1 100% Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra 1953504000 blocks) or continue with the current setting? parted: invalid token: 1 Fix/Ignore? F Partition number? Partition number? 1 End? [3001GB]? Information: You may need to update /etc/fstab. Was Partition number 1 right? What should I do now?

Somhow the 1 parameter isn't accepted: parted /dev/sda resizepart 1 100% Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra 1953504000 blocks) or continue with the current setting? parted: invalid token: 1 Fix/Ignore?

This is how far i got: $ wget http://mirrors.slackware.com/slackware/slackware-current/slackware/l/parted-3.2-i586-2.txz $ installpkg parted-3.2-i586-2.txz $ parted /dev/sda resizepart 1 100% bash: /usr/sbin/parted: cannot execute binary file: Exec format error What am I doing wrong?