Friction9045

I've been using a rootshare to access my files for 3 years, and then all of a sudden it stopped working. It just says access denied. I have created a new user, edited the rootshare, exported all my shares on smb with the new user, tried accessing my server via network and sharing on windows, getting rid of credentials and past connections, changing my password, running docker new safe perms. I cannot get it to work on any device. tower-diagnostics-20251204-2357.zip

I'll keep an eye on it then. If it keeps happening, does it mean I have to buy a new processor?

I just looked at fix common problems and it told me about a machine check event being logged. I took a look through my logs and saw this: Sep 21 11:18:23 Tower kernel: mce: [Hardware Error]: Machine check events logged Sep 21 11:18:23 Tower kernel: [Hardware Error]: Corrected error, no action required. Sep 21 11:18:23 Tower kernel: [Hardware Error]: CPU:1 (19:21:2) MC17_STATUS[-|CE|-|-|-|-|-|-|-]: 0x8000000100a08163 Sep 21 11:18:23 Tower kernel: [Hardware Error]: IPID: 0x0000000000000000 Sep 21 11:18:23 Tower kernel: [Hardware Error]: Bank 17 is reserved. Sep 21 11:18:23 Tower kernel: [Hardware Error]: cache level: L3/GEN, tx: INSN There's a also this that happened much earlier: Aug 30 07:26:43 Tower kernel: mce: [Hardware Error]: Machine check events logged Aug 30 07:26:43 Tower kernel: [Hardware Error]: Corrected error, no action required. Aug 30 07:26:43 Tower kernel: [Hardware Error]: CPU:1 (19:21:2) MC21_STATUS[-|CE|MiscV|AddrV|-|-|-|Poison|-]: 0x8d480824548d4808 Aug 30 07:26:43 Tower kernel: [Hardware Error]: Error Addr: 0x0000000000000000 Aug 30 07:26:43 Tower kernel: [Hardware Error]: IPID: 0x0000000000000000 Aug 30 07:26:43 Tower kernel: [Hardware Error]: Bank 21 is reserved. Aug 30 07:26:43 Tower kernel: [Hardware Error]: cache level: RESV, tx: GEN Full log zip is tower-diagnostics-20240922-0215.zip Is this anything to be concerned about?

I have a seagate external hard drive that I used to use with a separate computer, and I just shared it over the network with a username and password via SMB, I don't have this computer anymore so I wanted to see if I could just plug it in to my unraid server and just host that over a separate share since it's not going to be part of an array.

I'm trying to install some docker containers and whenever i do, it fails and gives me this: docker: Error response from daemon: failed to start shim: symlink /var/lib/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/37ebb92806ab824a813fde469a59c66548468a7a257b2d67e2b9bcae64880209 /var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/37ebb92806ab824a813fde469a59c66548468a7a257b2d67e2b9bcae64880209/work: no space left on device: unknown. I have plenty of space on my docker image, array, cache, and flash drive. I've tried removing other containers but no change. tower-diagnostics-20230715-1639.zip

Luckily, the names were the only changes. Everything works now, thanks!

Hi, I recently upgraded from my old xeon 2470v2 server to a ryzen 7 3700x computer (mainly for power savings). I followed a post on the forum, and transferred the drives and the flash drive to the new pc. I noticed my drives showed up as missing. The two drives are still there, but under different names. I assume this has something to do with the raid controller I had set to JBOD in the hp server that isn't present in my new build (I'm just using motherboard ports now). The solution I saw was to do a new config, and to me it seems pretty obvious which drive was which, but I wanted to make sure before I (potentially) nuke all my data. Thanks

I decided to take the drive out and make the MBR via disk management, and then put the drive back in the server, and I'm able to use it as a cache drive without issue now.

tower-diagnostics-20221013-0039.zip

Hi, I've tried the command you've given me, and then rebooting, however, I'm still getting the same MBR errors.

I recently added a spare NVME drive to my unraid server using a PCIE adapter. It shows up correctly and i'm able to add it to the cache pool, but it says: Unmountable: Unsupported partition layout. I have the option to format, but when i try to do this, the status doesn't change. I checked the disk log and I'm getting some MBR errors: Oct 12 00:05:47 Tower kernel: nvme0n1: p1 Oct 12 00:05:47 Tower root: /dev/nvme0n1: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54 Oct 12 00:05:47 Tower root: /dev/nvme0n1: 8 bytes were erased at offset 0xe8e0db5e00 (gpt): 45 46 49 20 50 41 52 54 Oct 12 00:05:47 Tower root: /dev/nvme0n1: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa Oct 12 00:05:47 Tower root: /dev/nvme0n1: calling ioctl to re-read partition table: Success Oct 12 00:05:47 Tower kernel: nvme0n1: p1 Oct 12 00:05:47 Tower emhttpd: writing MBR on disk (nvme0n1) with partition 1 offset 2048, erased: 0 Oct 12 00:05:47 Tower emhttpd: error: mkmbr, 2187: Input/output error (5): write: /dev/nvme0n1 Oct 12 00:05:47 Tower kernel: nvme0n1: I/O Cmd(0x1) @ LBA 0, 8 blocks, I/O Error (sct 0x0 / sc 0x4) MORE Oct 12 00:05:47 Tower kernel: I/O error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Oct 12 00:05:47 Tower kernel: Buffer I/O error on dev nvme0n1, logical block 0, lost async page write The drive worked fine when it was in my pc, and the smart report I generated came back with no errors. The drive is still formatted as NTFS with my old data on it (that i've already moved).

Everything works now. Thank you.

No dice. Still says not set. tower-diagnostics-20220914-0245.zip

Should i start it up with the ethernet connected to the on board ports, access the web ui, change the NIC port to eth0, power off, switch the ethernet cable to the NIC, and power it back on?

I think i've changed every variable I can, I've changed pci slots, changed network cards, turned of bond, set the ip manually, used a different usb port etc. Nothing has worked.