Installation blocked when configuring a mount point

English Install/Boot/Login
1

Hi,
During installation (expert partitioning) Yast 2 gives me the following message: “it is not allowed to assign a mount point to a device with non existent or unknown filesystem”

The mount point is to a 1T WD hard disk. Linux mint gparted “sees” one single partition /dev/sdd1 NTFS 931G (+ one unallocated part) while Yast2 apparently chops it into 4 partitions: sdd1 156G EFI Boot, sdd2 2G, sdd3 40G and sdd4 889G (?)
The message appears when I want to assign a mount point to sdd4 /WD using NTFS fs type.

So I am blocked; installation won’t continue. To note that assigning all the other mount points works without problems; it’s only this specific mount point that fails.
Thanks

2

Anything on it you need?

It maybe a GPT+MSDOS partitioning problem if the drive has had both it may have two partition tables and thus complicates and confuses things.

Wipe the first track and repartition

3

Your description is not quite clear to me. But reading the error message, I would say, is there a file system on sdd4? Who created it?

Also, a step back I assume, when the installer creates 4 partitions, it does so with a purpose. In this case I guess: EFI, Swap, / and /home. Why did you change that sdd4 from becoming the /home partition (with of course a Linux file system) to somethiing else? Anf how exactly did you do that.

Again a step further back. I do not know if you still have the starting situation of which you give a bit a vague description. Can you post a listing of it. Preferable using (from a live/rescue system)

fdisk -l
4

Hi, thanks for responding. I was about to give up when I found this forum. Anyway, it’s an internal HD, 1T, ntfs formatted that I use in my desktop since a year (windows, linux) and where I store personal data. That is the reason that I want to change the /, the /home etc. to a simple mountable ntfs drive, nothing special. I have it running under linux mint as /WDGREEN1T.

Here’s the output from fdisk -l under linux mint:

Disk /dev/sda: 256.1 GB, 256060514304 bytes
255 heads, 63 sectors/track, 31130 cylinders, total 500118192 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
Disk identifier: 0x42bf3992

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 331951094 165872123+ 7 HPFS/NTFS/exFAT
/dev/sda3 331951095 500103438 84076172 7 HPFS/NTFS/exFAT

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xdef19057

Device Boot Start End Blocks Id System
/dev/sdb1 2048 922307714 461152833+ 7 HPFS/NTFS/exFAT
/dev/sdb2 922308606 976771071 27231233 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sdb5 922308608 976771071 27231232 82 Linux swap / Solaris

Disk /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 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
Disk identifier: 0x00097230

Device Boot Start End Blocks Id System
/dev/sdc1 * 2048 143591423 71794688 83 Linux
/dev/sdc2 143591424 287719423 72064000 83 Linux
/dev/sdc3 287719424 432609279 72444928 83 Linux
/dev/sdc4 432611326 488396799 27892737 5 Extended
/dev/sdc5 432611328 488396799 27892736 82 Linux swap / Solaris

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xa87b2ba6

Device Boot Start End Blocks Id System
/dev/sdd1 2048 1953521663 976759808 7 HPFS/NTFS/exFAT

Disk /dev/sde: 1000.2 GB, 1000204885504 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525167 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
Disk identifier: 0x851f5086

Device Boot Start End Blocks Id System
/dev/sde1 2048 1953521663 976759808 7 HPFS/NTFS/exFAT

Disk /dev/sdf: 8076 MB, 8076132352 bytes
64 heads, 32 sectors/track, 7702 cylinders, total 15773696 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
Disk identifier: 0x20ca2c8b

Device Boot Start End Blocks Id System
/dev/sdf1 3780 11339 3780 ef EFI (FAT-12/16/32)
/dev/sdf2 * 11340 9078783 4533722 17 Hidden HPFS/NTFS

5

Linux will not work on NTFS file system. The permissions don’t exist in Windows and when you mount a Windows partition the permissions are faked. This will not work with Linux program they need a real Linux file system

All your drives seem to be MSDOS/legacy partitioned So you must install in legacy mode if your machine has an EFI BIOS you must boot the installer in legacy mode

Are you confusing /dev/sdd with /dev/sde Which ar you trying to install to??

If /dev/sde then you must reduce the partition size to allow space to install. Currently all is used by the single partition. Recommend doing that from Windows

6

Like gogalthorpe, I am still confused about what you want.

First, you mus decide if yoour system is using EFI or not. You can not mix them.

sdd has one partiotion sdd1 that fills the whole disk. The partition type is HPFS/NTFS/exFAT, which only says that it is to be used for one of those file system types, not that ther is actualy one on it. But when you have an NTFS file system there ad it contains valuable data, you should not install openSUSE on it, because that would destroy the data.

On the other hand, when there is nothing usefull there and you want to install openSUSE on sdd, then you somewhere in the installation process say that the installer should use “the whole disk” sdd. It will then offer you a proposal to create 3 partitions (when in legacy mode, else the EFI boot will be added): Swap (a few GB depending in memory size), / (40 GB with Btrfs), /home (the rest with Xfs). You can then change there, e.g. making a smaller /home and leaving some space for future use. You can even join /home in / (not recommended). But you can not use non-Linux file systems for those.

Use non-Linux file systems only for exchanging data bewteen your Linux system and non-Linux systems (like Windows systems, cameras, etc). That maybe for exchangig with a multi boot on the same hardware, or by using USB connecting devices. Never for integrated file systems in your Linux.

7

For clarification: I am running a dual boot system windows/linux on 2 different SSDs: sda is the first with windows, sdc the second SSD; the rest of the drives are internal or external HD ntfs formatted;

I do not want to install opensuse on sddhttps://forums.opensuse.org/images/icons/icon4.png; sdd is a hard disk (Western Digital) filled with user data and it is ntfs; I just want to have a mount point for ithttps://forums.opensuse.org/images/icons/icon4.png; sde is an external HD and it’s ntfs (Seagate)

Now I want to install opensuse on the 2nd SSD next to linux mint which is already installed on sdc1; now I want opensuse on sdc2

So I will end up with 1 windows and 2 linux partitions, all the rest is data (ntfs). Don’t worry, I am used to doing these kind of multi-boot installations; and maybe I will be so crazy to also install a 3rd linux on sdc3 in the futurehttps://forums.opensuse.org/images/icons/icon7.png

8

OK, thus you want to install openSUSE on sdc. You say sdc2. Does that imply that you:

  • want to use an existing Swap partition also for openSUSE (that is perfectly doable)?
  • do not want a separate /home for your openSUSE eiher by incorporating /home in the root partition, or by using an already existing /home partition also for openSUSE (thee last can be done, but care shoudl be taken because different applications, inclusing the desktop, may have different versions and thus different ideas about the configuration files that are in there)?

When that is the case, I do not understand why you are talking about problems with sdd1. That is not involved in the installation at all.

It could be that you want to use sdd1 as storage used by several of the systems you use, but that is of course of later interest after the installation is complete and running to satisfaction (and then you can use YaST > System > Partitioner too configure your fstab entry and create the mount point for it).

9

yes, swap is sdc5, no /home; if yast can do that after the install, fine for me; i’ll try

10

Note that /home can NOT be NTFS