Neldonado

Alright I tried it on a Macbook and PC and got the same error both times so I did a manual recreation of the USB device and it worked. Booted up the server and we're in! The bad part now is that I am now getting a new error when I try to update to 7.3.1 I've included my diagnostics after trying to update. t1000-diagnostics-20260838-1512.zip

I recently tried to update from 7.2.0 to 7.3.1 and was given a short error on the dashboard that my flash drive may be failing, the update did not work. I decided it would be best to try a new flash drive, so I purchased a Sandisk Cruzer Blade 16GB 2.0, plugged it into the usb creator and downloaded a backup of my flash. When I go to write to the usb drive though I get this error: Error extracting archive: ZIP bad CRC: 0x28118383 should be 0xa18a6db5 Where should I start looking to fix this? This happens around the 50% mark. Included my diagnostics as well. t1000-diagnostics-20260528-1512.zip

I bought this 5900X in November of 2023... does that mean the CPU is failing or what? What's the worst that could happen with something like this?

I replaced the PSU. I was running a 500W 80 plus white rated power supply for 12 SAS drives, 6 fans, and an hba card. I upgraded to an 850w power supply and well, I was able to rebuild the disk / parity and that finished this morning. No errors so far. Will closely monitor over the next few days, but I am wondering if this older power supply was just running at the max constantly and during rebuild when it's hitting everything it was pulling too much juice making the drives to drop off?

I’m pretty sure the cables are secure, so I will try a new PSU. Would it be beneficial to rebuild this disk while in maintenance mode?

Hello, A few weeks ago I got into my server and added a new drive. Everything seemed to go well until I started getting random drives with read or write errors. Most recently, I went several days with no issues and one of my two parity drives got disabled. I stopped the server, checked cables, started back up ran tests and everything seemed fine so I started the parity rebuild of parity drive 2. About 4-5 hours into this (while I was asleep), I had another drive get disabled due to write errors. At this point, it’s still in parity rebuild, and I’m not quite sure what to do. What happens if another drive gets disabled? should I stop parity, shut it down and replace all my cables? what’s the safest route to maintain my data? I have backups of the vital information but it would still be a massive blow to lose data. skynet-diagnostics-20250108-0559.zip

Hello, I recently oh I'd say in the last month or so noticed I am getting MCE alerts for my server. I tried looking through the sys lot and can't make too much sense out of it. I've attached a snip of one of them, and I'll upload my diagnostics as well. skynet-diagnostics-20250103-2209.zip

No read / write errors since last night, But I noticed these two kernel trap errors pop up. Any relevance?

That’s what I was thinking as the smart data came back good. I’m 33% through the parity rebuild, should I let it continue or should I stop had check wires? I have no way to know if it’s power or breakout data cables causing the issue. I have no errors since this initial incident though.

More errors on the rebuild, two different disks. This is really odd and doesn't make any sense why all these drives would be having issues all of a sudden? Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674512 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674520 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674528 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674536 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674544 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674552 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674560 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674568 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674576 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674584 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674592 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674600 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674608 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674616 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674624 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674632 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674640 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674648 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674656 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674664 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674672 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674680 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674688 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674696 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674704 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674712 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674720 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674728 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674736 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674744 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674752 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674760 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674768 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674776 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674784 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674792 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674800 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674808 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674816 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674824 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674832 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674840 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674848 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674856 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674864 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674872 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674880 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674888 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674896 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674904 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674912 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674920 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674928 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674936 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674944 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674952 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674960 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674968 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674976 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674984 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000674992 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675000 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675008 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675016 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675024 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675032 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675040 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675048 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675056 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675064 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675072 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675080 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675088 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675096 Jul 20 21:18:09 Skynet kernel: md: disk14 read error, sector=1000675104 Jul 20 21:18:09 Skynet kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Jul 20 21:18:09 Skynet kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Jul 20 21:18:09 Skynet kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Jul 20 21:18:09 Skynet kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Jul 20 21:18:09 Skynet kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Jul 20 21:18:09 Skynet kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Jul 20 21:18:09 Skynet kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Jul 20 21:18:09 Skynet kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Jul 20 21:18:09 Skynet kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Jul 20 21:18:09 Skynet kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Jul 20 21:18:09 Skynet kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Jul 20 21:18:09 Skynet kernel: sd 8:0:20:0: device_block, handle(0x001f) Jul 20 21:18:10 Skynet kernel: sd 8:0:20:0: device_unblock and setting to running, handle(0x001f) Jul 20 21:18:10 Skynet kernel: sd 8:0:20:0: Power-on or device reset occurred Jul 20 21:19:24 Skynet flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update

