adammerkley

Members
  • Posts

    122
  • Joined

  • Last visited

Everything posted by adammerkley

  1. Trying to get some data off of my old Unraid server. The hardware no longer boots so I have pulled the drives and plugged them into an external USB enclosure. I've plugged the drives into my current Unraid server, but I'm unable to mount any of them so far in UD. The drives are formatted in ReiserFS. I get these messages in the log when trying to mount: Oct 14 11:12:35 Tower unassigned.devices: Adding disk '/dev/sda1'... Oct 14 11:12:35 Tower unassigned.devices: Mount drive command: /sbin/mount -t reiserfs -o auto,async,noatime,nodiratime '/dev/sda1' '/mnt/disks/old1' Oct 14 11:12:35 Tower kernel: REISERFS (device sda1): found reiserfs format "3.6" with standard journal Oct 14 11:12:35 Tower kernel: REISERFS (device sda1): using ordered data mode Oct 14 11:12:35 Tower kernel: reiserfs: using flush barriers Oct 14 11:12:35 Tower kernel: REISERFS (device sda1): journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Oct 14 11:12:35 Tower kernel: REISERFS (device sda1): checking transaction log (sda1) Oct 14 11:12:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Oct 14 11:12:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current] Oct 14 11:12:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0 Oct 14 11:12:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 00 01 00 cf 00 00 08 00 Oct 14 11:12:35 Tower kernel: print_req_error: critical target error, dev sda, sector 65743 Oct 14 11:12:35 Tower kernel: print_req_error: critical target error, dev sda, sector 65743 Oct 14 11:12:35 Tower kernel: Buffer I/O error on dev sda1, logical block 8210, lost sync page write Oct 14 11:12:35 Tower kernel: REISERFS warning (device sda1): journal-837 _update_journal_header_block: IO error during journal replay Oct 14 11:12:35 Tower kernel: REISERFS warning (device sda1): reiserfs-2006 journal_init: Replay Failure, unable to mount Oct 14 11:12:35 Tower kernel: REISERFS warning (device sda1): sh-2022 reiserfs_fill_super: unable to initialize journal space Oct 14 11:12:35 Tower unassigned.devices: Mount of '/dev/sda1' failed. Error message: mount: /mnt/disks/old1: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error. Oct 14 11:12:35 Tower unassigned.devices: Partition 'ST315003 41AS' could not be mounted...
  2. Can't think of much benefit to doing that. I'm relying on CA Backup for this. But if you do backup using Github and you use DNS verification, you'll want to exclude the file with your DNS provider API key.
  3. Thank for the replies. Got LetsEncrypt DNS verification to work after messing around with various security settings on CloudFlare.
  4. I'm on Cox residential. Is there no way for me to do this since port 80 is blocked? I've tried to go around this by circumventing DuckDNS and registering a domain, and using CloudFlare as my name server, but I still can't figure out how to make DNS Validation work.
  5. Last night I noticed an error in Fix Common Problems, reporting that even though Appdata is set to be Cache Only, some of it's folders exist on Disk4. Sure enough, I looked at the Appdata share and it is indeed set to Cache Only, but there are folders on Disk4. I used the Dolphin docker to copy the data back to /mnt/cache/appdata, worked like a charm. How did this happen though? My Appdata share has always been set to Cache Only.
  6. Bought 2 8TB EasyStores last week. Shucked and found white drives inside. Both register just fine in my Rosewill RSV-L4411 case's backplane.
  7. Interesting. I've never had this issue in 3+ years of this build. How can I mitigate?
  8. Nevermind. I shutdown, then figured out which slots those 2 disks were in. Removed and reseated them, but switch disk 8 with another disk to see if the problem traveled or not. The problem didn't come back.
  9. Disks 8 and 10 both got a single error. I got an alert on my phone about it. Trying to run short or long SMART tests from the disk pages results in nothing. Haven't rebooted yet. Attached diagnostics. Any ideas? tower-diagnostics-20170805-1859.zip
  10. Oh cool. I'm transcoding to RAM already, how are you writing Plex logs to RAM?
  11. Am I crazy or does mapping /transcode to /tmp work again?
  12. CA Appdata Backup is only supposed to backup appdata, right? If you're backing up your entire cache drive then it's going to backup TV, or Movies or whatever temporary shares exist on the cache drive at that point, waiting to be written next time Mover runs. So when you restore using CA Backup it will overwrite everything in the folders it is restoring.
  13. Congrats on the shoutout in Plex's newsletter today! My lame-o Windows coworkers were talking about this "new Docker thing that Plex is doing." :0
  14. Oh man, that motherboard looks great. I think I may upgrade my mobo to that one.
  15. Is it just me or is our community getting inundated with these types of posts? Almost seems like some anti-UNRAID misinformation campaign.
  16. Coming here to pile on and say that auto update of docker apps worked great. Now I have peace of mind that my app data and flash will be backed up every Saturday morning at 4 am, and I don't have to worry about updating Dockers anymore. THANKS!
  17. I have found that IRQ 16 gets disabled if I attach a monitor and keyboard to my server. The USB keyboard causes the issue. Disconnecting the keyboard and then rebooting always clears it up. Since I very, very rarely have a monitor and keyboard attached, I've never investigated it further. Last time this came up was last weekend when I was diagnosing some bad memory with memtest.
  18. Doh! You're right. I ended up completely uninstalling the Preclear Plugin as well as Unassigned Devices, and removing all traces of them from my flash drive. Upon reinstall I only had bjp999's script so I tried that. Working like a charm
  19. Oh, what I meant is, should I try the beta plugin? I've never used it before but I saw that it was developed to work with 6.2-beta. Now that 6.2 is final, is it still needed?
  20. Running 6.2.4. Put a new 4TB Seagate in, but I'm getting the following when trying to preclear using the plugin: /boot/config/plugins/preclear.disk/preclear_disk.sh -M 3 -o 4 -c 3 -f -J /dev/sdl root@Tower:/usr/local/emhttp# /boot/config/plugins/preclear.disk/preclear_disk.sh -M 3 -o 4 -c 3 -f -J /dev/sdl sfdisk: invalid option -- 'R' Usage: sfdisk [options] [[-N] ] sfdisk [options] Display or manipulate a disk partition table. Commands: -A, --activate [ ...] list or set bootable MBR partitions -d, --dump dump partition table (usable for later input) -J, --json dump partition table in JSON format -g, --show-geometry [ ...] list geometry of all or specified devices -l, --list [ ...] list partitions of each device -F, --list-free [ ...] list unpartitions free areas of each device -s, --show-size [ ...] list sizes of all or specified devices -T, --list-types print the recognized types (see -X) -V, --verify [ ...] test whether partitions seem correct --part-label [] print or change partition label --part-type [] print or change partition type --part-uuid [] print or change partition uuid --part-attrs [] print or change partition attributes device (usually disk) path partition number partition type, GUID for GPT, hex for MBR Options: -a, --append append partitions to existing partition table -b, --backup backup partition table sectors (see -O) --bytes print SIZE in bytes rather than in human readable format -f, --force disable all consistency checking --color[=] colorize output (auto, always or never) colors are enabled by default -N, --partno specify partition number -n, --no-act do everything except write to device --no-reread do not check whether the device is in use -O, --backup-file override default backup file name -o, --output output columns -q, --quiet suppress extra info messages -X, --label specify label type (dos, gpt, ...) -Y, --label-nested specify nested label type (dos, bsd) -L, --Linux deprecated, only for backward compatibility -u, --unit S deprecated, only sector unit is supported -h, --help display this help and exit -v, --version output version information and exit Available columns (for -o): gpt: Device Start End Sectors Size Type Type-UUID Attrs Name UUID dos: Device Start End Sectors Cylinders Size Type Id Attrs Boot End-C/H/S Start-C/H/S bsd: Slice Start End Sectors Cylinders Size Type Bsize Cpg Fsize sgi: Device Start End Sectors Cylinders Size Type Id Attrs sun: Device Start End Sectors Cylinders Size Type Id Flags For more details see sfdisk(. Sorry: Device /dev/sdl is busy.: 1 root@Tower:/usr/local/emhttp# Unassigned devices shows the preclear as "Starting..." What can I do? The "sfdisk: invalid option -- 'R'" sure sounds a lot like the errors reported back in post #220, is the beta plugin still necessary?
  21. Perhaps you can use something like this?. We use these dongles all the time at work. We host a bunch of headless Mac Minis for a large client, and these dongles make the onboard video card think that a monitor with 1920x1080 is connected so they never revert to 640x480 or whatever the default resolution is. They make a 4K equivalent. Pair it with a DisplayPort adaptor and you'd be in business, I think.
  22. One last update: Exchanged the bad RAM kit at Fry's yesterday. Put the new kit through 2 full passes of memtest, plus 10 passes of just test #7. No errors. Server has been running all night using the full 16GB with no issues. Last week when this issue first came up, I had been getting BTRFS errors all through the syslog and assumed it was BTRFS corruption or failing cache drives. I reformatted as XFS and the BTRFS issues went away (of course) but I continued to notice other weird issues. Now I realize that it was all due to the bad RAM, so I've gone back to using a cache pool
  23. I'm going to say this was a bad stick of RAM. I got home after work and found 3 seperate errors on the memtest screen. All from Test 7 of Pass #1. No other errors, even though the system had gone all the way through Pass #5 by that time. Here's what I saw: Removed and reseated the sticks and tried again. Immediately got another error when memtest got to Test 7. Noticed this error was around the 2GB mark also, so I assumed that it was either the stick in DIMM slot 0 causing the issue, or DIMM slot 0 itself. Pulled the stick out of DIMM slot 0, and replaced it with the stick from slot 1 (in an effort to rule out slot 0). Started memtest again, this time telling it to just run test 7. Let it do a dozen passes with no errors, and then called it a day and booted back into unRAID. It's been running error free under heavy use, including a no correct parity check, SABnzbd doing it's thing for most of the night, and several Plex transcodes. I guess I'll have to decide whether to RMA this or see if Fry's will exchange. Fingers crossed!
  24. Went home over lunch and ran chkdsk on my flash drive. Came up clean. Hooked up a monitor and keyboard, and manually set the memory speed to 1600MHz instead of Auto. All the timings and voltage look correct (9-9-9-24 1.5V) Running memtest now because I'm suspecting bad RAM. I put this RAM in (brand new) on 11/6 without running any tests on it.
  25. My server has been SUPER reliable for the last few years. Now I'm seeing all shares drop off randomly, and python (or other modules) throwing general protection faults at times. Like this: Nov 21 07:28:09 Tower kernel: traps: python[9560] general protection ip:2ac4d15689fc sp:7ffc761d11e8 error:0 in libpython2.7.so.1.0[2ac4d1486000+341000] Attaching diagnostics. EDIT: Seeing tons of segfaults now. Where should I begin? RAM? Nov 21 09:51:01 Tower kernel: monitor[6649]: segfault at 2b17ffd61320 ip 00002b17ff24daae sp 00007ffe1262d060 error 4 in libcrypto.so.1.0.0[2b17ff126000+227000] Nov 21 09:51:01 Tower crond[1715]: exit status 139 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null Nov 21 09:51:01 Tower kernel: sendmail[6651]: segfault at 2b82438ac320 ip 00002b8242d98aae sp 00007ffc535588a0 error 4 in libcrypto.so.1.0.0[2b8242c71000+227000] Nov 21 09:51:49 Tower kernel: php[6863]: segfault at 2b4eef209320 ip 00002b4eee6f5aae sp 00007ffd3f57e7c0 error 4 in libcrypto.so.1.0.0[2b4eee5ce000+227000] Nov 21 09:51:49 Tower kernel: php[6864]: segfault at 2b99cc3c9320 ip 00002b99cb8b5aae sp 00007ffd19739ed0 error 4 in libcrypto.so.1.0.0[2b99cb78e000+227000] Nov 21 09:51:49 Tower kernel: php[6865]: segfault at 2afcd970a320 ip 00002afcd8bf6aae sp 00007fffa0818c50 error 4 in libcrypto.so.1.0.0[2afcd8acf000+227000] Nov 21 09:51:49 Tower kernel: php[6866]: segfault at 2add95a2b320 ip 00002add94f17aae sp 00007ffcfb922570 error 4 in libcrypto.so.1.0.0[2add94df0000+227000] Nov 21 09:51:49 Tower kernel: php[6867]: segfault at 2b860b9ae320 ip 00002b860ae9aaae sp 00007ffe00302870 error 4 in libcrypto.so.1.0.0[2b860ad73000+227000] Nov 21 09:51:49 Tower kernel: php[6868]: segfault at 2aaed9715320 ip 00002aaed8c01aae sp 00007ffe5ef804a0 error 4 in libcrypto.so.1.0.0[2aaed8ada000+227000] Nov 21 09:52:01 Tower kernel: monitor[6921]: segfault at 2b460a4eb320 ip 00002b46099d7aae sp 00007fff6cc50b80 error 4 in libcrypto.so.1.0.0[2b46098b0000+227000] Nov 21 09:52:01 Tower crond[1715]: exit status 139 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null Nov 21 09:52:01 Tower kernel: sendmail[6922]: segfault at 2b3ebfd57320 ip 00002b3ebf243aae sp 00007ffd81cb4140 error 4 in libcrypto.so.1.0.0[2b3ebf11c000+227000] Nov 21 09:52:49 Tower kernel: php[7128]: segfault at 2b6112a09320 ip 00002b6111ef5aae sp 00007fffda511930 error 4 in libcrypto.so.1.0.0[2b6111dce000+227000] Nov 21 09:52:49 Tower kernel: php[7133]: segfault at 2b28e06a0320 ip 00002b28dfb8caae sp 00007ffd866faa00 error 4 in libcrypto.so.1.0.0[2b28dfa65000+227000] Nov 21 09:52:49 Tower kernel: php[7134]: segfault at 2aeddf86d320 ip 00002aedded59aae sp 00007ffeb5d9ba80 error 4 in libcrypto.so.1.0.0[2aeddec32000+227000] Nov 21 09:52:49 Tower kernel: php[7135]: segfault at 2b62987c6320 ip 00002b6297cb2aae sp 00007fff08d0e7d0 error 4 in libcrypto.so.1.0.0[2b6297b8b000+227000] Nov 21 09:52:49 Tower kernel: php[7136]: segfault at 2b393178f320 ip 00002b3930c7baae sp 00007ffee8fe1e30 error 4 in libcrypto.so.1.0.0[2b3930b54000+227000] Nov 21 09:53:01 Tower crond[1715]: exit status 139 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null Nov 21 09:53:01 Tower kernel: monitor[7186]: segfault at 2b8211835320 ip 00002b8210d21aae sp 00007fffb7fb0eb0 error 4 in libcrypto.so.1.0.0[2b8210bfa000+227000] Nov 21 09:53:01 Tower kernel: sendmail[7187]: segfault at 2ad01ca84320 ip 00002ad01bf70aae sp 00007fff3563b9f0 error 4 in libcrypto.so.1.0.0[2ad01be49000+227000] Nov 21 09:53:49 Tower kernel: php[7396]: segfault at 2ab4cb87e320 ip 00002ab4cad6aaae sp 00007ffc231fe230 error 4 in libcrypto.so.1.0.0[2ab4cac43000+227000] Nov 21 09:53:49 Tower kernel: php[7397]: segfault at 2ab1d5d20320 ip 00002ab1d520caae sp 00007ffcfeeceef0 error 4 in libcrypto.so.1.0.0[2ab1d50e5000+227000] Nov 21 09:53:49 Tower kernel: php[7398]: segfault at 2af207ec6320 ip 00002af2073b2aae sp 00007ffe803a92b0 error 4 in libcrypto.so.1.0.0[2af20728b000+227000] Nov 21 09:53:49 Tower kernel: php[7399]: segfault at 2b935cf29320 ip 00002b935c415aae sp 00007fff93c40bc0 error 4 in libcrypto.so.1.0.0[2b935c2ee000+227000] Nov 21 09:53:49 Tower kernel: php[7400]: segfault at 2b7803aad320 ip 00002b7802f99aae sp 00007ffc05db27a0 error 4 in libcrypto.so.1.0.0[2b7802e72000+227000] Nov 21 09:54:01 Tower kernel: monitor[7473]: segfault at 2b2140905320 ip 00002b213fdf1aae sp 00007fff4167ae10 error 4 in libcrypto.so.1.0.0[2b213fcca000+227000] Nov 21 09:54:01 Tower crond[1715]: exit status 139 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null I wanted to attach an updated diagnostics report, but I get a segmentation fault when attempting that: root@Tower:~# diagnostics Segmentation fault Attaching a Syslog instead. tower-diagnostics-20161121-0930.zip syslog.txt