smarty39

Members
  • Posts

    9
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Location
    Alberta, Canada

smarty39's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I am slowly going through my BluRay folders and converting them to MKV. One issue I am having is the LOOOONG delete times when getting rid of the BDMV and CERT folders after I am done with them. I am new to MC but I don't see anywhere in there that I can access the actual share folders that contain the movie files. I have been able to drill down do the mnt/dsk folders to find certain files but that can be very cumbersome as I have 9 disks and the movie files are sometimes spread out across multiples... Any help would be appreciated?
  2. I tried everything from the webGUI and it wouldn't work lol. I ended up doing a TelNet session and running the repair from there. It said it was able to fix a bunch of the issues but also created a lost+found folder (which was expected). Now my issue is that when I try and access the folders that were broken before (as well as the new lost+found folder) it says that they too are not accessible OR I don't have permission...what gives? I have a new disk sitting here waiting to be installed in place of the bad one. Should I do a parity check and then just replace the disk or will I risk losing more data that way? Thanks again for all the help
  3. I must be losing it because I don't see anything in the help regarding the -n option. And what do you mean by 'remove' it anyway? If there is nothing there how do you remove it?
  4. Tried --rebuild-tree --yes and --rebuild-tree -y with no change, just keeps reverting back to the previous screen. Any other ideas?
  5. I don't know why I'm having such issues with this... I typed '--rebuild-tree' and clicked 'Check'. Then typed 'Yes' and clicked 'Check'. I thought the repair would start...but now I get this screen: Usage: /sbin/reiserfsck [mode] [options] device Modes: --check consistency checking (default) --fix-fixable fix corruptions which can be fixed without --rebuild-tree --rebuild-sb super block checking and rebuilding if needed (may require --rebuild-tree afterwards) --rebuild-tree force fsck to rebuild filesystem from scratch (takes a long time) --clean-attributes clean garbage in reserved fields in StatDatas Options: -j | --journal device specify journal if relocated -B | --badblocks file file with list of all bad blocks on the fs -l | --logfile file make fsck to complain to specifed file -n | --nolog make fsck to not complain -z | --adjust-size fix file sizes to real size -q | --quiet no speed info -y | --yes no confirmations -f | --force force checking even if the file system is marked clean -V prints version and exits -a and -p some light-weight auto checks for bootup -r ignored Expert options: --no-journal-available do not open nor replay journal -S | --scan-whole-partition build tree of all blocks of the device What do I have to type to actually start the bloody repair?!?!?!
  6. Also, if I go through with the --rebuild-tree command...do I simply type that into the dialog box next to the 'Check' button and then hit 'Check' again? Or is there a different (full) string that needs to be entered?
  7. Finally got to a disk that has errors but now I don't know what to do. This is what was displayed: reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md6 Will put log info to 'stdout' ########### reiserfsck --check started at Wed Sep 30 14:21:15 2015 ########### Replaying journal: Replaying journal: Done. Reiserfs journal '/dev/md6' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..Bad nodes were found, Semantic pass skipped 1 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Wed Sep 30 15:01:22 2015 ########### block 14909443: The level of the node (56336) is not correct, (1) expected the problem in the internal node occured (14909443), whole subtree is skipped vpf-10640: The on-disk and the correct bitmaps differs. I understand that the --rebuild-tree command will likely result in lost data to some degree. Am I better off to replace the drive (assuming the Parity drive is doing it's job and ZERO data will be lost), or has this corruption destroyed the data even with a Parity drive? I don't want to run the command and risk losing data if all I have to do is swap in a new drive for that one...and not lose anything. Or am I misinterpreting that incorrectly? Thanks again for all the help, it is greatly appreciated!
  8. Thank you very much for the tip...running the check on all disks now. So far 3 of the 8 have no issues so fingers crossed. My next question is...I noticed that some of the problematic folders are 'across' multiple disks (folders on both). I assume this is completely normal but wondering if a corruption on one disk will cause the remaining contents on the other disk to fail as well? Hopefully that makes sense lol. Thanks again for the help, this forum is great!
  9. Hi there, Been running an UnRaid server for quite a while now and recently upgraded to 6.1.2 (and today to 6.1.3). I have experienced folder issues in the past but was able to fix them with the 'Permission fix' using the webGUI. I now have another issue concerning multiple movie folder where I get the following error: V:\Movies\Carlito's Way (1993) is not accessible. The handle is invalid I cannot access that shared from windows explorer (or play it's contents in Emby) BUT I can see it's contents when using the webGUI. I have run the permission fix again but to no avail. This is now happening on quite a few folders (~25 out of 400). Any ideas?