ntfs resize takes forever

Asked by Stephen Buergler

When I select that it should erase a disk and install, It queries my disks to see if my other disks with ntfs on them can be resized. This is unnecessary since I'm not using those disks. It also takes forever. It basically makes installing ubuntu impossible unless I disconnect those disks or I go and kill the pids associated with querying that information.

Attached is "px auxfww" output.

Does this information have to be queried or can it be queried in the background?

Edit: test

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu ubiquity Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was originally filed as bug #1965681.

Revision history for this message
Erich Eickmeyer (eeickmeyer) said :
#1

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs.

Revision history for this message
Stephen Buergler (sixcorners) said :
#2

Why isn't it a bug? The installer does not complete. It freezes.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

I suggest you resize the NTFS in Windows. NTFS is proprietary to Microsoft and only they know how it works.

Revision history for this message
Stephen Buergler (sixcorners) said :
#4

What? Look at my attachment. It's running a program called ntfs resize.

Also I don't want to resize anything because 1. I'm telling it to erase the whole disk and install and 2. it's an entirely separate disk with no ntfs partitions.

Revision history for this message
Manfred Hampl (m-hampl) said :
#5

There is not enough information provided by you that anybody could be able to work on your problem.

You did not even tell us which Ubuntu version you use.

Which Ubuntu installer are you running (i.e. which installer iso file)?
How did you start running the installer?
What is the disk and partition layout of your system?
What exactly did you select with respect to disk partitioning?
etc.

If you want to create a bug report, then you are supposed to use the Ubuntu bug reporting tools (in this case probably "ubuntu-bug ubiquity"). That automatically collects information that is indispensable for working on the bug report.

Revision history for this message
Manfred Hampl (m-hampl) said :
#6

"Look at my attachment." Where is that attachment?

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#7

You cannot attach files on Launchpad for questions. You'll need to make it publicly available online then give the URL

Revision history for this message
Stephen Buergler (sixcorners) said :
#8

I attached it to the issue I created. Where did it go?

Revision history for this message
Stephen Buergler (sixcorners) said :
#9

It's the installer on this image: ubuntu-21.10-desktop-amd64.iso
The computer I installed to kind of didn't have internet. That's why I attached a picture taken from my cell phone.
The system has three disks. The disk I'm installing to has an old ubuntu installation and is attached over usb. There are two other disks with ntfs on them. One is a 1tb ssd with a windows installation another is a 12tb hdd with a bunch of games on it.
I booted into grub from the bios option to override the boot options and selected the "install ubuntu" option.
I chose the second option to erase the disk and install when it froze and I had to go around killing pids until it came back.

Revision history for this message
Stephen Buergler (sixcorners) said :
#10

I very explicitly didn't make a question. I made an issue. The question in my description are suggested ways to fix the bug.

Revision history for this message
Stephen Buergler (sixcorners) said :
#11

Ok how about this:
https://cdn.discordapp.com/attachments/919882621503275078/955419904704663582/PXL_20220317_171806443.jpg
Sorry. I really remember attaching it here.

I had to kill the choices script to unfreeze the installer.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#12

Are you installing in GUI or CLI?

If you try the latest ISO of Jammy (Ubuntu 22.04) then it may help. Jammy is also LTS and supported a LOT longer tan Ubuntu 21.10.

Revision history for this message
Stephen Buergler (sixcorners) said :
#13

GUI
I kind of didn't know that it was possible over a CLI.

hmm.. that's a good idea. I'll try it later today.
Thanks.

Revision history for this message
Manfred Hampl (m-hampl) said :
#14

I now partly understand: You created a bug report with an attachment Bug #1965681 which was refused as not being a bug and was converted into a question. In such case there are links created between the bug report and the question document. Why did you remove these cross references? You are impeding the supporters. With help of the related link it would have been possible to access the attachment in the bug report starting from the question document.

As already written in comment #5 there are several installer logs that are needed to find out what happened, in your case an important one (and not the only one) would probably have been UbiquityPartman.txt

Revision history for this message
Stephen Buergler (sixcorners) said (last edit ):
#15

I edited the description. Does that remove the cross reference? I replaced the word "there" with a comma.
Other than that the only thing I have done to my knowledge is add comments.

Revision history for this message
Stephen Buergler (sixcorners) said :
#16

I guess I'll link it now. Thanks for finding it.

Here i did the apport-collect thing on a soft locked install on this bug:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680

There you can find the files you are looking for.

Revision history for this message
Manfred Hampl (m-hampl) said :
#17

The log files point towards the problem already reported in Bug #1945011
The ntfs resize does not take forever, but there is a kernel crash.
I suggest that you continue in that bug report.

Revision history for this message
Stephen Buergler (sixcorners) said :
#18

What should I contribute over there?
Also what about my bug report? Shouldn't this long running process be put into the background?

Also I just did a test edit of the description and the related bug didn't get deleted so I don't think I affected it. Whoever did deleted it not only impended the supporters but also impended my bug report. Is it something that Erich could have forgotten to do? Is there a log of it anywhere?

Revision history for this message
Manfred Hampl (m-hampl) said :
#19

The step to query the resizability of a partition takes only fractions of a second, but due to the crash that happens, the results are not returned to the installer, and it looks as if that check takes forever, which isn't the case.

Suggestions:

1. comment in Bug #1945011 that you are affected, too (if you haven't done that already)
2. Try the command
sudo ntfsresize --info /dev/sdXN
replacing /dev/sdXN by the identifier of your NTFS partition(s), something like /dev/sda1 or /dev/sdb3
Does this work or crash?
3. Try the Ubuntu 22.04 installer https://cdimages.ubuntu.com/daily-live/current/jammy-desktop-amd64.iso

Can you help with this problem?

Provide an answer of your own, or ask Stephen Buergler for more information if necessary.

To post a message you must log in.