DevXen
-
Posts
73 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by DevXen
-
-
6 hours ago, DoeBoye said:
Yup. Fixed. I had to roll back as well, but no issues with this one.
Awesome. I'll update tomorrow. Thank you.
-
i didn't see it in the release notes. but does this resolve the adaptec 7000 series card issues that .6 had. i had to roll back to .4 to fix it,. it was an issue with the then current version of the kernel i guess. but if it's not fixed then I guess i'm stuck on .4 still.
-
just saw this all over my logs. any idea how to fix it?
Mar 2 15:59:52 MediaXen kernel: clocksource: timekeeping watchdog on CPU12: hpet wd-wd read-back delay of 108603ns
Mar 2 15:59:52 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 102736ns, clock-skew test skipped!
Mar 2 16:47:46 MediaXen flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Mar 2 16:59:55 MediaXen kernel: clocksource: timekeeping watchdog on CPU18: hpet wd-wd read-back delay of 66279ns
Mar 2 16:59:55 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 104761ns, clock-skew test skipped!
Mar 2 17:05:44 MediaXen kernel: clocksource: timekeeping watchdog on CPU21: hpet wd-wd read-back delay of 62577ns
Mar 2 17:05:44 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 102806ns, clock-skew test skipped!
Mar 2 17:15:01 MediaXen kernel: clocksource: timekeeping watchdog on CPU6: hpet wd-wd read-back delay of 61530ns
Mar 2 17:15:01 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 179911ns, clock-skew test skipped!
Mar 2 17:24:10 MediaXen kernel: clocksource: timekeeping watchdog on CPU1: hpet wd-wd read-back delay of 56850ns
Mar 2 17:24:10 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 178514ns, clock-skew test skipped!
Mar 2 17:52:08 MediaXen kernel: clocksource: timekeeping watchdog on CPU20: hpet wd-wd read-back delay of 97707ns
Mar 2 17:52:08 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 117263ns, clock-skew test skipped!
Mar 2 17:59:45 MediaXen monitor: Stop running nchan processes
Mar 2 19:02:57 MediaXen kernel: clocksource: timekeeping watchdog on CPU18: hpet wd-wd read-back delay of 106927ns
Mar 2 19:02:57 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 106228ns, clock-skew test skipped!
-
2 issues...
1. Starting with my backup last week I started getting errors for directories it says aren't there.
Event: Appdata Backup Subject: [AppdataBackup] Error! Description: Please check the backup log! Importance: alert '/mnt/disks/SSD/appdata/apache-php/logs' does NOT exist! Please check your mappings! Skipping it for now. --- '/mnt/disks/SSD/www' does NOT exist! Please check your mappings! Skipping it for now. --- '/dev/shfs' does NOT exist! Please check your mappings! Skipping it for now. --- '/mnt/disks/Docker_SSD/plex-utills/logs' does NOT exist! Please check your mappings! Skipping it for now. *Side note I've never had a docker_ssd mapping or drive* --- '/tmp/xteve' does NOT exist! Please check your mappings! Skipping it for now.----
2. Last week it took 4 and a half hours. Which is typical.. But that one last night took over 8 hours. Nothing has changed on my server in the last week.
Event: Appdata Backup Subject: Appdata Backup Description: Backup done [4h, 29m]! Importance: normal The backup was successful and took 4h, 29m! --- Event: Appdata Backup Subject: Appdata Backup Description: Backup done [8h, 5m]! Importance: normal The backup was successful and took 8h, 5m! -
I got a new server on eBay. Holds more drives and such and I would like to double check that I can move from
Adaptec ASR-72405 RAID controller (in hba mode)
To:
AOC-S3008L-L8e HBA (in it mode)
Without any problems.
I've read a few posts of people that have started the adaptec in simple mode in accident and it erased the drives on boot..and others I've read they had to rebuild the data on each drive 1-2 at a time. Cause the raid card keeps the partition outside of the drive I guess. (Not adaptec specifically and I dunno if they had their cards in hba mode)
I did replace my adaptec card when the current newest update had issues with the series 7 cards. (I rolled back the version.) But shen I got the new adaptec card I had to reassign each card as it assigned random different characters to the serial number of each drive..
So I just went to check if I can move from the adaptec in hba mode to this new card in IT mode. Also if anyone knows how to check it's in IT mode. That would be great too.
Thank you,
-Dev
-
How serious of an issue is this? It keeps happening with different CPU numbers? It keeps coming up in my logs online it said to very it to hpet which I did but it's still doing it.
Jan 1 06:05:11 MediaXen kernel: clocksource: timekeeping watchdog on CPU3: hpet wd-wd read-back delay of 62158ns
Jan 1 06:05:11 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 176069ns, clock-skew test skipped!Jan 1 08:14:43 MediaXen kernel: clocksource: timekeeping watchdog on CPU18: hpet wd-wd read-back delay of 69771ns
Jan 1 08:14:43 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 118520ns, clock-skew test skipped!Jan 1 08:56:06 MediaXen kernel: clocksource: timekeeping watchdog on CPU17: hpet wd-wd read-back delay of 55873ns
Jan 1 08:56:06 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 179422ns, clock-skew test skipped!Jan 1 10:14:01 MediaXen kernel: clocksource: timekeeping watchdog on CPU7: hpet wd-wd read-back delay of 65022ns
Jan 1 10:14:01 MediaXen kernel: clocksource: wd-tsc-wd read-back delay of 121942ns, clock-skew test skipped! -
9 hours ago, biggiesize said:
Looks like a setting from an older version of the template. Edit the container and change the icon url to this:
Just tried that. Thank you.
-
hey I've been getting this in my syslog over and over. not sure how to fix it?
root: ddns-updater: Could not download icon https://github.com/DiamondPrecisionComputing/unraid-templates/blob/main/templates/img/ddnsgopher.png?raw=true
-
43 minutes ago, Kilrah said:
Shows up as a vm_meta.tgz archive with the contents of /etc/libvirt/qemu here.
Awesome..I found it. In thank you..10k filesize.. But it's there.
-
I'm not sure if this is an issue but I just did my first scheduled backup with this new plugin. And I have VM meta checked as yes. But I couldn't find that or the libvert backed up anywhere in the backups. But as it says VM meta I'd assume it's not backing up the libvert anymore and just the meta data it uses to create the VMs? Either way I want able to find any VM related backup files. But my flash backup was there.
-
On 12/14/2023 at 1:40 AM, JorgeB said:
There is a regression in the driver in the latest kernels affecting the Adaptec 7 series controllers that use the aacraid driver, e.g., asr-72405, 71605, 71685, possibly others, for now you should remain on v6.12.4, see below for more info:
This absolutely fixed my issue. was able to rebuild both drives that had been disabled. and all is good.
any idea on how i can follow that to know when the driver in the kernel will be updated to fix this? so i know when i can upgrade my unraid again?
-
1 hour ago, sataris said:
is there a guide somewhere to downgrade from 6.12.6?
Here I just found this....
-
1
-
-
1 hour ago, sataris said:
is there a guide somewhere to downgrade from 6.12.6?
Yeah I need to downgrade too. I was on 6.11.5 and upgraded to the latest I think 6.12.6. so I can't revert to 6.12.4 not sure how I would go About that.
-
My hba card went out (I think) so I got a new one. Put it in. Set it to HBA mode. All my drives said wrong. Looking it up online it said it said to do a new config and that should fix it. However it says on the parity drives all the data will be overwritten.
One of my drives was in the middle of rebuilding so it needs to be rebuilt.
Here's some History...
I got a notification that 2 drives were disabled due to write errors. So I replaced them let them rebuild. 2 days later I woke up to an email saying 2 drives were disabled due to read errors, one being one that I replaced. - I ran chkdsk on Uber 2 I already replaced looking for bad sectors. Took like a week but not drives were fine..
So I decided to rebuild one of the disabled drives on it's self. Things were going well so I left. They got an email that another drive had gotten over 300 read errors.. like an hour later. So I shut down the server until I could replace my controller card.
So now I've replaced it. All the drives said they were wrong when j tried to assign them. But looking it up online it said to do a new config. But now I'm assigning them it says all existing data on will be overwritten when array starts.
I saw I can click at the bottom parity is valid.. will that stop it from being overwritten when I start it. and do I then stop it. Unassigned the disk that needs to be rebuilt then start the array then stop it then reassign. It. Then start the array to rebuild it?
knowing it needs to rebuild and onto has partial data will that cause an issue when I start the array?
thanks,
-Dev
-
11 minutes ago, Sardine8207 said:
I've had read errors multiple times, in my experience it's always been due to those fragile SAS breakout cables going bad. I had my server wall mounted, and the drive trays would slip down occasionally, pinching/chafing the data cables. You will get some better advice here soon enough.
Have you run a smart report on the disk?
No. I tried with the first ones that had write errors and the smart tests stuck At 100% and would never finish. But the diagnostics have the smart info for each drive I saw so that's good.
Here's a little back story... (Didn't put it here cause I already posted a different post about it. But here...
On Sat I had 2 drives disabled for write errors. Then I swapped them out and rebuilt data separately on them. Took one out ran an extensive chkdsk looking for bad sectors. It didn't find any. The second one still has like 6 days to go on it's check but so far no errors.
And then today I woke up to 2 drives disabled due to read errors. One brand New one I replaced on Sat and a different drive in the array.
About 3 hours into the rebuild on one of the drives I got 2 more drives with read errors.
So at that point I turned my server off. Thinking it's the hba controller card or the cables. But it would be strange for multiple cables die at the same time. They are really thick cables. Here's a pic.
-
-
So I'm rebuilding my parity on one of my 2 drives that was disabled earlier today for free l read errors and not 3a 3rs one has had read errors. Not sure what to do..
-
I woke up to 2 drives with read errors, one had 9, one had 32, this after having 2 drives with write errors a few days ago and replacing them. but scanning them in chkdsk for bad sectors in windows didn't find anything wrong with the previous 2 drives.
So i'm rebuilding parity on one of the drives with read errors., but this keeps pulling up, and the server seems to hang for a bit when it does. also the parity rebuild goes from 1day to fluxuates between 10-70 days) can only guess this is the issue...
Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,16,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,16,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,16,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,6,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,6,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,6,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,6,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,6,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,12,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,4,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,4,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,4,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,3,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,3,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,9,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,9,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,9,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,5,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,5,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,5,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,11,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,11,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,11,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,11,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,11,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,11,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,11,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,13,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,13,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,14,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,14,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,14,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,21,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,10,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,10,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,10,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,10,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,15,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,15,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,7,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,7,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host adapter abort request. Dec 5 16:36:21 MediaXen kernel: aacraid: Outstanding commands on (4,1,7,0): Dec 5 16:36:21 MediaXen kernel: aacraid: Host bus reset request. SCSI hang ? Dec 5 16:36:21 MediaXen kernel: aacraid 0000:82:00.0: outstanding cmd: midlevel-0 Dec 5 16:36:21 MediaXen kernel: aacraid 0000:82:00.0: outstanding cmd: lowlevel-0 Dec 5 16:36:21 MediaXen kernel: aacraid 0000:82:00.0: outstanding cmd: error handler-0 Dec 5 16:36:21 MediaXen kernel: aacraid 0000:82:00.0: outstanding cmd: firmware-42 Dec 5 16:36:21 MediaXen kernel: aacraid 0000:82:00.0: outstanding cmd: kernel-0 Dec 5 16:36:21 MediaXen kernel: aacraid 0000:82:00.0: Controller reset type is 3 Dec 5 16:36:21 MediaXen kernel: aacraid 0000:82:00.0: Issuing IOP reset -
9 minutes ago, JorgeB said:
In my experience unlikely that two disks getting disabled at the same time would be a disk problem.
Dec 5 06:20:03 MediaXen kernel: aacraid: Host bus reset request. SCSI hang ? Dec 5 06:20:03 MediaXen kernel: aacraid 0000:82:00.0: outstanding cmd: midlevel-0 Dec 5 06:20:03 MediaXen kernel: aacraid 0000:82:00.0: outstanding cmd: lowlevel-0 Dec 5 06:20:03 MediaXen kernel: aacraid 0000:82:00.0: outstanding cmd: error handler-28 Dec 5 06:20:03 MediaXen kernel: aacraid 0000:82:00.0: outstanding cmd: firmware-33 Dec 5 06:20:03 MediaXen kernel: aacraid 0000:82:00.0: outstanding cmd: kernel-0 Dec 5 06:20:03 MediaXen kernel: aacraid 0000:82:00.0: Controller reset type is 3 Dec 5 06:20:03 MediaXen kernel: aacraid 0000:82:00.0: Issuing IOP reset Dec 5 06:20:59 MediaXen kernel: aacraid 0000:82:00.0: IOP reset succeededLooks more like a controller issue, but not very familiar with these controllers, see if it's well seated or try a different PCIe slot, or if you have another you could try with, like an LSI HBA do it.
I don't have another one i can try with. it's weird cause it's been working fine for the last 4 years i guess. i'll try resenting it in the server. then do i just unassign both these disks then reassign them and rebuild parity one them? - one at a time?
it was weird cause like i said i replaced 2, one at a time just a few days ago and the parity rebuild ran fine on both of them which is pretty intensive for the drives i hear.
-
Sunday i woke up to an email with 2 of my disks (one of my parity drives, and disk 4) disabled for write errors. i replaced both disks with new 14tb drives. the first disk i ran through chkdsk looking for bad sectors in windows and after 1.2 days it didn't find any errors. the 2nd disk is still checking and has like 7 days to go looking for bad sectors.
i installed each disk one at a time then did the parity rebuild. everything finished with no problems.
I then yesterday updated the Unraid OS to 6.12.6. (I was on 6.11.5). and i had been copying 4TB From my Array to my newly free disk i took out of the array. which is now going to be a cold storage backup disk. it copied that for 2 days i think (but i paused it to update the OS). resumed it last night. had no issues.
woke up today 2 of my disks are disabled due to read errors. one of them being one of the disks I replaced a couple days ago. then a few hours later 4 more disks i think it was that had 1 read error each. so i'm not sure what to do. i'm probably going to replace the one that was disabled that hasn't been replaced yet. then check it as well in chkdsk.
but here's my diagnostics i'm not sure whats causing this or how to fix it. if someone there can look through them and help me out, that would be great.
thank you.
-Dev
-
Haven't had time to check out the update. I'll mess with it this weekend after work. But did we get the option to add the YouTube id and the name to the files yet by chance?
-
So i installed Kavita last night and let it scan my ebooks/comics/etc.
I'm getting this error:
There was an issue writing to the DB for Series API.Entities.Series An error occurred while saving the entity changes.
See the inner exception for details.
Not sure how to get to the inner exception. but i have included pics. and this is from the docker log..
Quote[Kavita] [2023-04-02 18:08:07.395 -06:00 71] [Error] Microsoft.EntityFrameworkCore.Database.Command Failed executing DbCommand (2ms) [Parameters=[@p0='?' (Size = 9), @p1='?' (Size = 9)], CommandType='"Text"', CommandTimeout='30']
INSERT INTO "Genre" ("NormalizedTitle", "Title")
VALUES (@p0, @p1);
SELECT "Id"
FROM "Genre"
WHERE changes() = 1 AND "rowid" = last_insert_rowid();
[Kavita] [2023-04-02 18:08:07.405 -06:00 71] [Error] Microsoft.EntityFrameworkCore.Update An exception occurred in the database while saving changes for context type 'API.Data.DataContext'.
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
[Kavita] [2023-04-02 18:08:07.410 -06:00 71] [Fatal] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] There was an issue writing to the database for series Age of Heroes
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at API.Data.UnitOfWork.CommitAsync() in /home/runner/work/Kavita/Kavita/API/Data/UnitOfWork.cs:line 81
at API.Services.Tasks.Scanner.ProcessSeries.ProcessSeriesAsync(IList`1 parsedInfos, Library library, Boolean forceUpdate) in /home/runner/work/Kavita/Kavita/API/Services/Tasks/Scanner/ProcessSeries.cs:line 206
[Kavita] [2023-04-02 18:08:07.413 -06:00 71] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Beginning series update on 201507 Avengers in Gearing Up
[Kavita] [2023-04-02 18:08:07.461 -06:00 71] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Processing series 201507 Avengers in Gearing Up
[Kavita] [2023-04-02 18:08:07.461 -06:00 71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Updating 1 volumes on 201507 Avengers in Gearing Up
[Kavita] [2023-04-02 18:08:07.462 -06:00 71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Looking up volume for 0
[Kavita] [2023-04-02 18:08:07.462 -06:00 71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Parsing 201507 Avengers in Gearing Up - Volume 0
[Kavita] [2023-04-02 18:08:07.462 -06:00 71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Adding new chapter, 201507 Avengers in Gearing Up - Vol 0 Ch 1
[Kavita] [2023-04-02 18:08:07.574 -06:00 14] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Finished series update on Secret in 6506 ms
[Kavita] [2023-04-02 18:08:07.574 -06:00 14] [Debug] API.Services.MetadataService [MetadataService] Processing cover image generation for series: Secret
[Kavita] [2023-04-02 18:08:07.577 -06:00 14] [Debug] API.Services.MetadataService [MetadataService] Generating cover image for /library/[Comics]/[New]/[From DC++]/Marvel (2019)/0/Nueva carpeta/Comics/2012/4/Abril 2012 1ª quincena/Secret 001 (2012) (Digital) (Fawkes-Empire).cbr
[Kavita] [2023-04-02 18:08:07.589 -06:00 71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Updated 201507 Avengers in Gearing Up volumes from count of 0 to 1
[Kavita] [2023-04-02 18:08:07.590 -06:00 71] [Debug] API.Services.Tasks.Scanner.ProcessSeries Updating 201507 Avengers in Gearing Up FolderPath to /library/[Comics]/[New]/[From DC++](process:8): VIPS-WARNING **: 18:08:07.643: unknown JFIF resolution unit
(process:8): VIPS-WARNING **: 18:08:07.659: unknown JFIF resolution unit
(process:8): VIPS-WARNING **: 18:08:07.668: unknown JFIF resolution unit
[Kavita] [2023-04-02 18:08:07.712 -06:00 14] [Debug] API.Services.MetadataService [MetadataService] Generating cover image for /library/[Comics]/[New]/[From DC++]/Marvel (2019)/0/Nueva carpeta/Comics/2012/6/Junio 1 semana 2012/Secret 002 (2012) (Digital) (Fawkes-Empire).cbr
[Kavita] [2023-04-02 18:08:07.812 -06:00 55] [Information] Serilog.AspNetCore.RequestLoggingMiddleware HTTP GET /api/series/6733 responded 200 in 12.5737 ms
[Kavita] [2023-04-02 18:08:07.839 -06:00 14] [Debug] API.Services.MetadataService [MetadataService] Generating cover image for /library/[Comics]/[New]/[From DC++]/Marvel (2019)/0/Nueva carpeta/Comics/2013/8/Agosto 2013/Secret 003 (2013) (Digital) (Fawkes-Empire).cbr
[Kavita] [2023-04-02 18:08:13.611 -06:00 14] [Information] API.Services.MetadataService [MetadataService] Updated covers for Secret in 6036 milliseconds
[Kavita] [2023-04-02 18:08:13.611 -06:00 14] [Debug] API.Services.MetadataService Dispatching 5 update events
[Kavita] [2023-04-02 18:08:13.612 -06:00 14] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Beginning series update on X-Men Series
[Kavita] [2023-04-02 18:08:13.665 -06:00 14] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Processing series X-Men Series
[Kavita] [2023-04-02 18:08:13.665 -06:00 14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Updating 1 volumes on X-Men Series
[Kavita] [2023-04-02 18:08:13.665 -06:00 14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Looking up volume for 0
[Kavita] [2023-04-02 18:08:13.666 -06:00 14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Parsing X-Men Series - Volume 0
[Kavita] [2023-04-02 18:08:13.666 -06:00 14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Adding new chapter, X-Men Series - Vol 0 Ch 1
[Kavita] [2023-04-02 18:08:13.706 -06:00 14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Adding new chapter, X-Men Series - Vol 0 Ch 2
[Kavita] [2023-04-02 18:08:13.795 -06:00 55] [Information] API.Services.Tasks.Metadata.WordCountAnalyzerService [WordCountAnalyzerService] Updated metadata for Secret in 180 milliseconds
[Kavita] [2023-04-02 18:08:14.134 -06:00 14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Updated X-Men Series volumes from count of 0 to 1
[Kavita] [2023-04-02 18:08:14.134 -06:00 14] [Debug] API.Services.Tasks.Scanner.ProcessSeries Updating X-Men Series FolderPath to /library/[Comics]/[New]/[From DC++]
[Kavita] [2023-04-02 18:08:17.540 -06:00 71] [Error] Microsoft.EntityFrameworkCore.Database.Command Failed executing DbCommand (2ms) [Parameters=[@p0='?' (Size = 9), @p1='?' (Size = 9)], CommandType='"Text"', CommandTimeout='30']
INSERT INTO "Genre" ("NormalizedTitle", "Title")
VALUES (@p0, @p1);
SELECT "Id"
FROM "Genre"
WHERE changes() = 1 AND "rowid" = last_insert_rowid();
[Kavita] [2023-04-02 18:08:17.550 -06:00 71] [Error] Microsoft.EntityFrameworkCore.Update An exception occurred in the database while saving changes for context type 'API.Data.DataContext'.
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
[Kavita] [2023-04-02 18:08:17.555 -06:00 71] [Fatal] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] There was an issue writing to the database for series 201507 Avengers in Gearing Up
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
at API.Data.UnitOfWork.CommitAsync() in /home/runner/work/Kavita/Kavita/API/Data/UnitOfWork.cs:line 81
at API.Services.Tasks.Scanner.ProcessSeries.ProcessSeriesAsync(IList`1 parsedInfos, Library library, Boolean forceUpdate) in /home/runner/work/Kavita/Kavita/API/Services/Tasks/Scanner/ProcessSeries.cs:line 206
[Kavita] [2023-04-02 18:08:17.559 -06:00 71] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Beginning series update on 1978-12 Flintstones
[Kavita] [2023-04-02 18:08:17.622 -06:00 71] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Processing series 1978-12 Flintstones
[Kavita] [2023-04-02 18:08:17.623 -06:00 71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Updating 1 volumes on 1978-12 Flintstones
[Kavita] [2023-04-02 18:08:17.623 -06:00 71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Looking up volume for 1
[Kavita] [2023-04-02 18:08:17.624 -06:00 71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Parsing 1978-12 Flintstones - Volume 1and I dunno what to do or how to fix it?
-
Hey i found an issue. - Youtube has changed usernames to have a @ in the beginning. and i think thats causing an issue.
For example I want to get all the videos of this channel: https://www.youtube.com/@8BitUniverse/videos
which it doesn't add, and the log shows:
WARNING:root:Illegal channel-URL
WARNING:root:Illegal playlist-URL -
10 minutes ago, almulder said:
So sorry, I just see your post. Whenever I check my logs the background is black with white text. Mind showing me where your having the issue, and what theme do you have set in Settings/Display Settings/Dynamix color theme
Should be set to black
Hahaha this was fixed long ago. We talked about it in the unRAID group. It was just never replied to on here.
I'm Clint W. On fb..
-
1
-
Adaptec 72405 to Replace Existing Array on LSI 9210-8i ?
in Storage Devices and Controllers
Posted
Hey. Any ideas what would happen if you moved from that adaptec card to an LSI card? I bought a new server a few months ago. And if has a lsi card. Your other post you linked scares the crap out of me in trying to move my hard drives over. But today my adaptec just died (as far as I can tell.) so I'm trying to find a new one. But I'd rather just hook my drives up to the new server. It's faster and holds more.
-Dev