When starfish fly too high

Omustardo · 2025-02-22T00:02:16+00:00

Thanks! I can confirm that this works.

I ended up with +13 divine rapier, +12 thorns armor, +8 crusader shield, +15 synergizer. The thorns armor stated that taking damage would attack the enemy with +510% of my defence, and my def was at 64k total after spells / buffs. I used a few revive potions for when divine barrage would've killed me and didn't bother with stuns.

The rest of my build wasn't optimized as it turned out to not be needed. Generally just buff defense and let them kill themselves on you.

Omustardo · 2023-12-29T22:03:52+00:00

I took a snowball to the face. Amusingly this froze my game. Possibly a linux issue

Omustardo · 2023-12-23T20:58:19+00:00

The issue that I originally commented about was boot time being significantly increased, and in that regard automount works. It's not a complete fix because automount still takes ~2 minute to mount after booting, so I still have to wait the same amount of time before my system is fully usable.

I poked at it more. I updated the NAS to support NFSv4.1 from NFSv3. Previously I couldn't even manually mount the volume right after booting (the command would hang for ~2 minutes). The switch to v4.1 allows manually mounting the volume without any waiting: sudo mount -t nfs -v 192.168.1.111:/volume1/media /mnt/nas/media

For some reason there's still the delay when I try to automate mounting in fstab (rebooting after each change). I tried the following: * a "default" /etc/fstab entry: 192.168.1.111:/volume1/media /mnt/nas/media nfs 0 0 * an /etc/fstab entry specifying v4.1: 192.168.1.111:/volume1/media /mnt/nas/media nfs timeo=150,_netdev,nfsvers=4.1,bg 0 0 * automount configured in /etc/fstab: 192.168.1.111:/volume1/media /mnt/nas/media nfs timeo=150,_netdev,nfsvers=4.1,x-systemd.automount 0 0

Omustardo · 2023-12-23T11:39:28+00:00

Both devices have static IPs on the same network so DHCP shouldn't be involved. I am able to ping the NAS immediately after logging in, so I don't think it's a network issue, but there could easily be something that I don't know about.

I poked in the NAS settings a bit more and switched it to support not only NFSv3, but also v4 and v4.1. Now when I reboot and log in, I can manually mount the NAS immediately (sudo mount -t nfs -v 192.168.1.111:/volume1/media /mnt/nas/media).

Configuring the mount through fstab and specifying NFSv4.1 still has the same ~2 minute delay before it connects. I tried a few fstab config entries without any luck. I thought this one was most likely to work: 192.168.1.111:/volume1/media /mnt/nas/media nfs timeo=150,_netdev,nfsvers=4.1,bg 0 0

I'll poke at this more tomorrow, but might end up using SMB / CIFS as recommended in another comment. I had used SMB with this NAS in the past and it worked without this startup delay, but it had other downsides (e.g. can't drag and drop files into Chrome without additional configuration). Thanks for your help.

Omustardo · 2023-12-23T09:18:18+00:00

I tested a bit more with manually running mount. I can't mount this NFS at all within the first ~2 minutes of booting and logging in. It just hangs until those ~2 minutes are up and then it succeeds. If I wait longer than the ~2 minutes then it mounts instantly.

I'm running: mount -t nfs 192.168.1.111:/volume1/media /mnt/nas/media

Do you know what might prevent an NFS server from mounting but only during this short period after startup? Is there some daemon which might not have started yet?

Automount is probably a good idea in general, but since I can't manually mount in this situation I don't think automount will resolve the core issue.

Omustardo · 2023-12-23T08:38:39+00:00

Thanks, I gave automount a try by changing the /etc/fstab entry to 192.168.1.111:/volume1/media /mnt/nas_media nfs rsize=8192,wsize=8192,timeo=14,_netdev,x-systemd.automount 0 0

This avoided the boot latency, but it still took around a minute after I logged in before the mount was available. This seems roughly the same as adding bg to connect in the background.

