j.metts

Members
  • Posts

    101
  • Joined

  • Last visited

Everything posted by j.metts

  1. 15 day trial, but I have found them to be very easy to work with. While trying to get it to work, you should be able to ask for it to be extended.
  2. Not sure if it matters, but my version of python is 2.6.5.
  3. So far so good. Everything downloaded from Google Drive just fine (all 20GB). I moved and created more folders, added some more files, etc, to test things out and all changes made there way to the server. I've never made one of the new plugins. I did a plugin/package installer for unmenu many years ago, but that was a different thing. I'll look into what I would need to do to make it happen, but if anyone is jumping in to read this thread....feel free to take a stab at it before I'll be able to get around to it. For the time being I have my go script creating a folder at /root/.config/ , sym-linking the original Insync folder from what I mentioned before to /root/.config/Insync, cd'ing to my insync_portable folder, then starting the app.
  4. So I was looking for trying to get Google Drive working on my unRAID server and running across this thread made me feel like it would be too much of a hassle, but digging further I found a very quick and easy way with insync rather than grive. I'm still under their 15 day trial right now to see if this will really work out long term before plopping down the $15 for it. Here's what I did. - Download the portable version from https://www.insynchq.com/linux - Put the decompressed folder on a cache or user drive - cd to the folder and run ./insync-portable start This will provide you a link that you need to authorize Google Drive to work with insync. Once authorized, it will provide you a very long key. With the long key, I got everything up and running, verified, then quit the app to generate the config directory under my home folder. ./insync-portable add_account <long key> /path/to/google/drive - ./insync-portable get_status - ./insync-portable quit Without a path to where you want your Google Drive, it will default to a folder with your email address as the name in your home directory. So, set a path somewhere on your array. Once this has been done, a folder in your home folder at ~/.config/Insync will have been created. After quitting the app, I moved the 'Insync' config directory to a user drive (I don't have a cache drive), and created a symlink of the directory from its new location to the old and started the app back up. ./insync-portable start Run './insync-portable help' to see all the commands. It does support selective sync and other things, but I haven't played with any of the settings just yet. It's currently downloading all 20GB of stuff I have up on Google Drive, so I'll report back here on the progress and how well it is working. One thing to note. The app wants to be run from it's working directory even when you start the app with the full path to the executable since the executable simply cd's into the client directory to run all the commands.
  5. I've never really had any issues with RAM. I normally go with RAM that has good reviews, etc, but this board has now gotten the best of me. At this point, I'm about to call the board defective. It's been in a box, never removed from it's anti-static bag for a couple years now. As a quick sanity check on if I've done everything possible, here's the breakdown of everything I've tried and checked. - 3 different types of RAM: 8GB Kit (Kingston HyperX Blu DDR3 1333, not on Supermicro's list), 4GB kit (Microcenter DDR3 1333, which is A-DATA RAM, not on Supermicro's list), and another 4GB Kit (Crucial DDR3 1333 which IS on Supermicro's list). I have tested every configuration I can think of...both sticks in, only one stick in, testing with both RAM slots, etc. - Known good CPU pulled from another build. Intel e6600 Core 2 Duo (on the mobo's list of supported CPU's). I checked for any bent pins on the board and all is good. I tested with the heat sink on and CPU fan plugged in, then tested very quickly with the heat sink off and finger on the CPU to confirm I could feel heat and the CPU was receiving power. The heat sink has been reseated with fresh thermal paste 3-4 times. - 2 known good PSU's. One that is currently powering my unRAID box, and another that is currently powering my HTPC. Initially before I realized there was a problem, all drives and cards were hooked up to the board. During the troubleshooting, nothing was attached to the board except for the power supply and CPU heat sink fan. Is there anything else I'm missing?
  6. Hit my first problem last night with this board. Tried 2 types of RAM, one 8GB kit (Kingston HyperX Blu DDR3 1333) and one 4GB kit (Microcenter DDR3 1333, which is A-DATA RAM). Got constant beeping from the mobo. After some research there seems to be a bit of confusion whether this is a RAM issue or an overheating trigger issue. After a good bit of trial and error testing, I've decided it may be a RAM issue as I have also read this board is very finicky with RAM. So, my next step is to grab some RAM that is on Supermicro's official list (I can pick up some of the Crucial 4GB DDR3-1333 RAM Kit pretty easily) and give it a go. Decided not to even bother tracking down an 8GB kit that will work at this point since I can't find any official word about this board accepting >4GB aside from what is printed on the box. Everything online simply says 4GB max. I'll save big RAM for when I completely rebuild this server for much more powerful tasks when I ditch LGA 775.
  7. Since they appear to simply be 5 in 3 cages, I don't see why the hot swaps wouldn't work in their place. The hot swap bay fans will be awfully close to the middle fans, so I'm not sure how that portion would work since the drives currently have a push-pull fan setup, and this would make it into a pull-pull (??) setup?
  8. My case arrived yesterday, so I had "fun" putting everything together last night. My attempt to use the C2SEE mobo I've had in my closet for a few years was a no-go due to some finicky RAM issues (I think/hope that's the problem). That was the "fun" part. Assembling everything only to realize your RAM is not going to work, then disassembling everything to re-assemble the previous rig. Now to get some RAM on Supermicro's approved list (which is what I should have done to begin with). Initial impressions: Cable management was kind of a pain with all of the fan's molex cables. Routing cables under the middle fans and using the bar at the top for routing with zip ties wasn't too bad, but soooooo many molex connectors with curled up wires! Seriously, 8 fans = 8 annoying curly wires + 16 molex connectors (male/female). Combine this with the fact that my PSU isn't modular made for some painful moments. Also, the space between the middle fans and back of the drives is not for bigger hands. With a few cuts and scrapes, I warn others to be a bit more careful than I was. This thing is big! This is my first rack mountable server case, so those that have/do use them, this is probably no surprise. Big case = lots of space = good. Hard drive cages weren't as difficult to deal with as I have read. 2 screws holding each cage in, and they pop right out. Some people made it seem like they had to put some force behind it to get them in and out. Maybe I'm the lucky one? Over time I'll probably replace them with Norco SS-500 cages, but since I didn't have much issue with them I am in no rush at all. If I do eventually replace them with the SS-500's, I realize at that point I could have bought a Norco RPC-4220, but the price of admission to the 4U world was $70 and who knows how long I'll take to turn these into hot swap bays. May just wait for the right deals to come along and piece it together in time. This thing is quiet! I've read reports of both quiet and loud. I'm not sure where the loud reports are coming from because this thing is much quieter than my previous setup with double the amount of fans, as well as my gaming tower (of course, that doesn't say much since it sounds like a jet). With 6 120mm & 2 80mm fans, I had expectations of it being loud. Luckily, this is NOT the case. Not a fan of the power/reset buttons, but how often are they used anyway? With that said, I think the plastic portion over my power button may not be as intended. The reset button is slightly convex whereas the power button is slightly concave. Maybe this is intentional? Again, not a big deal. All black! I'm not a fan of the bare metal that the Norco's and others have, and yes I understand they are meant to be in racks where this isn't seen, but for me, this case sits on a nice "ledge" in a closet, not in a rack. So I like the fact that it looks like a normal case. I read some reports of it coming with rubber feet. Mine doesn't have them, but I plan on putting some kind of rubber feet on it anyway. Cooling. This doesn't say much since my previous case had absolutely terrible cooling (killed 2 WD Black drives with heat until I pulled it out of the closet in a more open space for over a year before buying this). Put this back in the same closet, closed the door, and monitored temps last night. Easily 10C less for each drive, and this is in a smallish closet whereas the hard drive killer was out in the open! Insane I know, but again....previous case sucked!! The real test will be next summer. During this time of year those drives will stay nice and cool in the mid to low 20's spiking to around 27-28. A good test will be a parity check, so I'll plan that over the next week or 2. For my 7 drive system, this will offer some great expansion for me in the future until I have the need for 16+ drives.
  9. I had a feeling it would, just wanted to check with others that may have the board. Figured for ~$25 more I could get 8GB instead of 4, so might as well. Thanks!
  10. I recently decided to grab a spare C2SEE mobo I've had for a few years now from the closet since I am about to rebuild my unRAID box with a new case I just purchased, but now I need to get some RAM. Figured I would max it out, but now I'm confused. According to newegg and specs on the supermicro website, the board maxes out at 4GB (with C2SEA maxing out at 8GB), but the box says the C2SEE maxes out at 8GB (and the C2SEA is 16GB). I know that sometimes boards reference maxes for the modules that exist at the time the board is released, and maybe firmware upgrades can increase maxes, but can anyone tell me 100% what the max for this board is? See attached for a pic of the box I took.
  11. *** Price changed from $69.99 w/ FS to $99.00 w/o FS. Although not as good a deal, it's still not bad. *** I didn't see this listed anywhere here and not sure how long it has been, or will be, at this price, so I figured I'd post it. I've been putting off replacing a piece of junk case that has been housing my unRAID server for way too long and started looking into some towers with top to bottom 5.25 bays, then looked into some of the Norco hot swappable cases people use and love. Perusing newegg, I came across this case, and saw others here that use it. I don't need hot swap and for this price, I couldn't pass it up. Beats all other options for me right now. My system only has 6 HDD's for now, so this offers good expansion before I jump into the 16+ market. 15 Internal HDD Bays 8 x included Cooling Fans http://www.newegg.com/Product/Product.aspx?Item=N82E16811147164
  12. Thanks. I ran through all of my top level directories on all of my drives and found that several had the extended attributes set on the directories. I ran Tom's script and cleared them all up (just triple checked to make sure) and I'm still getting the kernel panic trying to enable AFP or creating a directory on the top level of this particular drive.
  13. I have narrowed it down to a single disk. It's odd, but the panic occurs whenever a new directory is made on the top level. I can make folders and copy files to all other levels of the drive. Both the smart report and reiserfsck --check both came out fine for this disk.
  14. I guess I wasn't thinking of the new webgui as being an add-on. Also, I don't recall installing dmidecode. Was this installed along with the new webgui? Either way, I started from scratch. I backed up my flash drive. Oddly, when I did, it wouldn't let me copy over one of the share config files due to corruption. Well, I formatted the flash drive, did a fresh install, but this time left off the share configs and reconfigured everything. Everything came up fine, but I am still having a panic when I interact with certain shares...the 2 shares that use all of the installed drives. Earlier, I mentioned that it paniced when I tried to move files directly from 1 disk to another. Again, the smart reports are fine with these 2 drives and the "reiserfsck --check" for both drives were fine too. Attached is the most recent syslog up until crash. panic3.txt
  15. Still can't figure out what is going on, but I'm starting to think a filesystem issue or something. This is only happening on a few shares and any new shares I try and create that involve all disks. I can modify and do whatever I want to certain shares that are limited to a single disk or 2. I figured this out when I tried to copy some files to a certain share. The copy itself caused a kernel panic. I then tried to mv via telnet some files from one disk to another and got a kernel panic. I ran smart tests on the disks and everything checks out. I'm currently running reiserfsck --check on them as well. See the link below for a couple of pics I took of 2 of the panics. One was caused by enabling AFP on a share that includes all disks. The other is when I tried to move files from one disk to another. I suspect filesystem issues with one of these 2 disks. Thoughts?? http://www.flickr.com/photos/icedtrip/sets/72157636526537334/
  16. I booted in safe mode and am still getting a panic. Attached is the log from this time. Again, turning on AFP for a user share and hitting apply. panic2.txt
  17. I don't have any addons installed at the moment. Also, safe mode? I didn't know unraid had a safe mode.
  18. Finally got around to testing things out. It seems to kernel panic with a couple of things. Creating a new share is one and panics when it tries to create the directory at /mnt/user. It also panics when I try and change the settings on a share. Attached is a log from boot to crash. The cause of the crash was enabling AFP for a share. panic.txt
  19. I upgraded my 4.7 server to 5.0 last week. I didn't do any of the beta since I felt I couldn't afford to lose anything on my main server. The upgrade went smooth. Everything came up in the right place and I have been running fine since the upgrade until I tried to add a new user share last night. When I went to add a new share, the server crashed with a kernel panic. I forced a reboot, everything came back online just fine and thinking it may have been a fluke, I tried adding a new share again. Same thing, kernel panic. I never had any issues with 4.7. I was able to add and modify my shares to my hearts content. I know I have nothing to provide to get help just yet, so my first question is, how can I get a log to see what may be happening? Since the syslog doesn't' persist after a reboot, and I can't access the server after the kernel panic, what should I do? My build: Intel BOXDG43NB Intel G43 ATX Intel Pentium Dual-Core E6500 Wolfdale 2.93GHz CORSAIR CMPSU-400CX 400W 4GB RAM
  20. Is RC-5 the first time you have tried accessing the server from a Mac? Were you ever running 4.7 or another version that didn't cause the problem? I'm still running 4.7 for unRAID and Mac OS 10.6.8 on 4 different systems without any problems (SMB, NFS, but no AFP). I haven't attempted anything with the 5.0-x releases yet.
  21. Wow! What a learning experience. Time to close this one out. Got home and ran a file system check, and sure enough, it requested that I run a --rebuild-tree. I did this, but about halfway in, started getting a good bit of read errors. I suspected a cable problem, not a problem with the drive, but rebuilding the tree was getting to a failing point, so I stopped it knowing that this could be a devastating decision. After re-seating cables, etc, I proceeded to pre-clear the replacement drive for good measure, and for extra good measure, I pre-cleared it again. I then added the drive into the disk5 spot, reset the config, invalidated slot 5, and started the rebuild....again. Once the rebuild started, I noticed the drive was shown as "unformatted" and I had a message in the syslog concerning not being able to mount the drive due to a bad superblock (I figured this was due to me terminating the rebuild-tree command). Regardless, the rebuild of the drive was successful, so I knew it was time to tackle the file system issues. A 'reiserfsck --check' produced a 'Bad root block 0' message: root@Tower:~# reiserfsck --check /dev/md5 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md5 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 Sun Aug 26 12:44:17 2012 ########### Replaying journal: Done. Reiserfs journal '/dev/md5' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) Aborted Combining this with the message in the syslog about the bad superblock, I figured I needed to rebuild the superblock, then scan and rebuild the tree. Here is the result: root@Tower:~# reiserfsck --rebuild-sb /dev/md5 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* 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]: n rebuild-sb: wrong block count occured (488378638), fixed (488378624) rebuild-sb: wrong free block count occured (488378638), zeroed rebuild-sb: wrong tree height occured (65535), zeroed Reiserfs super block in block 16 on 0x905 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 clean Tree height: 0 Hash function used to sort names: "r5" Objectid map size 8, max 972 Journal parameters: Device [0x0] Magic [0x6806df07] 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: 0x3: FATAL corruptions exist. some corruptions exist. sb_version: 2 inode generation number: 141383 UUID: 3915e40c-fac1-493c-873c-745110598104 LABEL: Set flags in SB: ATTRIBUTES CLEAN Mount count: 27 Maximum mount count: 30 Last fsck run: Mon Dec 19 18:36:29 2011 Check interval in days: 180 Is this ok ? (y/n)[n]: y The fs may still be unconsistent. Run reiserfsck --check. The suggested --check still produced the 'Bad root block 0' error, so at this point, it was time to rebuild the tree and not wanting to leave anything in question, went with a --scan-whole-partition as well (I think this is primarily for recovering deleted data, but at this point, figured anything would be good to get out of this). root@Tower:~# reiserfsck --scan-whole-partition --rebuild-tree /dev/md5 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** Do not run the program with --rebuild-tree unless ** ** something is broken and MAKE A BACKUP before using it. ** ** If you have bad sectors on a drive it is usually a bad ** ** idea to continue using it. Then you probably should get ** ** a working hard drive, copy the file system from the bad ** ** drive to the good one -- dd_rescue is a good tool for ** ** that -- and only then run this program. ** ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will rebuild the filesystem (/dev/md5) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Replaying journal: Done. Reiserfs journal '/dev/md5' in blocks [18..8211]: 0 transactions replayed Zero bit found in on-disk bitmap after the last valid bit. Fixed. ########### reiserfsck --rebuild-tree started at Sun Aug 26 13:32:35 2012 ########### Pass 0: ####### Pass 0 ####### The whole partition (488378624 blocks) is to be scanned Skipping 23115 blocks (super block, journal, bitmaps) 488355509 blocks will be read 0%..block 68291055: The number of items (65047) is incorrect, should be (1) - corrected block 68291055: The free space (58943) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 68291055, item (0): Unknown item type found [2147421952 4043308799 0xfffff0108000000 (13)] - deleted block 124369524: The number of items (29440) is incorrect, should be (1) - corrected block 124369524: The free space (63743) is incorrect, should be (976) - corrected pass0: vpf-10110: block 124369524, item (0): Unknown item type found [1828717057 201389567 0x2000701bd00feff (5)] - deleted block 133173034: The number of items (645) is incorrect, should be (1) - corrected block 133173034: The free space (264) is incorrect, should be (3537) - corrected pass0: vpf-10110: block 133173034, item (0): Unknown item type found [151060991 50496768 0x8c000101 (15)] - deleted block 361671850: The number of items (1) is incorrect, should be (0) - corrected block 361671850: The free space (2) is incorrect, should be (4072) - corrected block 362288797: The number of items (5) is incorrect, should be (0) - corrected block 362288797: The free space (4) is incorrect, should be (4072) - corrected block 363026220: The number of items (1) is incorrect, should be (0) - corrected block 363026220: The free space (2) is incorrect, should be (4072) - corrected block 364672792: The number of items (11) is incorrect, should be (0) - corrected block 364672792: The free space (65247) is incorrect, should be (4072) - corrected block 366030089: The number of items (2) is incorrect, should be (0) - corrected block 366030089: The free space (1) is incorrect, should be (4072) - corrected left 0, 28080 /sec 8856 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 488355509 Leaves among those 483564 - corrected leaves 1 - leaves all contents of which could not be saved and deleted 9 pointers in indirect items to wrong area 14 (zeroed) Objectids found 8866 Pass 1 (will try to insert 483555 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 73 /sec Flushing..finished 483555 leaves read 478273 inserted 5282 not inserted non-unique pointers in indirect items (zeroed) 2531 ####### Pass 2 ####### Pass 2: 0%....20%....40%....60%....80%....vpf-10260: The file we are inserting the new item (8711 8718 0x71298001 IND (1), len 488, location 3608 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped 100% left 0, 11 /sec Flushing..finished Leaves inserted item by item 5282 Pass 3 (semantic): ####### Pass 3 ######### /Complete/Happy Birthday.movvpf-10680: The file [4 770] has the wrong block count in the StatData (238968) - corrected to (236816) /Movies/Bluray/Donnie.Darko.(2001)/BDMV/STREAM/00097.m2tsvpf-10680: The file [122 2579] has the wrong block count in the StatData (38567040) - corrected to (31162272) /Movies/Bluray/Burn.After.Reading.(2008)/Burn.After.Reading.mkvvpf-10680: The file [35 39] has the wrong block count in the StatData (51111744) - corrected to (51111632) Flushing..finished Files found: 7927 Directories found: 876 Broken (of files/symlinks/others): 1 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: /758_8711rebuild_semantic_pass: The entry [8711 8744] ("CONSTANTINE.meta") in directory [758 8711] points to nowhere - is removed rebuild_semantic_pass: The entry [8711 8754] ("Subtitles_12_English_exp.sup") in directory [758 8711] points to nowhere - is removed rebuild_semantic_pass: The entry [8711 8719] ("Chapters_2.txt") in directory [758 8711] points to nowhere - is removed /Audio_5_English.W64vpf-10670: The file [8711 8716] has the wrong size in the StatData (0) - corrected to (6261678080) vpf-10680: The file [8711 8716] has the wrong block count in the StatData (1039462) - corrected to (12229840) /Audio_5_English.WAVvpf-10670: The file [8711 8717] has the wrong size in the StatData (0) - corrected to (6257692672) vpf-10680: The file [8711 8717] has the wrong block count in the StatData (2023069) - corrected to (12222056) /Subtitles_13_English_exp.supvpf-10680: The file [8711 8756] has the wrong block count in the StatData (56800) - corrected to (54416) rebuild_semantic_pass: The entry [8711 8720] ("CONSTANTINE") in directory [758 8711] points to nowhere - is removed vpf-10650: The directory [758 8711] has the wrong size in the StatData (48) - corrected to (216) /770_8246get_next_directory_item: The entry ".." of the directory [770 8246] pointes to [741 770], instead of [2 8235] - corrected /770_8250get_next_directory_item: The entry ".." of the directory [770 8250] pointes to [741 770], instead of [2 8235] - corrected /770_8252get_next_directory_item: The entry ".." of the directory [770 8252] pointes to [741 770], instead of [2 8235] - corrected /00000.m2tsvpf-10680: The file [8252 8253] has the wrong block count in the StatData (42397720) - corrected to (42390656) /8237_8241get_next_directory_item: The entry ".." of the directory [8237 8241] pointes to [770 8237], instead of [2 8235] - corrected /8237_8243get_next_directory_item: The entry ".." of the directory [8237 8243] pointes to [770 8237], instead of [2 8235] - corrected /8711_8745get_next_directory_item: The entry ".." of the directory [8711 8745] pointes to [758 8711], instead of [2 8235] - corrected vpf-10650: The directory [8711 8745] has the wrong size in the StatData (352) - corrected to (120) /8720_8721get_next_directory_item: The entry ".." of the directory [8720 8721] pointes to [8711 8720], instead of [2 8235] - corrected rebuild_semantic_pass: The entry [8721 8735] ("JAR") in directory [8720 8721] points to nowhere - is removed rebuild_semantic_pass: The entry [8721 8736] ("META") in directory [8720 8721] points to nowhere - is removed rebuild_semantic_pass: The entry [8721 8740] ("STREAM") in directory [8720 8721] points to nowhere - is removed rebuild_semantic_pass: The entry [8721 8738] ("PLAYLIST") in directory [8720 8721] points to nowhere - is removed /CLIPINFrebuild_semantic_pass: The entry [8732 8733] ("00000.clpi") in directory [8721 8732] points to nowhere - is removed vpf-10650: The directory [8721 8732] has the wrong size in the StatData (80) - corrected to (48) rebuild_semantic_pass: The entry [8721 8737] ("MovieObject.bdmv") in directory [8720 8721] points to nowhere - is removed /BACKUPrebuild_semantic_pass: The entry [8723 8724] ("BDJO") in directory [8721 8723] points to nowhere - is removed rebuild_semantic_pass: The entry [8723 8729] ("PLAYLIST") in directory [8721 8723] points to nowhere - is removed rebuild_semantic_pass: The entry [8723 8727] ("index.bdmv") in directory [8721 8723] points to nowhere - is removed rebuild_semantic_pass: The entry [8723 8725] ("CLIPINF") in directory [8721 8723] points to nowhere - is removed rebuild_semantic_pass: The entry [8723 8728] ("MovieObject.bdmv") in directory [8721 8723] points to nowhere - is removed vpf-10650: The directory [8721 8723] has the wrong size in the StatData (184) - corrected to (48) vpf-10650: The directory [8720 8721] has the wrong size in the StatData (304) - corrected to (176) /8720_8742get_next_directory_item: The entry ".." of the directory [8720 8742] pointes to [8711 8720], instead of [2 8235] - corrected rebuild_semantic_pass: The entry [8742 8743] ("BACKUP") in directory [8720 8742] points to nowhere - is removed vpf-10650: The directory [8720 8742] has the wrong size in the StatData (72) - corrected to (48) Looking for lost files:9 /sec vpf-10670: The file [11 2335] has the wrong size in the StatData (0) - corrected to (21399552000) vpf-10680: The file [11 2335] has the wrong block count in the StatData (1665753) - corrected to (41796000) vpf-10670: The file [8711 8757] has the wrong size in the StatData (0) - corrected to (11908571136) vpf-10680: The file [8711 8757] has the wrong block count in the StatData (426936) - corrected to (23258928) vpf-10670: The file [8760 8873] has the wrong size in the StatData (3450077184) - corrected to (3480838144) vpf-10680: The file [8760 8873] has the wrong block count in the StatData (6738432) - corrected to (6798448) Flushing..finished Objects without names 20 Empty lost dirs removed 16 Dirs linked to /lost+found: 9 Dirs without stat data found 2 Files linked to /lost+found 11 Pass 4 - finished done 483076, 28 /sec Deleted unreachable items 6671 Flushing..finished Syncing..finished ########### reiserfsck finished at Mon Aug 27 01:01:39 2012 ########### All said and done, everything is up and running, my current parity check is almost finished and has only made a single correction thus far. I have a handful of items in the "lost+found" directory that I'll be sorting through tonight. The couple of Bluray movies that showed up in pass 3 will simply be deleted and re-ripped. All in all, long process, but feel much better now.
  22. Yep, same size drives. Actually same exact drives, 2TB WD Blacks. Heading home now and will run a file system check first and report back.
  23. I haven't been able to get to my system since the NOCORRECT parity check, but when I do, I want to tackle this incorrectly reported free space issue. Assuming all went well with the parity check, what should be my next step? Should a file system check on the drive fix the wrong free size reported problem?