wickedathletes
-
Posts
435 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by wickedathletes
-
-
any chance this was resolved in rc2 @limetech?
Here are diags from beta 30:
https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/page/2/?tab=comments#comment-10968And here are the results of `hexdump -C -n 512 /dev/sdh`
limetech said: Thanks, yes that explains it. Probably, with -beta25 and even earlier releases, if you click on the device from Main and then look at 'Partition format' it will say 'GPT: 4KiB-aligned (factory erased)' - that (factory erased) shouldn't be there. Will fix for next release.
-
@ljm42, yes, thank you for that!
-
looks like this is still an issue for me in RC1 (beta 25 and back works fine, bug first discovered in beta 30), any update on a potential fix timeline?
One of my drives shows "Unmountable: Unsupported partition layout."
-
@limetech, any chance this is fixed in beta35? I can't chance it as I wont have a recourse back to nvidia drivers since the old plugins are dead in the water so I don't want to change bumping up to then have to go back without a way to go to the nvidia driver sets.
"Thanks, yes that explains it. Probably, with -beta25 and even earlier releases, if you click on the device from Main and then look at 'Partition format' it will say 'GPT: 4KiB-aligned (factory erased)' - that (factory erased) shouldn't be there. Will fix for next release."
-
23 hours ago, limetech said:
Is it possible that this drive was pre-cleared and then used to rebuild a disabled disk?
No you won't be stuck on beta25 🤪
that is definitely possible, but asking my brain to think back 3 years is a big task hahaha. It would have been one of 2 things, a rebuild of a disabled disk or a replacement of a 4TB disk as 3 years ago my server only had room for 8 drives.
-
6 hours ago, limetech said:
The issue you are seeing with -beta30 is being caused by that particular hard drive having a "pre-cleared" signature in the MBR, yet, I'm assuming that when you boot -beta25 (or earlier), it mounts ok and there are files on that disk - is that correct?
If so, this should be an "impossible" state to get into - I'm wondering if you recall and give me a little background info that particular drive. That is, did you at one time in the past run 'pre-clear' on that drive?
This drive is functioning 100% fine in beta25 and earlier. 29/30 it wont mount.
I honestly don't recall. I would say I have pre-cleared 90% of my drives but their was a time when I didn't have the ability to pre-clear due to a drive failure and no extra bays to use (aka I was under the gun). Its possible this was the drive that was not, but I doubt it. The drive is roughly 3 years old.
Is their a way out of this state, or with this drive am I stuck on beta25 for eternity haha?
-
15 hours ago, limetech said:
Thanks, yes that explains it. Probably, with -beta25 and even earlier releases, if you click on the device from Main and then look at 'Partition format' it will say 'GPT: 4KiB-aligned (factory erased)' - that (factory erased) shouldn't be there. Will fix for next release.
thank you and as always, you guys are the best!
-
55 minutes ago, limetech said:
On beta25 is fine. Just make sure the problematic device is still 'sdh' - if not, substitute that device id.
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001c0 02 00 00 ff ff ff 01 00 00 00 ff ff ff ff 00 00 |................|
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200 -
7 minutes ago, limetech said:
Thank you. Please open terminal, type this command and post the output:
hexdump -C -n 512 /dev/sdh(that is non-destructive, it's dumping the first 512 bytes of the device, aka, the MBR - Master Boot Record)
I assume in a "broke" state? or as beta25 right now?
-
23 hours ago, limetech said:
Just don't click "Format"
attached. I also tested beta29, same issue. beta25 is good though.
-
1 minute ago, JorgeB said:
Please post the complete diagnostics after you get the partition error.
I am kind of scared to do it again, for a 3rd time haha. Before I do, if the drive goes into that state, is that a state that parity can get it out of? I just don't want to lose 8TB of data because a drive is failing but not throwing a "failure" per-say.
-
Coming from beta25, beta30 keeps throwing one of my drives into "Unsupported partition layout." Restoring back to 25 fixes it. Drive details attached, not sure if you would like anything else. It happened both attempts. I am using the linuxservio version of beta30.
Unraid OS version 6.9.0-rc2 available
-
-
-
-
-
in Prereleases
Posted
@limetech, just wanted to confirm the issue still exists in RC2:
Here are diags from beta 30:
https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/page/2/?tab=comments#comment-10968
And here are the results of `hexdump -C -n 512 /dev/sdh`
https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/page/3/?tab=comments#comment-10972
limetech said: Thanks, yes that explains it. Probably, with -beta25 and even earlier releases, if you click on the device from Main and then look at 'Partition format' it will say 'GPT: 4KiB-aligned (factory erased)' - that (factory erased) shouldn't be there. Will fix for next release.