magmpzero

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

3 Neutral

About magmpzero

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Yeah, I think it is a linux problem because I futzed around in the cli for a while. when fdisking or doing anything I kept getting errors / warnings about the GPT mismatch GPT PMBR size mismatch (4294967294 != 35156656127) will be corrected by write I reformatted multiple times on a real mac machine and tried several drives (I bought 4). I even tried creating new partitions under linux but could never get anything to work. Unfortunately, I can't do any further testing as I shucked the drive(s) and put them in my array.
  2. I do. Just yesterday I plugged in a 8tb hfs+ external drive and was able to use without problem.
  3. Great plugin! I use it all the time. Quick question: I bought a bunch of 18tb external drives for shucking but thought I would try to use one on my mac. Formatted normally and verified it was a good drive. Unassigned devices failed to work on such a large drive and would only show about 800gb free (if I remember right). Is this a known problem and is it a problem with linux hfs+ support or something to do with unassigned devices?
  4. Hi all: Sorry for not paying attention to this thread. I really had no idea people were actually using magrack. Looking over the comments I will get an update out in the next week or two to address the folder structuring and then take a stab at adding stack support where magazines are grouped by name. The image display bug is because of how I create the preview image. I name it preview.jpg when it should be the name of the mag. That being said, my weakness is UI design and development for the frontend code. If anyone could help out with this aspect, please let me k
  5. Dude, settle down. I just found a random docker image on the hub and made a template for it so more people could use booksonic. How was I supposed to know you were an unraid user that actually had an account and was the same person who created the image. I don't have a crystal ball. Sorry for trying to help. I remove this template and let you create one so you can get all the credit for creating the image.
  6. Try using the following to connect from the app: https://yourip:yourport/booksonic I have had to add booksonic to the end of the URL for some reason. I didn't build this docker, just the template for unraid but may start building my own so I can help out more with issues that pop up.
  7. Application: Booksonic Docker Hub: https://hub.docker.com/r/ironicbadger/booksonic/ GitHub: https://github.com/magmpzero/docker-templates Overview: Booksonic is a fork of the popular Subsonic streaming server but modified to focus 100% on audiobooks. I put this simple template together so others could enjoy using this software. For more information on booksonic, visit the official website: http://booksonic.org/
  8. Thanks for the kind words. This is kind of a UnRaid exclusive app right now as I haven't made it available anywhere else. It's pretty basic but has surely made my life easier for reading magazines. I suppose it will work with any PDF including tech books. If you have any ideas for improvements, please let me know. I am thinking about automation but not sure if the market is large enough to justify the time it would require to implement. The one thing I would love to figure out is how to reduce duplicates on my automated RSS downloads. I generally get two versions of some issues
  9. Just following up on. Issue has been resolved after formatting /md8 and copying data back over.
  10. I think the failed drive is mostly readable for the data I care about saving. Most I can lose. Do anyone have a link that explains the process to basically wipe this drive to clear both the drive and reset /md8 data on the parity drive and then copy over what I want to keep? I am thinking just a format of /md8 would work and then rebuild parity, finally copy over what I want to keep from previous failed drive from another box. -- gs
  11. Attached is the output from the check. I am curious, is it possible that because the drive failed when rebuilding my parity drive if bad data was written to parity and then when restored is restored bad data that makes it appear the FS is corrupted? ---- node allocation btrees are too corrupted, skipping phases 6 and 7 No modify flag set, skipping filesystem flush and exiting. ---- xfs_check.txt
  12. Hey folks: I really need some help here. I had a failed drive so I bought a new one and replaced it. The drive rebuilt fine and was humming a ong fine for a day and then I noticed some weird behavior in logs: Mar 4 03:40:10 Hog logger: *** Skipping any contents from this failed directory *** ar 4 03:40:10 Hog kernel: XFS (md8): Internal error XFS_WANT_CORRUPTED_RETURN at line 1137 of file fs/xfs/libxfs/xfs_ialloc.c. Caller xfs_dialloc_ag+0x195/0x248 Mar 4 03:40:10 Hog kernel: CPU: 1 PID: 23476 Comm: shfs Not tainted 4.1.17-unRAID #1 Mar 4 03:40:10 Hog kernel: Hardware
  13. Just an update on the automation. I think I have figured out a way to do it but it's going to be a lot of work. It will probably take me 2-3 months to have a system that is ready to be used for others. I will keep updating with progress as I am working on it if people care.
  14. Are you suggesting you have a figured out a way to automate placing magazine issue into a title folder? If so, I would love to know how you do this. The real problem with magazines there isn't a naming standard that I have been able to figure out. But yeah, I could certainly add that as a feature.
  15. Thanks for alerting me about the port. I just fixed it and pushed a new version up.