These drives work fine on an RS2416RP+ running DSM 6.2, no issues.
Don't whine they're "surveillance" drives, blah blah. They're hard drives, they work like you expect hard drives to work.
I don't know about DSM 7.x or newer NAS units, but I see no reason why they wouldn't work on them as well.
That's all.
May be associated with other errors, such as "Check Engine" light, ICS / backup system warning, etc.
Simple fixes that may save you time/money:
1. Check gas cap is tight.
Yes, it's stupid - damn stupid, in fact. But it worked for me and others.
Note the old RX330s had a similar issue, in that it would throw error codes if the gas cap was loose. Happened to me a few time when the weather got really cold. It's all because the car is looking for leaks in the emissions control system and sees that the pressure in the gas tank is not holding steady.
2. If codes do not clear themselves, disconnect battery for 5 min, then reconnect and start.
• Open the door during that 5+ min, to ensure system is fully discharged. Not needed but can't hurt.
• Yellow ICS light (top right-hand corner on RX350) will flash on restart. It will self-reset upon driving, don't worry about it.
3. Recharge battery to full, then retry. Worked for him and others.
It seems a near-dead or weak battery will cause the car to puke lots of codes. If this is your issue, consider replacing your battery, as it's likely on its way out.
I recommend disconnecting the battery while recharging so you can get the benefits of (2) and (3) in one go. Not necessarily required, though.
Some people say this occurs when the gas is low / very low., even to the point of claiming you're risking damage to your fuel pump.
I call BS on this since automakers know people will run their car down past reserve, and a few people will inevitably run out of gas, and the car / fuel pump has to tolerate this gracefully. Honestly, how stupid do you have to be to make a fuel pump system that will be damaged if you run low on gas?
Regardless, you can try filling up (and making sure your gas cap is TIGHT).
First, follow this tutorial, it's awesome.
A few changes, as follows:
1. If you can't install the OpenVPN Client Export package, update your pfsense. (It's scary but the latest stable version is stable, and will work.) Then the package will install.
2. When doing the Client settings Export (6:35), in "Host Name Resolution:, don't choose "xxx.dnsomatic.com", whatever it is, as DNS-O-Matic will not respond to this type of request.
Instead, choose "other" and type in the domain name associated with your dynamic DNS (i.e. "spacelasers.ca".
3. Once connected on Windows, be aware that Windows File Explorer DOES NOT WORK over a VPN tunnel.
This means that stuff like "\\mynas\drive" typed into Windows will not work, and you will not see your NAS in the Network pane.
Example: "net use h: \\192.168.1.10\drive" will mount it to H:\.
Apparently there is some way to automate mounting the network share once OpenVPN connects, but it seems to rely on using some specific OpenVPN client software on Windows. I haven't figured it out yet.
In the meantime, a good old batch file to run the above command will work.
I could not find a current / simple reference, and the Disney app is tedious to page through, so I had to put a quick GF reference list together. Hope this helps someone.
All info pulled from the Disneyland app Jan 07, 2023 unless otherwise noted.
Disneyland only - not for Walt Disney World! Breakfast menus, lounges and bars are not listed. All French fries listed here are gluten-free. For those unfamiliar, a "Power Pack" is basically a kids snack pack, it's not a meal. All items are "allergy-friendly", but I've never heard of anyone having any issues.
* = Info from internet
** = Info from last known menu, see bottom of post for copies
** ALWAYS SPECIFY GLUTEN-FREE OPTION TO SERVER. IF IN DOUBT, ASK TO SEE THE CHEF. **
DISNEYLAND
Alien Pizza Planet
Bengal BBQ *
Blue Bayou (Reservation only) **
Cafe Orleans (Reservation only) **
Carnation Cafe (Reservation only) **
Docking Bay 7
French Market Restaurant
Galactic Grill
Golden Horseshoe
Harbour Gallery
Hungry Bear Restaurant
Jolly Holiday Bakery Cafe
Oga's Cantina (Reservation only)
Rancho Del Zocalo
Red Rose Taverne
Refreshment Corner
River Belle Terrace (Reservations recommended) **
Ronto Roasters *
Stage Door Cafe
CALIFORNIA ADVENTURE
Award Wieners *
Carthay Circle Restaurant (Reservation only) *
Cocina Cucamonga Mexican Grill
Flo's V8 Cafe
Lamplight Lounge (Reservations recommended) *
 |
| Smokejumpers |
 |
| Lucky Fortune |
 |
| Flo's V8 Cafe |
 |
| Cocina Cucamonga |
 |
| Village Haus |
 |
| River Belle |
 |
| River Belle Lunch |
 |
| Rancho del Zocalo |
 |
| Rancho del Zocalo |
 |
| Pym Test Lab |
 |
| Pizza Planet |
 |
| Jolly Holiday (Winter menu) |
 |
| Jolly Holiday (GF menu) |
 |
| Jolly Holiday (Fall menu) |
 |
| Hungry Bear |
 |
| Galactic Grill |
 |
| French Market |
 |
| Docking Bay 7 (menu 1) |
 |
| Docking Bag 7 (menu 2) |
 |
| Docking Bay 7 (breakfast) |
 |
| Carnation Cafe |
 |
| Cafe Orleans |
 |
| Blue Bayou 1 |
 |
| Blue Bayou 2 |
Problem: One of these programs is incorrectly using an alternative-language keyboard layout (French, German, etc.). The system keyboard is set correctly and all other programs work as intended.
Possible solution: Press ALT-SHIFT to make the (probably hidden) Language Bar feature switch back to English.
Problem: Macroworks suddenly and inexplicably starts coming up with the "Unit ID Conflict" error / screen, claiming one or more Xkeys has a unit ID conflict that was never there before. Happens on a previously stable system.
(OK, maybe it's not exactly "Unit ID Conflict", but it's close. I didn't write it down.)
In my case, I had a bad label printer that was causing my USB hub to reboot over and over. This confuses MW and makes "see" the same Xkeys device over and over, making it think there are multiple identical devices plugged in when there is, in fact, only one.
Removing the offending printer stopped the hub reboots, which stopped the Macroworks error.
Per the Freedom Mobile Compatibility Checker, my Canadian-model Galaxy S9+ (SM-G965W) should no longer work in the USA. 3G shutdown has taken effect, and phones without "LTE Roaming" - which is somehow different than LTE "calling" - are no longer functional.
So I went to a shit-ton of work to get alternative phones lined up - an S22 and an S10+ - for my upcoming business trips. (The S10+ was the last model with a headphones jack.)
However, two separate trips from July 23 to August 04, 2022, to Philadelphia, PA and Denver, CO, show that my S9+ still works just fine on T-Mobile in the USA - even though according to Freedom, it shouldn't.
I tested the Samsung Galaxy S10+ and Galaxy S22 5G as well. They both work too.
For reference, the S9+ did show LTE when calling, so it's not likely picking up on some leftover 3G kit that hasn't been decommissioned yet. It did initially have a touch of trouble - the T-Mobile signal was weaker, so I think it tried AT&T first - but really had no issues beyond that initial hiccup.
It will register on AT&T but won't call/text, and won't register on Verizon at all, both of which are to be expected. In areas where you can't call, it's probably because T-Mobile coverage is bad, not because the phone is no longer working.
I am quite happy with this since the S22 felt like a downgrade: no headphones jack, a poorer fingerprint sensor, and a smaller screen than the S9+ or S10+, yet it does nothing that I need better than the older phones. And I'm bloody not well paying $1200+ for an S22+. I will be selling the S20 and using either the S9+ or S10+ depending on how well the S10+ fingerprint works.
