Jarrodr

Thanks. That didn't help so I removed and installed again. Works now 🙂

Anyone have any ideas? The Web UI just won't load. I've disabled the VPN so that strikes that out. 2024-04-15 04:58:27.853379 [info] Host is running unRAID 2024-04-15 04:58:27.885629 [info] System information Linux 222c668176a2 5.19.17-Unraid #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022 x86_64 GNU/Linux 2024-04-15 04:58:27.922436 [info] PUID defined as '99' 2024-04-15 04:58:28.008334 [info] PGID defined as '100' 2024-04-15 04:58:28.125813 [info] UMASK defined as '000' 2024-04-15 04:58:28.169173 [info] Permissions already set for '/config' 2024-04-15 04:58:28.209140 [info] Deleting files in /tmp (non recursive)... 2024-04-15 04:58:28.258098 [info] VPN_ENABLED defined as 'no' 2024-04-15 04:58:28.282725 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE 2024-04-15 04:58:28.321015 [info] WEBUI_PORT defined as '8282' 2024-04-15 04:58:28.358829 [info] Starting Supervisor... 2024-04-15 04:58:28,769 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing 2024-04-15 04:58:28,770 INFO Set uid to user 0 succeeded 2024-04-15 04:58:28,775 INFO supervisord started with pid 7 2024-04-15 04:58:29,777 INFO spawned: 'start-script' with pid 62 2024-04-15 04:58:29,779 INFO spawned: 'watchdog-script' with pid 63 2024-04-15 04:58:29,780 INFO reaped unknown pid 8 (exit status 0) 2024-04-15 04:58:29,800 DEBG 'start-script' stdout output: [info] VPN not enabled, skipping configuration of VPN 2024-04-15 04:58:29,800 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-04-15 04:58:29,800 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-04-15 04:58:29,800 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22364966405840 for <Subprocess at 22364969660432 with name start-script in state RUNNING> (stdout)> 2024-04-15 04:58:29,801 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22364966397200 for <Subprocess at 22364969660432 with name start-script in state RUNNING> (stderr)> 2024-04-15 04:58:29,801 INFO exited: start-script (exit status 0; expected) 2024-04-15 04:58:29,801 DEBG received SIGCHLD indicating a child quit 2024-04-15 04:58:29,819 DEBG 'watchdog-script' stdout output: [info] qBittorrent not running 2024-04-15 04:58:29,820 DEBG 'watchdog-script' stdout output: [info] qBittorrent config file already exists, skipping copy [info] Removing session lock file (if it exists)... 2024-04-15 04:58:29,879 DEBG 'watchdog-script' stdout output: [info] Attempting to start qBittorrent... 2024-04-15 04:58:29,885 DEBG 'watchdog-script' stdout output: [info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8282... 2024-04-15 04:58:30,330 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8282

I gave up and formatted all drives, I lost all movies, TV shows and VMs. So I started off a fresh and now only use dockers to run deluge vpn, sonarr, Jackett, blah and blah. Is there a security docker and would it be worth it? Sent from my SM-A526B using Tapatalk

I've discovered I've been hit with the makop randsomware. Most of my drives have been encrypted. https://www.pcrisk.com/removal-guides/16848-makop-ransomware Is there anyway to recover my data? How do I protect myself in future? Possible cause: I have a windows vm running ExpressVPN and utorrent with no antivirus. The VM has shared folders to unraid shared folders.

Resolved. Installed the new drive. With the array off, assign the new drive as a parity and old parity as a new disk. Start array, it copies the parity then installs the new disk.

Was hoping for a miracle :-|. Will have to replace the parity with the new drive first and then use the old parity drive as disk 2.

Sorry, totally forgot about this. By the way, I just picked up my 4tb hard drive. Haven't installed it yet. tower-diagnostics-20220818-1239.zip

@trurl Not sure if this helps, I picked it up. I followed this yesterday, and no luck. Took some time.

I actually cancelled that check now

Sorry, this is what I see.

Here is the smart report for Disk 1 attached. Where can I find the Notification history? WDC_WD20EZRX-00D8PB0_WD-WMC4M0H0VPEJ-20220817-1624.txt

Step 1: Parity swap Step 2: Swap disk 2

