• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About newbie_dude

  • Rank


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Oh I didn't even notice that. Thanks for the clarification!
  2. Thank you!! Is there some test I can run to get greater confidence it's not the drive? Never had this error before and I've had the controller for years. Always appreciate your prompt help JB.
  3. Just installed this not too long ago and some read errors reported. Got a diagnostics after it happened and put the system to sleep in case I needed to grab any other details that would be lost on a restart. Is the drive actually failing or could this be caused by another issue? Never had issues with my cabled. Any help would be greatly appreciated!
  4. Hopefully this is the right spot for this question! I'm using an ASrock 970 Extreme3. When I use the S3 Sleep Plugin to put the system to sleep, the front LED blinks. According to The Manual blinking means S1 Sleep. PLED (System Power LED): LED is on when the system is operating. The LED keeps blinking when the system is in S1 sleep state. The LED is off when the system is in S3/S4 sleep state or powered off (S5). This seem to indicate the system is in S1 sleep and not S3. This would explain why I can't wake it up using etherwake -i eth0 xx:xx:xx:xx:xx:xx From my raspberry pi. I
  5. Hi, A drive that I just bought a few months ago is now disabled, and I'm not quite sure what happened. I've just recently run a parity check and it came back fine. I don't think there are any errors in the smart report (from what I understand). I've moved the sata connections around and it didn't seem to fix the issue. Before I switch more cables round or order a new drive, is there anything else I can do see if the drive is bad or it;s something else? Thank you!
  6. Thanks! Guess I have to do funky business to get my data off the drive and format.
  7. Same "Cache drive unmountable: No pool uuid" issue when I tried to add a second cache disk. Original was formatted XFS. Error occurred when I started the array after choosing two slots and added the second drive. Now I notice the option to format as XFS is gone and only BTRFS is available. Also I can't change slots back to 1 and just go back to the old configuration. Is there a way to revert back? Does this mean I cannot have XFS formatted cache drives and must have BTRFS if I want cache protection? While googling I saw others had mentioned issues with B
  8. Thanks so much Ran ddrescue and as per your post to move data onto a spare drive I had. Thankfully it seems as if I was able to recover most. I did a file system check and said all was good but I couldn't use it as a cache drive (file system error).. I don't know if I was doing something wrong or you can't just add a drive with some random data on it and call it a cache drive on unraid. Apologies if this sounds silly! Wanted to use the method to replace the cache drive as if it hadn't failed. So then I followed this video
  9. Omg you're amazing. I'll plug in a new drive tonight and run ddrescue and reiserfsck. I'll keep fingers crossed. Thank you!
  10. LOL Apologies. Should have posted diagnostics initially.
  11. I ran the File system check and received the following output. Partially cropped. Looks as if the drive has actually gone bad and I would need to replace it. But in the mean time I did have data on the drive and would like to recover as much as I can. It was ~60% full (300GB capacity). Is there a way for me to recover the data on the drive onto another drive incase it fails mid recovery? I don't fully understand the suggestion below and would love an expert opinion on what my next steps should be. I've been putting off getting a couple of ssds to be redundant cache
  12. init: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: Id "c6" respawning too fast: disabled for 5 minutes init: cannot execute "/bin/sh" init: Id "c3" respawning too fast: disabled for 5 minutes init: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: Id "c4" respawning too fast: disabled for 5 minutes init: cannot execute "/bin/sh" init: Id "c1" respawning too fast: disabled for 5 minutes init: cannot execute "/bin/sh" init: Id "c5" respawning too fast: disabled for 5 minutesi
  13. Thanks for the clarification. Just wanted to make sure I wasn't the only one getting the issue. I guess I'll just keep disconnecting and reconnecting until I see the update dialogue box and go from there. Cheers
  14. Is anyone getting the issue where you can't click inside the filezilla interface? I can click on the initial "OK" Button, but when filezilla GUI starts, nothing responds. Edit: Submitted too early. I suspect it has something to do with the update filezilla dialog box. If I keep reloading the page, after a long time, I might get the update filezilla dialog box to show up inside the docker. Most of the time, it doesn't appear. And then I can click "no don't update" and go on as normal. I hope that wasn't too confusing