xrqp

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.

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 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 2 - agno = 7 - agno = 0 - agno = 4 - agno = 6 - agno = 5 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. Next ran file system check with no switches (no -n, and no -L) gets: 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 and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 1 - agno = 5 - agno = 7 - agno = 2 - agno = 6 - agno = 4 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done Then I stopped array, then restarted it in normal mode. Disk 1 is still disabled and emulated. Reboot did not help either. I will try to replcae disk 1 now.

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 own risk. Then add to array. When adding to array it is automatically "formatted" if needed. Is the above correct? if it is intended for unassigned devices, which preclear option should I use to stress test: "Verify all the disk", or "erase all the disk" or ? Thanks.

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 think the SAS cables are often a problem? I will keep testing things, including replacing a disk or two, until I get fewer orange messages. Lately, I have problems with the array not showing files that exist, untiI reboot, then they show up again but only for a few minutes sometimes.

Thanks very much for the reply.

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 cache, because I did a move, then ran Sonarr for about 30 minutes with not much downloading. Then i did the mistake.

Do you mean the disk repair that is done with -L in the "Check file system" ? Did you see anything in the diagnostic.zip?

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

should I run diagnostic when it is not mountable? Or can I run diagnostic after the repair fixes the drive and it mounts good?

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 to get things to work again. Prior to this I never needed to restart Roon docker or power cycle the Unraid NAS to fix problems. But next time it won't take me 40 minutes before I try that. Has anyone else had this happen?

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 zero_log: cannot find log head/tail (xlog_find_tail=5) - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Metadata CRC error detected at 0x45d399, xfs_dir3_leafn block 0x161508f48/0x1000 bad directory leaf magic # 0x6f93 for directory inode 6442451074 block 8388609 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 0 - agno = 3 - agno = 2 - agno = 4 - agno = 5 - agno = 6 - agno = 7 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... Metadata corruption detected at 0x45553e, xfs_da3_node block 0x161508f48/0x1000 unknown magic number 0x6f93 for block 8388609 in directory inode 6442451074 rebuilding directory inode 6442451074 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (4:65268) is ahead of log (1:2). Format log to cycle 7. done Thanks for your thoughts.

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.

deleted accidental double post

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) ?

MULTIPLE FILE LOCATIONS FOR MUSIC With this container, can you add multiple file locations for music? Do you have to add them in both 1) the container mappings and 2) in the app mappings? In this paragraph, I am showing the mappings as they appear in Windows file viewer, where Z: is my Unraid Tower. I am currently mapping both app and container using a relatively direct share "Z:\music\". I want to add another location, less direct, in a different share called "data" like this "Z:\data\media\music". Can I do that, and if I can, do I need to add it to both the app and the container mappings? Thanks.

HOW TO KNOW IF AN UPDATE OCCURS In Roon Remote go to Settings/About (which is near the bottom of settings list) there is a section for Remote and another for Core. Both have a gear icon (settings) you need to click, then change to "ask before installing any updates". So I did that today and will report back if core updates go well or not in the future. I am not sure if I had a successful core update yet. The remote update went well today from build 77x to 783, but it is the core update that is the concern. But so far it is all working for about a month. I realized today, in order for me to know when an update occurs, I have to do this setting.

Does this trash-guides, work good in conjunction with the binhex unraid docker containers for nzbget, sonarr, radarr, lidarr? https://trash-guides.info/Misc/how-to-set-up-hardlinks-and-atomic-moves/#unraid In the guide he used containers by "ghcr.io/hotio", but I hope it works with binhex's too. Anything to add for people using that guide with binhex containers? How important do you think it is to use hardlinks? My guess is that it is fairly important. It's been difficult for me to get it all to work correct, and that was the first guide that seemed more complete than other guides on the subject, and that uses all 4 containers and more. I followed spaceinvader videos for paths, and when i got to using radarr it did not work and i did not understand it well. I hoped using trash-guides I could just copy it and not have to fully understand it.

In Unraid, or in UD, can we merge partitions without losing data? Or can it merge partitions and wipe clean only one partition?

thanks.

Does this also apply to Unassigned Devices, with hot plugging a SATA spinning disk, and a USB spinning disk? If UD will not hot plug these, does one need to simply "Reboot", or is power cycle required?

Because I do not understand those scripts. I don't speak Linux. Maybe I should try harder. Another docker option with GUI is LuckyBackup. Does anyone use it, or something with GUI?

RE: Backup of some folders in unraid array to unassigned hard drives: My unraid is at home. As a backup stategy, I am thinking after backing up certain folders in the array to the UD drives, I would remove the UD drives and take them to store at my work place. I was thinking a full backup once a year, and incremental backups every 3 months. Should I use urbackup docker? Or do it from Windows 10 using Macrium Reflect? Or other recommendation? Thanks.

It is 2021. Do we still need Dynamix TRIM for SSD's?

Do we need ALSA to play DSD audio recordings? If yes, then I want it too.

It was, but that was when I had the wrong paths (everything went to RAM only) and it locked up and crashed, never really doing a build. Now that I fixed it, I do not see the nags yet. After my library and analysis is done, I will do a backup, then try update, and report back here.