markguy

Members
  • Posts

    103
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

markguy's Achievements

Apprentice

Apprentice (3/14)

0

Reputation

  1. You'd think it would... I sure as hell did... but it doesn't. It returns: rm: cannot remove `FOO': Directory not empty You can rm the .fuse_hidden file, but it just adds another after incrementing the number after .fuse_hidden.
  2. I'm having the same trouble and cannot find a post with details on this... If someone could point this out to me, I'd appreciate it. EDIT: I think this is it, or at least the start of the relevant information. Also, apparently 3.6.9 is the new hotness.
  3. This should likely be under WebGUI... somehow missed that subforum when looking for a place to post this. Apologies!
  4. Turns out the tiny "Cancel" button is remarkably close to the tiny "Refresh" button on the main page of the 5.0-rc8a web interface. Which leads up to a funny story about how I accidentally canceled a parity check seven hours after starting it instead of refreshing the page. And by "funny," I mean "enraging." I seem to remember there being a pop up alert in earlier versions, preventing this sort of clumsy mousework on my part. Regardless, does anyone know how easy it would be to add simple javascript to that page... or, I don't know, moving those two buttons to opposite corners of the screen?
  5. Right. Done and it's chugging along at 33MB/s. That's certainly better than nothing! Thanks!
  6. Well, it doesn't look like it'll work using my openelec box... ./preclear_disk.sh.1.13: line 196: /boot/config/disk.cfg: No such file or directory '
  7. I had this thought on my way out to get kids from school, so it's not *quite* as lazy as it appears: can anyone tell me if preclear_disk.sh can run under any distro or just unRAID OS? By the way, it's taking longer than 13 hours. Looks more like 18 hours.
  8. Thanks for the reply! Drive info below (hard to pass up for $70): Seagate Barracuda 7200.14 ST3000DM001 3TB 7200 RPM 64MB Cache SATA 6.0Gb/s
  9. I'm building a new unRAID array and have what's going to be the parity drive hooked up to the only 6.0GB/s header on the motherboard. It's preclearing at 170MB/s (3TB in 13 hours!) and I'm wondering if it would be worth swapping out the other drives to that header for preclearing. I can't think of a reason why this would not be worthwhile, but honestly, it's never occurred to me before. Does the array care what header a drive was attached to? I'm assuming since preclear_disk.sh -t shows it's precleared state, that would be good regardless where else it showed up. While I've got your attention, I'm working under the assumption that having the parity drive on the 6.0GB/s header is the best plan. Is there something I'm overlooking, some reason to follow a different plan? Annnnnnd further wondering if I could preclear disks on different boxes, then add them all into a single array? Parallel preclearing, of a sort. Thanks! (I'm using 5.0-rc8a)
  10. Make sure your PSU has the rails and the wattage to add more drives, too.
  11. I have a parity drive that won't spin and two data drives (of four) that don't show up in BIOS. As far as I can tell from reading, that's the end of my array. In an attempt to figure out how the hell I lost three drives in the space of a week, I got an external cage and thought to test them on my Windows 7 box... thinking (hoping) maybe the motherboard went wonky, not the drives. While I wait for that cage to show up, is there anything else I can do to resurrect the array? And after the cage shows up, if I do have three failed drives, is there any way to pull info off drives that are still good while hooked up as an external drive?
  12. So my replacement WD drive showed up... Any advice on what to do with an array holding one red drive and one blue drive? I wasn't going to bother with the pre-clear script, since the array is not going to be up and running.
  13. Swapping cables eventually got the BIOS to see the drive, but it returned a warning of "SMART Capable but Command Failed" and unRAID considers it missing. I'm going to call that dead. While googling about to see what I could find on that warning, I discovered Western Digital has a pretty slick, painless way of checking if your drive is still under warranty here. That's a silver lining, I suppose.
  14. With one drive red and one blue, I'm "only" going to lose the red? Thanks for the response, by the way. As an aside, it's uncanny and immensely frustrating how changing anything at all in the box causes me issues. Losing a 2TB drive while replacing a 2TB drive seems a harsh penalty.
  15. I've replaced the SATA cable, swapped out ports... I can't get the drive to show up in the BIOS. Anyone have any other suggestions, short of pulling it and trying it in a different motherboard? Also, if it is toast, this does mean I've lost the entire array, correct?