Extended partition error on boot

CaraGk · 05-09-2015, 11:18 AM

Did you find any way to get out with this error ? I've got the same with an extended partition...

Code:

# fdisk /dev/sda

Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): p
Disk /dev/sda: 55,9 GiB, 60022480896 bytes, 117231408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00015c35

Device     Boot    Start       End  Sectors  Size Id Type
/dev/sda1  *        2048  19531775 19529728  9,3G 83 Linux
/dev/sda2       19533822 117229567 97695746 46,6G  5 Extended
/dev/sda5       19533824  23558143  4024320  1,9G 82 Linux swap / Solaris
/dev/sda6       23560192 117229567 93669376 44,7G 83 Linux

Code:

# dmesg|less
[   84.343741] EXT4-fs (sda2): unable to read superblock
[   84.348074] EXT4-fs (sda2): unable to read superblock
[   84.352391] EXT4-fs (sda2): unable to read superblock
[   84.357159] XFS (sda2): Invalid superblock magic number
[   84.373676] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[   84.373891] FAT-fs (sda2): bogus logical sector size 65535
[   84.373897] FAT-fs (sda2): Can't find a valid FAT filesystem
[   84.378220] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[   84.378444] FAT-fs (sda2): bogus logical sector size 65535
[   84.378449] FAT-fs (sda2): Can't find a valid FAT filesystem
[   84.386262] ntfs: (device sda2): is_boot_sector_ntfs(): Invalid boot sector checksum.
[   84.386270] ntfs: (device sda2): read_ntfs_boot_sector(): Primary boot sector is invalid.
[   84.386275] ntfs: (device sda2): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
[   84.386279] ntfs: (device sda2): ntfs_fill_super(): Not an NTFS volume.
[   84.390737] MINIX-fs: unable to read superblock
[   84.395176] attempt to access beyond end of device
[   84.395185] sda2: rw=16, want=3, limit=2
[   84.395191] hfsplus: unable to find HFS+ superblock
[   84.404204] qnx4: no qnx4 filesystem (no root dir).
[   84.408959] You didn't specify the type of your ufs filesystem

mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[   84.417367] hfs: can't find a HFS filesystem on dev sda2

michaelk · 05-09-2015, 11:40 AM

CaraGk,
Welcome to LinuxQuestions.

An extended partition can not be mounted and in a nutshell just a container for logical partitions. Are you manually trying to mount sda2. What are you trying to accomplish?

CaraGk · 05-09-2015, 11:47 AM

Thanks for your reply.

I'm aware that an extended partition is just a container et I'm not trying to mount it manually.

Like Masuch before, those lines are from dmesg at the end of the bootlog.

It look like the kernel wants to mount automaticaly every not mounted partition that it finds...
Of course, /dev/sda2 do NOT appear in the fstab.

michaelk · 05-09-2015, 11:55 AM

What version of debian are you running?

CaraGk · 05-09-2015, 11:58 AM

Debian 8 Jessie (since a week). And the kernel :

Code:

# uname -a
Linux systar 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) x86_64 GNU/Linux

Gen_Dave · 06-29-2015, 11:35 AM

I also have this problem, identical log, sda2 is my extended container and its tried to mount as OP lists. My fstab is clean.
I'm running running debian 8, 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GMU/Linux.
Any hints would be appreciated.
Thanks

veerain · 06-30-2015, 01:07 AM

The kernel might not be source of problem but some script perhaps systemd is at fault.

joethetester · 09-22-2015, 08:14 PM

Quote:

Originally Posted by Gen_Dave

I also have this problem, identical log, sda2 is my extended container and its tried to mount as OP lists. My fstab is clean.
I'm running running debian 8, 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GMU/Linux.
Any hints would be appreciated.
Thanks

Same problem.

Regards,
Joseph

fogpipe · 09-22-2015, 10:16 PM

I have had the same problems with debian testing and the latest jessie. Specifying the partitions in /etc/fstab and your boot manager as UUIDs fixed it for me.
To get the UUID for a partition:

example /dev/sda5

Code:

blkid /dev/sda5
/dev/sda5: UUID="35f59c3a-1217-4f66-9300-02bfd2adaaad" TYPE="ext4" PARTUUID="4b0c250a-05"

so for instance in fstab instead /dev/sdaN i have entered:
UUID=176093be-40c0-4dc9-93fc-cec72925e432 / ext4 errors=remount -ro 0 1
UUID=decc8d5b-ce3a-4a52-a418-22244ebdcba9 /home xfs defaults 0 2

As far as i can tell its the wonderful ridiculous systemd doing its thing, details on the debian list if you want more:
https://lists.debian.org/debian-user.../msg01366.html

mrswzrd · 01-21-2016, 10:31 AM

Thanks, fogpipe! You helped me narrow it down. I was having the same problem as Gen_Dave, same log errors with my extended partition on a couple of jessie vm's running on Xenserver 6.5 with the 3.16.0-4-amd64 kernel. My fstab already had uuid's, but I noticed GRUB_DISABLE_LINUX_UUID=true was commented out in /etc/default/grub. Uncommented it and ran update-grub, and now the error is gone.

Thanks!
mrswzrd