Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix any assumptions about sector sizes always being 512 bytes #177

Open
mmstick opened this issue Apr 12, 2019 · 7 comments
Open

Fix any assumptions about sector sizes always being 512 bytes #177

mmstick opened this issue Apr 12, 2019 · 7 comments

Comments

@mmstick
Copy link
Member

mmstick commented Apr 12, 2019

Seems there's some hardware out there which does not provide 512-byte logical sizes.

@bcorcoran
Copy link

I'm running into this on my machine (Dell XPS 15 9560 with 1TB NVME & native 4k sectors) but I noticed that the PR was recently marked as "Done"

How can I get the new build?

@mmstick
Copy link
Member Author

mmstick commented Jul 21, 2020

There is no build, and this hasn't been fixed yet

@bcorcoran
Copy link

I'd like to help test a fix if that's at all possible!

@vjr vjr mentioned this issue Dec 1, 2021
@vjr
Copy link
Contributor

vjr commented Dec 2, 2021

For anyone following this issue - I've filed PR #278 mainly to enable the elementary OS installer to install on 4k sector disks to go along with PR elementary/installer#621

@kostadinsh
Copy link

Is this going to be fixed?

@LivInAbsurdism
Copy link

I'm also running into this issue while trying to install. Are there plans on fixing this or methods of getting around it?

@Tijs-B
Copy link

Tijs-B commented Feb 6, 2024

I'm having this issue when trying to install Pop!_OS on my 2017 MacBook Pro, which has logical sectors of size 4096. I can't seem to find a way to switch this size to 512. Are there plans on fixing this or merging vjr's PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants