Diego Tr

Hi One of the disks in the array reported a SMART error for reallocated sectors. I replaced it with a new one without doing a preclear, and during data rebuilding, the new disk shows a value of 923 for the reallocated sectors attribute. Should I return it to the provider?

It worked, VMs and dockers are back Thank you very very much, both of you

Indeed, I see that I have the docker.img and libvirt.img files duplicated: in cache and in disk1, which was the one with the corrupted file system. The size of the docker.img file is different in each location. What should I do now, then? Should I change the settings of the system share to indicate secondary storage: None, and delete the system directory on disk1? Sorry for asking so many details, but I’m afraid of making things worse.

Yes, I see that the VMs are on another disk, in /mnt/disk3/domains. Before recreating them, I’m attaching the diagnostic file, in case you can think of a way to recover them microserver-diagnostics-20240713-1641.zip

Finally, the disk has mounted :). Unfortunately, all the Docker containers and VMs have disappeared. I am reinstalling the containers from Previous Apps, which seems to be going smoothly. As for the VMs, I understand that there is no easy solution; in any case, I don't care about them as much as the docker containers...

Thank you very much for your help I have run the check and this is the result: 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... sb_fdblocks 2076704, counted 5488271 - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - 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... Maximum metadata LSN (17:1514943) is ahead of log (0:0). Would format log to cycle 20. No modify flag set, skipping filesystem flush and exiting. I suppose I will have to run the check again, removing the -n option, right?

Hi I’m not sure if it was after rebooting unRaid, or if the problem was already there, but one of the disks in the array is showing the error “Unmountable: Unsupported or no file system.” According to S.M.A.R.T, the disk seems to be fine. I would really appreciate the help; I’ve been dealing with this all day and I’m desperate. I understand that, as a last resort, I can buy a new disk, replace it, and rebuild the data from the parity disk, right? I’m attaching the diagnostic file. Thank you for your help microserver-diagnostics-20240713-1046.zip