Cannot move up and down in a Setup screen

**Huevos** · 01-01-22, 10:07

Originally Posted by birdman

And the relevance is?

The user still has a problem.

No, he does not have a problem. He was trying to use a name that was not the partition name. But as the log shows the correct partition name is present and file system is ntfs. Later he managed to change the partition name to what he wanted in MountManager.

**birdman** · 01-01-22, 12:26

Originally Posted by Huevos

No, he does not have a problem. He was trying to use a name that was not the partition name. But as the log shows the correct partition name is present and file system is ntfs. Later he managed to change the partition name to what he wanted in MountManager.

But has not yet reported being able to use it for the default movie location.
Which I reckon should be checking "ntfs-3g" against a list that doesn't contain it (it contains "ntfs").

**Huevos** · 01-01-22, 13:45

Yes he can.

**birdman** · 01-01-22, 21:38

I did just manage to get a "Partition must be ext or nfs" message. But it went away when I restarted the GUI so might just have been an artefact of moving a different disk into the /media/hdd position.

I suspect I confused myself by asking for the contents of /etc/fstab (which actually now contains auto, but did at one point contain ntfs-3g), but the code actually looks at /proc/mounts (which makes sense, as that won't ever contain "auto").

So yes, it does seem to be working, although it might take a few restarts to get it in place.
Also, how can you create the initial movie directory?

**Huevos** · 01-01-22, 21:48

The important thing is to make sure the disc is properly mounted and with the right name before trying to set up recording locations. The reason the OP had failures was because that was not the case.

**Juhola** · 23-08-22, 15:11

To OP, try this: Menu -> Setup -> System -> User interface -> Settings: Sort settings screens alphabetically YES

**chulann** · 27-09-22, 23:20

Originally Posted by abu baniaz

< 7307.9526> [InfoBarGenerics] Key: 399 (Make) KeyID='KEY_GREEN' Binding='('GREEN',)'.
< 7307.9530> [ActionMap] Keymap 'ConfigListActions' -> Action = 'save'.
< 7307.9554> [Skin] Processing screen 'MessageBox', position=(380, 355), size=(520 x 10) for module 'MessageBox'.
< 7307.9611> [ePNG] loadSVG /usr/share/enigma2/skin_default/icons/input_question.svg 53x53 from 53x53
< 7307.9633> [ePNG] loadSVG /usr/share/enigma2/skin_default/icons/input_info.svg 53x53 from 53x53
< 7307.9650> [ePNG] loadSVG /usr/share/enigma2/skin_default/icons/input_error.svg 53x53 from 53x53
< 7307.9660> [Screen] Warning: Skin is missing element 'icon' in <class 'Screens.MessageBox.MessageBox'>(Directory '/media/sda2/' not valid. Partition must be ext or nfs

Sorry, out of ideas. Might be related to this commit
https://github.com/OpenViX/enigma2/c...061a66b1e3894f

Funnily enough, I'm getting the "partition must be ext or nfs" error on OpenVix 6 2 010 on my Formuler F1 box (previously posted here)

I'm trying to save to a mounted ZFS partition - I've had to mount using nfsvers=4 option in /etc/fstab so I can get at all my datasets.

Looking at that commit, I notice the supported filesystem includes "nfs" but not the "nfs4" that df -Th shows me - could this be the reason for my problem?

**Huevos** · 28-09-22, 09:00

Originally Posted by chulann

Funnily enough, I'm getting the "partition must be ext or nfs" error on OpenVix 6 2 010 on my Formuler F1 box (previously posted here)

I'm trying to save to a mounted ZFS partition - I've had to mount using nfsvers=4 option in /etc/fstab so I can get at all my datasets.

Looking at that commit, I notice the supported filesystem includes "nfs" but not the "nfs4" that df -Th shows me - could this be the reason for my problem?

Why don't you try?

**chulann** · 29-09-22, 00:14

Originally Posted by Huevos

Why don't you try?

Fair point! To be honest, I thought compiling the Python was a bit more difficult.

I did give it a go but it didn't work. I did a bit more debugging. Specifically, I added this to Timeshift.py as part of the isValidPartition function:

print("[Timeshift] DEBUG: mountpoint %s and filesystem %s" % (partition.mountpoint, partition.filesystem()))

Results I got as I was cycling through the various partitions was:
[Timeshift] DEBUG: mountpoint / and filesystem ubifs

I read that as it not actually checking the actually directory, but rather always / which is failing (because it's always ubifs)

Will do a bit more digging tomorrow hopefully

**Huevos** · 29-09-22, 08:07

"/" is not a valid timeshift location.

**Huevos** · 29-09-22, 09:26

This is what I get on my working system:

Code:

			for partition in Components.Harddisk.harddiskmanager.getMountedPartitions():
				print("[Timeshift] DEBUG: mountpoint %s and filesystem %s" % (partition.mountpoint, partition.filesystem()))
				print("Valid", partition.filesystem() in supported_filesystems)
				if partition.filesystem() in supported_filesystems:

Code:

< 41323.0026> 10:21:58.5063 [Timeshift] DEBUG: mountpoint / and filesystem rootfs
< 41323.0034> 10:21:58.5071 Valid False
< 41323.0044> 10:21:58.5080 [Timeshift] DEBUG: mountpoint /media/hdd/ and filesystem ext4
< 41323.0050> 10:21:58.5087 Valid True
< 41323.0060> 10:21:58.5096 [Timeshift] DEBUG: mountpoint /media/usb/ and filesystem ext4
< 41323.0067> 10:21:58.5103 Valid True

**chulann** · 29-09-22, 22:08

I get a different result. I tweaked the code:

Code:

for partition in Components.Harddisk.harddiskmanager.getMountedPartitions():     
       print("[Timeshift] DEBUG: path %s, mountpoint %s and filesystem %s" % (path, partition.mountpoint, partition.filesystem()))
       print("Valid", partition.filesystem() in supported_filesystems)                                                            
       if partition.filesystem() in supported_filesystems:                                                                        
             valid_partitions.append(partition.mountpoint)

These are the results in my log:

Code:

<   210.0182> [Timeshift] DEBUG: path /beast/, mountpoint / and filesystem ubifs
<   210.0202> Valid False
<   221.3488> [Timeshift] DEBUG: path /media/, mountpoint / and filesystem ubifs
<   221.3506> Valid False
<   224.8464> [Timeshift] DEBUG: path /e2/timeshift/, mountpoint / and filesystem ubifs
<   224.8483> Valid False
<   228.7765> [Timeshift] DEBUG: path /beast/enigma2/timeshift/, mountpoint / and filesystem ubifs
<   228.7786> Valid False

So the getMountedPartitions() function is not picking up my mounted NFS partition (/beast). Not sure why - trying to track down the getMountedPartitions function to see what's going on.

For reference, the partition does show up in mount:

Code:

172.30.1.2:/beast on /beast type nfs4 (rw,relatime,vers=4.0,rsize=8192,wsize=8192,namlen=255,soft,proto=tcp,port=0,timeo=14,retrans=2,sec=sys,clientaddr=172.30.1.18,local_lock=none,addr=172.30.1.2)

(and equivalent in df)

**twol** · 30-09-22, 11:17

Originally Posted by chulann

I get a different result. I tweaked the code:

Code:

for partition in Components.Harddisk.harddiskmanager.getMountedPartitions():     
       print("[Timeshift] DEBUG: path %s, mountpoint %s and filesystem %s" % (path, partition.mountpoint, partition.filesystem()))
       print("Valid", partition.filesystem() in supported_filesystems)                                                            
       if partition.filesystem() in supported_filesystems:                                                                        
             valid_partitions.append(partition.mountpoint)

These are the results in my log:

Code:

<   210.0182> [Timeshift] DEBUG: path /beast/, mountpoint / and filesystem ubifs
<   210.0202> Valid False
<   221.3488> [Timeshift] DEBUG: path /media/, mountpoint / and filesystem ubifs
<   221.3506> Valid False
<   224.8464> [Timeshift] DEBUG: path /e2/timeshift/, mountpoint / and filesystem ubifs
<   224.8483> Valid False
<   228.7765> [Timeshift] DEBUG: path /beast/enigma2/timeshift/, mountpoint / and filesystem ubifs
<   228.7786> Valid False

So the getMountedPartitions() function is not picking up my mounted NFS partition (/beast). Not sure why - trying to track down the getMountedPartitions function to see what's going on.

For reference, the partition does show up in mount:

Code:

172.30.1.2:/beast on /beast type nfs4 (rw,relatime,vers=4.0,rsize=8192,wsize=8192,namlen=255,soft,proto=tcp,port=0,timeo=14,retrans=2,sec=sys,clientaddr=172.30.1.18,local_lock=none,addr=172.30.1.2)

(and equivalent in df)

Harddisk.py

Code:

	def getMountedPartitions(self, onlyhotplug=False, mounts=None):
		if mounts is None:
			mounts = getProcMounts()
		parts = [partition for partition in self.partitions if (partition.is_hotplug or not onlyhotplug) and partition.mounted(mounts)]
		devs = set([partition.device for partition in parts])
		for devname in devs.copy():
			if not devname:
				continue
			dev, part = self.splitDeviceName(devname)
			if part and dev in devs:  # If this is a partition and we still have the wholedisk, remove wholedisk.
				devs.remove(dev)
		# Return all devices which are not removed due to being a wholedisk when a partition exists.
		return [partition for partition in parts if not partition.device or partition.device in devs]

	def addMountedPartition(self, device, desc):
		for partition in self.partitions:
			if partition.mountpoint == device:
				return  # Already_mounted.
		self.partitions.append(Partition(mountpoint=device, description=desc))

**abu baniaz** · 30-10-22, 07:09

Recording is one thing, timeshift is another. The requirements for timeshift do not need to be applied to those for recording.

**Huevos** · 30-10-22, 17:04

?... who are you replying to?

Thread: Cannot move up and down in a Setup screen

Thread Tools

Display

The Following User Says Thank You to Huevos For This Useful Post:

Posting Permissions

Options

About

Site Links

Social Media