Hello, I recently got an error that my drive was failing. I had to manually stop the mover, and after the system went unresponsive for 10+ minutes I made the decision to do an unclean shutdown. When I booted back up I deselected the disabled drive in parity 2 slot, started the array, stopped array, selected an unassigned disk already in my machine, started array, and then started the parity rebuild. I am about 30 minutes into that rebuild and the parity 2 drive has failed again. I've attached my errors below, and attached my diagnostics. Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223797856 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223797864 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223797872 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223797880 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223797888 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223797896 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223797904 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223797912 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798352 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798360 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798368 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798376 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798384 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798392 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798400 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798408 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798416 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798424 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798432 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798440 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798448 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798456 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798464 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798472 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798632 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798640 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798648 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798656 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798664 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798672 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798680 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798688 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798696 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798704 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798712 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798720 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798728 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798736 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798744 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798752 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798760 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798768 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798776 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798784 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798792 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798800 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798808 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798816 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798824 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798832 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798840 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798848 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798856 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798864 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798872 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798880 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798888 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798896 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798904 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798912 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798920 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798928 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=1223798936 Jul 20 17:47:43 Skynet kernel: md: disk29 write error, sector=8593780232 Jul 20 17:47:44 Skynet flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Jul 20 17:47:44 Skynet kernel: mpt2sas_cm0: handle(0x18) sas_address(0x5000c500a6c8fc21) port_type(0x1) Jul 20 17:47:44 Skynet kernel: scsi 8:0:25:0: Direct-Access SEAGATE ST10000NM0226 KTB5 PQ: 0 ANSI: 6 Jul 20 17:47:44 Skynet kernel: scsi 8:0:25:0: SSP: handle(0x0018), sas_addr(0x5000c500a6c8fc21), phy(5), device_name(0x5000c500a6c8fc20) Jul 20 17:47:44 Skynet kernel: scsi 8:0:25:0: enclosure logical id (0x5001438022e55665), slot(38) Jul 20 17:47:44 Skynet kernel: scsi 8:0:25:0: qdepth(254), tagged(1), scsi_level(7), cmd_que(1) Jul 20 17:47:44 Skynet kernel: scsi 8:0:25:0: Power-on or device reset occurred Jul 20 17:47:44 Skynet kernel: sd 8:0:25:0: Attached scsi generic sg18 type 0 Jul 20 17:47:44 Skynet kernel: end_device-8:1:13: add: handle(0x0018), sas_addr(0x5000c500a6c8fc21) Jul 20 17:47:44 Skynet kernel: sd 8:0:25:0: [sdac] Spinning up disk... Jul 20 17:48:01 Skynet kernel: ...............ready Jul 20 17:48:01 Skynet kernel: sd 8:0:25:0: [sdac] 2441609216 4096-byte logical blocks: (10.0 TB/9.10 TiB) Jul 20 17:48:01 Skynet kernel: sd 8:0:25:0: [sdac] Write Protect is off Jul 20 17:48:01 Skynet kernel: sd 8:0:25:0: [sdac] Mode Sense: db 00 10 08 Jul 20 17:48:01 Skynet kernel: sd 8:0:25:0: [sdac] Write cache: disabled, read cache: enabled, supports DPO and FUA Jul 20 17:48:01 Skynet kernel: sd 8:0:25:0: [sdac] Preferred minimum I/O size 4096 bytes Jul 20 17:48:01 Skynet kernel: sdac: sdac1 Jul 20 17:48:01 Skynet kernel: sd 8:0:25:0: [sdac] Attached SCSI disk Jul 20 17:48:02 Skynet root: file: /mnt/mediacache/TV/Rugrats/Season 2/Rugrats (1991) - S02E40-E41 - Feeding Hubert and Spike The Wonder Dog [WEBDL-1080p].mkv Jul 20 17:48:02 Skynet unassigned.devices: Partition '/dev/sdac1' does not have a file system and cannot be mounted. Jul 20 17:49:21 Skynet root: file: /mnt/mediacache/TV/Rugrats/Season 2/Rugrats (1991) - S02E39 - My Friend Barney [WEBDL-1080p].mkv Jul 20 17:49:25 Skynet emhttpd: error: hotplug_devices, 1709: No such file or directory (2): tagged device ST10000NM0226_ZA290T3P0000C905MDCF_35000c500a6c8fc23 was (sdr) is now (sdac) Jul 20 17:49:25 Skynet emhttpd: read SMART /dev/sdac Jul 20 17:49:25 Skynet kernel: emhttpd[11286]: segfault at 67c ip 0000000000418359 sp 00007ffcc60002c0 error 4 in emhttpd[404000+1a4000] likely on CPU 16 (core 4, socket 0) Jul 20 17:49:25 Skynet kernel: Code: c0 75 15 48 c7 45 f8 75 ce 5a 00 48 c7 45 f0 a5 bb 5a 00 e9 38 01 00 00 8b 45 ec 89 c7 e8 2d 95 ff ff 48 89 45 d8 48 8b 45 d8 <8b> 80 7c 06 00 00 85 c0 0f 94 c0 0f b6 c0 89 45 d4 48 8b 45 e0 be Jul 20 17:49:44 Skynet flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update skynet-diagnostics-20240720-1917.zip

