Welcome!

The kernel problem with recent updates has been solved. Find the solution here

Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Startup failure after installation: media test failure check cable

cedricoola
Forum Novice
Forum  Novice
Posts: 21
Joined: Mon Jun 10, 2019 12:04 pm

Re: Startup failure after installation: media test failure check cable

#11

Post by cedricoola » Tue Jun 11, 2019 11:06 am

First of all, here you are

Code: Select all

[code]
System:    Host: mx1 Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum May 26  2019 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Laptop System: FUJITSU product: LIFEBOOK A532 v: N/A serial: <filter> 
           Mobo: FUJITSU model: FJNBB1C serial: <filter> UEFI: FUJITSU // Phoenix 
           v: Version 1.09 date: 05/22/2012 
Battery:   ID-1: BAT1 charge: 27.6 Wh condition: 29.7/47.5 Wh (63%) model: PAC BAT1 
           status: Unknown 
CPU:       Topology: Dual Core model: Intel Core i3-2370M bits: 64 type: MT MCP 
           arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19155 
           Speed: 823 MHz min/max: 800/2400 MHz Core speeds (MHz): 1: 1142 2: 938 3: 1076 
           4: 1024 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
           vendor: Fujitsu Limited. driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.2.6 
           direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Fujitsu Limited. 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.19.0-5-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Fujitsu Limited. driver: r8169 v: kernel port: 3000 bus ID: 02:00.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Intel Centrino Wireless-N 2230 driver: iwlwifi v: kernel port: 3000 
           bus ID: 08:00.0 
           IF: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 262.7 MiB (0.1%) 
           ID-1: /dev/sda vendor: Seagate model: ST9500325AS size: 465.76 GiB 
Partition: ID-1: / size: 2.93 GiB used: 262.7 MiB (8.8%) fs: overlay source: ERR-102 
           ID-2: swap-1 size: 3.91 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda10 
