December 28, 20169 yr Community Expert Try running with --rebuild-tree, the partition was expanded to 4tb, just down know if reiserfsck can use it without resizing first.
December 28, 20169 yr Author Maybe the --scan-whole-partition would help since we resized the partition?
December 29, 20169 yr Author 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
December 29, 20169 yr Community Expert You're in a catch 22 situation, resize_reiserfs doesn't work because the filesystem is not clean, reiserfsck doesn't work because there's not enough space. Assuming you still have the original disk, this is the cloned one, and as a last ditch attempt you can rebuild the superblock, it can or not detect the extended partition, so type: reiserfsck --rebuild-sb /dev/sda1 Follow this guide exactly for the answers to the questions it's going to ask, any doubts or any question not on the guide ask: https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Rebuilding_the_superblock When done run with --rebuild-tree again.
December 29, 20169 yr Community Expert Just to add that I tried the superblock rebuild on my test server and it worked, it correctly detected the expanded partition and expanded the filesystem. Of course I'm doing this on an undamaged filesystem, but I'm hopeful that it will also work for you. root@Tower8:~# reiserfsck --rebuild-sb /dev/sde1 reiserfsck 3.6.24 Will check superblock and rebuild it if needed Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Did you use resizer(y/n)[n]: rebuild-sb: wrong block count occured (61049638), fixed (78142784) rebuild-sb: wrong bitmap number occured (1864), fixed (2385) Reiserfs super block in block 16 on 0x841 of format 3.6 with standard journal Count of blocks on the device: 78142784 Number of bitmaps: 2385 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 60883756 Root block: 32770 Filesystem is clean Tree height: 3 Hash function used to sort names: "r5" Objectid map size 2, max 972 Journal parameters: Device [0x0] Magic [0x6ee6ce07] Size 8193 blocks (including 1 for journal header) (first block 18) Max transaction length 1024 blocks Max batch size 900 blocks Max commit age 30 Blocks reserved by journal: 0 Fs state field: 0x1: some corruptions exist. sb_version: 2 inode generation number: 0 UUID: d9ed83d3-4481-4708-be9e-657f165e6dfc LABEL: Set flags in SB: ATTRIBUTES CLEAN Mount count: 16 Maximum mount count: 30 Last fsck run: Tue Dec 27 14:50:50 2016 Check interval in days: 180 Is this ok ? (y/n)[n]: y The fs may still be unconsistent. Run reiserfsck --check.
December 30, 20169 yr Author 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.
December 30, 20169 yr Community Expert Parity won't be valid with that disk, is the original 3TB disk still on the array?
December 30, 20169 yr Author 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?
December 30, 20169 yr Community Expert Click on the 3TB disk and change filesystem type to XFS, on array start you'll have the option to format it, after that mount the 4TB disk with unassigned devices plugin and copy everything to the array.
January 24, 20179 yr Author 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?
January 25, 20179 yr Author I started the array after assigning a ne partity disk. here is the syslog: syslog.txt
January 25, 20179 yr Community Expert Post the complete diagnostics, not just the syslog: Tools -> Diagnostics From the syslog you're board is using IDE legacy mode, go into the bios and change sata controller to AHC. Also disk5 needs a new sata cable: ata2.00: ATA-8: SAMSUNG HD204UI, S2H7J1AB118856, 1AQ10001, max UDMA/133
January 25, 20179 yr Author There you go. The unmountable disk is disk 5. tower-diagnostics-20170125-0948.zip
January 25, 20179 yr Community Expert Replace disk5 SATA cable and boot up, if there are still issues post new diags.
Archived
This topic is now archived and is closed to further replies.