All right so I've gotten the server up and running on the stable release branch! thank you so much. The next hurdle I am dealing with is the installation of mods. I have followed all the documentation, it's the same as the windows directions with the caveat that everything needs to be lowercase (files and folders). Where I am stuck is where to put the startup command "-mod=@unlimited-stamina;" I tried in the `GAME_PARAMETERS` and that didn't work. Any idea?

I deleted the container, made sure all previous files were deleted and I created a new container with the DayZ server app ID: 223350. Was I correct up to this point? Where would I go to put my login information? I already have a Steam burner account for this specific process.

So switching the app ID didn’t do it, but it looks like there’s official progress being made here: https://community.bistudio.com/wiki/DayZ:Hosting_a_Linux_Server

I’ll have to give this a shot. This is what I was referring to:

With DayZ 1.24 officially supporting Linux , will we see official standalone game server support on unraid now? `Official release of the Linux version for the DayZ server slated for the stable branch`

Did you figure it out? in a similar situation

In unraid or my motherboard?

See picture, unable to start a trial. I’m wondering if I need to do something in bios because it says uptime of over 6 years when in reality it’s like 3 minutes.

I found this: https://steamcommunity.com/sharedfiles/filedetails/?id=1517338673 in this Linux guide it says It will look for the Workshop ID in the '.workshop.cfg' file. do I just need to create that file?

How-To Add Mods To A DayZ SA Server – The Dead Return (wordpress.com) here is one example, I think I am just confused on where to store them, and then how to activate.

DayZ server- How exactly do I add mods and have them load during the startup of the server? Any help would be appreciated, total noob with DayZ and it's hard to find help since I am running it on unraid.

I am going to stop and replace the SSD with a different brand SSD.

I ran into this issue again. This time with the OTHER ssd. This was the other one of the pair I originally had in here. Am I just really unlucky with having two SSD’s fail close to each other? the drive dropped offline. skynet-diagnostics-20230702-1659.zip

Wow! I must have set this when I originally created my unraid server back in 2020. Thanks, all is looking correct now.