mason

Members
  • Posts

    95
  • Joined

  • Last visited

Everything posted by mason

  1. I tried to find an answer in this threat, but sorry it's just too hughe... since I see to experience problems with my SASLP cards, I guess i try to switch them over to flashed H310, does these support the latest drive size i.e. 12TB?
  2. Good point, taken. But with the additional storage on disk1 I might have some emtpy space then to shuffel stuff around.
  3. Okay, lets see how far it will run... after that I guess I can compare the content of old disk1 against the rebuild one. Then i would be able to replace disk11 maybe without buying another hdd I won't need... (since i would like to downsize the count of discs anyway with the 12TB route) Thanks a lot for your support!
  4. Thanks a lot for your feedback Johnnie! Sounds like a reasonable route to go... will see what I can organize and report back. Currently the rebuild on disk1 is running for 2 hours, it failed the last two times in the first half hour. What would happened if the rebuild will finish successfully? I'm irritated by the unmountable part.
  5. Yes, I have the original disk1 which I intended to preclear. Script was already running but I was only some percent into the preread process which I cancled (for my understanding it should be untouched). And I have a static setup, so nothing was written to the server.
  6. Thanks for the reply jhonnie, I canceled the rebuild, rebooted. server start again to rebuild with disk11 online... like the first 2 times. Looks like disk11 has pending sectors What is the typical SASLP error you mentioned? The server grew 10 years on me with this setup, never had problems with the controller. Okay I found something in the wiki with dropped drives issues on the SASLP with v6 ... I guess I need to throw even more bucks against my server to replace them
  7. Hey there, I'm currently in the process of expanding my unraid server. I have a 20 (18x4TB + 2x2TB) disk unraid server which is much maxed out. So i bought 2x12TB did a parity check, replaced the parity drive with a 12TB, rebuild went fine. So I swapped the first disc with the next 12TB and its throwing errors on disc11 while rebuilding. Rebuild is still running but doesn't seem to write any more to disk1. So I stopped the rebuild, checked the cables and stuff and tried again. Same errors... also disk1 shows now as unformated, I think this was different on the first try. What do do and how to prevent data loss? I have backed up the config and the flash prior to the disc1 rebuild. Also i was in the pre read progress of cleaning the old 4TB disk1 but stopped it. Is it possible to revert back to my configuration with the old disk1 so i can rescue disc11? I'm a little lost here... what are my options?
  8. I just setup this docker, build the db and working fine so far. Mainly I did this to get faster lookups and not hitting any api limits. Unfortunatly looking up albums with the Picard Tagger is even slower than with the official server, anyone knows what might be wrong there? Weblookups working fine in an instant. But if i throw a handfull albums into Picard it takes minutes...
  9. Also, installation of the docker was fine, took 6 hours to update and build db. Now when I do an indexed search I get a 503 regarding a rate limit. Direct DB search is working fine, but headphones won't work properly. Also tried to point the LUCENE variabe in the DBDefs.pm file to point to localhost but doesn't work either. any hints?
  10. looks like: 2.6.9 ======================= IMPORTANT: with tinyMediaManager version 2.7 we do not support Java6 anymore. If you are still using Java6, please update or you will stay at version 2.6.x so I guess the container needs to be updated with java7? since it looks like the container tries to update to the latest version...
  11. Hey there, someone capable of stuffing kvibes MediaElch into an unraid container? I guess this would be pretty helpfull for a lot of people to manage their media... not only for me. Pretty nifty tool, tinymediamanager just has too much issues regarding the nfos for XBMC. http://www.kvibes.de/en/mediaelch/features/ Cheers, mason
  12. thanks for the answer. good to keep this in mind.. for the next upgrade.
  13. Nevermind, right after hiting the post button server started rebuilding... it took 10 minutes to mount the new disk, weird! Hey guys, having trouble with my server again, swapped out a 2TB WD against a precleard Seagate 4TB, but while starting and upgrading array it just hangs while mounting the disk. Webif is not responding anymore and syslog states it just stuck at mounting... any advice? I'm always a little scared rebooting the machine in a undefined state. logfile:
  14. the parity rebuild just finished as expected. Thanks for all the input. I suspect the USB Drive regarding the lost configuration. With a former failed migration to a new faulty disc, unraid generated a 2GB syslog file which was recently copied to the stick earlier, maybe this triggered some bad behavior.
  15. thanks for the detailed information, will try and do so...
  16. thanks for the response, so basically you're saying if i restart the array the parity will get rebuild? So the only thing to make sure is that the parity drive is correctly assigned, preventing overwriting a data disc? just to be sure, better safe than sorry. and i have no idea why it got lost?!
  17. hi, restarted my unraid server to day, just to find out all disks are marked as blue. as far as i see it the assignment of the discs is correct but im not sure if starting the array woud reset the configuration?! Any hints? the only thing i did was migrating disc14 to a new 2TB drive yesterday, but rebuild went flawless. Syslog is attached. syslog.zip
  18. Maybe I was a little vague here, I wasn't after a solution for the problem. I was more about the generel behaviour of the server since I thought, like Falcon, this is the normal behaviour of the whole system since i have this from day one?!
  19. Hi, since I use Unraid i have several problems regarding file operations to the servers. I run 4.7 maxed out with 20 drives. So far it's working well, but i store all my tvshows and media files on the server, so I scan them a lot, make changes, you know the drill. Something that bothers me for quiet some time: If I access the server (SMB connection from Ubuntu and W7) while some other file operation is ongoing the whole thing becomes unresponsive. It takes 10-30 seconds until the operations continue. Am I the only one with this problem? Is there anything I can tweak? My understanding is that unraid is also used for small workgroups, but I really can't believe that since it's locking up constantly with more than one operation to the server. Thanks
  20. I rebuild the array on the WD again, and everythings looking fine... strange. Anyway thanks a lot for your support all! Going to upgrade now to 4.7... to be ready for further hdd crashs.
  21. @christuf my intention with the upgrade to 4.7 was not to worry about jumpers and allignements with further upgrades to new 4k discs. yeah i mixed up the brands since I where at work when I posted. The connections are hopefully fine, I rebuilded the server with most efficient way of cabeling in mind half a year ago to prevent these kind of errors. @lionelhutz sounds good this would be my prefered next step
  22. @bcbgboy13 sorry, mixed this up while posting (where at work) @Joe L. yeah the disk is back up, but of course still red...but since i copied data to it while it might was red, a check and trust my array procedure wouln't be out of the question (as far as i understand it it would result in data loss if I ran a parity check again). Is there maybe a procedure to preclear the disc and rebuild it again?
  23. Thanks for the suggestions... @christuf I know, this wouldn't solve the problem... but I thought its easier without fighting the 4k topic on an old installation. I'll attached a syslog and a smart report for the device... i cut out 10MB of repeating errors like this Apr 3 10:33:49 SPACEHOG kernel: ata11.00: device reported invalid CHS sector 0 Apr 3 10:33:49 SPACEHOG kernel: ata11: status=0x41 { DriveReady Error } Apr 3 10:33:49 SPACEHOG kernel: ata11: error=0x04 { DriveStatusError } Apr 3 10:33:49 SPACEHOG kernel: ata11: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 bevor it shows read errors after that the drive wasn't accessible at all, maybe the system shut it down? I don't know....but the smart report don't indicate anything, atleast how far I can interpret it... unraid.zip
  24. Hi, just wan't a quick confirmation, im running 4.5.6 right now and one of my old Samsung HD203WI Drives seems to making problems (write errors and marked as red). Due to the fact that i can't buy any new ones of this modell I thought of switching to the 4k 204er Modell, all others are non-4k-drives. I would like the most hassle free approach here, can I update unraid to 4.7 and rebuild after onto the new 204er Samsung or is this not recommended? Thanks...