All Activity

I went to my trakt account today only to realize it had been deactivated for inactivity and I lost everything on there that accumulated over the past 6 years or so. I then went to check in emby and the pin was gone from the config somehow. So basically my question is wtf happened? Why was my config wiped with no warning.

Edit: it actually does have the same issue in browser, it just isnt as bad

QUANDO O EMBY VAI TER ESSES RECURSOS, E OS MODELOS DE SEPARAÇÃO IGUAIS AO XSPF, LOGO CND's MAIS ROBUSTOS. QUANDO O EMBY VAIS SER PARCEIRO DOS GRANDES CDNS. E O PLUGUINS IPTV, NÃO CONSIGO CONECTAR NADA, ELE SEMPRE DA ERROS. O QUE TENHO QUE FAZER PARA ESSE PLUGUIM PEGAR PERFEITAMENTE. Quando o Emby terá esses recursos e modelos de divisão semelhantes ao XSPF, resultando em CDNs mais robustos? Quando a Emby firmará parcerias com os principais players do mercado? E o plugin de IPTV, não consigo conectar nada, sempre dá erro. O que é preciso fazer para que este plugin funcione perfeitamente?

Im using emby theater on cachyos and have been having issues with jiddery and playback. Audio is fine but video looks like its skipping frames. The computer it plays on has a 5060ti and has the issue on both 580 and 590 series drivers. Works fine in chromium browsers. I tried out the beta app but get black artifacts on the screen during playback. I would be eternally grateful for any help. embyserver.txt

Just installed on cachyos cause ive been having issues with videos stuttering in theater. I get strange artifacts on the screen during playback.

1. TheTVDB 2. TheMovieDb (these were the default settings at the time of creating of this Movie-type library) I discovered the area where I can filter for duplicates. About half of the duplicates are correctly grouped, the other half having grouped two or more unrelated movies together. How do I ungroup them? Regarding the movie in question (Ex Machina), it is not in any of the duplicates.

https://developer.roku.com/en-gb/docs/developer-program/dev-tools/resource-monitor.md https://developer.roku.com/en-gb/docs/developer-program/dev-tools/brightscript-profiler.md I knew I checked the forum at the right time. You can sort of do most of this already using the Roku Resource Monitor together with the Brightscript Profiler. But it is grunt work. You can fix the slowdowns and find your culprits and which line of code in which sections is doing too much work. But you must know how to read the graphs and everything in those apps. The brightscript profiler has to be built into the app so it can provide feedback from within the app to outside of it. There are small nuances that make it both easier and harder to do it this way. But if someone was already proficient with Perfetto (which I am not) it would be simple to watch in real time. The Roku Resource Monitor lets you also watch in real time, but it is a little laggy, which is fine you can still see everything, but it isn't bleeding edge live. But live really doesn't matter when debug Roku applications. It might if we were having issues with video playback. But this isn't where we suffer issues. https://blog.roku.com/developer/rsg-1-3 The bigger news is hidden in this blog post. Roku made sure to send a scary email to all developers that this must completed by October of 2026 so we have a little time. But they are making sure that apps are using the most efficient methods to distribute data around their apps. So there is less crashing, less complaints, and more happy Roku users. We have some parts that will benefit from those changes and speed things up, but for the most part any improvements have already been made by us some while ago to avoid anything that would greatly impact speed. But wring every bit of milliseconds you can out of things here, there, and everywhere, perhaps it will improve load times with responses and some render times. Those are the areas where parsing (exchange fields) are slowing things down. With those new components Roku added in v15 we should be able to get things somewhat faster. There is new updates coming to the Roku app in several areas to improve things. The new v15 improvements will need to happen by October 2026 so you will see those in an update probably closer to around that time. But it isn't like we aren't already working on some of that. I know all my Roku devices have updated to v15 already. So we can almost safely assume all devices which can update via the Roku store and obtain a new app would not crash if running code specific to only v15. It is a super pain to have to support both methods old and new in one app. That is why the switch would happen not immediately. But by that Oct 2026 time for sure. Read this part below closely.. it affects you... Roku OS update policy changes Roku’s OS update policy focuses on automatic, continuous updates for security, performance, and new features, which ensures Roku devices stay current without any user action (manual updates are always available via Settings > System > Software Update). Updates include security patches and feature enhancements that are deployed in stages from beta to general availability. Newer current models and updatable older models receive these automatic updates; however, discontinued (legacy) models do not. Furthermore, legacy models freeze the app versions running on their final Roku OS version. To achieve 100% device updates, Roku will begin checking for updates upon device boot and force an update when needed as part of the Roku OS 15.2 release. Although this can be done on older Roku OS versions via a config service flag, which is also being explored for Roku OS 15.2, the mandatory updates will become standard policy starting with Roku OS 15.2. With Roku OS updates being mandatory, Roku wants all users to benefit from the newest Roku OS features in all apps on our platform. Similarly, all apps can take advantage of the latest Roku OS and leverage the new APIs provided by that release. Your last app update will continue to serve devices that have not yet updated to the latest Roku OS, as Roku does a progressive, verified update across our installed base.

