curtis-r

I don't see how I could have been looking at the parity data . I was able to mount the disk, toggle sharing, and then view it on my network. It appeared with Toshiba + model + serial#. I've already started a rebuild, so no going back now. The lost+found was not on the physical drive. I just meant I'm glad I have the lost+found (in the parity). Thanks again. Glad to have people like you on the forumn.

I thought I already did a repair and that's what created the lost+found.

Well, though I was able to share the disk and view the contents, unfortunately it is the same as the parity. The good news is the lost+found folder, and the fact that I have a not-terribly old backup of the more critical stuff on another disk Not knowing how this happened and that the parity didn't save the day, I'm disappointed. But I thank everyone a ton for their help and patience.

Well (of course) that worked! It cleared log & reset UUID. And now it mounted! It now shows used & free space. And to continue my ignorance, now what?

My bad. I didn't change the 'X' to the drive letter. My problem now is what letter? Under unassigned devices, it's listed as "Dev 1".

I think I'm too much of a newb because I'm unclear where to enter that code. I tried through putty but it returned "fatal error -- couldn't initialize XFS library". Is there another place to run this? Sorry.

How do I execute an uuidgen, if that's the suggestion?

Done. Thanks for being patient with me.tower-diagnostics-20210303-1626.zip

There is no additional option in the UUID drop-down. I clicked 'Change UUID' anyhow.

Diagnostics attached. Thanks. tower-diagnostics-20210303-1510.zip

Ha, never needed Unassigned Devices plugin until now ;). Anyhow, installed. Clicked Mount for disk1, but nothing seems to happen. There is a sublisting of that disk also with 'Mount" grayed-out.

Ok, I stopped the array & unassigned the disk, & started array. Disk shows under unassigned. Does that folder/magnifying glass still reflect the parity or the actual disk? The contents look the same as the parity (missing stuff). Is that what you mean by mounting in Unassigned Devices?

I'm trying to handle this remotely from work, but as of the update, WOL isn't working, so had to wait for someone to manually wake my unraid. An issue for another time... As you theorized, the lost+found had a bunch of stuff missing from the emulated disk (3577 files/folders). When you ask if I can mount the disk as Unassigned, do you mean clicking the folder/magnifying glass icon to the right of it or something else? When I click the folder/magnifying glass, it looks like the emulated view (missing stuff).

Thanks a ton for the quick replies. Makes total sense. What are your thoughts about just rebuilding to the existing disk?

Silly me. So sorry for the post before being on the latest version. Upgraded. Big difference with the new scan, in that the log was huge (attached). The -L repair ran (also a huge log, attached). Re-started array in normal mode, but Drive1 still has red 'x'. Says it's unmounted. Ran a new scan, and that one was much shorter and didn't seem to have anything clearly wrong. I feel I'm now missing something obvious, no? BTW, this all started when doing a lengthy scan of my array content by a new media server. tower-diagnostics-20210303-0835.zip Drive1 check after repair.txt drive1 repair.txt Drive1 check.txt

Got a red 'x' and "Unmountable: No file system". Followed the wiki instructions for a check/repair. Got this: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Invalid block length (0x0) for buffer Log inconsistent (didn't find previous header) empty log check failed zero_log: cannot find log head/tail (xlog_find_tail=5) Then tried -L then press "check" for a repair but nothing happens. Thanks in advance. tower-diagnostics-20210302-1839.zip

@Pipould, that seems to have fixed it. Placed your code in the pre & post, rebooted, then checked back couple of hours later & it was asleep. Thanks!!!

Also having sleep issues. Worked perfectly for years, but some months ago (after an OS & plugin update), it never sleeps unless I manually spin-down the drives. The sleep log repeatedly states 'drive activity', yet (as you can see) all the drives are inactive. I tried tweaking the network activity settings to no avail.

Thanks.

For my understanding, can you tell me what in the SMART tells you the drive is failing? thanks.

Before seeing the last posts, changed Parity SATA port only. Started New Config & rebuild. If disk5 shows errors will do the same for it. thanks. Parity rebuild completed but disk5 had errors (SMART attached). Tomorrow I'll replace it's cable & possible move it to a new SATA port. tower-smart-20200410-2337.zip

Before seeing the last posts, changed Parity SATA port only. Started New Config & rebuild. If disk5 shows errors will do the same for it. thanks.

Spoke too soon. Parity failed again . Diag attached. tower-diagnostics-20200410-0824.zip

The parity-rebuild finished with no errors on the parity, so fingers-crossed that this sticks. 1 other drive did have some errors, so I'm not sure what that's about. Diag & SMART attached. tower-diagnostics-20200410-0806.zip tower-smart-20200410-0808.zip

After trying New Config again, it maintained all my drive assignments, but the parity was blank and my drive was not listed as available. I rebooted (with array still stopped) & all assignments were lost, so I reassigned them as the were & started the array. Parity now has orange triangle and is running parity rebuild. Already changed the cable but if this fails, I think I have an extra SATA port, so I'll try switching the parity to that. The diagnostics I attached was after a reboot, so probably not useful. If the rebuild fails, I'll post that diag. Thanks. tower-diagnostics-20200409-1348.zip