Sensors:   System Temperatures: cpu: 55.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/stretch stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 203 Uptime: 8m Memory: 3.72 GiB used: 905.8 MiB (23.8%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33 
[/code]

cedricoola
Forum Novice
Forum  Novice
Posts: 21
Joined: Mon Jun 10, 2019 12:04 pm

Re: Startup failure after installation: media test failure check cable

#12

Post by cedricoola » Tue Jun 11, 2019 11:15 am

Now this:

Code: Select all

demo@mx1:~
$ sudo chroot-rescue-scan

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for demo: 
===============================================================================
Starting chroot-rescue-scan
===============================================================================
Scanning partitions ...
Scanning directories ...
Only one Linux system was found
                                                                                                  
Please select a Linux System to visit                                                             
    Distro     Date        Dir  Device      Arch                                                  
  = 19.1 tessa 2019-06-04  sda9 sda9        64-bit                                                
  > Rescan all partitions for Linux systems                                                       
  > Quit                                                                                          
Press <Enter> to select the highlighted entry                                                     
Use 'r' to redraw, 'q' to quit                                                                    
                                                                                                  
Chrooting into distro 19.1_tessa
Directory: /media/sda9  Device: sda9
Use exit command or <ctrl>-d to exit the chroot
===============================================================================

(19.1_tessa) Tue Jun 11 17:09:33 /
chroot> grub-install --target=i386-pc /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.

(19.1_tessa) Tue Jun 11 17:13:23 /
chroot> 

cedricoola
Forum Novice
Forum  Novice
Posts: 21
Joined: Mon Jun 10, 2019 12:04 pm

Re: Startup failure after installation: media test failure check cable

#13

Post by cedricoola » Tue Jun 11, 2019 11:38 am

Now I restarted my pc
and the same thing happens.
screens of my first post.

Note that when running grub-install I was in MX LiveDVD in UEFI mode. Is that ok?

Now do you suggest me to try the method of reinstalling with BIOS mode?

or should we investigate your assumption that the boot flag is too far? 1TB ! but my disc is only 500Gb. how can it be?

I also have the Windows 7 DVD that came with the pc, in case it can help. (it say on it "this DVD allows to restore the OS" but it also says "all data will be deleted")

cedricoola
Forum Novice
Forum  Novice
Posts: 21
Joined: Mon Jun 10, 2019 12:04 pm

Re: Startup failure after installation: media test failure check cable

#14

Post by cedricoola » Tue Jun 11, 2019 11:45 am

Please note that prior to installing MX Linux last week, I have installed and run other Linux distributions in dual boot on this pc, always on that same partition.

User avatar
fehlix
Forum Veteran
Forum Veteran
Posts: 4262
Joined: Wed Apr 11, 2018 5:09 pm

Re: Startup failure after installation: media test failure check cable

#15

Post by fehlix » Tue Jun 11, 2019 11:47 am

cedricoola wrote:
Tue Jun 11, 2019 11:38 am
Now I restarted my pc
and the same thing happens.
screens of my first post.

Note that when running grub-install I was in MX LiveDVD in UEFI mode. Is that ok?

Now do you suggest me to try the method of reinstalling with BIOS mode?

or should we investigate your assumption that the boot flag is too far? 1TB ! but my disc is only 500Gb. how can it be?

I also have the Windows 7 DVD that came with the pc, in case it can help. (it say on it "this DVD allows to restore the OS" but it also says "all data will be deleted")
Sorry yes it's a 500GB not a 1TB. So better move the bootflag closer to the beginning of the disk.
Adjust the boot-flag, open Gparted when boote live an select the first partion mark with a boot flag. Some older BIOS, will simply dont see a boot flag on extented partions, and only check primary partions, which is the first partition.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
fehlix
Forum Veteran
Forum Veteran
Posts: 4262
Joined: Wed Apr 11, 2018 5:09 pm

Re: Startup failure after installation: media test failure check cable

#16

Post by fehlix » Tue Jun 11, 2019 11:48 am

cedricoola wrote:
Tue Jun 11, 2019 11:45 am
Please note that prior to installing MX Linux last week, I have installed and run other Linux distributions in dual boot on this pc, always on that same partition.
Right, but other distro might not have changed the orignal boot flag from the first partition ...
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

cedricoola
Forum Novice
Forum  Novice
Posts: 21
Joined: Mon Jun 10, 2019 12:04 pm

Re: Startup failure after installation: media test failure check cable

#17

Post by cedricoola » Tue Jun 11, 2019 11:55 am

fehlix wrote:
Tue Jun 11, 2019 11:48 am
cedricoola wrote:
Tue Jun 11, 2019 11:45 am
Please note that prior to installing MX Linux last week, I have installed and run other Linux distributions in dual boot on this pc, always on that same partition.
Right, but other distro might not have changed the orignal boot flag from the first partition ...
Then my situation may be an improvement opportunity for MX Linux. Support BIOSes that only check the first partition.

User avatar
fehlix
Forum Veteran
Forum Veteran
Posts: 4262
Joined: Wed Apr 11, 2018 5:09 pm

Re: Startup failure after installation: media test failure check cable

#18

Post by fehlix » Tue Jun 11, 2019 11:58 am

cedricoola wrote:
Tue Jun 11, 2019 11:55 am
fehlix wrote:
Tue Jun 11, 2019 11:48 am
cedricoola wrote:
Tue Jun 11, 2019 11:45 am
Please note that prior to installing MX Linux last week, I have installed and run other Linux distributions in dual boot on this pc, always on that same partition.
Right, but other distro might not have changed the orignal boot flag from the first partition ...
Then my situation may be an improvement opportunity for MX Linux. Support BIOSes that only check the first partition.
First confirm that my receipt works, and than write a bug report at https://bugs.mxlinux.org/
as otherwise it may be get lost ;)
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

cedricoola
Forum Novice
Forum  Novice
Posts: 21
Joined: Mon Jun 10, 2019 12:04 pm

Re: Startup failure after installation: media test failure check cable

#19

Post by cedricoola » Tue Jun 11, 2019 12:24 pm

One last doubt before I proceed: you mention the dev/sda5, this is indeed the partition where I have Windows. Note that sda5 is inside sda2 (extended partition).
But before sd2 there is sda1 (ntfs, Label Winre, size 2,00Gb, used 674,37Mb, flag Diag).
Do you confirm I should put the flag on sda5?
I ask because I have no clue about this.

User avatar
fehlix
Forum Veteran
Forum Veteran
Posts: 4262
Joined: Wed Apr 11, 2018 5:09 pm

Re: Startup failure after installation: media test failure check cable

#20

Post by fehlix » Tue Jun 11, 2019 1:04 pm

cedricoola wrote:
Tue Jun 11, 2019 12:24 pm
One last doubt before I proceed: you mention the dev/sda5, this is indeed the partition where I have Windows. Note that sda5 is inside sda2 (extended partition).
But before sd2 there is sda1 (ntfs, Label Winre, size 2,00Gb, used 674,37Mb, flag Diag).
Do you confirm I should put the flag on sda5?
I ask because I have no clue about this.
better put the flag on sda1 (the first system / diag partion)
Note: The flag is only used by bios, just to quickly check whether the drive is a boot-drive.
Grub does not care about the flag. Windows does care, but as we boot into Grub, the flag is only needed by bios,
and not used by anything else. Booting into WIndows from Grub does not need the flag.
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

Post Reply

Return to “Installation”