erikatcuse

Members
  • Posts

    355
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

erikatcuse's Achievements

Contributor

Contributor (5/14)

0

Reputation

  1. I have four - Cooler Master 4 in 3 HDD Modules I need to sell. All offers considered Looking for $30 a piece shipped buy 2 for $55 shipped buy all 4 for $100 shipped I would be willing to ship international (Outside USA) but shipping costs would need to be worked out. Paypal for payment
  2. I have four - Cooler Master 4 in 3 HDD Modules I need to sell Looking for $45 a piece shipped buy 2 for $80 shipped buy all 4 for $140 shipped I would be willing to ship international (Outside USA) but shipping costs would need to be worked out. Paypal for payment
  3. I haven't done a major disk reorganization in a while (around 4.0) and I was use to the Restore button...anyway with the long weekend I only had a chance to examine one 2TB drive so far and it's looking good. I'll have a better feel for what's been lost when I know how many folders I've recovered and comparing my backed up spare drive to the drive in my server. So far only the main folders were turned into numbers. All the files in each folder have the correct names so that;s a plus. Thanks Joe for the help
  4. It is b7 as for the button I thought it said restore but looking at screen shots of others I think it was start with the warning about new disks being added will be cleared. I had to check the box to say yes and I miss read the statement. For some reason I didn't see my disks as new. It was early in the morning and I was in a rush. With all 5 disks clearing at once hopefully it didn't get too far. Fortunatly all my critical data is also on an external drive I keep too.
  5. I'm running 5.0b7. Long story short it was early in the morning and I press the start button after checking yes to clear all new disks(I didn't see my disks as new) Here's what happened. I had a protected array with 2 disks. 1 parity, 1 data (both new). I then stopped the array and added my 5 disks with data on them. Thinking that if I clicked start that the array would come online and add the drives to the array. I thought unraid would recognize they had data on them. After rereading the caution after seeing disk clear at the bottom of the screen I realized the disks had started to clear. Needless to say I hit the reset button on the server when I realized it was clearing the disks (within a minute of originally hitting the start button) When unraid came back up the 5 disks with data on them were marked unformatted. I didn't care about parity so I went to utils cleared the array to start fresh. I tried to assign just the data disks with no parity and they were still unformatted. After reading this post http://lime-technology.com/forum/index.php?topic=4006.0 and http://lime-technology.com/forum/index.php?topic=1483.msg9973#msg9973 on data recovery I did a reiserfsck --check on one of the drives with the least amount of data on it. It came back and told me to run “--rebuild-sb option” So I did. after that I ran “reiserfsck –scan-whole-partition –rebuild-tree" It's currently running My question is do I have to run reiserfsck on both the /dev/sdc and /dev/sdc1 or just the sdc1? Before I do this on any other drives is this the best option? Thanks
  6. All the drives were spun up at the time. After removing a stick of memory and reseating everything in b6 I rebuilt parity (I marked all drives as new). Yesterday went back to b7 and ran a parity check. It completed successfully. I might take the other match pair or memory and put it back in and see if it was because something wasn't seated right.
  7. Moved back to b6 to see if it would work...and it didn't. I'm now testing the memory. When I ran a parity check it the system froze again but this time the caps locks and scroll lock light were flashing.
  8. I'm running b7 and when I do a parity check the system hangs up. I've left a telnet window open with the syslog running and nothing shows up on the screen. I have no control over the keyboard either. I can leave the system on and it's fine. We can watch movies and have not problem with it freezing up. Only during a parity check does it hang. I've done it several times and it hangs between 20-30 min in. I've also done file system checks on all the disks and they come back fine. I've attached a syslog of a recent reboot.
  9. What are these websites you speak of?
  10. If its windows 7 you need to see if you have passthrough selected. It should be an option in the sound properties.
  11. Received the cables the other day...thanks
  12. You might consider forwarding this one to Tom...he might want to switch to this type of card/reader combo.
  13. I've been with unraid since 1.0 and this has happened a few times in the past. Once he moved from the west coast to Colorado, a few vacations and to concentrate on a new release. It's already been suggested that he's been out of the country on a trip and more than likely is trying to push 5.0 out the door since he had wanted to complete it by Jan. I wouldn't read to much into it....
  14. Added 2 Adaptec 1430sa to the server yesterday and reconfigured the hard drives. In total I have 8 drives, 5 1tb (mixture of WD, Hitachi, Samsung) and 3 2tb (Hitachi, Seagate) 2 on each controller. Parity finish fine and I've re-enabled diskspindown. From the sys log sync done. time=28608sec rate=68285K/sec. Hard drive speed test from unmenu /dev/sda: (WD green 1tb) Timing cached reads: 10294 MB in 2.00 seconds = 5153.88 MB/sec Timing buffered disk reads: 236 MB in 3.01 seconds = 78.53 MB/sec /dev/sdb: (Hitachi 2tb) Timing cached reads: 10168 MB in 2.00 seconds = 5090.75 MB/sec Timing buffered disk reads: 362 MB in 3.01 seconds = 120.09 MB/sec /dev/sdc: (WD green 1tb) Timing cached reads: 10168 MB in 2.00 seconds = 5090.72 MB/sec Timing buffered disk reads: 250 MB in 3.02 seconds = 82.87 MB/sec /dev/sdd: (Samsung 1tb) Timing cached reads: 10756 MB in 2.00 seconds = 5385.45 MB/sec Timing buffered disk reads: 284 MB in 3.00 seconds = 94.62 MB/sec /dev/sde: (Hitachi 2tb) Timing cached reads: 10100 MB in 2.00 seconds = 5056.42 MB/sec Timing buffered disk reads: 356 MB in 3.01 seconds = 118.19 MB/sec /dev/sdf: (Hitachi 1tb) Timing cached reads: 9946 MB in 2.00 seconds = 4978.84 MB/sec Timing buffered disk reads: 248 MB in 3.00 seconds = 82.61 MB/sec /dev/sdh: (Seagate 2tb) Timing cached reads: 9894 MB in 2.00 seconds = 4953.51 MB/sec Timing buffered disk reads: 346 MB in 3.01 seconds = 115.10 MB/sec /dev/sdi: (Hitachi 1tb) Timing cached reads: 10114 MB in 2.00 seconds = 5063.46 MB/sec Timing buffered disk reads: 250 MB in 3.01 seconds = 82.94 MB/sec