Partition(s) type + error on modyfing (-3002)

seden · February 28, 2017, 8:43am

Hello,

Another day, others unknown, while pretty sure not to be that uncommon (already documented) finding about them did not help, not really a surprise.

So, I use (windows) several hard driver with on each more than one partition, as to personal documents, apps, pro docs on distinct partition (some connected, others not) etc.

Now, the drive using as to host documents is not even recognized, Ill add in the error message later on, something relating to windows (there is only documents on here, no windows install ever).

Then, the drive used to install Leaf is using two main partition, as to begin use it as I did previously, I selected the option to add in a new one, from there, it was quite unknown territory (unusual, but wiki did help as to partition type, and so, it installed correctly.

Still, the added partition is not usable at all, I can move/copy or do anything with it, while there is quite a lot of already created folders (did not check if there was files in them that said).

Now, trying to see how to handle from now, I get a -3002 Error. Why ?

What should I do now ?

gogalthorp · February 28, 2017, 2:03pm

To start show use fdisk -l please use code tags (# in tool bar) to let us see what you are talking about.

seden · February 28, 2017, 3:35pm

Absolute path to 'fdisk' is '/usr/sbin/fdisk', so running it may require superuser privileges (eg. root).

Something missing, also, Yast keep asking for my password even after selecting the “memorize the password” check box each time.

seden · March 1, 2017, 2:33pm

Any idea as to how to handle it from there ?

hcvv · March 1, 2017, 2:44pm

We assumed you know that fdisk requires root privileges. And even when you did not know, the message is clear enough. In any case do:

su -l -c 'fdisk -l'

seden · March 1, 2017, 3:18pm

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 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: 0x0006bca0

Device     Boot      Start        End    Sectors  Size Id Type
/dev/sda1             2048    4208639    4206592    2G 82 Linux swap / Solaris
/dev/sda2  *       4208640   88100863   83892224   40G 83 Linux
/dev/sda3         88100864 2017490943 1929390080  920G 83 Linux
/dev/sda4       2017490944 3907028991 1889538048  901G 83 Linux


Disk /dev/sdf: 31.3 GiB, 33554432000 bytes, 65536000 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: 0x688fd856

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdf1  *      128 65535999 65535872 31.3G  c W95 FAT32 (LBA)


Disk /dev/sdg: 60 GiB, 64424509440 bytes, 125829120 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: 0xc2eda536

Device     Boot Start       End   Sectors Size Id Type
/dev/sdg1  *       64 125829119 125829056  60G  c W95 FAT32 (LBA)

seden · March 1, 2017, 3:24pm

Also, I have a usb3 8Go (Internal) now not used (was mainly for boot process over windows), would there is some use for it ? (placing the Swap there ? Given Im on a single disk setup for now, not sure of the interest ?)

Thanks, in any case.

seden · March 1, 2017, 8:50pm

No idea as to what to do or is the provided log not usable ?

Thanks to let me know.

hcvv · March 1, 2017, 9:05pm

Apart from all your talking. let us concentrate first on what we see and then on what your problem is.

What we see is three disks:

sda, a 1,8 TiB sized disk
Being MBR partitioned into four primary partitions. All space used.
sda1: 2GiB partition to be used for Swap. Most probably the swap of your openSUSE system.
sda2: 40 GiB partition to be used for a Linux type file system. Most probably your openSUSE root file system.
sda3: 920 GiB partition to be used for a LInux type file system.
sda4: 901 GiB partition to be used for a Linux type file system.
I assume that one of the last two is used for your openSUSE /home file system and the other one, only you can tell or find out. You can show us what is used for what

mount | grep '^/dev'

sdf, a 31.1 GiB sized disk
Being MBR partition into one, disk filling, partition.
sdaf1: 31.3 GiB partition to be used for a Windows file stem

sdg, a 60 GiB sized disk
Being MBR partitioned into one, disk filling partition.
sdg1: 60GiB partition to be used for a Windows file system.

No idea if you use those two disks for something (maybe a Windows system on there?).

We do miss sdb, sdc, sdd and sde. Do you have some storage card with 4 places?

Now please tell us what your problem is with this layout. You talk about partitions not “seen”. Explain what partition is used for what ad if (and how) you mount them in your openSUSE, etc. etc. And the more relevant computer output comes with it, the better. We tend not to believe stories, but we do believe what the computer says.

gogalthorp · March 2, 2017, 2:11am

An aside note. When GUI asks for root to start a program like Yast and you check the box to remember the system only remember for about 15 min I think. If you start the program in under 15 min then it should not ask over 15 min then the system asks again. It is to keep random people walking by from gaining root access.

seden · March 2, 2017, 6:19am

YAST login / credential :
15mn, without any way to change that ?

Quite an pain, albeit I guess I wont be using it that much once my environment has reached a good status.

As to SDA :

sdb, sdc, sdd and sde would be the slots from the multi card read/writer ?

It is sda4 who is my current worry (along with the -3002 error, not being able to make change using the partition tool).

I cant create anything (neither move a file, create a file or a folder, it is not even appearing as far as Dolphin and others explorators can see.
It is apparently used for/by some applications (cache contains : apparmor, cups, fontconfig, gio-2.0, krb5rcache, Idconfig, libx11, man, PackageKit, susehelp & zypp folders, for example).

The small volumes (…) are cards, some micro sd others usb, flash memory in all case. I’ve indeed a portable version of windows on one, not sure if I will keep it (need to figure where I can go cross-compatibility wise (opensuse <> Android).

Some offtopic (again), there is quite some others things but I will see to read and check some more (if time allow, no surprise there).

hcvv · March 2, 2017, 9:18am

Can you please walk through my posts step by step and comment and answer the different items there in sequence? And leave out the small talk about other things. How can we concentrate on finding the cause of your problem when you jump around and in the mean time do not even answer my questions.

Where is the

mount | grep '^/dev'

At least it seems that you think you have problems with the file system on sda4.
Please confirm if that is correct!
What should be on sda4. Most probably a file system. What type of file system?

And let we try to do something with it:

su -l -c 'mount /dev/sda4 /mnt'

To make it clear, when I suggest something like this, you should do it in a terminal and post it complete (prompt, command, output, next prompt) in your answer.

seden · March 4, 2017, 6:52pm

mount | grep '^/dev'

= :

/dev/sda2 on / type btrfs (rw,relatime,space_cache,subvolid=259,subvol=/@/.snapshots/1/snapshot)
/dev/sda2 on /srv type btrfs (rw,relatime,space_cache,subvolid=263,subvol=/@/srv)
/dev/sda2 on /boot/grub2/i386-pc type btrfs (rw,relatime,space_cache,subvolid=260,subvol=/@/boot/grub2/i386-pc)
/dev/sda2 on /tmp type btrfs (rw,relatime,space_cache,subvolid=264,subvol=/@/tmp)
/dev/sda2 on /.snapshots type btrfs (rw,relatime,space_cache,subvolid=258,subvol=/@/.snapshots)
/dev/sda2 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,space_cache,subvolid=261,subvol=/@/boot/grub2/x86_64-efi)
/dev/sda2 on /opt type btrfs (rw,relatime,space_cache,subvolid=262,subvol=/@/opt)
/dev/sda2 on /usr/local type btrfs (rw,relatime,space_cache,subvolid=265,subvol=/@/usr/local)
/dev/sda4 on /var type xfs (rw,relatime,attr2,inode64,noquota)
/dev/sda3 on /home type xfs (rw,relatime,attr2,inode64,noquota)

Then :

su -l -c 'mount /dev/sda4 /mnt'

= :

> su -l -c 'mount /dev/sda4 /mnt'

The cursor then go back to the next line, without any other message (stay there).

As double check :


seden@linux-kbxw:~> su -l -c mount /dev/sda4 /mnt'
> su -l -c 'mount /dev/sda4 /mnt'

hcvv · March 4, 2017, 9:34pm

When you copy/paste it in one sweep (prompt, command, output, next prompt) there is no need to split it in two (the command and the output) with the text " =: " between the two. Why so difficult where it is so easy?

Then first command shows that sda4 contains an xfs file system and is mounted on /var. So it is in use. Why you have that as such is up to you to explain.

The next came a question:

What should be on sda4. Most probably a file system. What type of file system?

Why did you not answer this?

And then the last command. Again we want to see exactly copied/pasted what you did and got. No story telling. We can read computer text.
In any case what you show as last is NOT correct. Your line

su -l -c mount /dev/sda4 /mnt'

is different from what I posted. That may be a typo, but why do you type? You should copy/paste my command. And when you want to type it, you should check character for character if you typing is correct before you hit the return key. In this case, nothing happened, but mistyping things when being root can create a disaster.

So home work for you now is:

answer my question: what do you have that sda4 partition for, what is on it (file system type?) and where should it be mounted.
it is now mounted on /var. Have you any idea why it is so?
the following command

cat /etc/fstab

And please put some effort in it to do this carefully and precise. That may help to bring this thread to an end before the end of 2017.

seden · March 5, 2017, 3:23pm

sda4 was to be used as to store documents, pdf, txt, jpg etc.
No idea/not know as of yet.


seden@linux-kbxw:~> cat /etc/fstab
UUID=2b2a7ce5-cb69-4d73-b5d3-8bb8262e44ac / btrfs defaults 0 0
LABEL=Home           /home                xfs        defaults              1 2
LABEL=Documents      /var                 xfs        defaults              1 2
UUID=ac3dfa82-c2f6-486e-a20e-52180a240b90 swap swap defaults 0 0
UUID=2b2a7ce5-cb69-4d73-b5d3-8bb8262e44ac /boot/grub2/i386-pc btrfs subvol=@/boot/grub2/i386-pc 0 0
UUID=2b2a7ce5-cb69-4d73-b5d3-8bb8262e44ac /boot/grub2/x86_64-efi btrfs subvol=@/boot/grub2/x86_64-efi 0 0
UUID=2b2a7ce5-cb69-4d73-b5d3-8bb8262e44ac /opt btrfs subvol=@/opt 0 0
UUID=2b2a7ce5-cb69-4d73-b5d3-8bb8262e44ac /srv btrfs subvol=@/srv 0 0
UUID=2b2a7ce5-cb69-4d73-b5d3-8bb8262e44ac /tmp btrfs subvol=@/tmp 0 0
UUID=2b2a7ce5-cb69-4d73-b5d3-8bb8262e44ac /usr/local btrfs subvol=@/usr/local 0 0
UUID=2b2a7ce5-cb69-4d73-b5d3-8bb8262e44ac /.snapshots btrfs subvol=@/.snapshots 0 0

Why not copy/paste ? Seen that ctrl+c/v = direct input (must use right click command) I did not to more check.
Dully noted & applied from now on.

seden@linux-kbxw:~> su -l -c 'mount /dev/sda4 /mnt'
Password : 
mount: /dev/sda4 is already mounted or /mnt busy
       /dev/sda4 is already mounted on /var
       /dev/sda4 is already mounted on /mnt

hcvv · March 5, 2017, 4:09pm

Well, look at this line:

LABEL=Documents      /var                 xfs        defaults              1 2

You apparently have labeled the file system with the label Documents. You can prove this with

ls -l /dev/disk/by-label/Documents

And this line says it should be mounted at /var. And that is done at boot.
I have no idea why you did so, but as I understand you, this is not what you want.
You say there must be put all sorts of files on it. But who is to be the owner of those files? And where does the owner wanted them to be mounted?

And at the end of your post you show the trial to mount it. As you see the error is very illuminating. It says it is already mounted on /var. Which we now found out on another way

Now, how to repair?
I think it i would be good to know when you created this entry in /etc/fstab. When did you try to use that sda4 for your documents?
Was this right from the installation? Or is this a later adaption?
I ask, because from the moment on that sda4 is mounted in /var, the system will put all sort of files there. And I am not sure if the system will run correctly when we remove sda4 from /var.
(In other words, you really made a mess of it )

seden · March 7, 2017, 4:23am

Yes, it was at installation, I tried to see with my smartphone which options go with, it seem I did not choose correctly.

Guess I could see to redo the installation, so far I did not make that much changes.

Of course if there is another option, it would be preferable ?

As to the files already on the sda4, they are put there by applications mostly, I’ve listed some them earlier in one of my post.
As said already, I cant put/modify or do anything on that partition, 900gb offered to the system use, more than generous.

Seem like it is progressing in any case, thanks a lot hcvv !

hcvv · March 7, 2017, 9:44am

I now guess that at installation you wanted already to add that file system, but you forgot to enter he proper mount point. The installation then will use the first default from a list of much used mount points and that is /var. But that is definitely not what you want.

/var is much used by the system and some applications while the system is running and contains many variable files that should survive from one boot to another. You will find there e.g. many log files.

Now part of this can be destroyed without more harm then “loss of memory about what happened earlier”. But I am not really sure what the consequences will be when we just remove all that.

You say there is not much lost when you re-install. In that case we could try the following:
Edit /etc/fstab and put a # in front of that line. It will now be:

#LABEL=Documents      /var                 xfs        defaults              1 2

Reboot. Check if it runs “normally”. That means if you think anything strange happens. When all seems to be OK, you do not need a re-installation.

Then report back and we can continue with using sda4 for what you want it to be used for.
One thing only. You AGAIN forgot to answer all of my questions. One of them:

You say there must be put all sorts of files on it. But who is to be the owner of those files? And where does the owner wanted them to be mounted?

I normally get very frustrated already when people do not answer in a conversation, but this conversation having a cycle time of about 24 hours (you seem to live at the opposite of the globe) it is really killing my enthousiasm to continue here. >:(