Jump to content

lostwebb

Members
  • Content Count

    77
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lostwebb

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • Location
    Cornwall, UK
  • Personal Text
    UnRAID'r

Recent Profile Visitors

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

  1. I don't know much about the docker, but i found this information about upgrading and some Mongol changes...scroll down to the update to 3.10.2 instructions. Might not mean anything though. https://github.com/exsilium/docker-unifi-video
  2. I too would be very grateful to see it updated :). Thanks for all the work with the dockers.
  3. Hi there. Thank you fro all the work you put in to the dockers. I don't pretend to know how exactly they work, I am using the Jottacloud docker and all the files from UnRaid are getting uploaded to a folder called "sync" in the synced files main directory. Where it should be just to the root directory. I believe the issue may be in the following command: jotta-scanner /sync /Jotta/Sync From what I understand I THINK the initial "/sync" reference is unneeded and is what is causing everything to upload to the folder called 'sync". Not specifying a directory should just upload it to the root of the Jottacloud folder. I am not able to test this as I don't know how to. Really sorry if I'm wrong, thanks for taking the time. Regards
  4. I did that, and it wouldn't work even after manually configuring it. I have installed it from the command line and got it working now
  5. Looking forward to this also. Not sure how to get it working by myself.
  6. Thank you very much for this thread, I have bene having problems for ages with disk errors on parity check and rebuild and never knew about this until the "Fix Common Problems" plugin sent me here. I got with of my SAS LAPS and bought two Dell Percs and its perfect, no errors, nothing. Just perfect working server. Thank you everyone that has put time into researching the cards and posting their experiences.
  7. Just wanted to say thank you for this! I used to use this on UnRaid when it was called Mobile PC Monitor but then it stopped working. Its great to have it working again. Have setup all the port monitors and everything for my setup. Thanks again
  8. Getting this problem too. did you find a fix?
  9. Ok fantastic thank you. I will try that! Sent from my iPhone using Tapatalk
  10. Do have older logs, from when the errors occurred, it could be more helpful. I do not have any older logs Im sorry. I got everything running again and now another disk has gone and has loads of errors. I have stripped out all the cables and redone them, reseated the cards etc. Is it possible there is some underlying file system corruption on the disks? I have moved files onto the disk that has now failed, is it possible to move corrupted files and damage a new disk? I have attached a new set of logs: https://db.tt/qXVKYuoN Regards
  11. Different controller cards. Have reseated the one card. Have not checked the PSU end but have the other end. I'll take everything out and reseat them all and run memtest. Thank you so much for the help. Anything in the logs that stands out?
  12. Its a CX750M Did memtest around 6 months ago when I upgraded the server. I have precleared most of the disks, some have not. The disks that have been acting up are new and old ones. tower-diagnostics-20160801-1435.zip
  13. I have repaired the disks, got everything working then another disk showed as needing to be formatted. I replaced it and did a rebuild and now a different disk has started showing as needing to be formatted. This is now the 4th disk. I'm starting to think there is a bigger problem here somewhere. Can I post logs or something that might help, if someone could take a look? thank you all
  14. Thank you again. I did a rebuild of the drives previously and they still said that they were being emulated after the rebuild, anyway, i have done it for a second time and drives are showing as unformatted. I have run xfs_repair and got this one the disks: Linux 4.4.15-unRAID. root@tower:~# xfs_repair -v /dev/md4 Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... <few thousand more dots> ..................................found candidate secondary superblock... verified secondary superblock... writing modified primary superblock - block cache size set to 1470096 entries sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap ino pointer to 97 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary ino pointer to 98 Phase 2 - using internal log - zero log... zero_log: head block 3289420 tail block 3289415 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. SECOND DISK: Linux 4.4.15-unRAID. root@tower:~# xfs_repair -v /dev/md8 Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... <few thousand more dots> .................found candidate secondary superblock... verified secondary superblock... writing modified primary superblock - block cache size set to 1470088 entries Phase 2 - using internal log - zero log... zero_log: head block 109735 tail block 109729 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. I am currently looking on here and google for the correct command to mount the file system, just posting the logs here before I loose them.
  15. Thank you for the reply. I ran: xfs_repair -v /dev/md5 on the disk Sunday evening and ever since then it has been stuck at: attempting to find secondary superblock..... With more dots appearing every second for the last 5 days. I canceled it today as there is not even any disk activity anymore. I am very confused because in maintenance mode it says that the "disk is disabled contents are emulated" so does that mean that xfs_repair is working or not? When I start the server and it mounts the disks it shows them as needing to be formatted and the array size does not take into account the two unformatted disks and the data is missing. So why does unraid say the contents are emulated if they clearly aren't? Where did the contents actually go? This all came about from doing a 2 disk parity rebuild. As parity was valid before the rebuild? I really dont understand whats going on with it, doesn't seem to add up? The worst part is that due to split level I could have lost loads of picture, videos etc for projects I have not started yet that I naively thought were protected. All my old stuff is on Dropbox but more recent stuff I dumped on UnRaid waiting to be sorted. I would really be so grateful to anybody that could help! :-*