Jump to content

zOnk

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About zOnk

  • Rank
    Newbie
  1. Maybe a stupid question, but since it shows parity is valid and I have a 4TB disk that isn't in the array. Can I just replace this md10 (2TB) disk with this new 4TB?
  2. Ok...did it. Here's what I got: Check interval in days: 180 Is this ok ? (y/n)[n]: y The fs may still be unconsistent. Run reiserfsck --check. root@Tower:~# reiserfsck --check /dev/md10 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md10 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 Mon Sep 2 11:11:27 2019 ########### Replaying journal: No transactions found Zero bit found in on-disk bitmap after the last valid bit. Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) Aborted (core dumped) root@Tower:~#
  3. Ok...ran reiserfsck --rebuild-sb /dev/md10 and followed the directions in Wiki. Got all the way to the bottom, but instead of what the wiki shows, I see this: Set flags in SB: Mount count: 1 Maximum mount count: 30 Last fsck run: Mon Sep 2 10:19:35 2019 Check interval in days: 180 Is this ok ? (y/n)[n]: I got the above instead of the (y/n) prompt after Set flags in SB: Here's the whole line by line, just in case: root@Tower:~# reiserfsck --rebuild-sb /dev/md10 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 reiserfs_open: the reiserfs superblock cannot be found on /dev/md10. what the version of ReiserFS do you use[1-4] (1) 3.6.x (2) >=3.5.9 (introduced in the middle of 1999) (if you use linux 2.2, ch oose this one) (3) < 3.5.9 converted to new format (don't choose if unsure) (4) < 3.5.9 (this is very old format, don't choose if unsure) (X) exit 1 Enter block size [4096]: 4096 No journal device was specified. (If journal is not available, re-run with --no- journal-available option specified). Is journal default? (y/n)[y]: y Did you use resizer(y/n)[n]: n rebuild-sb: no uuid found, a new uuid was generated (d309e289-04e3-4cca-8a56-31f 51d62fe67) rebuild-sb: You either have a corrupted journal or have just changed the start of the partition with some partition table editor. If you are sure that the start of the partition is ok, rebuild the journal header. Do you want to rebuild the journal header? (y/n)[n]: y Reiserfs super block in block 16 on 0x90a of format 3.6 with standard journal Count of blocks on the device: 488378624 Number of bitmaps: 14905 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 0 Root block: 0 Filesystem is NOT clean Tree height: 0 Hash function used to sort names: not set Objectid map size 0, max 972 Journal parameters: Device [0x0] Magic [0x0] 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: d309e289-04e3-4cca-8a56-31f51d62fe67 LABEL: Set flags in SB: Mount count: 1 Maximum mount count: 30 Last fsck run: Mon Sep 2 10:19:35 2019 Check interval in days: 180 Is this ok ? (y/n)[n]:
  4. Ok...good news (for me) parity-sync finished without any issues/errors. Started the array in maintenance mode and ran: reiserfsck --check /dev/md10 Got this: reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md10 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes reiserfs_open: the reiserfs superblock cannot be found on /dev/md10. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. root@Tower:~# Since the Wiki recommends talking to experts first, I'm posting this and gonna wait to hear back before moving forward.
  5. Dude...no way?! For real? I honestly don't even know what hardware is in that old ass machine...I just figured it's so old there's no way it can be 64 bit. Does the motherboard matter tho? (sorry to sound so IT ignorant, but...at times, I am). At this point I'm 65% through the parity-sync and 0 errors. Fingers still crossed.
  6. Thanks for the quick replies. *I would have upgraded long ago...but not having a 64bit setup laying around has kept me where I'm at. Plus...never had any issues til now. It's on the todo list tho.
  7. Hello. After many years of zero problems, I'm finally posting due to an issue I can't seem to get myself out of. I was trying to Upgrade my parity...5TB to 6TB. The rebuild was going super slow...less than 5MB/s. I figured out it was something funky with a Sata card/cable. While trying to figure out that issue, I resorted to skipping the upgrade, going back to my original 5TB parity. I think in my haste, I somehow messed with disk10. Now, I can access my files, but cannot reassign disk10 as it only shows up as 'unformatted'. I've been running around in circles getting nowhere. I even went out and purchased a new disk hoping it was disk related and that it would rebuild. No such luck. I finally went with the 'New Config' option, but that hasn't helped either. The system is in the process of a parity-sync after the New Config. Disk10 still unformatted. There's nothing wrong with the disk, the cable, the sata card. I've troublshot all those. I'm sure I'm not giving enough info. Anyone able/willing to try to help a brother out? Thanks in advance. unraid_syslog.txt