filk

Members
  • Posts

    10
  • Joined

  • Last visited

filk's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Cheers @Squid. Running a syslog server on a pi was on my todo list actually so maybe that now needs to become a thing. Marking as solved. Edit: Doh! I can't do that! I'll let you do it then 😜
  2. Hi all, My server was working fine until I woke up one morning and it had suddenly become unrepsonsive and I could not access the webUI or any of my containers. I could not ping it either from another local machine. Unfortunately it is remote so I could not see if it had shutdown or what. However, after a day had passed, I tried to access the webUI. To my suprise, it loaded and I was able to login. After logging in, I saw my array was not running. The below is from the System Log and I'm not sure if I should be worried: Jun 21 02:36:46 gunnhild kernel: mce: [Hardware Error]: Machine check events logged Jun 21 02:36:46 gunnhild kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 3: be00000000800400 Jun 21 02:36:46 gunnhild kernel: mce: [Hardware Error]: TSC 0 ADDR ffffffffa010c039 MISC ffffffffa010c039 Jun 21 02:36:46 gunnhild kernel: mce: [Hardware Error]: PROCESSOR 0:306c3 TIME 1624239386 SOCKET 0 APIC 0 microcode 28 I've also attached my diagnostics ZIP. Any help is greatly appreciated. Thank you. gunnhild-diagnostics-20210621-1152.zip
  3. Apologies for hijacking this old thread, but I'm also getting the same issue. My Unraid server is 192.168.1.8, the port forwarding is as follows: HTTP: 180 > 80 HTTPS: 1443 > 443 I've sense checked everything multiple times but I can't find anything wrong with the below which makes me think it's something else but I'm falling short on what it could be. Any help is greatly appreciated!
  4. Thank you, @johnnie.black. Removing the referenced files in the scrub seems to have resolved the issue.
  5. Hi all, As the title suggests, after running Mover, I am immediately presented with csum errors, as per below: Aug 16 15:15:23 gunnhild emhttpd: shcmd (313): /usr/local/sbin/mover &> /dev/null & Aug 16 15:15:26 gunnhild kernel: BTRFS warning (device dm-3): csum failed root 5 ino 293582 off 757051392 csum 0x0d54183c expected csum 0xb4018745 mirror 1 Aug 16 15:15:26 gunnhild kernel: BTRFS warning (device dm-3): csum failed root 5 ino 293582 off 757051392 csum 0x0d54183c expected csum 0xb4018745 mirror 1 Aug 16 15:15:26 gunnhild kernel: BTRFS warning (device dm-3): csum failed root 5 ino 293582 off 757051392 csum 0x0d54183c expected csum 0xb4018745 mirror 1 Aug 16 15:15:26 gunnhild kernel: BTRFS warning (device dm-3): csum failed root 5 ino 293582 off 757051392 csum 0x0d54183c expected csum 0xb4018745 mirror 1 Aug 16 15:15:31 gunnhild kernel: BTRFS warning (device dm-3): csum failed root 5 ino 354615 off 1305513984 csum 0x73d2e631 expected csum 0x8ae53185 mirror 1 Aug 16 15:15:31 gunnhild kernel: BTRFS warning (device dm-3): csum failed root 5 ino 354615 off 1305513984 csum 0x73d2e631 expected csum 0x8ae53185 mirror 1 Aug 16 15:15:31 gunnhild kernel: BTRFS warning (device dm-3): csum failed root 5 ino 354615 off 1305513984 csum 0x73d2e631 expected csum 0x8ae53185 mirror 1 Aug 16 15:15:31 gunnhild kernel: BTRFS warning (device dm-3): csum failed root 5 ino 354615 off 1305513984 csum 0x73d2e631 expected csum 0x8ae53185 mirror 1 After researching the forum, I had suspected this was down to faulty RAM or cache drive at first. A memtest corroborated this theory and I thought it was the root cause. I replaced the RAM and ran another memtest which came back with 0 errors after 14 passes. The cache drive was old and low capacity so this also was changed to an MX500. However, I'm still getting the same BTRFS errors and now I'm at a loose end as to what to do. FWIW, Mover does infact move the files from the Cache onto the Array as expected. It's not like it ever fails. A side note as I'm not sure if it's related or not: I also received the error below. It's worth mentioning it could be because the box was off for around 2 weeks and potentially could be a result of that? Aug 16 15:19:46 gunnhild ntpd[1675]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Any help would be greatly appreciated!
  6. FYI to those who find this post on Google: The SanDisk Cruzer Nano/Fit will not work with the USB Creator, you'll have to use the manual method. I'm back in, kind of. I had trial and error in terms of what dirs I could copy over from my old /config dir on the corrupt USB flash drive. Initially I copied over the whole /config folder but nginx and php wouldn't start automatically, and when I did, I had a lot of the same web UI errors I had in my first post. Thus I created a fresh USB with only the shares folder and smb-extra.conf file which worked. Unfortunately now I have a bit of configuring to get my docker containers and Unraid settings back to how they were. I'm currently in the middle of reconfiguring my containers by redownloading them from Community Apps and mapping paths, IP:ports again as this is the current state of my containers: Documenting this here in case anyone else comes across the same issue.
  7. Bosh: https://wiki.unraid.net/index.php/FAQ#How_do_I_upgrade_my_unRAID_flash_drive_to_a_larger_size_drive.3F Thank you, @Squid. I've ordered a SanDisk Cruzer Fit 16GB USB 2.0, fingers crossed it lasts!
  8. @Squid: Thank you for the reply. I think so too. I'm shopping for a "proper" drive on Amazon as we speak, however, what's the next steps for me? As it's a trial, am I able to pick up where I left off with a new drive? I've spent a good few days configuring Unraid to how I want and I'd rather not lose my configs.
  9. Hi all, I am in the process of migrating data to my Unraid server (6.8.3). I am still in my trial period of my license. My suspicion is my USB drive has become corrupt because of the following: 1. After a turning the machine on after a shutdown (executed via web UI), the web UI is now not accessible. After searching the forums on how to restart nginx, there were a lot of the following errors when it finally became accessible. Warning: parse_ini_file(state/disks.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/template.php on line 27 2. Running fsck -n -f resulted in: fsck from util-linux 2.34 fsck.fat 4.1 (2017-01-24) 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit. Checksum in long filename part wrong (56 vs. expected 5e). Not auto-correcting this. Wrong checksum for long file name "templšࡴes-õser". (Short name TEMPTA~3 may have changed without updating the long name) Not auto-correcting this. /CONFIG/PLUGINS/dockerMan "." is missing. Can't fix this yet. /CONFIG/PLUGINS/dockerMan ".." is missing. Can't fix this yet. Leaving filesystem unchanged. /dev/sda1: 284 files, 54704/980863 clusters Note the weird character in "templšࡴes-õser" 3. I noticed the .plg file for Unassigned Devices plugin was "unassignud.?e?ic?s.plg". I doubt that's supposed to be like that. As previously said, I can still SSH into the box and thus the USB drive is still readable. Results from running diagnostics has been attached. What would you recommend my next steps to be? I've tried searching the forums for this use case but I couldn't find anything. I do apologise if there's already a post about this or an obvious fix for this. Many thanks for any help tower-diagnostics-20200504-1635.zip