spanky

Members
  • Posts

    7
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

spanky's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I love that while Unraid has evolved a lot since I've been running it - it's always 'just worked' Not a lot on my wishlist, I'll be happy if everything stays nice & stable :)
  2. I've attached the syslog, and can confirm you're correct about the disk in question. Not able to get to the server until Friday so can't check any connections at the moment - that will be more of a re-seat than anything as it's a HP N54L microserver with drive bays (drive bolted into a cage which seats into the bay) syslog.txt.zip
  3. Thanks for checking, I realise the risk. Cheers, Shane. config_folder.zip system_folder.zip SMART_folder.zip
  4. Hi, Received worrisome messages (via prowl) that my parity disk was in an error state so remote desktop'ed into a machine on that LAN and had a look, sure enough had a red X for the parity disk. Ran the diagnostics (couldn't attach as it's 210kb and limit here is 192kb) and it looks to have been unable to get any SMART data for that disk (an Seagate 8TB archive disk). Attached is the disk error report obtained by clicking on the drive from the MAIN window. Reading some of the help docs I have brought the array down and rebooted it in the hope of being able to get a SMART report, however there's no disk showing against the parity slot now, and there is none that can be selected from the dropdown - presumably this means a catastrophic failure of the disk or a cable issue. I won't be able to get to the server until late Friday so trying to work out what to do next. (I will buy another drive to take home with me just in case) As I have backups of everything important on other disks / servers, and working on the assumption that one way or another parity is going to have to be rebuilt anyway, is it an option to bring the array back online and run unprotected for a few days ? Thanks in advance for any wisdom you care to share. Cheers, Shane. disk_error.pdf
  5. Hi, I have been following these instructions to migrate two disks from reiserfs to XFS: There are 3 disks in the mix - (all 4TB), an empty drive formatted as XFS (disk3) + two disks (disk1 and disk2) to be moved over. All has gone to plan, with step 7 running now from disk1 to disk3 (to a 't' directory on the new drive as suggested). When I have a look at the contents of disk3 from the GUI I see the files I expect + a corresponding 4.10KB file for each that has it's name beginning with '._' Hoping someone can tell me if this is expected while the process is underway - are these temp files created as part of the copy process ? Thanks. **UPDATE** I actually went and had a look at disk1 (source disk) and all those 4.10KB files are there, which explains why they're being copied d'oh. I still have no idea what they are though. **UPDATE 2** Did some searching and apparently these '._' files are a legacy mac thing that I don't see when using finder on the mac. Cheers.