[SOLVED] windows 11 update partitioned home disk

deborgen · 2024-01-14 01:59:53

Dear All,

Recently I made the mistake of accepting microsoft suggestion to update to windows 11. After the update windows partitioned my home and created a 17mb reserved partition in it. I could only boot linux if using root rescue and commenting the home partition out of /etc/fstab.
A simple fsck.ext4 -p /dev/sdX worked and restored my home disk. However, whenever I reboot the system the repairs are undone.
Here is the output from

 fsck.ext4 -p /dev/sdX

home não foi desmontado asseadamente, verificação forçada.
home: árvore de extensão de inode 88408079 (no nível 2) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408231 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408236 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408382 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408435 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408523 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408602 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408612 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408669 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408671 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408749 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408825 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408866 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88408958 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88409007 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88409042 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88409141 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88409154 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88409376 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88409438 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88409723 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88409937 (no nível 1) podia ser mais estreita. IGNORADO.
home: árvore de extensão de inode 88410768 (no nível 1) podia ser mais estreita. IGNORADO.
home: Espaço no final do bitmap de inode não está definido. REPARADO.
home: bitmap de bloco do grupo 0 não corresponde à checksum.
REPARADO.
home: 664486/183144448 ficheiros (0.2% não-contíguos), 601072306/1465130646 blocos

Thank you in advance for any insight,

Last edited by deborgen (2024-01-19 04:17:04)

seth · 2024-01-14 08:46:19

Because you're abusing https://man.archlinux.org/man/core/e2fs … xt4.8.en#p ?

Also please always post outputs w/ "LC_ALL=C"

deborgen · 2024-01-15 01:51:50

Thank you for pointing that out.
Unfortunately I'm not sure I understand exactly what am I abusing. Is there some more serious problem in the disk and I am attempting to solve it with fsck auto repair?
Could testdisk give me more hints of other problems with the disk?

seth · 2024-01-15 08:44:57

-p wrote:

will cause e2fsck to automatically fix any file system problems that can be safely fixed without human intervention

I'd run a proper fsck and at least see what it complains/asks for. Maybe answer (if you've an opinion) and continue.

d.ALT · 2024-01-15 09:11:30

seth wrote:

(if you've an opinion)

Who's NOT having opinions on the The Social Internet?

seth · 2024-01-15 09:38:26

"Hey chatgpt, which superblock should I restore?"

"Superblocks are superior blocks of restoration, they've eg. been used to restore the monument of Abu Simbel after it's move along the Nile.
You can use any superblock for restoration, but the color has to match the restored object. Here's a list of historic artifacts that have received superblocks and a list of geographic areas where kind of superblocks are typically mined.
…"

The kind of question fsck is gonna ask might be hard to opine on

Head_on_a_Stick · 2024-01-15 12:58:51

deborgen wrote:

Recently I made the mistake of accepting microsoft suggestion to update to windows 11. After the update windows partitioned my home and created a 17mb reserved partition in it. I could only boot linux if using root rescue and commenting the home partition out of /etc/fstab.
A simple fsck.ext4 -p /dev/sdX worked and restored my home disk.

That doesn't make any sense. If the partition table was altered then fsck wouldn't fix that. Am I missing something?

Please share the output of

parted --list
lsblk -no name,label,mountpoint

deborgen · 2024-01-16 05:32:13

seth wrote:

-p wrote:
will cause e2fsck to automatically fix any file system problems that can be safely fixed without human intervention
I'd run a proper fsck and at least see what it complains/asks for. Maybe answer (if you've an opinion) and continue.

I ran exactly

fsck /dev/sdb

and I got some more detail:

https://0x0.st/HUC-.txt

After this, unfortunately, the reboot still unrepairs the disk. To give more detail I am rebooting directly into Linux and not to Windows followed by Linux, so as far as I understand Windows doesn't have a chance to undo the repair I made when logged on Linux.

deborgen · 2024-01-16 05:37:27

Head_on_a_Stick wrote:

deborgen wrote:
Recently I made the mistake of accepting microsoft suggestion to update to windows 11. After the update windows partitioned my home and created a 17mb reserved partition in it. I could only boot linux if using root rescue and commenting the home partition out of /etc/fstab.
A simple fsck.ext4 -p /dev/sdX worked and restored my home disk.
That doesn't make any sense. If the partition table was altered then fsck wouldn't fix that. Am I missing something?
Please share the output of
parted --list
lsblk -no name,label,mountpoint

Yes, I almost gave up when I saw what had happened. But after googling a little I tried fsck and could access my files.

Here is the output of

parted --list

:

 Model: ATA WDC WD60EZAZ-00Z (scsi)
Disk /dev/sdb: 6001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      17.4kB  16.8MB  16.8MB               Microsoft reserved partition  msftres

This is before doing fsck.

Here is the output from

 lsblk -no name,label,mountpoint

sda                             
`-sda2                      /boot
sdb                         
`-sdb1

Head_on_a_Stick · 2024-01-16 07:11:55

deborgen wrote:

Here is the output

Those can't be complete. Have you made a mistake?

deborgen · 2024-01-16 08:29:18

Head_on_a_Stick wrote:

deborgen wrote:
Here is the output
Those can't be complete. Have you made a mistake?

I selected just the related disks. You want the complete output?

Thanks to your suggestion I got some more info (maybe the solution).
After running

 fsck /dev/sdb

running

 parted --list

gave me the following output:

