+- Linux Lite Forums (https://www.freecinema2022.gq/forums)
+-- Forum: Software - Support (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=5)
+--- Forum: Installing Linux Lite (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=17)
+--- Thread: Error when booting: Diskfilter writes not supported (/showthread.php?tid=5344)
Re: Error when booting: Diskfilter writes not supported - kpanic - 06-18-2018
[member=5059]whateverthing[/member], did you remember to disable the automounter?
'Menu' -> 'Settings' -> 'Removable Drives and Media'
And under "Removable Storage" make sure that every button is unchecked
and then close the settings.
Also, when you create these partitions and file systems, you may as well
do it as root: just command
Code:
sudo su...in case you are not root already for some reason.
If this does not work, then try:
Code:
umount /dev/sda1 && mkfs.ext4 -t ext4 -m 2 -L root /dev/sda1If even this does not work, then try:
Code:
umount /dev/sda1 && wipefs -a /dev/sda1 && mkfs.ext4 -t ext4 -m 2 -L root /dev/sda1Hopefully this helps. Just a few steps left to do
Re: Error when booting: Diskfilter writes not supported - whateverthing - 06-18-2018
I'm sure I did:
'Menu' -> 'Settings' -> 'Removable Drives and Media'
...and unchecked all Removable Storage boxes.
And after the error I checked to make sure, and they were still unchecked.
Re: Error when booting: Diskfilter writes not supported - kpanic - 06-18-2018
[member=5059]whateverthing[/member], ok good.
Please try those two methods, which I wrote
Re: Error when booting: Diskfilter writes not supported - whateverthing - 06-18-2018
I just tried them both. Both times it said it's not mounted, but both times it said it was in use and could not execute the commands.
Code:
linux ~ sudo umount /dev/sda1 && mkfs.ext4 -t ext4 -m 2 -L root /dev/sda1
umount: /dev/sda1: not mounted.
linux ~ sudo mkfs.ext4 -t ext4 -m 2 -L root /dev/sda1
mke2fs 1.44.1 (24-Mar-2018)
/dev/sda1 contains a LVM2_member file system
Proceed anyway? (y,N) y
/dev/sda1 is apparently in use by the system; will not make a filesystem here!
linux ~ sudo umount /dev/sda1 && wipefs -a /dev/sda1 && mkfs.ext4 -t ext4 -m 2 -L root /dev/sda1
umount: /dev/sda1: not mounted.
linux ~ sudo mkfs.ext4 -t ext4 -m 2 -L root /dev/sda1
mke2fs 1.44.1 (24-Mar-2018)
/dev/sda1 contains a LVM2_member file system
Proceed anyway? (y,N) y
/dev/sda1 is apparently in use by the system; will not make a filesystem here!Re: Error when booting: Diskfilter writes not supported - kpanic - 06-18-2018
This is strange. Please try to boot into Safe Mode and try again.
If it succeeds in Safe Mode, then boot back to normal mode
Re: Error when booting: Diskfilter writes not supported - kpanic - 06-18-2018
[member=5059]whateverthing[/member], if even Safe Mode does not allow you to create the ext4, then maybe LVM daemon is running
and does not let you do it.
Please try:
Code:
systemctl stop lvm2-lvmpolld.servicefollowed by:
Code:
kill -HUP $(cat /run/lvmetad.pid)Re: Error when booting: Diskfilter writes not supported - trinidad - 06-18-2018
[member=7701]kpanic[/member]
I've been following this discussion and if you come up with a solution using the LL live disk I think it should be stickied here. Your last answer is a logical suggestion but I expect that the LVM tools will just restart as soon as you try to repartition because of the sector misalignment, and even if the sector misalignment seems to resolve there is a good chance that kernel updates will rediscover it. I have experienced this behavior from Ubuntu 16.04 on an ASUS AMD box originally with a Windows 8 default OS with a 1T SATA drive. I eventually solved the issue but my solution is too ugly to recommend here. Below is some info that may or may not be worthwhile to add to the discussion.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799295
http://ask.xmodulo.com/mount-lvm-partition-linux.html
TC
Re: Error when booting: Diskfilter writes not supported - kpanic - 06-18-2018
[member=5916]trinidad[/member], thanks for the comment!
I don't know why his drive is 'in use' since I'm a newbie when it comes to LL or Ubuntu
installations but in my opinion, if you boot a Live system, which remains only in RAM,
it should NOT touch (or even worse, use) your hard drives in any way.
I mean, that is the whole idea of a "Live System", right?
However, if you know a solution to this particular problem, please help the guy out,
since I'm soon out of solutions to his problem...
Cheers!
kpanic
Re: Error when booting: Diskfilter writes not supported - kpanic - 06-18-2018
Meanwhile, let me introduce a more brutal approach to this problem.
Since the partitioning succeeded, then you may as well do:
(First disable the lvm daemon(s) as I explained before. Then (as root):
Code:
dd if=/dev/zero of=/dev/sda1The dd command does not watch other processes or existing signatures,
so it just wipes out every lvm-signatures among everything else in your root partition.
Just let it do it's job two minutes (then CTRL+C) and I'm quite sure LVM does not lock
that partition after you reboot...
Re: Error when booting: Diskfilter writes not supported - trinidad - 06-18-2018
It was probably caused when the OP installed the 3.8 system. Just took the whole drive and went MBR and broke a Windows 32bit BIOS partition. I pulled the drive and plugged it into my one pure Linux box that has never had Windows on it and installed the system to the drive there. I plugged it back into the Windows 8 problem box, tweaked a few hardware settings and all is well with the HDD though I must hit F1 to boot. Ugly I know, but it was a long day and I got the box and drive in that condition from another person.
I tried zeroing the whole drive initially with a gparted live disk which took quite a while but then the ISO wouldn't install. Even Debian net install bailed at grub installation so it did not solve the sector misalignment issue. That's when ugly came into play. The drive can't be zeroed out of misalignment running on the offending machine once the BIOS persistent partition is corrupted. Drive must be removed from the Windows machine with the broken BIOS to do so, OR initially set up for Ubuntu from a Windows power shell which is unfortunately an option the OP no longer has.
TC