

[US-NY] [H] Boxed N64 Console w/ Expansion Pack & OEM Blue Controller [W] PayPal G&S, Local Cash
Pictures / Timestamp: https://imgur.com/a/eQdJr41
Description:
Up for sale is my personal Nintendo 64 setup. This is a hybrid bundle—it comes with the original retail box and the highly coveted original styrofoam inserts, but please note it does not include the original gray controller. Instead, I am bundling it with an official OEM Blue controller (my personal controller).
Please see images for a game booting on the system.
What's Included:
- Nintendo 64 Console (Charcoal Black, NUS-001)
- Official Nintendo Expansion Pack (Installed, OEM NUS-007)
- Original Retail Box (Condition: see photos)
- Original Styrofoam Inserts
- OEM Nintendo Blue Controller (NUS-005)
- Original Power Supply & AV Cables
Pricing:
- Price: $240 + PirateShip UPS Label
- Open to reasonable offers, but not looking to split up the bundle or take trades at this time.
Terms & Shipping:
- Payment: PayPal Goods & Services (G&S) or local cash if you are in NYC (I am in NYC).
- Shipping: Will ship via UPS within a day or two of payment. I will put in an outer box to protect the original box.
- Please Comment Before PMing!
Thanks!
Unsuccessful move to internal boot
I am trying to transition from a flash drive to an internal boot. I. have a 1tb NVME that I was using as cache. I used mover to clear the disk. I then went through the internal boot menu, I selected the 1tb NVME, did boot + pool. It finished almost instantaneously. However, when I reboot my server, there is no option to boot from the NVME drive.
I then tried to boot back from my flash drive. This gave errors. This made me think perhaps that the flash was corrupted (it is like 3 months old and Samsung drive, so fairly high quality). So I restored my flash after which I was able to boot from the flash. Note that the backup was a couple days old and version 7.3.0 (my backup when I updated to 7.3.1). After booting to flash I again tried to transition to internal boot. I had to remove a pool (I think either cause flash backup was old or because of previous internal boot steps). After doing so, I was warned there was data on the 1tb nvme but I proceeded. Again, when I go to bios, no option to boot of the 1tb nvme I am trying to use for internal boot.
I would like to transition to internal boot once and for all. Can you please help me troubleshoot?
edit: I resolved this. On my NAS bios (UGREEN DXP 6800) there is an option where you have to set the NVMEs to bootable. It was defaulted to off, but turned that to on and now it boots.
I have a container which I recently transitioned to being managed/run via docker compose (specifically, a dockhand client running on another host) rather than the Unraid Community Apps template.
Whenever the container is stopped/started, for example for app data backup, or for auto update applications (side note: forgot I had this and turned off for all docker containers) it restarts an older version of the container: namely a different container build, not routing the container through gluetun, etc.
I deleted the template in /boot/config/plugins/dockerMan/templates-user/ and I am hoping this fixes it. I had already disabled the container from being backed up but maybe because gluetun was backed up via app data backup, it still stopped and started the container in question. Basically I want to make sure if Unraid/the plugin ever stops this container, the newer version managed by compose (with all its variables, network, etc) is setup. Any advice?
TLDR: Migrated qBittorrent from Unraid Community Apps to Docker Compose (managed by Dockhand on a separate host). Unraid's Appdata Backup plugin keeps restarting the old version of the container.