MX-19 Beta 3 Feedback

Forum rules
Locked
Message
Author
User avatar
Jerry3904
Administrator
Posts: 23098
Joined: Wed Jul 19, 2006 6:13 am

Re: MX-19 Beta 3 Feedback

#361 Post by Jerry3904 »

No it's not a problem. That file is simply not being used in MX Linux.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Top
User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#362 Post by bpr323 »

A new bunch of negative tests for failed "auto-install"
You do not have the required permissions to view the files attached to this post.
Top
User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#363 Post by bpr323 »

continued ..
You do not have the required permissions to view the files attached to this post.
Top
User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#364 Post by bpr323 »

continued ...
You do not have the required permissions to view the files attached to this post.
Top
User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#365 Post by bpr323 »

continued ...
You do not have the required permissions to view the files attached to this post.
Top
User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#366 Post by bpr323 »

1) It appears to me that in "full mode" minstall writes back to boot disk and "remembers" that the last attempted install was on NTFS-formatted single gpt-partitioned NVMe.
So even if I blow away all partitions with EASEUS boot USB, the NTFS comes back on the target disk.
2) installing from snapshot ISO doesn't work for me
3) the only (final ) succesfull install was when I created a single partition on the NVMe (gpt table) and formatted it with ext4
4) has anyone tested the "read-only" (dd) version of USB creator? It produces a weird single partition on USB - it boots, but fails to install.
Top
User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#367 Post by bpr323 »

corrupted NVMe partitions after failed auto-install onto single ext4 partition
You do not have the required permissions to view the files attached to this post.
Top
User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#368 Post by bpr323 »

bpr323 wrote: Sun Oct 13, 2019 10:29 am 1) It appears to me that in "full mode" minstall writes back to boot disk and "remembers" that the last attempted install was on NTFS-formatted single gpt-partitioned NVMe.
So even if I blow away all partitions with EASEUS boot USB, the NTFS comes back on the target disk.
2) installing from snapshot ISO doesn't work for me
3) the only (final ) succesfull install was when I created a single partition on the NVMe (gpt table) and formatted it with ext4 and burned a new USB from 19b3 factory ISO
4) has anyone tested the "read-only" (dd) version of USB creator? It produces a weird single partition on USB - it boots, but fails to install.
Top
hunghung

Re: MX-19 Beta 3 Feedback

#369 Post by hunghung »

Weired, I always use ddrescue to "burn" the MX iso to my usb stick and it never fail me. What would you do when you're on other Unix-like system and don't have MX Live USB Maker? gddrescue or the plain old dd is universal and guaranteed to always works.
Top
hunghung

Re: MX-19 Beta 3 Feedback

#370 Post by hunghung »

I also used to have installation failure once, also resulted in a corrupt partition table with a plain 256 MB ext4 partition. How did I solve this problem? Haha, I just reboot and try again, this time it worked ;)

p/s: I did nuke the drive with dd if=/dev/zero with bs=1M count=1000 before try again, though :happy:
Top
Locked

Return to “General”