I believe this was sent to developers some time ago but: Roku Launches New Tools To Speed Up Its Apps & Improve Streaming I read most of that and I know if I were still able to code and wanted to code for Roku it would be of great interest to me. At least I hope someone finds it of interest.

The fix for this is simple. Don't use the type of subs that cause the problem or, do like I do, and don't use subs at all except for the very rare places where it is unavoidable. There seems to be a problem with burning in subs and you really need the subs there is a way to use programs like Handbrake to produce a video that have with the subs actually as part of the video. I use that for the few videos I have that are in a language I do not understand, like the ones I have in Tagalog. I see no advantage but a LOT of disadvantages to using external sub files and burdening Emby or Plex or Kodi or Jellyfin or any other media playback program with a lot of unneeded extra work.

Image based subtitles are a serious problem. They were designed to be used in a closed eco-system and burning them in is single threaded and requires an ungodly powerful system. I've discussed this before in the hardware thread, where my i5-1235u can only handle 1 burn in with pgssubs. 1. That's it, that's all. Even Plex and Jellyfin struggle with PGS.

I ran into the exact same issue on my setup (Intel Arc A380 / DG2, Emby 4.9.x on Unraid) and spent some time digging into the root cause. What's happening: Emby's ffdetect queries the Intel MFX runtime for HEVC encoder capabilities, and the runtime returns MaxLevel = 153 (HEVC Level 5.1). Emby then maps Level 5.1 to a max bitrate of 39 Mbps per the HEVC spec, and rejects the hardware encoder for any content above that threshold — falling back to software libx265. But it's not a hardware limitation. The Intel vpl-gpu-rt driver source code sets MaxcodecLevel = MFX_TIER_HEVC_HIGH | MFX_LEVEL_HEVC_62 (Level 6.2 High Tier) in its codec description. The Level 5.1 value returned by the runtime query seems to reflect the minimum guaranteed level for default parameters, not the hardware's actual ceiling. As @embart0r demonstrated, ffmpeg with hevc_qsv happily encodes at 80-100 Mbps on the same hardware without issue. I've confirmed this on my Arc A380. After working around the cap, I've been running multiple concurrent 4K HEVC transcodes at 50-67 Mbps, all on hardware with the CPU basically idle. Workaround: I put together a script that patches Emby.Media.Model.dll to raise the Level 5.1 bitrate cap from 40,000 kbps to 160,000 kbps (a 2-byte hex edit). It's reversible, idempotent, and designed to be re-run after Emby updates. Details and source here: https://github.com/jesposito/emby-hevc-qsv-fix I also filed this as an issue with the Emby team: https://github.com/MediaBrowser/Emby/issues/3956 Ideally Emby could address this properly... perhaps by allowing a user override for the reported max bitrate, or by querying the hardware capability more aggressively. To be clear, the script is not tested by anyone but me and anyone using it does so at their own risk. @Cobester — you mentioned seeing the same 39 Mbps cap on a 14th gen CPU. The script should work for your setup too since the root cause is the same (MFX runtime reporting Level 5.1). Would be great to get confirmation on non-DG2 hardware if you're willing to try it.

I think we can all agree it’s pretty useless to bitch about this. It is very clear that live tv is not a priority for emby and they don’t care about those of us that do. So we either need to use it as it is or move on.

