-
Fatal Crash
I did the check filesystem with the -L flag on disk1. Then started the array and it did a rebuild overnight. As you can see in wednesday's post, when the drive was unmounted it was ntfs. When part of the array it was changed to xfs. I did change its format so it was part of the array. Was that my mistake? After rebuild disk1 has only 27.9 Gb written on it. So I assume the data are gone?
-
Fatal Crash
The new disk1 that was added was ntfs. I made it xfs to be part of the array. That's it. The drive was brand new to obviously empty. I would assume as such that I didn't erase data. Am I wrong in this assumption? The array was then rebuilt with this new disk1 drive in place of the previous one. Are the data rebuilt or gone?
-
Fatal Crash
I reformatted the new drive that was ntfs to xfs. there were no data on the new drive (obviously). I followed what was posted. Was I misled?
-
Fatal Crash
So I ran it on disk1 with the -L flag and then started the array. it did rebuild overnight and now the array is up. I'm not sure that the data on disk1 are there however. I'm trying to mount the share and see if the data are there but it's taking a while. I will post tomorrow.
-
Fatal Crash
Thanks. I don't know if I did what you asked properly. I initially couldn't get to the check filesystem even after clicking on the drive. It's simply wasn't there. The drive was ntfs so I reformated the disk1 to xfs and now it mounts and can be part of the array. I checked the file system status. I started the array in maintenance mode and the drive is part of it. The drive is emulated (and shows a SMART error although it's not clear why because it seems fine). Should I now click the SYNC button and try a data-rebuild? Would that possibly restore what was on the original disk1? Thanks.
-
Fatal Crash
Thanks JorgeB. Sorry for the delay but I was waiting for a replacement drive to arrive. I followed the instruction and post the new diags below and the current status of the array after having unassigned drive 1 and restarting the array as advised. What should I do now? any hope to rebuild drive 1 and recover the data? Thanks for your help. tower-diagnostics-20240110-0850.zip
-
Cannot connect to Shares from Mac Os after 6.11.1 update
No take? Downgraded to a lower version of unraid. Could then access the shares. Problem is that no app could be installed, which is a problem as I use it as roon core. So installed the 6.11.1 upgrade again and reinstalled everything to discover that the roon server doesn't start anymore. Or it starts but then fails to read library. Still can't access the shares... so no music, can't transfer to external drive either... Krusader installation fails... What an update !! next step is remove flash and try a clean install... am I the only one with these problems?
-
Cannot connect to Shares from Mac Os after 6.11.1 update
System diagnostics added. Thanks ! tower-diagnostics-20221010-0731 2.zip
-
Cannot connect to Shares from Mac Os after 6.11.1 update
Hi, I would appreciate some help. I just updated to 6.11.1 and now I cannot access any of the shares. Didn't change anything from before. I tried restarting both the Unraid server and the Mac, no luck. I tried accessing as root or as a user, no luck either. I'm unsure what else to try/change and would appreciate some help from experienced users. I should mention that shares are seen but then it says that the shares do not exist on the server (?) Thanks
gapinl
Members
-
Joined
-
Last visited