diskfilter writes are not supported

[firenice03]

The bug was marked in the Ubuntu 14.04. Current version is Ubuntu 20.04. If I am installing with the default partition with the Ubuntu 20.04, I am not getting that error.
But with the default installer why I am getting the error with LL 5.0 ?

I can create the partition manually. But when the default installer can do the task why should I do that manually ?

It's most likely still in Ubuntu 20.xx until they correct it, it will propagate to the derivatives....
Why do it manually - why do it automatically   lol

@firenice03

Using LL for 1st time.
Helped my nephew installing it (remotely) for his school assignments.
Used Default lvm that installer gave.

Also, seen a lot of LL folks complaining about same warning / error for various LL versions.

But its looking like the bug maybe with how the installer creates the LVM's... And not so much the overall LVM tool...

[Şerban S.]

[...]But with the default installer why I am getting the error with LL 5.0 ?[...]

I can create the partition manually. But when the default installer can do the task why should I do that manually ?

Hi!

Simply, because the installer has nothing to do with GPT partitioning.
Read carefully what Jerry said about the UEFI support in Linux Lite:

Release Announcement

[...]
Changes:

UEFI is now supported out of the box. It is recommended that you disable Secure Boot even though it will work, it's just a huge hassle to have it enabled. See the new inbuilt Help Manual for ways to do this on the Start page.
[...]
- Detailed UEFI & Secure Boot information
[...]
[...]
But I thought Linux Lite didn't support UEFI?

For those that don't follow us and our development, that was a common misconception. We've actually supported UEFI since Series 2.x, that's nearly 6 years now. You've gotten the same programs, features and tweaks as all the other Linux Lite releases, just with UEFI added. The only difference that's ever existed was that it was never pushed in the media as the default release.

Further to the above, I said we would only provide a UEFI build as default, if our hand was forced. Without going into too much detail, you can draw your own conclusions here - https://www.anandtech.com/show/12068/intel-to-remove-bios-support-from-uefi-by-2020 Now was the latest we could react. It is what it is...
In a nutshell, Intel is dropping legacy BIOS's this year. That's roughly half the CPU market. I'd say 50% is a strong, impactful enough statistic for us to act in favour of our target base. Our goal after all, has always been to expose Windows and Mac users to an alternative operating system. We can't look at ourselves and say that we are doing that effectively if we restrict half of that market, some of which have never installed an OS before, to legacy technology.

How do I know if my Windows pc has UEFI?

In Windows Search, type msinfo or msinfo32 and launch the desktop app named System Information. Look for the BIOS Mode item, and if the value for it is UEFI, then you have the UEFI firmware. If it says BIOS Mode Legacy, then that’s the firmware you’re running.

Secure Boot is supported, but unless you know exactly how to handle it, it is a P.I.T.A. at best so I am going to say...you must disable Secure Boot to enable stress free computing.

[...]
Known Issues:

No prompt to eject Media at the end of the Legacy install, prompt is available at the end of the UEFI install.
Release Notes - works only in some installation modes.
Desktop icons - English support only.
Grub - holding shift down whilst booting in UEFI mode does not bring up the Grub menu (works in Legacy mode), waiting for Ubuntu fix.
Grub menu shows Linux Lite as 'Ubuntu'. After you install Linux Lite, you can change Grub to show 'Linux Lite':
Jerry and the team.

Further more, I installed Linux Lite on a UEFI machine (See left, Dell Precision T1700) and works fine, I already made lots of updates, one of them yesterday, another, today and everything works fine.
I do all partitioning BEFORE anything else, because I always make CUSTOM installations (/home and /data partitions that need to be left as they are and mounted at boot time.)

Below is the layout of my SSD:

https://www.facebook.com/photo/?fbid=3069450323102858

I guess it is obvious that the boot partition has a bootloader and it works.
And the "Legacy Mode" is disabled, because I need to backup with CloneZilla (which I already did, twice) and if this is enabled, CloneZilla raises errors when checking if images can be restored.
So yeah, it definitely works!

Read carefully the Lite Manual and GOOD LUCK!

[Makrand]

The bug was marked in the Ubuntu 14.04. Current version is Ubuntu 20.04. If I am installing with the default partition with the Ubuntu 20.04, I am not getting that error.
But with the default installer why I am getting the error with LL 5.0 ?

I can create the partition manually. But when the default installer can do the task why should I do that manually ?

There are various reasons for doing the partition manually. For starters, you may want to mount /home or /var on different partition.
I almost all time do partition manually.

I think this is LL specific issue. May be I will create issue on GitHub of LL.

Sent from my RMX1911 using Tapatalk

[Udayendu Kar]

The bug was marked in the Ubuntu 14.04. Current version is Ubuntu 20.04. If I am installing with the default partition with the Ubuntu 20.04, I am not getting that error.
But with the default installer why I am getting the error with LL 5.0 ?

