• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About xrqp

  • Rank
  1. I replaced an array drive, but the new drive stays in unassigned devices. Both are 8TB. How can i get it to show in the array, so I can enable it to the array? Never mind. I found that i just needed to stop the array in order to pick the new drive into the array.
  2. I was going to replace disk 3, but before I could, now my disk 1 was disabled by Unraid. So I ran file system check with -L, but that changed nothing. Then I ran file system check (-n) and got this: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno =
  3. Have I got this correct: If I have a new external hard drive using USB3, and: A) if it is intended for unassigned devices (not the array), then I would delete all partitions, then run preclear if I want a bit of a stress test, then format (like NTFS). Then I can shuck it if desired, at my own risk. B) if it is intended to be readied to be put into the array, then I would delete all partitions, then run preclear if I want a bit of a stress test, then DO NOT format. Then I can shuck it so I can use SATA instead of USB3, at my ow
  4. I am starting to think it is normal and common to Now I am getting orange warnings for the unassigned disk I just started using. I got simialr mesages for other disks. get these mild warnings (yellow, not red). Bad orange, Good green, repeat, repeat. I tried improving the power cables to the disks. Next I may try to use more motherboard sata connections, and fewer of SAS to SATA i have using the approved "Dell H310 6Gbps SAS HBA w/ LSI 9211-8i P20 IT Mode for unRAID" which has 8 SAS I got SAS cables on ebay cheap ($10 each) 2x Mini SAS to 4-SATA SFF-8087. Do you
  5. The mistake i made: I forgot to use mover before I changed the share to "no cache". So i got this message: First suggested fix is "change the share settings appropriately". Does that mean, I should set the share back to use cache again, then do the mover, then I can safely stop caching? (That's what i did, then re-ran "fix common problems" and there were no errors listed. 🤥). Is it bad I did that. I am not sure what a happens when the cache has an orphan files for the share, then share cache is stopped, then started again. It did not have much in c
  6. Do you mean the disk repair that is done with -L in the "Check file system" ? Did you see anything in the diagnostic.zip?
  7. Problems again. Does not say "not mounted" this time. Here is what "fix common problems" showed: But it is not full or read only. It does say "disk 3 not defined/installed in the array". Which sounds similar to unmountable. Here is my main screen It looks normal. When I get unmmountable error, it does not look normal like this. Here is the diagnostic zip before repair. tower-diagnostics-20210503-0046.zip
  8. should I run diagnostic when it is not mountable? Or can I run diagnostic after the repair fixes the drive and it mounts good?
  9. A few post above this I reported my Roon core update went well. One possible minor glitch is that it may require a restart, or a power cycle, especially if you also update a remote later. Here is why I say that: The Unraid core update was working good for me for a few days, then came an update on my remote ipad. Then it worked for an hour. Then it stopped working. I tried power cycle on my Auralic G2 (a music computer between Unraid and DAC), which usually fixes these issues, and I tried other things for 40 minutes, with no success. Then when I did power cycle on Unraid, I was able t
  10. This is the 3rd time in 6 months that my disk #3 (out of 5) has become "unmountable". Each time, I go into maintenence mode, and did a check/repair with option -L. Here is what it showed after this last -L repair. Do I need to replace the drive? This latest instance of becoming unmountable happened after a power cycle. I do not do the -n anymore, but I can next time, it you think it is needed to know what is going on. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) failed to find log head
  11. Using this container, I was able to do an update on my Unraid core last night with good results. From 1.8 785 to 1.8 790. I am very pleased and relieved it can do this. Thanks to steef, and dkerlee, and xthursdayx ! My Unraid machine only uses 35 watts overall, and now I don't need to run my other desktop to play music. My other audio equipment are energy hogs, even on standby. I had to setup a web based power switch to easily disconnect them from power when I am not listening.
  12. The solution at that post is So it does have to be mapped at both the container and the app, with an extra requirement that "music" is not used used for mapping both locations. In the above example, could it work if it was changed to: 1. music 2/ > /music 2. music (Blu-ray)/ > /music (Blu-ray) ?