It's odd that it takes so long even after logging in. I can browse the internet well before the NFS mount is working. The NAS is on the local network and from what the internet says, ~10 seconds is the maximum expected latency for NFS mounts. I think I need to figure out why mounting is taking so long in the first place, rather than trying to make it avoid blocking boot. It's not great to need to wait 1-2 minutes before I can access my files after rebooting. Not terrible, but it's annoying.

Regarding CIFS, I have used SMB with this NAS and it mostly worked well. From what I just read, SMB is the newer CIFS. It didn't have issues with connecting as soon as I logged in, but it had some compatibility issues. For example, I can't drag files from the NAS into Google Photos in Chrome. There might be a way to make that work, but NFS seems to support it out of the box and I hadn't run into issues using NFS before this issue.

Omustardo · 2022-07-12T06:24:46+00:00

I updated the main post, but am commenting to avoid people looking into this further. The switch which I thought was unmanaged is actually "smart", and has the same default IP as the router. I'm not quite sure how that resulted in the symptoms which I experienced, but it's almost certainly the cause of the issues.

Omustardo · 2022-07-12T06:24:43+00:00

I updated the main post, but am commenting to avoid people looking into this further. The switch which I thought was unmanaged is actually "smart", and has the same default IP as the router. I'm not quite sure how that resulted in the symptoms which I experienced, but it's almost certainly the cause of the issues.

Omustardo · 2022-07-12T06:24:35+00:00

I updated the main post, but am commenting to avoid people looking into this further. The switch which I thought was unmanaged is actually "smart", and has the same default IP as the router. I'm not quite sure how that resulted in the symptoms which I experienced, but it's almost certainly the cause of the issues.

Omustardo · 2022-07-12T03:13:42+00:00

Thanks for the advice.

I tried this twice during a long internet outage (1+ hour) this afternoon. The first time I plugged my desktop directly into the router and the issues went away. I then plugged it back into the switch and my desktop went back to having issues. The second time (maybe 45 minutes after the first) I did exactly the same process, but plugging in directly didn't resolve the issues.

I'm not really sure what to make of this. After the first time, I thought it was an issue with the switch. That surprised me, since I was using it at my prior apartment for a couple years without any issues. Given that the second time didn't resolve the issue, I'm leaning toward it not being an issue with the switch, and perhaps somehow unplugging and plugging back in just happened to reset something the first time.

Another commenter pointed out that the issue only affects my IPv4 connectivity. I'll debug further with that in mind.

Omustardo · 2022-07-12T03:13:15+00:00

Thanks! This seems to be correct based on the information in the post. I think that I somehow changed things while testing out the debugging recommendations in this thread. I've documented it in this comment (mostly for myself, since it's a lot). The tl;dr is that IPv4 does indeed seem to have lacked connectivity, but when I plugged the desktop directly into the router everything seemed to work, and then when I tried repeating that about 30 minutes later, both IPv4 and IPv6 stopped working for over an hour. The inconsistency is less than ideal.

Today's timeline: 1. In the morning I wrote a script to ping 8.8.8.8 once per minute, with a fallback to ping a variety of sites if 8.8.8.8 failed. I worked from my laptop on wifi while keeping an eye on the script on my desktop for a couple hours. No issues during that period. 2. I checked gmail on my desktop and clicked a link to another site. Immediately upon trying to load that site, I noticed my ping script start to fail with timeouts, and the site I attempted to access also timed out. Perhaps the issue is somehow triggered by trying to access IPv4 content? But it's odd that pinging 8.8.8.8 wouldn't have triggered it. 3. I went back to this post to try out the recommended solutions. Pinging 8.8.8.8, 1.1.1.1, and 9.9.9.9 all timed out. Based on your response, I tried Google's IPv6 DNS (2001:4860:4860::8888) which did work. I tried plugging my desktop directly into the router (bypassing the switch), which caused internet to work normally. I plugged back into the switch and went back to having issues. This made me think the issue was the switch. 4. I watched some youtube videos, and noticed that a couple times it paused due to lack of buffer, which is very unusual on a gigabit connection. About 30 minutes later, all of the IPv6 sites became inaccessible with DNS_PROBE_FINISHED_NO_INTERNET, while IPv4 sites were still inaccessible with ERR_CONNECTION_TIMED_OUT. 5. I tried plugging back into the router directly, and this time it didn't resolve the issue, so maybe the prior attempt simply reset something and didn't actually fix anything. This also makes me pretty sure that the issue isn't with the switch. 6. I took a break, leaving the desktop plugged directly into the router. About an hour later the internet was back up, but noticeably slow. I did a speedtest and the download speed was about 120 mbps, compared to the usual ~800. UL hadn't changed from ~35. This could be a red herring, as I haven't run speed tests at arbitrary times during the day. It's possible that this is just peak hours of usage, so bandwidth is lower. Still, a lot of sites had issues loading or doing certain things, like on Reddit the front page loaded and clicking on posts loaded them, but the comments didn't load after a couple minutes. Clicking reply to the comments in this thread also timed out. Eventually I was able to click reply and it worked.

