Jump to content

yumbrad

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

1 Neutral

About yumbrad

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. This is a Gigabyte "GA-K8N Ultra SLI" (http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=1867&ProductName=GA-K8N%20Ultra-SLI) ... It's a pretty old mobo with 8 onboard SATA ports - 4 from the NForce chipset and 4 from an added Silicon Image sil3114 controller. The NForce ports are 3gb/s, the Simg ports are 1.5gb/s. It was my Windows desktop before I went pretty much all mac + linux, and has worked well over the years - like you said, nice to have 8 onboard sata ports. Yeah, I know the taped drive is ghetto, and yes - it is the cache drive. I couldn't figure out a place to mount an IDE drive - I tried a few places. Might be better for heat to stick it back by the unused power supply cables. It's the last vestige of my IDE drives.
  2. Well, pretty common around here, and no custom 140mm fans, but I really like my new Norco 4220 setup. Replaced the jet engine fans w/quiet cheap ones from newegg (masscool).
  3. I use Time Machine w/Unraid. Originally started by using it over NFS (the hacks to get unsupported network volumes working as a Time Machine target work for both NFS and Samba). That was bad news - Time Machine seemed to have some problems with it, and iTunes REALLY didn't like using that as its library drive. Had a lot of purchased downloads end up getting access errors - had a friend at Apple look a little bit, and its a "you're wrong" "no, you're wrong" kind of situation between linux NFS server implementations and the MacOS client. Bottom line: maybe it'll work with Snow Leopard, but it's not happy currently. Samba seems to work fine. I'd love to do AFP, however, since it's not quite a "seamless" experience mounting samba shares, performing the hack to get them recognized by TM, etc... If something doesn't get mounted right, it's my job as "IT" at home to get it up and running - if it were AFP, I think it would be automatic enough that my wife could just reboot things til they worked, no Terminal necessary. Although Avahi + Samba sounds like it might help a bit towards that goal! Unless I'm mistaken, I don't think afpfs-ng would help for this? It seems to be a linux client for mounting AFP shares. Not sure how this would help enable Unraid to serve up AFP?
  4. Thanks, this found a bunch of problems, and all the error messages referred to files within the sparse bundle that (was) my time machine backup. So hopefully it'll run clean now, and I can just recreate that backup!
  5. Well, something's borked when I try to access the sparse disk image that is on my user share, which is actually split across several drives. I hope it's just the sparse disk image - it'd be a bummer, but it's my Time Machine backups, so I could delete them and start fresh from now. Here's what gets printed out in the syslog when accessing this sparse image (which is a directory structure) ... ideas? Should I force an fsck somehow? Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9205 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9206 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9207 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9208 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9209 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9220 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9221 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9222 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9223 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9224 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9225 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9236 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9237 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9238 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9239 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9240 0x0 SD] Apr 15 18:21:17 files kernel: ReiserFS: warning: is_tree_node: node level 0 does not match to the expected one 2 Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-5150: search_by_key: invalid format found in block 2037165. Fsck? Apr 15 18:21:17 files kernel: ReiserFS: md3: warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [4178 9241 0x0 SD]
  6. Well, it seems to have completed successfully, all green. There's a ton of data on the drive, including a sparse disk image, so hopefully nothing got corrupted, I'll give an update in a week or so. Thanks for all the help! Especially the recovery procedure bjp999!
  7. I'm trying your more conservative first suggestion So far, it is behaving as you said it would. I replaced the bad 250GB disk 3 with a 500GB disk. Interestingly, when it was "Starting...", bad disk3 initially said the same amt free as the old HD - 9GB free or so. After it got going, it changed to 250GB free. Starting: Rebuilding: I'll report back when it's done with the results!
  8. Wow, thanks. I will get such a disk and report back - I probably would have tried for a new "biggest" disk as a replacement, so I'm glad you gave me this procedure.
  9. Indeed, "Start" is disabled, I assume because of the orange parity disk. I had started rebuild and stopped, unsure, so I'm not sure of the parity drive's state. Since it won't rebuild without the failed disk (which isn't plugged in because it hangs up Unraid), won't I lose the failed disk's data if I replace it with a new disk and rebuild? Or will it use as much of the "good" parity as it can?
  10. I have a mixed Pro setup, current state shown in the pic below. I had a 250gig drive with a couple of errors, so I decided to run a parity check to see if that would reallocate all the bad sectors. Well, that got progressively slower until it was crawling and essentially hung - couldn't unmount, etc. So I removed the bad drive and started back up - it started to do a rebuild, but I saw how long it was going to take, and got a bit scared that the orange parity ball + the red missing ball meant I would lose data (dumb noob mistake, now I've read the Top Ten Ways to lose data), so I put the drive back in and tried to start up so I could probe it with Smart view on unmenu (installed right then). Everything became totally unresponsive after it started going for a while and had a bunch of errors (of course) on the bad drive, so I decided to shut everything down and see if I could restart the array as I had done before. No - now it shows as below. Doh! What should I do to minimize data loss??? Thanks!! Edit: here's the syslog I just grabbed, if it helps: http://pastebin.com/f48235285