I can create the partition manually. But when the default installer can do the task why should I do that manually ?

[Makrand]

@firenice03

Using LL for 1st time.
Helped my nephew installing it (remotely) for his school assignments.
Used Default lvm that installer gave.

Also, seen a lot of LL folks complaining about same warning / error for various LL versions.


Sent from my RMX1911 using Tapatalk

[firenice03]

@Udayendu Kar   @Makrand
You may want to give the link below a read thru...
I assume the Installer configured the LVM for you? On my install I set up the partitioning/LVM prior then installed (I wanted the LVM different than what the installer defaulted) -- I don't have the error.. I have Root, Home and SWAP all on LVM on a single VG..

https://www.linuxliteos.com/forums/installing-linux-lite/error-when-booting-diskfilter-writes-not-supported/

Code: [Select]

sudo lvs
  LV      VG       Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  home-lv linux-vg -wi-ao---- 100.00g                                                   
  root-lv linux-vg -wi-ao----  40.00g                                                   
  swap-lv linux-vg -wi-ao----   8.00g                                                   


sudo vgs
  VG       #PV #LV #SN Attr   VSize    VFree 
  linux-vg   1   3   0 wz--n- <160.00g <12.00g


[Udayendu Kar]

I am using Linux Lite 5.0 on both Dell Inspiron and on vms running on VMwrae as well as Oracle VirtualBox. And at all the places I am getting this message:

---
error: diskfilter writes are not supported.

Press any key to continue...
---

I am not using RAID but my root is on LVM. If I am using normal Ubuntu 18.04 LTS or 20.04 LTS, I never get this message but with Linux Lite its coming.

Even tried following the "quick_boot" parameter change as mentioned in:  https://askubuntu.com/questions/468466/diskfilter-writes-are-not-supported-what-triggers-this-error#:~:text=This%20is%20a%20bug%20that,LVM%20or%20a%20RAID%20partition.

But thats still not working.

==: Out put from my VM :==
 root  ~  df -PTH
Filesystem               Type      Size  Used Avail Use% Mounted on
udev                     devtmpfs  2.1G     0  2.1G   0% /dev
tmpfs                    tmpfs     413M  2.8M  411M   1% /run
/dev/mapper/vglinux-root ext4       78G  9.1G   65G  13% /
tmpfs                    tmpfs     2.1G     0  2.1G   0% /dev/shm
tmpfs                    tmpfs     5.3M  4.1k  5.3M   1% /run/lock
tmpfs                    tmpfs     2.1G     0  2.1G   0% /sys/fs/cgroup
/dev/sda1                vfat      536M  8.2k  536M   1% /boot/efi
tmpfs                    tmpfs     413M  8.2k  413M   1% /run/user/110
tmpfs                    tmpfs     413M  4.1k  413M   1% /run/user/1000
 root  ~  pvs
  PV         VG      Fmt  Attr PSize   PFree
  /dev/sda5  vglinux lvm2 a--  <74.50g    0
 root  ~  vgs
  VG      #PV #LV #SN Attr   VSize   VFree
  vglinux   1   2   0 wz--n- <74.50g    0
 root  ~  lvs
  LV     VG      Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  root   vglinux -wi-ao---- <73.54g
  swap_1 vglinux -wi-ao---- 980.00m
 root  ~

[firenice03]

Brand New installation of Linux lite latest 5.0. while booting getting message on screen as shown in title. Asking to press (K) to continue. If not pressed....boot ok.

Looks like this is some bug that is travelling in each LL version??

Note -  used LVM in setup for root disk.

Have you set up an LVM in each previous version of LL that you had this message?
I have LVM on my LL4.8 - I don't get prompted to press a key or that message - but I dont visually see grub load (i know its prolly there in the background). Although I did set up my partitioning outside of the install.

[Şerban S.]

Note -  used LVM in setup for root disk.

Read the whole thread. It is exactely what was the point: Virtual drives raise this kind of error.
LVM is exactely this: Logical Volume Management. That means that the drive is managed as a logical drive, as opposed to a PHYSICAL drive.
Do a search on "Installing GRUB on LVM" or the like.

Good luck!

[Makrand]

Hi,
thanks for reply.

Nah....it was an old machine. Dell inspiron 1420 laptop with 120G of single Sata SSD.

Plus the link you gave is like ubuntu 14.04. LL 5.X is based on ubuntu 20.04. not sure if that still applies.

Note -  used LVM in setup for root disk.

[Şerban S.]

Hi!

Read this article:

https://askubuntu.com/questions/468466/diskfilter-writes-are-not-supported-what-triggers-this-error

You probably installed Linux Lite using RAID.

Best regards!

[Makrand]

Brand New installation of Linux lite latest 5.0. while booting getting message on screen as shown in title. Asking to press (K) to continue. If not pressed....boot ok.

Looks like this is some bug that is travelling in each LL version??