Hi All, I bought a 4tb to replacement my Parity, I haven't installed yet though. I have a dilemma, Issue: I have a corrupt disk and want to replace it. Requirement: Parity - 4tb (new) Disk 1 - remains the same. Disk - 3tb (using the old parity drive) How do I replace the parity and disk with losing data? WDC_WD20EARX-00PASB0_WD-WCAZAD059495-20220817-0914.txt

Thanks. Changing to NTFS works. Is there a way to speed up the copying time? I have a single ISO file which is 50GB, the estimated time is 4 hours.

I want to transfer files to a windows pc. Should I format to NTFS?

Sorry for the delayed information. Still getting the same error. tower-diagnostics-20210902-2118.zip

Hi I have mounted a external HDD to my unraid. I used MC (Midnight Commander) to copy between shares. When I copy/move a file which is 27GB, does not allow me. How do I fix this?

Thanks so much. I've been breaking my head. Now I see it. But I get this now. Copying from a shared to usb.

Hi I know this has been asked before but nothing from those posts have worked. I am using Unraid Version: 6.8.3. When I plug in my USB drive, formatted as Fat32. I cannot share/ access the drive. System logs: Aug 9 10:38:02 Tower kernel: usb 1-5: new high-speed USB device number 3 using xhci_hcd Aug 9 10:38:02 Tower kernel: usb-storage 1-5:1.0: USB Mass Storage device detected Aug 9 10:38:02 Tower kernel: scsi host5: usb-storage 1-5:1.0 Aug 9 10:38:03 Tower kernel: scsi 5:0:0:0: Direct-Access KIOXIA TransMemory 1.00 PQ: 0 ANSI: 4 Aug 9 10:38:03 Tower kernel: sd 5:0:0:0: Attached scsi generic sg5 type 0 Aug 9 10:38:03 Tower kernel: sd 5:0:0:0: [sdf] 60549120 512-byte logical blocks: (31.0 GB/28.9 GiB) Aug 9 10:38:03 Tower kernel: sd 5:0:0:0: [sdf] Write Protect is off Aug 9 10:38:03 Tower kernel: sd 5:0:0:0: [sdf] Mode Sense: 45 00 00 00 Aug 9 10:38:03 Tower kernel: sd 5:0:0:0: [sdf] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Aug 9 10:38:03 Tower kernel: sdf: sdf1 Aug 9 10:38:03 Tower kernel: sd 5:0:0:0: [sdf] Attached SCSI removable disk Aug 9 10:38:04 Tower unassigned.devices: Disk with serial 'TransMemory_0022CFF6BD70C420E5EE3F4C', mountpoint 'JAR' is set as pass through.

Will do. I have nothing to lose. Lol Sent from my Mi 9T using Tapatalk

Tried 2 different ports. One the backpanel and side. On the previous version I had no issues. Any other thoughts? tower-diagnostics-20200610-1832.zip

Thanks @Hoopster. attached tower-diagnostics-20200610-1720.zip

Hi I updated to the latest version and have a Basic package. Ever since the latest version update, I cannot mount any external drives. Does not even allow me to spin up. Please can you assist. ATA Error Count: 6 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 6 occurred at disk power-on lifetime: 6891 hours (287 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 08 04 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- Error 5 occurred at disk power-on lifetime: 6891 hours (287 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 08 04 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- Error 4 occurred at disk power-on lifetime: 6891 hours (287 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 08 04 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- Error 3 occurred at disk power-on lifetime: 6876 hours (286 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 08 04 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- Error 2 occurred at disk power-on lifetime: 6873 hours (286 days + 9 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 08 04 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- SMART short self-test:

That's the thing. Previously the port didn't open, step 4 didn't help. But adding step 3 made a difference. Sent from my ONEPLUS A3003 using Tapatalk

Boom. Fixed it. Here's my solution: 1) Unplug all drives. 2) Browse the flash using your computer. (make a backup just incase) 3) edit \config\network.cfg. Set to default values. (I got the defaults from looking at a fresh install) # Generated network settings USE_DHCP="yes" IPADDR= NETMASK= GATEWAY= BONDING="yes" BRIDGING="yes" 4) edit \config\go. (xx being the port) #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp -p xx & 5) Put the flash into the NAS and boot up. Select the GUI. Using Firefox access localhost:xx. Then boom. . 6) Take a picture of the "Main" tab to identify the order of your drives. Then switch off. 7) Setup all your drives in the correct order and you're done. This worked for me. Not sure if it will help you