Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About thespooler

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If we're not using VMs, should we stay the course with rc7 until 6.9.0-rc1 is out?
  2. I'm having a problem that has only appeared since I've updated my PCs to Windows 10 1903. I can no longer drag and drop files onto network shares (files with the green pipe coming out of them) or even paste on to them. I have to open the network share first so there is a folder view, then I can drop or paste on the white space to add them to the root of that network share. This is super unproductive. It's likely not unRaids fault, but I also find it hard to see why MS would do this on purpose. Hoping there is some tweak to restore this ability between the server or the clients. I can drop files on to the network share directly in the bread crumb bar but technically that represents the open folder so I guess it's treated differently.
  3. I'm running the latest Jellyfin docker from here. CPU is pegged at 100%, memory is instantly eaten up, and the Jellyfin GUI doesn't come up, though it tries. Unraid is still responsive. From what I can tell, Jellyfin is indexing and it's running hundreds of /usr/bin/ffprobe -i commands until all my memory is gone, then it sits there. After around 5 minutes, dotnet crashes with an our of memory error according to the Unraid log and the whole process starts again. It's hard to get a sense of what's happening as I'm not much of a Linux guy and the delay in doing everything is so great. I can stop the docker, but starting it back up just results in the same scenario. I'm seeing all the ffprobes when I run top or ps when I ssh into Unraid itself. I don't quite understand why the ffprobes just sit there. They don't seem to be doing anything, not even erroring out. If I manually look in the /usr/bin unRaid directory, I don't see ffprobe, but I would have assumed this was running from the docker container anyways. I see someone else has complained about ffprobe missing, but in my scenario, how can a process being showing in top if it's truly missing. Not sure why Jellyfin would launch more than a few ffprobes at a time anyways. At this point, I'm just waiting things out to see what happens. I'm at the letter T in the indexing after 22 hours, but thought I'd pop in here and post this. Just tried to copy the top output to the clipboard and Kitty crashed... It did manage to copy though. There are more than 900 ffprobes listed in top.
  4. How are these doing years later? Now that I'm not SATA port limited, I'm thinking of tossing one of these into my array. Had 2 for backup, but I dropped one! So the other has been sitting on a shelf for years.
  5. If you're still interested in maintaining this, there are some corrections you need to do. For the thread: I also got the "DOS/16M Error: [40] not enough available extended memory (XMIN)" error. Pulling a stick did nothing, that still left me with 4GB in the PC. I couldn't get around this no matter what I tried. I ultimately had to replaced DOS4GW.EXE with DOS/32A a more recent DOS Extender which didn't have a problem with what I guess is TOO MUCH ram. I just dumped everything from the extract binw directory into the root of my USB drive and renamed DOS32A.EXE to DOS4GW.EXE and the DOS parts worked. The EFI shell scripts have a few problems, mostly cosmetic: "@echo is off" should be "@echo -off" "cd..\xxxxxxxxx" should be "cd ..\xxxxxxxxx" <- you need the space after "cd" or it fails. "echo . sas2flash.efi -l blah blah" <- this confused "echo", it thinks the "-l" is meant for it, which is invalid. Perhaps wrapping the echo with quotes would make that work. Since you were unsure of EFI, I was following along with another blog to verify the commands, and the other blog had a reboot between 5.2 (P7) and 5.3 (P20). Ultimately I didn't reboot. Step 6 looked sketchy since it wants you to edit it, but doesn't say that until you run it. Maybe REM the sas2flash.efi line so they have to add the SAS Address and remove the REM. In any case, your part was easy, thanks for doing this, maybe 10 minutes to flash between DOS and EFI Shell. But getting around the DOS4GW errors took hours. Out of curiosity, I've only hooked up my cache drive to the controller since mine was eBayed and I'll stay like that until the controller earns my confidence. But has anyone every encountered issues with moving drives between controllers? Should I turn parity correction off?
  6. Inside the configuration.yaml file, your "dash_url" is blank. Makes you wonder what other trivial errors you will see if it can't handle that happening. Even if you remove the dash_url, it will generate a different error. Remove the entire "hadashboard" section so the dashboard will be disabled, and the Docker should start up. #hadashboard: # dash_url:
  7. Ah, interesting! Previously, when the flash dropped, all the other drives stayed assigned. But I guess that's the difference between having an array started, and then the flash dropping vs the flash dropping before the array is started. I've rebuilt drive 2 and so far so good. I didn't realize dropping of drives was an issue. I would have saved myself $500 bucks in new hardware had I known. I just assumed it was a definite hard drive failure. Thanks for your assistance.
  8. I've disconnected and reconnected the cables and moved the flash drive to a USB2 port. I also plugged in my spare precleared drive to a PCIE SATA card I wasn't using just to see if it persists if the others drop again. unRAID has booted, everything assigned correctly without me doing anything, but array is stopped and drive 2 is still red x'd. Since drives are dropping, I'm not sure how concerned I should be with the array. How do I get disk 2 back? Remove it, start array, stop array and reassign the original disk 2 back to disk 2? Will that cause a rebuild of that drive? I'm a little nervous with what happens if the drive or other drives start dropping during that process.
  9. Right above your post is mine having a similar problem, but there is a file created "/tmp/preclear_stat_sd?" that you can look at. The file not changing, or the time stamp might help you understand if it's still functioning.
  10. Sorry for the confusion. These are two unrelated events. Pre reboot, I remounted /boot to sdh1 in case I modified the drives. The mounting worked, the errors went away, but I ultimately didn't do anything since the new SATA device wasn't detected. After reboot, everything was detected and in its place. All drives were assigned, disk 2 was still red x'ed, but now SMART was working. Later, if you look at the system log, when the USB was dropped, so were all the drives. That's when everything showed up under Unassigned Devices. In the original scenario, only the flash and disk 2 dropped. This time after adding a new drive to the system, they all did. I think the configuration is good, but I haven't rebooted yet. Going to redo the cables first.
  11. Corsair CX430M. This is an i3 setup. Nothing major. The server ran in its original state for many months, with I think 2 flash drives needing to be replaced during the a time. Adding this new drive today was the only other physical change.
  12. Thanks for your reply. I've been through a lot since was originally posted this in an effort to resolve it. In any case, I have my replacement drive. It's precleared. I popped it in hoping it would be picked up through hot plug-in support, but it wasn't. To sum up where I was, the /boot drive had dropped, and disk 2 was being emulated and listed a few write errors, but the array itself was still serving files, dockers were running. I ultimately mounted /boot on /sdh1 which was where the flash drive had shown up after checking it out on a Win10 PC. I was hoping that would allow me to save the config and rebuilt, but since the hot plug in didn't work it didn't matter. I restarted today and the /boot drive was back. Previously drive 2 couldn't show SMART info while it was being emulated. I thought this was normal, but I see now when unRAID came back up, the array was not started but SMART tests were available. So I started to wonder if disk 2 dropped in the same way the /boot drive had. Maybe there wasn't anything wrong with it at all. I left it running a SMART extended test and it seemed stuck at 10% for a long time. I clicked Main, and was a bit shocked to find all the drives now sitting in Unassigned Devices. I'm just using the motherboard SATA connections. I didn't previously post the diagnostics because there wasn't much in them once /boot dropped days earlier. This one catches the drop at Mar 10 15:55:41 Tera kernel: usb 4-4: USB disconnect, device number 2. I'll remove and reseat all the cables next. tera-diagnostics-20170310-1602.zip
  13. Hmm, well it doesn't appear to have worked. Preclear is hung at 98% on the first of three cycles' preread stage using the built in preclear script. How should I recover from that? The "/tmp/preclear_stat_sd?" file has a time stamp of 3 hours ago (the preclear itself reports 6 hours have passed, but I started with a reboot and my system uptime is 10 hours. Top shows preclear with 99% usage though the uptime is only 187:33. Is that the missing 3 hours? Perhaps the preread did complete and the next phase is where it hung. Pre-Read (1 of 3): 98% @ 126 MB/s (6:30:25)
  14. I'm trying to do a preclear in a VirtualBox VM on Windows. I have a trial unRAID, with no config or key, unRAID has started. I have installed the Preclear plugin. The HD is passed through and recognized with VirtualBox's RAW mode. Preclear is running, but there is no SMART info available. Am I just wasting my time with this? Or will Preclear still be able to tell me if the drive is okay through actual drive errors it might encounter? I can always check the SMART stats once it's hooked up natively or through Windows. The drive is a NewEgg HGST refurb (supposedly EOL from a data center) and it passed all the SMART tests with HGST's WinDFT.
  15. So I rebooted to finish installing 6.3.1 3 days ago. Did some Docker updates before the reboot. Today, I logged into the web GUI to update a Docker and it told me there was a read error on a drive. Sure enough I see one of my hard drives has an X on it, and 3 read errors. Okay. I acknowledge the notifications, but the GUI is clearly struggling. Every page wants me to install the Preclear Tor crap which is annoying. The plugin page isn't even showing Preclear to uninstall the thing. It only shows unRAID and the web GUI installed. The main tab isn't doing anything. There are no Dockers, or Docker tab. Checking the syslog makes the browser unresponsive, but I can see this in gray. Feb 14 04:40:01 Tera liblogging-stdlog: [origin software=rsyslogd" swVersion="8.23.0" x-pid="1426" x-info="http://www.rsyslog.com] rsyslogd was HUPed Feb 14 04:40:01 Tera root: Feb 14 04:40:01 Tera root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Feb 14 04:40:01 Tera kernel: fat__get_entry: 182 callbacks suppressed Feb 14 04:40:01 Tera kernel: FAT-fs (sda1): Directory bread(block 8192) failed Feb 14 04:40:01 Tera kernel: FAT-fs (sda1): Directory bread(block 8193) failed Feb 14 04:40:01 Tera kernel: FAT-fs (sda1): Directory bread(block 8194) failed Feb 14 04:40:01 Tera kernel: FAT-fs (sda1): Directory bread(block 8195) failed Feb 14 04:40:01 Tera kernel: FAT-fs (sda1): Directory bread(block 8196) failed Feb 14 04:40:01 Tera kernel: FAT-fs (sda1): Directory bread(block 8197) failed Feb 14 04:40:01 Tera kernel: FAT-fs (sda1): Directory bread(block 8198) failed Feb 14 04:40:01 Tera kernel: FAT-fs (sda1): Directory bread(block 8199) failed Feb 14 04:40:01 Tera kernel: FAT-fs (sda1): Directory bread(block 8200) failed Feb 14 04:40:01 Tera kernel: FAT-fs (sda1): Directory bread(block 8201) failed Feb 14 04:40:02 Tera root: Feb 14 04:40:02 Tera root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 I'm assuming SDA1 is my USB flash drive, as the /boot directory is empty in MC. How did the system even boot?! It must have died after it booted?! If so this would be the 3rd USB flash drive I will have burned through since I started using unRAID last year. These issues are always discovered after an upgrade, probably because it gets rebooted so infrequently. I plugged the USB flash drive into my Windows machine and it lights up and seems fine. I was able to copy all the files, Windows sees nothing wrong with the FAT. Windows can open /config/docker.cfg no problem. But plugging it back into my unRAID box and it doesn't light up in any USB port. I'm reluctant to reboot as my files are being served and my dockers actually are running right now. One thing I did think was strange with 6.3.1 was after it booted, I could see my USB flash drive listed under Boot Drive as sda (which is confirming my suspicion that it is my boot drive that is no longer readable), but also listed under Unassigned Devices as sdg. Boot Device Device Identification Temp. Reads Writes Errors FS Size Used Free View Flash USB_Flash_Drive - 16.0 GB (sda) * 443,036 411,842 0 vfat 16.0 GB 304 MB 15.7 GB Unassigned Devices Device Identification Temp FS Size Open files Used Free Auto mount Share Script Log Script sdg USB_Flash_Drive_AA437O23EKVFSJJYFSVA Mount * vfat 16.0 GB - - - The main screen seems to cache the Boot Device, as even if I unplug it, it's always there. System Devices shows it missing and when I plug it in, it appears as sdg. I tried to mount it with Unassigned Devices to see if the files were there now, but it just refreshes and shows the Mount option again, never getting past it.