newbie_dude

Members
  • Posts

    76
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

newbie_dude's Achievements

Rookie

Rookie (2/14)

0

Reputation

  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! tower-diagnostics-20200307-1219.zip
  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. Is there a way to verify what sleep state it's in? I have "Suspend to Ram: Auto" (manual page 50) Selected in BIOS. Or why my Wake on Lan isn't working? I do have "PCI Devices Power On"(manual page 50) enabled in the BIOS as well. Thank you! Below is an excerpt of the s3_sleep log. Not sure if it would shed any light: Jan 19 20:00:42 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:00:43 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:00:45 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:00:45 Tower s3_sleep: ---------------------------------------------- Jan 19 20:00:45 Tower s3_sleep: command-args=-C 1 -h 17 -h 18 -h 19 -h 20 -h 21 -h 22 -h 23 -m 30 -e eth0 -N 0 -D 0 Jan 19 20:00:45 Tower s3_sleep: action mode=sleep Jan 19 20:00:45 Tower s3_sleep: check disks status=no Jan 19 20:00:45 Tower s3_sleep: check network activity=no Jan 19 20:00:45 Tower s3_sleep: check active devices=no Jan 19 20:00:45 Tower s3_sleep: check local login=no Jan 19 20:00:45 Tower s3_sleep: check remote login=no Jan 19 20:00:45 Tower s3_sleep: version=3.0.6 Jan 19 20:00:45 Tower s3_sleep: ---------------------------------------------- Jan 19 20:00:45 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl Jan 19 20:00:45 Tower s3_sleep: excluded disks=sda Jan 19 20:00:45 Tower s3_sleep: ---------------------------------------------- Jan 19 20:00:45 Tower s3_sleep: s3_sleep process ID 9973 started, To terminate it, type: s3_sleep -q Jan 19 20:00:46 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:00:47 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:00:48 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:17 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:18 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:19 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:21 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:21 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:21 Tower s3_sleep: command-args=-q Jan 19 20:02:21 Tower s3_sleep: action mode=sleep Jan 19 20:02:21 Tower s3_sleep: check disks status=no Jan 19 20:02:21 Tower s3_sleep: check network activity=no Jan 19 20:02:21 Tower s3_sleep: check active devices=no Jan 19 20:02:21 Tower s3_sleep: check local login=no Jan 19 20:02:21 Tower s3_sleep: check remote login=no Jan 19 20:02:21 Tower s3_sleep: version=3.0.6 Jan 19 20:02:21 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:21 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl Jan 19 20:02:21 Tower s3_sleep: excluded disks=sda Jan 19 20:02:21 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:21 Tower s3_sleep: killing s3_sleep process 9973 Jan 19 20:02:22 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:22 Tower s3_sleep: command-args=-C 1 -h 17 -h 18 -h 19 -h 20 -h 21 -h 22 -h 23 -a -m 30 -n -e eth0 -N 0 -D 0 Jan 19 20:02:22 Tower s3_sleep: action mode=sleep Jan 19 20:02:22 Tower s3_sleep: check disks status=yes Jan 19 20:02:22 Tower s3_sleep: check network activity=yes Jan 19 20:02:22 Tower s3_sleep: check active devices=no Jan 19 20:02:22 Tower s3_sleep: check local login=no Jan 19 20:02:22 Tower s3_sleep: check remote login=no Jan 19 20:02:22 Tower s3_sleep: version=3.0.6 Jan 19 20:02:22 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:22 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl Jan 19 20:02:22 Tower s3_sleep: excluded disks=sda Jan 19 20:02:22 Tower s3_sleep: ---------------------------------------------- Jan 19 20:02:22 Tower s3_sleep: s3_sleep process ID 10561 started, To terminate it, type: s3_sleep -q Jan 19 20:02:22 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:23 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:24 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:02:25 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jan 19 20:23:25 Tower root: plugin: running: anonymous Jan 19 20:25:49 Tower kernel: i2c /dev entries driver Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: command-args=-q Jan 19 20:27:28 Tower s3_sleep: action mode=sleep Jan 19 20:27:28 Tower s3_sleep: check disks status=no Jan 19 20:27:28 Tower s3_sleep: check network activity=no Jan 19 20:27:28 Tower s3_sleep: check active devices=no Jan 19 20:27:28 Tower s3_sleep: check local login=no Jan 19 20:27:28 Tower s3_sleep: check remote login=no Jan 19 20:27:28 Tower s3_sleep: version=3.0.6 Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl Jan 19 20:27:28 Tower s3_sleep: excluded disks=sda Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: killing s3_sleep process 10561 Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: command-args=-C 1 -h 17 -h 18 -h 19 -h 20 -h 21 -h 22 -h 23 -a -m 30 -n -e eth0 -N 62500 -D 0 Jan 19 20:27:28 Tower s3_sleep: action mode=sleep Jan 19 20:27:28 Tower s3_sleep: check disks status=yes Jan 19 20:27:28 Tower s3_sleep: check network activity=yes Jan 19 20:27:28 Tower s3_sleep: check active devices=no Jan 19 20:27:28 Tower s3_sleep: check local login=no Jan 19 20:27:28 Tower s3_sleep: check remote login=no Jan 19 20:27:28 Tower s3_sleep: version=3.0.6 Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl Jan 19 20:27:28 Tower s3_sleep: excluded disks=sda Jan 19 20:27:28 Tower s3_sleep: ---------------------------------------------- Jan 19 20:27:28 Tower s3_sleep: s3_sleep process ID 18608 started, To terminate it, type: s3_sleep -q Jan 19 20:37:19 Tower emhttpd: req (3): startState=STOPPED&file=&csrf_token=****************&cmdStart=Start Jan 19 20:37:21 Tower emhttpd: shcmd (2755): /usr/local/sbin/set_ncq sdb 1 Jan 19 20:37:21 Tower kernel: mdcmd (46): set md_num_stripes 1280
  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! tower-smart-20200111-2318.zip tower-diagnostics-20200111-2316.zip
  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 BTRFS and recommended XFS. Looks like that's where my screwup was? tower-diagnostics-20200111-0937.zip
  8. Thanks so much @johnnie.black 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 https://www.youtube.com/watch?v=ij8AOEF1pTU to put in a new ssd and copy the recovered data back onto the cache drive manually. The video had hints to get my dockers running again exactly as they were before. Next step would be to install the additional ssd and setup cache redundancy. Not sure if that was a good idea to not do that at the same time, but I didn't want to introduce too many variables at the same time. Thanks everyone for the help. Everyone here is the best!
  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. tower-diagnostics-20200107-2226.zip
  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 drives. I don't think I should have :( Thanks kindly for any help! reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/sdb1 Will put log info to 'stdout' ########### reiserfsck --check started at Tue Jan 7 20:25:34 2020 ########### Replaying journal: Trans replayed: mountid 254, transid 2230635, desc 1490, len 7, commit 1498, next trans offset 1481 Replaying journal: | | 0.2% 1 trans Trans replayed: mountid 254, transid 2230636, desc 1499, len 7, commit 1507, next trans offset 1490 ... ... ... Replaying journal: |====== \ 14.5% 91 trans Trans replayed: mountid 254, transid 2230726, desc 2654, len 7, commit 2662, next trans offset 2645 Trans replayed: mountid 254, transid 2230727, desc 2663, len 7, commit 2671, next trans offset 2654 Replaying journal: |====== | 14.8% 93 trans Trans replayed: mountid 254, transid 2230728, desc 2672, len 7, commit 2680, next trans offset 2663 Replaying journal: |====== / 14.9% 94 trans Trans replayed: mountid 254, transid 2230729, desc 2681, len 7, commit 2689, next trans offset 2672 The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2688): (Input/output error).
  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 minutesinit: cannot execute "/bin/sh" init: cannot execute "/bin/sh" init: Id "c2" respawning too fast: disabled for 5 minutes Everything was fine up until I upgraded to 6.4. Now I get this while booting and it's stuck after that. I saw in another thread to check if the USB drive had any issues by plugging it into a windows computer. I did and there was no issues. And also renamed the EFI- folder to EFI. No change. Still stuck here. Is anyone else having this issue? If so, solution? Thanks!
  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