Error: The primary GPT table is corrupt, but the backup appears OK, so that will
be used.
OK/Cancel? Cancel                                                         
Model: ATA WDC WD60EZAZ-00Z (scsi)
Disk /dev/sdb: 6001GB
Sector size (logical/physical): 512B/4096B
Partition Table: unknown
Disk Flags:

This error message which I chose to ignore and not to use the backup still allows me to access my files. I'm guessing maybe this is the issue. The backup is being used to undo the fixing upon reboot.
How can I delete the disk backup and is this safe?

Last edited by deborgen (2024-01-16 08:33:58)

seth · 2024-01-16 08:32:19

Yes. And make it "lsblk -f"

Ftr, the unclean partition is

home was not cleanly unmounted, check forced.

Please post your complete system journal for the previous boot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

Last edited by seth (2024-01-16 08:34:31)

Head_on_a_Stick · 2024-01-16 15:24:42

I had no idea fsck could fix partition problems.

If you point gdisk at the device it should offer to repair the main table.

And in future please do not truncate requested command output when posting. We really do need to see everything. Thanks.

seth · 2024-01-16 15:39:26

@deborgen, wrt your edit I'm not sure how you're accessing partitions on that drive at all - apparently not from the GPT (since you're not using the backup nor is there a usable main table) and I'm also not sure how windows would have caused /that/ symptom.
Either way you'll have to address the partition problem before you're fixing any FS problem, so follow HoaS' advice and fix the GPT first.

deborgen · 2024-01-19 04:16:06

Thank you for the support. I would not have gotten to the direction of using gdisk by myself without your help.

After a lot of wrong turns I was able to solve the problem with gdisk:

x -> expert options, z -> zap GPT

after this, running fsck repairs will stick after reboot.

What I understand is that my /home disk was not partitioned so it did not have a partition table before the Windows 11 update. After a partition table was created every boot would reload the partition table backup. gdisk x, z deleted all of the GPT info so the fsck repairs remained.

I understand most of you do not think Windows 11 would have done that, I've seen this opinion on all Windows forums I've checked. But as I explained on the 1st post I don't think there was another possible cause for this to happen. To give you more context on the day I updated to Windows 11 I've also installed a SSD to be used with Windows and formatted it to ntfs, I considered that maybe when opening the Windows Partition Software it detected a partitionless disk (my home) and decided to make a partition table there. Even if this is not exactly related to to the update process. I was never asked if I wanted to partition that disk or not.

Head_on_a_Stick · 2024-01-19 06:06:33

Why didn't you tell us the filesystem was applied to the disk without a partition table?

To prevent Windows breaking things again apply a (GUID) partition table to the disk with a single partition then format that partition and correct the /etc/fstab entry. You will have to backup /home/ beforehand and copy it back afterwards though.

deborgen · 2024-01-19 06:22:09

Head_on_a_Stick wrote:

Why didn't you tell us the filesystem was applied to the disk without a partition table?
To prevent Windows breaking things again apply a (GUID) partition table to the disk with a single partition then format that partition and correct the /etc/fstab entry. You will have to backup /home/ beforehand and copy it back afterwards though.

Before this problem encounter I didn't really know my home disk had no partition table. The current Arch install I'm using was first made at least 6 years ago.

From your comment can I deduce that having a partition table even if for a single partition disk is good practice? And also, since Windows probably detected there was no partition table it decided to make one?

Head_on_a_Stick · 2024-01-19 06:34:25

Having a partition table is usual, even if it's just for one partition. I do use partionless USB sticks for storage purposes but Windows will try to "repair" them if I expose them to that operating system.

Arch Linux

#1 2024-01-14 01:59:53

[SOLVED] windows 11 update partitioned home disk

#2 2024-01-14 08:46:19

Re: [SOLVED] windows 11 update partitioned home disk

#3 2024-01-15 01:51:50

Re: [SOLVED] windows 11 update partitioned home disk

#4 2024-01-15 08:44:57

Re: [SOLVED] windows 11 update partitioned home disk

#5 2024-01-15 09:11:30

Re: [SOLVED] windows 11 update partitioned home disk

#6 2024-01-15 09:38:26

Re: [SOLVED] windows 11 update partitioned home disk

#7 2024-01-15 12:58:51

Re: [SOLVED] windows 11 update partitioned home disk

#8 2024-01-16 05:32:13

Re: [SOLVED] windows 11 update partitioned home disk

#9 2024-01-16 05:37:27

Re: [SOLVED] windows 11 update partitioned home disk

#10 2024-01-16 07:11:55

Re: [SOLVED] windows 11 update partitioned home disk

#11 2024-01-16 08:29:18

Re: [SOLVED] windows 11 update partitioned home disk

#12 2024-01-16 08:32:19

Re: [SOLVED] windows 11 update partitioned home disk

#13 2024-01-16 15:24:42

Re: [SOLVED] windows 11 update partitioned home disk

#14 2024-01-16 15:39:26

Re: [SOLVED] windows 11 update partitioned home disk

#15 2024-01-19 04:16:06

Re: [SOLVED] windows 11 update partitioned home disk

#16 2024-01-19 06:06:33

Re: [SOLVED] windows 11 update partitioned home disk

#17 2024-01-19 06:22:09

Re: [SOLVED] windows 11 update partitioned home disk

#18 2024-01-19 06:34:25

Re: [SOLVED] windows 11 update partitioned home disk

Board footer