- This topic has 10 replies, 8 voices, and was last updated Sep 3-11:18 am by ModdIt.
-
Posts
-
PenguinGuy
Hi,
Trying to get antiX installed on a newish machine that supports EFI (i7, 16gb RAM, 900gb SSD).
SSD passes SMART test & installs.
Tried both custom configuration & auto — the last is auto.
I’ve tried about 5 times (use G-Parted to unmount & delete), but still no boot device is detected by the BIOS (endless load BiOS loop without USB).
The GRUB boot rescue tools are also unable to detect it.
In LIVE USB I can see the files in Space-FM & they appear to work. I can use the MBR repair tool on the install, but it doesn’t seem to help. I also tried antiX update before install, but it ends with after some writes with a blank Ok dialog (also doesn’t seem to help).
Screencaps:
https://i.postimg.cc/WzSR7zq8/ss-00.jpg
https://i.postimg.cc/p27jQkZK/ss-01.jpg
NOTE: there are no ‘Secure’ or ‘Fast’ Boot settings (or anything odd) enabled.
Any ideas?
$ inxi -zv7
System:
Host: antix1 Kernel: 4.9.0-264-antix.1-amd64-smp x86_64 bits: 64
compiler: gcc v: 8.3.0 Desktop: IceWM 2.3.4 dm: SLiM 1.3.6
Distro: antiX-19.4_x64-full Grup Yorum 20 May 2021
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Desktop Mobo: ASRock model: H97 Performance serial: <filter>
UEFI [Legacy]: American Megatrends v: P2.40 date: 07/28/2015
Memory:
RAM: total: 15.66 GiB used: 676.1 MiB (4.2%)
RAM Report:
permissions: Unable to run dmidecode. Root privileges required.
CPU:
Topology: Quad Core model: Intel Core i7-4790K bits: 64 type: MT MCP
arch: Haswell rev: 3 L2 cache: 8192 KiB bogomips: 64001
Speed: 4361 MHz min/max: 800/4400 MHz Core speeds (MHz): 1: 4361 2: 4381
3: 4368 4: 4332 5: 4398 6: 4368 7: 4397 8: 4347
Flags: abm acpi aes aperfmperf apic arat arch_perfmon avx avx2 bmi1 bmi2
bts clflush cmov constant_tsc cx16 cx8 de ds_cpl dtes64 dtherm dts ept
erms est f16c flexpriority fma fpu fsgsbase fxsr hle ht ida invpcid
invpcid_single kaiser lahf_lm lm mca mce mmx monitor movbe msr mtrr
nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln
pni popcnt pse pse36 pts rdrand rdtscp rep_good rtm sdbg sep smep ss sse
sse2 sse4_1 sse4_2 ssse3 syscall tm tm2 tpr_shadow tsc tsc_adjust
tsc_deadline_timer vme vmx vnmi vpid x2apic xsave xsaveopt xtopology xtpr
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412
Device-2: NVIDIA GM200 [GeForce GTX 980 Ti] vendor: Micro-Star MSI
driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:17c8
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1680×1050~60Hz
OpenGL: renderer: NV120 v: 4.3 Mesa 18.3.6 direct render: Yes
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:03.0
chip ID: 8086:0c0c
Device-2: Intel 9 Series Family HD Audio vendor: ASRock
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8ca0
Device-3: NVIDIA GM200 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fb0
Device-4: Logitech type: USB
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus ID: 4-1:2
chip ID: 046d:085e serial: <filter>
Sound Server: ALSA v: k4.9.0-264-antix.1-amd64-smp
Network:
Device-1: Intel Ethernet I218-V vendor: ASRock driver: e1000e v: 3.2.6-k
port: f080 bus ID: 00:19.0 chip ID: 8086:15a1
IF: eth0 state: down mac: <filter>
Device-2: Realtek RTL8187 Wireless Adapter type: USB driver: rtl8187
bus ID: 3-2:123 chip ID: 0bda:8187 serial: <filter>
IF: wlan0 state: down mac: <filter>
Device-3: Linksys WUSB54GC v3 802.11g Adapter [Ralink RT2070L] type: USB
driver: rt2800usb bus ID: 3-5:4 chip ID: 1737:0077 serial: <filter>
IF: wlan1 state: up mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IP v6: <filter> type: dynamic mngtmpaddr scope: global
IP v6: <filter> scope: link
WAN IP: <filter>
Drives:
Local Storage: total: 3.85 TiB used: 2.40 TiB (62.3%)
ID-1: /dev/sda vendor: SanDisk model: SDSSDXPS960G size: 894.25 GiB
speed: 1.5 Gb/s serial: <filter> rev: T0RL scheme: MBR
ID-2: /dev/sdb vendor: Crucial model: CT256MX100SSD1 size: 238.47 GiB
speed: 6.0 Gb/s serial: <filter> rev: MU01 scheme: MBR
ID-3: /dev/sdc type: USB vendor: Western Digital
model: WD My Passport 0827 size: 2.73 TiB serial: <filter> rev: 1012
scheme: MBR
ID-4: /dev/sdd type: USB vendor: SanDisk model: Ultra size: 14.91 GiB
serial: <filter> rev: 1.00 scheme: MBR
Message: No Optical or Floppy data was found.
RAID:
Message: No RAID data was found.
Partition:
ID-1: / size: 12.46 GiB used: 41.2 MiB (0.3%) fs: overlay source: ERR-102
label: N/A uuid: N/A
ID-2: /live/boot-dev raw size: 14.91 GiB size: <root required>
used: <root required> fs: vfat dev: /dev/sdd1 label: ANTIX-LIVE
uuid: 0699-CBFA
ID-3: /live/linux raw size: 1.14 GiB size: <root required>
used: <root required> fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A
ID-4: /media/demo/System Reserved size: 100.0 MiB used: 26.7 MiB (26.7%)
fs: ntfs dev: /dev/sdb1 label: System Reserved uuid: 8CA29ACDA29ABAE2
ID-5: /media/demo/WD3tbUSB3_00 size: 2.73 TiB used: 2.31 TiB (84.6%)
fs: ntfs dev: /dev/sdc1 label: WD3tbUSB3_00 uuid: 24D48569D4853E54
ID-6: /media/demo/sdb2-ata-Crucial_CT256MX1 size: 120.00 GiB
used: 85.27 GiB (71.1%) fs: ntfs dev: /dev/sdb2 label: N/A
uuid: 01D76AEB356131E0
ID-7: /media/demo/sdb3-ata-Crucial_CT256MX1 size: 463.0 MiB
used: 9.9 MiB (2.1%) fs: ntfs dev: /dev/sdb3 label: N/A
uuid: C48CCC8C8CCC7A86
ID-8: /media/demo/sdb4-ata-Crucial_CT256MX1 size: 20.00 GiB
used: 5.59 GiB (27.9%) fs: ntfs dev: /dev/sdb4 label: N/A
uuid: 01D76AEB4635AAA0
ID-9: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
label: swapantiX uuid: ca602bda-3910-4cb6-b091-0f8ab3d60b2d
Unmounted:
ID-1: /dev/sda1 size: 26.59 GiB fs: ext4 label: rootantiX19
uuid: c3005cb0-680d-4353-b3e7-edad60347bf2
ID-2: /dev/sda3 size: 859.64 GiB fs: ext4 label: homeantiX
uuid: 832bde39-370e-4ebb-8074-913b9735f960
USB:
Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0
speed: 480 Mb/s chip ID: 1d6b:0002
Hub: 1-1:2 info: Intel ports: 6 rev: 2.0 speed: 480 Mb/s
chip ID: 8087:8009
Device-1: 1-1.6:3 info: Western Digital type: Mass Storage
driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s
chip ID: 1058:0827 serial: <filter>
Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0
speed: 480 Mb/s chip ID: 1d6b:0002
Hub: 2-1:2 info: Intel ports: 8 rev: 2.0 speed: 480 Mb/s
chip ID: 8087:8001
Hub: 3-0:1 info: Full speed (or root) Hub ports: 14 rev: 2.0
speed: 480 Mb/s chip ID: 1d6b:0002
Device-2: 3-2:123 info: Realtek RTL8187 Wireless Adapter type: N/A
driver: rtl8187 interfaces: 1 rev: 2.0 speed: 480 Mb/s chip ID: 0bda:8187
serial: <filter>
Device-3: 3-5:4 info: Linksys WUSB54GC v3 802.11g Adapter [Ralink RT2070L]
type: Network driver: rt2800usb interfaces: 1 rev: 2.0 speed: 480 Mb/s
chip ID: 1737:0077 serial: <filter>
Hub: 3-13:6 info: Texas Instruments TUSB2040/2070 Hub ports: 4 rev: 1.1
speed: 12 Mb/s chip ID: 0451:1446
Device-4: 3-13.1:8 info: Microsoft Internet Keyboard Pro
type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 1.1
speed: 1.5 Mb/s chip ID: 045e:002b
Device-5: 3-14:7 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID
driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
chip ID: 046d:c52b
Hub: 4-0:1 info: Full speed (or root) Hub ports: 6 rev: 3.0 speed: 5 Gb/s
chip ID: 1d6b:0003
Device-6: 4-1:2 info: Logitech type: Video,Audio,HID
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo interfaces: 5 rev: 3.1
speed: 5 Gb/s chip ID: 046d:085e serial: <filter>
Device-7: 4-5:3 info: SanDisk Ultra type: Mass Storage driver: usb-storage
interfaces: 1 rev: 3.0 speed: 5 Gb/s chip ID: 0781:5581 serial: <filter>
Sensors:
System Temperatures: cpu: 48.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 207 Uptime: 16m Init: SysVinit v: 2.93 runlevel: 5 default: 5
Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: roxterm
inxi: 3.0.36- This topic was modified 1 year, 8 months ago by PenguinGuy.
- This topic was modified 1 year, 8 months ago by PenguinGuy.
- This topic was modified 1 year, 8 months ago by christophe. Reason: marked solved at request
marcelocripe
Hello PenguinGuy.
Welcome to antiX Linux and the forum.
Regardless of your level of knowledge about GNU/Linux, I recommend you read these excellent tutorials created by @PPC:
Short essential how-to list for the complete Linux newbie and How-to install applications – 2020 version.
I don’t know how to write in English and I send you my texts translated by the internet translator, I hope you can understand everything.
When you start a thread or participate with a post, remember to check the option “Notify me of follow-up replies via email”, by checking this option, you will receive a message in your inbox whenever there are replies from the topic in question.
After this short introduction, let’s get to your case…
Looking at the https://postimg.cc/N90QxHsh image, you can confirm that you are using the ISO with the 4.9.0.264 kernel, try using the official ISO “antiX-19.4_x64-full.iso” with kernel 4.19.184. If it still doesn’t work, have this ISO created by Xecure with kernel 5.8.16. I tend to make this sequence from kernel 4.9.0.264, then 4.19.184, when neither works, certainly with kernel 5.8.16 it works.
marcelocripe
(Original text in Brazilian Portuguese)– – – – –
Olá PenguinGuy.
Seja bem-vindo ao antiX Linux e ao fórum.
Independentemente do seu nível de conhecimento sobre GNU/Linux, eu recomendo você ler estes excelentes tutoriais criados pelo @PPC:
Short essential how-to list for the complete Linux newbie e How-to install applications – 2020 version.
Eu não sei escrever em inglês e te envio os meus textos traduzidos pelo tradutor da internet, eu espero que você consiga compreender tudo.
Quando você iniciar algum tópico ou participar com alguma postagem, lembre-se de marcar a opção “Notify me of follow-up replies via email”, marcando esta opção, você receberá uma mensagem na sua caixa de e-mail sempre que houver respostas do tópico em questão.
Depois desta pequena introdução, vamos ao seu caso …
Observando a imagem https://postimg.cc/N90QxHsh, é possível confirmar que você está usando a ISO com o kernel 4.9.0.264, tente usar a ISO oficial “antiX-19.4_x64-full.iso” com kernel 4.19.184. Se mesmo assim não funcionar, tem esta ISO criada pelo Xecure com kernel 5.8.16. Eu costumo fazer esta sequência de kernel 4.9.0.264, depois 4.19.184, quando nenhuma das duas funcionam, certamente com o kernel 5.8.16 funciona.
marcelocripe
(Texto original em Português do Brasil)
rokytnji
Made the same mistake as I* did.
You need a small boot partition on these uefi gear.
It is late here so I’ll leave off on this this thread till later.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problems
caprea
It might would be helpfull to know some more about your hardware, might post the output of
inxi -zv7
from the live stick. I wonder if this could be a problem with “secure boot” adjusted in biosModdIt
Hi, as roki wrote you probably need a small boot partition, I met that numerous times.
I have about 200 MiB formatted Fat 32 Marked Boot and ESP. Can be a bit bigger or smaller.
Then root, home, you can of course use a large single partition. I do not swap to SSD.
no need with 8 Gig memory.
If you are able turn off secure boot in BIOS, it is intended to force you to use windoze.OT: but maybe useful.
Lately I no longer install on own systems, just run from a customised USB sticks is as
fast running as from my internal SSD. I save data to a separate stick or internal drive.
Regular remastering after changes is antiX magic.
Xecure
On UEFI systems you need to mount the fat32 ESP partition to store the antiX .efi files (so that they are detected at boot time).
On the new installer, I think you have to select that partition before continuing. If it doesn’t exist, you will need to create it with Gparted.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.PenguinGuy
On UEFI systems you need to mount the fat32 ESP partition to store the antiX .efi files (so that they are detected at boot time).
On the new installer, I think you have to select that partition before continuing. If it doesn’t exist, you will need to create it with Gparted.
UPDATE SOLVED: So basically after getting the new 19.4 from Sourceforge, preformatting with g-parted, + (the most important part) was checking the option ‘Check for bad sectors’. This SSD has barely been used other than the bunch of formats I recently did to install antiX — not quite sure why it is worn out or damaged.
NOTE: Also I tried making a USB live install of the antiX b1.iso (beta) & ran that first, but it kept telling me to remove the disk & wouldn’t boot (maybe the iso was corrupted somehow?).
Old text….
——————————————————————-
After installing ESP at 112MB & 99MB with the older 19.4 it still wouldn’t boot.I downloaded the new 19.4 x64 iso directly from Sourceforge, but now it keeps erroring out “Failed to format the required partitions.” my SSD at about 1 or 2% (even if I use g-parted to preformat or pre-delete + reboot the antiX Live to make sure the drives are properly formatted): https://i.postimg.cc/wqZ7Zgv3/screenshot.jpg
Pretty confused now. Also, this newer Antix iso also seems to not mount my other USB drives randomly at start.
Never had any of these problems with the older Antix 19.4 iso.
- This reply was modified 1 year, 8 months ago by PenguinGuy.
- This reply was modified 1 year, 8 months ago by PenguinGuy.
- This reply was modified 1 year, 8 months ago by PenguinGuy.
Anonymous
It is totally possible bad ssd or iso.
In gparted could try creating a new partition table with gpt for the uefi
device >> create partition table
and setting the esp partition with the bootable flag under
partition >> manage flags
in the gparted menu
Your initial inxi post showed the drives as mbr scheme, that is for legacy boot
in the bios settings.from initial inxi post: Local Storage: total: 3.85 TiB used: 2.40 TiB (62.3%) ID-1: /dev/sda vendor: SanDisk model: SDSSDXPS960G size: 894.25 GiB speed: 1.5 Gb/s serial: <filter> rev: T0RL scheme: MBR ID-2: /dev/sdb vendor: Crucial model: CT256MX100SSD1 size: 238.47 GiB speed: 6.0 Gb/s serial: <filter> rev: MU01 scheme: MBR ID-3: /dev/sdc type: USB vendor: Western Digital model: WD My Passport 0827 size: 2.73 TiB serial: <filter> rev: 1012 scheme: MBR ID-4: /dev/sdd type: USB vendor: SanDisk model: Ultra size: 14.91 GiB serial: <filter> rev: 1.00 scheme: MBRalso checksum the md5 on the downloaded iso
PenguinGuy
How do I change this post to [SOLVED] — does an admin need to increase my privileges? I only see ‘reply quote #(post)’.
sybok
@[SOLVED]:
It is possible to edit/change the 1st post (incl. topic) for only 2-3 days.
You may private-message one of the moderators of the forum.Regarding health of SSD, your near new ssd will not be worn out, if it is really near new.
Maybe worth installing smartctl then take a look at results. Like many electronic devices
SSD have early failure modes then errors may start to rise after a couple of years.sudo smartctl -t short -a /dev/sdX (in place of sdX, use the name of your SSD).
This will run a short test that takes approximately 2 minutes.
When the test is complete, run command sudo smartctl -a /dev/sdX to display the results.I never swap to an SSD as the possible very frequent writes could reduce life, on my fairly modern device
with 8GB memory I have no swap at all, fine for my usage although processing Nikon Raw images is very memory
intensive.
- You must be logged in to reply to this topic.