Today I was logged into my Emby server and noticed the Emby tray icon was not showing. I went into Task Manager and sure enough, no Emby Server. So, I manually started Emby Server. The tray icon showed up briefly and then it was gone. I rebooted the computer, logged in and saw the Emby Server icon show up in the tray again and then disappear. I checked my hard drive, plenty of open space. I deleted the Library.db file. Rebooted. Same thing. I re-installed the latest version of Ember server and rebooted. Same thing. I finally checked the log file and I'm getting the following error. Can anyone tell me what happened and what I need to do to fix it? I'm not new to Emby. I've been running it for many years. I hadn't changed anything in settings for a long time. This just happened out of thin air. Any help would be greatly appreciated! 2026-02-22 15:59:21.792 Error GlobalExceptionHandler: UnhandledException *** Error Report *** Version: 4.9.3.0 Command line: C:\Users\soopa\AppData\Roaming\Emby-Server\system\EmbyServer.dll Operating system: Microsoft Windows 10.0.19045 OS/Process: x64/x64 Framework: .NET 8.0.22 Runtime: C:/Users/soopa/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll Processor count: 4 Data path: C:\Users\soopa\AppData\Roaming\Emby-Server\programdata Application path: C:\Users\soopa\AppData\Roaming\Emby-Server\system System.InvalidCastException: System.InvalidCastException: [A]Emby.Dlna.DlnaOptions cannot be cast to [B]Emby.Dlna.DlnaOptions. Type A originates from 'Emby.Dlna, Version=1.5.4.0, Culture=neutral, PublicKeyToken=null' in the context '"Assembly.Load(byte[], ...)" System.Runtime.Loader.IndividualAssemblyLoadContext #8' in a byte array. Type B originates from 'Emby.Dlna, Version=1.5.4.0, Culture=neutral, PublicKeyToken=null' in the context '"Assembly.Load(byte[], ...)" System.Runtime.Loader.IndividualAssemblyLoadContext #9' in a byte array. at MediaBrowser.Common.Configuration.ConfigurationManagerExtensions.GetConfiguration[T](IConfigurationManager manager, String key) at Emby.Dlna.ConfigurationExtension.GetDlnaConfiguration(IConfigurationManager manager) at Emby.Dlna.Main.DlnaEntryPoint.ReloadComponents(CancellationToken cancellationToken) at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state) at System.Threading.ExecutionContext.RunForThreadPoolUnsafe[TState](ExecutionContext executionContext, Action`1 callback, TState& state) at System.Threading.QueueUserWorkItemCallback`1.Execute() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart() Source: System.Private.CoreLib TargetSite: System.Object ChkCastAny(Void*, System.Object) 2026-02-22 15:59:21.792 Info App: Entry point completed: Emby.Server.Implementations.Library.DeviceAccessEntryPoint. Duration: 9.36E-05 seconds 2026-02-22 15:59:21.792 Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup 2026-02-22 15:59:21.806 Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.0138036 seconds 2026-02-22 15:59:21.806 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint 2026-02-22 15:59:21.806 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 5.08E-05 seconds 2026-02-22 15:59:21.806 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake 2026-02-22 15:59:21.806 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 2.61E-05 seconds 2026-02-22 15:59:21.806 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier 2026-02-22 15:59:21.806 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0001138 seconds 2026-02-22 15:59:21.806 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LogLibrariesEntryPoint 2026-02-22 15:59:21.806 Info App: Libraries Server Configuration: CollapseVideoFolders: True 2026-02-22 15:59:21.806 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LogLibrariesEntryPoint. Duration: 0.000156 seconds 2026-02-22 15:59:21.806 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier 2026-02-22 15:59:21.807 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0002096 seconds 2026-02-22 15:59:21.807 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard 2026-02-22 15:59:21.807 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 6.31E-05 seconds 2026-02-22 15:59:21.807 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents 2026-02-22 15:59:21.807 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 2.07E-05 seconds 2026-02-22 15:59:21.807 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier 2026-02-22 15:59:21.807 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 5.14E-05 seconds 2026-02-22 15:59:21.807 Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint 2026-02-22 15:59:21.810 Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0030843 seconds 2026-02-22 15:59:21.810 Info App: Starting entry point Emby.LiveTV.EntryPoint 2026-02-22 15:59:21.810 Info LiveTV: Loading live tv data from C:\Users\soopa\AppData\Roaming\Emby-Server\programdata\data\livetv\timers 2026-02-22 15:59:21.811 Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.001113 seconds 2026-02-22 15:59:21.811 Info App: Starting entry point Emby.LiveTV.RecordingNotifier 2026-02-22 15:59:21.811 Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0001244 seconds 2026-02-22 15:59:21.811 Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint 2026-02-22 15:59:21.813 Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.0022981 seconds 2026-02-22 15:59:21.814 Info App: Starting entry point Emby.Notifications.NotificationManagerEntryPoint 2026-02-22 15:59:21.830 Info Main: Closing tray icon 2026-02-22 15:59:21.830 Info HttpClient: POST http://127.0.0.1:8024/exit 2026-02-22 15:59:21.835 Info Notifications: Registering event nofitier Activity Log 2026-02-22 15:59:21.835 Info Notifications: Registering event nofitier Emby Server User Notifications 2026-02-22 15:59:21.835 Info Notifications: Registering event factory CoreNotificationTypeFactory 2026-02-22 15:59:21.835 Info Notifications: Registering event factory BackupNotificationTypeFactory 2026-02-22 15:59:21.835 Info Notifications: Registering event factory BackupNotificationTypeFactory 2026-02-22 15:59:21.846 Info App: Entry point completed: Emby.Notifications.NotificationManagerEntryPoint. Duration: 0.0325017 seconds 2026-02-22 15:59:21.846 Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint 2026-02-22 15:59:21.846 Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0002812 seconds 2026-02-22 15:59:21.846 Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint 2026-02-22 15:59:21.872 Info HttpClient: Http response 200 from http://127.0.0.1:8024/exit after 42ms 2026-02-22 15:59:21.876 Info Main: tray icon WaitForExit 2026-02-22 15:59:21.897 Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0507313 seconds 2026-02-22 15:59:21.897 Info App: Starting entry point CoverArt.ServerEntryPoint 2026-02-22 15:59:21.901 Info CoverArt: CoverArt plugin loading SkiaCoverArtImageProcessor image processor 2026-02-22 15:59:21.903 Info CoverArt: CoverArt plugin loading NetVipsCoverArtImageProcessor image processor 2026-02-22 15:59:21.911 Info App: Init BeginReceive on 0.0.0.0 2026-02-22 15:59:21.911 Info App: Init BeginReceive on 0.0.0.0 2026-02-22 15:59:21.911 Info App: Init BeginReceive on 10.0.0.232 2026-02-22 15:59:21.911 Info App: Init BeginReceive on 127.0.0.1 2026-02-22 15:59:22.016 Info HttpClient: POST https://mb3admin.com/admin/service/registration/validate 2026-02-22 15:59:22.021 Info App: Entry point completed: CoverArt.ServerEntryPoint. Duration: 0.1239535 seconds 2026-02-22 15:59:22.021 Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding 2026-02-22 15:59:22.022 Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.0009212 seconds 2026-02-22 15:59:22.022 Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding 2026-02-22 15:59:22.023 Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.000601 seconds 2026-02-22 15:59:22.023 Info App: Starting entry point Emby.Security.PluginSecurityManager 2026-02-22 15:59:22.023 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 3.2E-05 seconds 2026-02-22 15:59:22.023 Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint 2026-02-22 15:59:22.023 Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 8.35E-05 seconds 2026-02-22 15:59:22.023 Info App: Starting entry point Emby.Security.PluginSecurityManager 2026-02-22 15:59:22.023 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 3.02E-05 seconds 2026-02-22 15:59:22.023 Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint 2026-02-22 15:59:22.023 Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 6.95E-05 seconds 2026-02-22 15:59:22.023 Info App: Starting entry point MBBackup.ServerEntryPoint 2026-02-22 15:59:22.023 Info App: Entry point completed: MBBackup.ServerEntryPoint. Duration: 2.58E-05 seconds 2026-02-22 15:59:22.023 Info App: Starting entry point MBBackup.ServerEntryPoint 2026-02-22 15:59:22.023 Info App: Entry point completed: MBBackup.ServerEntryPoint. Duration: 4.57E-05 seconds 2026-02-22 15:59:22.023 Info App: Starting entry point MediaBrowser.Plugins.Trailers.EntryPoint 2026-02-22 15:59:22.023 Info App: Entry point completed: MediaBrowser.Plugins.Trailers.EntryPoint. Duration: 2.35E-05 seconds 2026-02-22 15:59:22.023 Info App: Starting entry point NfoMetadata.EntryPoint 2026-02-22 15:59:22.023 Info App: Entry point completed: NfoMetadata.EntryPoint. Duration: 0.0001028 seconds 2026-02-22 15:59:22.023 Info App: Starting entry point NfoMetadata.EntryPoint 2026-02-22 15:59:22.023 Info App: Entry point completed: NfoMetadata.EntryPoint. Duration: 7.65E-05 seconds 2026-02-22 15:59:22.023 Info App: Starting entry point Tvdb.EntryPoint 2026-02-22 15:59:22.023 Info App: Entry point completed: Tvdb.EntryPoint. Duration: 2.68E-05 seconds 2026-02-22 15:59:22.023 Info App: Starting entry point Tvdb.EntryPoint 2026-02-22 15:59:22.024 Info App: Entry point completed: Tvdb.EntryPoint. Duration: 2.63E-05 seconds 2026-02-22 15:59:22.024 Info App: All entry points have started 2026-02-22 15:59:22.183 Info Main: tray icon exited

Is this plug-in operating correctly anymore? It did exactly what I expected it to on my last Emby install where it could monitor a folder and then automatically grab files that were already given a proper naming convention and putting them into the correct movie or TV show folder for Emby to apply metadata to. I have reinstalled Emby on a new Synology and when using this plug-in I only get the error mentioned above in this thread. They're also used to be a way to manually identify a movie / TV show that's in the folder but that seems to be gone in the auto organize section. This plug-in doesn't seem to do anything correctly or use useful right now… Is this just me?

1. Le choix du 1080p vs 4K Tu as raison sur un point crucial : la 4K est une dévoreuse de ressources. Stockage : Un film en 4K peut peser 4 à 5 fois plus lourd qu'une version 1080p bien compressée. Bande passante : Streamer de la 4K à l'extérieur demande une connexion solide, ce que tous les invités n'ont pas forcément. Transcodage : Si le client ne peut pas lire le fichier brut, ton CPU/GPU va souffrir pour transcoder de la 4K en temps réel. En résumé : Rester sur du full HD (1080p) est le "sweet spot" pour garantir que tout le monde puisse lire le contenu sans buffering, tout en gardant une image très propre. 2. Pourquoi les logs plutôt que la détection HEVC ? Ma méthode de fichier .txt a un avantage majeur : la rapidité. Scanner chaque fichier avec un outil comme ffprobe pour vérifier s'il est déjà en HEVC prend quelques secondes par fichier. Sur une grosse bibliothèque, cela peut ralentir le lancement du script. Cependant, si tu veux rendre le script plus "intelligent" à l'avenir, voici comment fonctionne la détection automatique : Avantages de la détection automatique via script : Zéro maintenance : Pas besoin de gérer un fichier texte qui peut être supprimé par erreur. Précision : Si tu ajoutes un fichier déjà en HEVC manuellement, le script le sautera tout seul sans que tu aies besoin de l'inscrire dans ton log. Une petite astuce pour le script Si tu veux un jour mixer tes deux idées (logs + détection), tu peux ajouter une ligne de commande simple avec ffprobe pour vérifier le codec avant de lancer ffmpeg. Par exemple, en Bash : ffprobe -v error -select_streams v:0 -show_entries stream=codec_name -of default=noprint_wrappers=1:nokey=1 "ton_fichier.mp4" Si le résultat est hevc, tu passes au suivant. Sinon, tu convertis et tu logues.

Hello jvickers, ** This is an auto reply ** Please wait for someone from staff support or our members to reply to you. It's recommended to provide more info, as it explain in this thread: Thank you. Emby Team

I am new to using Emby. All of a sudden all remote connections are freezing on playback. This just started this morning and everything worked great before. No changes were made so I hope someone can help figure this out. embyserver-63907353388.txt ffmpeg-transcode-9f0da7ea-f4bb-410f-949a-82a7ba0f899a_1.txt

Kinda what I thought. Thanks for verifying.

It was what was available from the guide at the time. Live events like these don't always have distinct episode numbers.

Unfortunately, the file system containing my movies has become corrupted. Fortunately, the file system containing emby is intact. I wanted to know if the emby database stores the media file checksum so I can use it to identify corrupted movies. Thanks

At least an official statement regarding the bug and its fix is needed. They said it would be fixed a month ago, and nothing has been done since. LG users are constantly experiencing problems; sometimes we feel abandoned.

I'm still having the same issue after the LG .50 update. It no longer has the strange characters in the subs but they're still positioned in the top left corner and it's putting most of it off screen

Hi, we are working on this. Thanks.

I think my Raid Array failed. It was probably going bad causing the issues. I rebooted the system and the box is recognized, but the drives appear as unconfigured. 4 TB may be gone. I had 2 2tb drives configured in stripe mode. I will investigate more fully when I have time. - Techowl -

Any updates on this?