wes.crockett

Members
  • Posts

    10
  • Joined

  • Last visited

About wes.crockett

  • Birthday February 19

Converted

  • Gender
    Male
  • URL
    https://wescrockett.com
  • Location
    Fresno, CA

wes.crockett's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Awesome! I couldn't get SMART data to show up or run until I unassigned the disk. It shows 100 reallocated sectors, so replacing it is probably a good idea anyways. As far as connections, all drives connect to a backplane, so there isn't a single cable going to each disk. I'm running an extended SMART test now. Thanks for your help!
  2. Thanks Jorge. Sorry about not posting the complete diagnostics. I do see 1 unassigned device as you said (that I didn't notice last night). How do I tell it to put that disk back as SDH? smartctl output.txt
  3. Hello all, I have 5 3tb disks with 2 additional as parity. While away, we had a power outage which brought the system down. Got home today and brought the array back online. Now getting a red X on the disk1 showing 'Device is Disabled, contents emulating... click to spin down device.' I cannot access any SMART data and it doesn't do anything when I hit to test. Here are snippets from the log: Jul 3 15:12:14 Kuiper kernel: mdcmd (2): import 1 sdh 64 2930266532 0 Hitachi_HUS724030ALE641_P8GUXJYP Jul 3 15:12:14 Kuiper kernel: md: import disk1: (sdh) Hitachi_HUS724030ALE641_P8GUXJYP size: 2930266532 Jul 5 14:36:47 Kuiper kernel: blk_update_request: I/O error, dev sdh, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Jul 5 14:36:47 Kuiper kernel: blk_update_request: I/O error, dev sdh, sector 3820608 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820544 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820552 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820560 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820568 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820576 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820584 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820592 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820600 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820608 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820616 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820624 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820632 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820640 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820648 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3820656 Jul 5 14:36:47 Kuiper kernel: blk_update_request: I/O error, dev sdh, sector 3821632 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821568 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821576 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821584 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821592 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821600 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821608 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821616 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821624 Jul 5 14:36:47 Kuiper kernel: md: disk1 read error, sector=3821632 Jul 5 14:44:00 Kuiper root: Fix Common Problems Version 2021.05.03 Jul 5 14:44:01 Kuiper root: Fix Common Problems: Error: disk1 (Hitachi_HUS724030ALE641_P8GUXJYP) is disabled Jul 5 14:44:01 Kuiper root: Fix Common Problems: Error: disk1 (Hitachi_HUS724030ALE641_P8GUXJYP) has read errors Jul 5 22:02:53 Kuiper unassigned.devices: Error: shell_exec(/usr/sbin/smartctl -n standby -A /dev/sdi | /bin/awk 'BEGIN{t='*'} =='Temperature:'{t=;exit};==190||==194{t=0;exit} END{print t}') took longer than 10s! Jul 5 22:02:53 Kuiper unassigned.devices: Error: shell_exec(/usr/sbin/smartctl -n standby -A /dev/sdi | /bin/awk 'BEGIN{t='*'} =='Temperature:'{t=;exit};==190||==194{t=0;exit} END{print t}') took longer than 10s! Jul 5 22:02:57 Kuiper unassigned.devices: Error: shell_exec(/usr/sbin/smartctl -n standby -A /dev/sdi | /bin/awk 'BEGIN{t='*'} =='Temperature:'{t=;exit};==190||==194{t=0;exit} END{print t}') took longer than 10s! Jul 5 22:02:57 Kuiper unassigned.devices: Error: shell_exec(/usr/sbin/smartctl -n standby -A /dev/sdi | /bin/awk 'BEGIN{t='*'} =='Temperature:'{t=;exit};==190||==194{t=0;exit} END{print t}') took longer than 10s! I have attached the syslog and smart report. I assume the drive is toast? I have ordered a new one already, but want to make sure I understand what is wrong too... Just in case it may not be the drive. Any ideas? anything I need to try? We are headed back out for the week tomorrow... I may take the system offline for that time just in case there are more power outages. Also... Will be getting a UPS for this system. kuiper-syslog-20210706-0554.zip kuiper-smart-20210705-2214.zip
  4. It's always the setting you don't think about... set it to do Full SSL on CloudFlare and good to go.
  5. Good evening all, My web host raised their rates again and... well... screw that... $15/mo for a simple, mostly static, WP site... I don't think so. I already have MariaDB, SWAG, and a NextCloud instance set up and working. I blew away swag and redid it so that it includes top level domain certificate and not just sub-domains. My subdomain for Nextcloud is working, as well as one that I called web.exampledomian.com [using my actual domain]. The web one goes straight to the SWAG page. As does www.exampledomain.com. That said, I get 'ERR_TOO_MANY_REDIRECTS' when I just try https://exampledomain.com I am using Cloudflare for dns. Once I get my site up and running, I plan to transition my DNS registration to Cloudflare entirely for $8/yr. Any idea where to look as to why https://exampledomain.com would get a Too Many Redirects error while the subdomains (including www) do not?
  6. Apparently today was a good day to Google 'Unraid Grafana Dashboard'. I await your next post, @falconexe.
  7. I created a new share for Docker files only and set it to ONLY for cache. Removed old container and deleted previous folders (even though they were on the old share). I reinstalled the app and put in the new paths. Booted the container fine. then took it down, replaced the world files, and started it back up. Everything looked good. I then restarted the container, and it created a Dedicated.db.new file that is about 26MB smaller (71.4MB total) than the existing Dedicated.db file. Restarted again and the .new file grew to 81MB (16MB smaller than original save file).
  8. In reviewing, I kind of had a hunch that this could have an impact but my experience with UNraid extends super far back... to yesterday evening I just set it to only. That said, I only have a single disk (NVME on PCIe riser card...) in the cache pool. Is there a simple way to create backups to disk from there? (this question, i'm sure, is very out of scope of this thread, but figured I would ask.) Also, thank you for being a super awesome and responsive contributor!
  9. I just submitted an issue on your github, but i'll put it here too since this is probably more appropriate.: I had a dedicated box running Ubuntu for a Valheim server. I used the docker template to move it to my new UNRaid box. I set the parameters and moved a copy of my world file over to the unraid share (used default... /appdata/... Not sure what cache settings are OK for this.) When I start the server, it's golden! Glad I thought to test a bunch before telling my buddies to go ham. Restarting does one of three things: a new world file is created with the moniker of .new at the end. It is about 1/2 the size of the old one and, when logging in, I spawn at the beginning shrine and the map is not uncovered. a new world file is created and it is 1mb and is a fresh world instance. I spawn it at the location that I previously logged out at, but no buildings or items are present. When this happens, it appears as if the old file is archived with the .old extension. RARELY, it launches fine and as expected. I will read the rest of the thread, but thought I would chime in early on my current experience. Please let me know if any more details are needed.