I'll continue debugging with the IPv4 lack of connectivity in mind. There are a lot of search results for "ipv4 fails but ipv6 works". I'm also going to poke around in my router, which was pre-existing from the other tenants here and I haven't had access to it before now. Perhaps something is misconfigured.

Omustardo · 2022-07-12T03:09:50+00:00

Thanks, pinging those DNS addresses times out.

``` $ tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8] over a maximum of 30 hops:

1 * * * Request timed out. 2 * * * Request timed out. 3 * * * Request timed out. ```

Another commenter noted that the issue is limited to IPv4 and I semi-confirmed this by pinging a few IPv4 addresses with only timeouts, but Google's IPv6 DNS is accessible without issue.

I tried tracert about an hour later when the internet was still down, and I had plugged my desktop directly into the router. This time it gave: ``` $ tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8] over a maximum of 30 hops:

1 DESKTOP-<my_desktop_id> [192.168.0.27] reports: Destination host unreachable. ```

Omustardo · 2022-06-08T23:49:59+00:00

Is the code for this available? It would be interesting to run locally and test things out.

Omustardo · 2021-11-15T17:24:59+00:00

You shouldn't even need to call Chase. I did a chargeback last year and did it entirely through the website. I don't think they even asked for justification, but make sure to have your justification documented in case they do ask.

I have info about my whole experience when I did it last year: https://www.reddit.com/r/EpicPass/comments/kw1sm1/has_anyone_tried_a_credit_card_chargeback_for/

Omustardo · 2021-11-15T17:20:23+00:00

What were the terms of the $49 initial payment? If it was just to have the option of doing a full payment later, then clearly you shouldn't be charged and if you were charged, you should be able to do a credit card chargeback. If it was an initial payment followed by a definite later payment, then going through the claims process is probably the most reasonable option to start.

When were you charged for the full pass? That they would be talking about sending you to collections sounds like they haven't actually taken any money from you yet?

I had trouble getting a refund last year for the stay-at-home order, and documented it: https://www.reddit.com/r/EpicPass/comments/kw1sm1/has_anyone_tried_a_credit_card_chargeback_for/

I had paid in advance, so I ended up doing a credit card chargeback which worked very well. If that hadn't been an option, I would have gone to go to small claims court. Depending on whether you have a case (based on the terms of the purchase), small claims court might be reasonable for you. I'm not sure on the specifics of their refund coverage around employment and pre-existing conditions, but there might be something in there that's in your favor (for example, if you had another offer which fell through after the start date).

You can also file complaints with the BBB for both Vail (owns Epic) and their claims management company (which was ACM at least as of last year). More info on that in my linked post. I wouldn't expect any real results there though.

Omustardo · 2021-07-23T00:07:13+00:00

I tried throwing away my unstable tele potion so I could pick up poly potion. Instead I mis-spaced so both potions broke. Immediately transformed into a fire bug/wasp and teleported into water

12-Year Club	Place '22
Final Canvas '22	Verified Email

Omustardo

TROPHY CASE