Dosraid

Considering that the array is working with emulated content because disk3 is failing, and the disks I have are larger and I cannot directly put them as disk3 and rebuild the array. Could I put one of the new disks as parity 2 (18tb) even without having disk3? And when this is done, remove parity 1(10tb) and then replace disk3 with one of the new disks(18tb)?

I'm no expert, but normally the diagnostics are in a zip file rather than several separate files. In this case, I would miss the syslog-previous.txt file, which is the one that can give us more information about what happened in the system when it shut down, since the syslog.txt file you attached will be from this execution and we won't be able to see the errors.

Hi, my knowledge of Unraid is quite limited, but I do have some knowledge of Docker. No Docker images are failing; the dockerd service itself is failing to start, as shown in syslog.txt. The logs don't show much more information (at least that I can interpret), so I would try to access it via terminal and try to start the process manually to see if that works or if you get more details about the error. You can do this with /etc/rc.d/rc.docker. If this doesn't work, you can try directly with dockerd (this runs the Docker runtime directly in the terminal and not as a daemon).

Hi, I currently have a server consisting of a 4x10TB HDD array and a pool with 2x2TB SSDs with a basic license. Right now, I have a faulty disk in the array (currently running as emulated content). This is not the first time this disk has given errors, which are solved with xfs_repair, but after a couple of days (or hours this list time), there are write errors again and in the end the disc disconnected and the same thing happens, so it's time to change it. I'm not very happy with the disks I currently have, so I've bought three new 18TB disks. The idea is to create a new array and copy the data from the old one. Any suggestions or recommendations on how to do this? Another thing is that I have a basic license limited to six disks, so I'm not sure how I can do this migration. Thanks

Hello, I have a 3-disk + 1 parity array, each with 10 TB, using XFS as the file system. I started the server as usual, and shortly after disk 3 (ST10000NM0046_ZA24KBAS (sde)) was unmounted. I stopped the array and started it in maintenance mode, ran SMART on all disks and xfs_repair -n. All SMART tests (short) completed successfully. I am attaching the logs from xfs_repair -n. Also try the old one of restarting the served down and up again but and the problem persists Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_ifree 254, counted 255 - 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 imap claims in-use inode 4902619454 is free, would correct imap - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 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.Can somebody assist me? Thank you

After running one by one the docker services I have, it only failed after running a torrent client. After deleting all the incomplete files and turning on the service, the problem has not happened again (for the moment).

Hi I have some problems, I detected that my volumes were not mounted, when looking at the logs in the Unraid WebUI I see things like this (not in this order, with more logs in between): XFS (dm-0): Corruption detected. Unmount and run xfs_repair kernel: XFS (dm-0): Internal xfs_trans_cancel error on line 1104 of file fs/xfs/xfs_trans.c. Call xfs_bmapi_convert_delalloc+0x377/0x3b5 [xfs]. writeback error on inode xxx, offset xxx, sector xxx kernel: XFS (dm-0): In-memory data corruption (0x8) detected in xfs_trans_cancel+0xd6/0x114 [xfs] (fs/xfs/xfs_trans.c:1105). Shutting down file system. kernel: XFS (dm-0): Please unmount the file system and rectify the problems. (diagnostics attached with the full logs) Seeing that I stopped the array, mounted it in maintenance mode and ran the xfs_repair (without any arguments) attached logs as well of this. After that I unmounted the array again because was in maintenance mode and mounted it normally. But the same thing happens again and the system is unmounted. Recently had some problems with data data-rebuild which was solved in this post (maybe it is related):

Thank you! After running the filesystem check (xfs_repair) without parameter and starting the array without the maintenance mode the data reappears.

What's the next step? Run 'xfs_repair' without any parameters too fix de xfs filesystem? Is the data already lost and cannot be recovered?

I attach the disk2 xfs_repair status logs:

I have an array of 3x10TB disks (Parity, Disk1, and Disk2; both Disk1 and Disk2 have around 5TB of data each one, in total the array had a little more of 10TB in usage). Last week, Disk2 failed, but I was able to continue operating without any issues due to the parity protection. On Friday, I received a new disk to replace Disk2 (the one that failed). However, when I tried to start the array with the rebuild, it didnt give me the option, because the system reported that the new disk was bigger than the parity disk (both are labeled as 10TB, but there may be slight differences in manufacturer specifications). So I I followed the steps in the guide, starting from step 6 (as the earlier steps were already completed when the disk initially failed). I progressed to step 14, which took around 15 hours, and then moved on to step 15, where I started the array and began the rebuild. At this point, the array became available, but I didn’t check whether all my data was intact. I also didn’t start any services, as I wanted to wait until the rebuild finished, which took another 15 hours. After the rebuild finished, I started some of my services and noticed that I had lost some data—specifically al the newest files, that I think was previously stored on Disk2, which amounted to about 5TB. At this point, I returned to the Unraid dashboard to investigate. Disk2 (the newly rebuilt disk) showed no data usage or capacity. Instead, it displayed the message: Unmountable: Unsupported or no file system after buld array Since the data rebuild had completed some minutes ago (maybe a hour), I had no idea what this error meant or what was happening. I stopped the array and rebooted the server. Upon restarting, Disk2 was marked as a "new device" and the array operations says start the array and rebuild again. Now the disk is rebuilding once more, but I’ve already lost a significant amount of data. My questions are: - What did I do wrong? (I just follow the guide and use the WebUI) - Did I lose the data because the parity-swap procedure or during the rebuild phase? Because when I was with the failed disk and the emulated disk2, the data existed - Is there any way to recover the lost data? Thanks for reading and helping me