Splintered Thread from___Drive Failure Imminent_"Last Option"

So I'm just going to put this here, a couple of questions actually.

It seems that there is a lot of work to install Etcher on Linux. Is there a better a

I'm continuing this post using my tablet because Last Option just froze up again.

Has ANYONE had so many obstacles getting FULLY moved over to Linux???
 


Sherri is a Cat said:
Has ANYONE had so many obstacles getting FULLY moved over to Linux???
Click to expand...

Yes, sadly, we get some, and sometimes they drift back to "the Giant".

You could fire up the "bye-bye" machine and put Etcher on it and burn USB sticks from there.

I would be inclined to make use of it, that imminent drive failure might be weeks or even months away, and it has a working LM 21.3 on it.

I have to keep working on generating a USB stick with LM 21.2 on it and with Persistence, using Ventoy, but I'll get back when I can.
 
wizardfromoz said:
Yes, sadly, we get some, and sometimes they drift back to "the Giant".
Click to expand...
Nope, not going back to the Giant.
wizardfromoz said:
You could fire up the "bye-bye" machine and put Etcher on it and burn USB sticks from there.
Click to expand...

Bye-Bye doesn't recognize the USB drives
wizardfromoz said:
I would be inclined to make use of it, that imminent drive failure might be weeks or even months away, and it has a working LM 21.3 on it.

I have to keep working on generating a USB stick with LM 21.2 on it and with Persistence, using Ventoy, but I'll get back when I can.
Click to expand...
 
I'm nearly ready to give up and keep using a live version.
I've taken maybe a ten minute break over an 8 hour period of time.

Two Lenovo's both have problems with the hard disk...
 
I'm going to post images of some things that someone else might understand better than I do, maybe it might help something.
1708227796198.png







Code: 
boot-repair-4ppa200                                              [20240218_0340]

============================== Boot Info Summary ===============================

 => No known boot loader is installed in the MBR of /dev/sdb.

sda: ___________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Grub2 (v1.99-2.00)
    Boot sector info:  Grub2 (v1.99-2.00) is installed in the boot sector of
                       sda and looks at sector 0 of the same hard drive for
                       core.img, but core.img can not be found at this
                       location.
    Mounting failed:   mount: /mnt/BootInfo/FD/sda: /dev/sda already mounted or mount point busy.


================================ 0 OS detected =================================


================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: Stoney [Radeon R2/R3/R4/R5 Graphics] from Advanced Micro Devices, Inc. [AMD/ATI]
Live-session OS is Linuxmint 64-bit (Linux Mint 21.2, victoria, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: AYCN25WW(1.25) from LENOVO
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
No EFI in dmseg.
SecureBoot enabled but mokutil says: SecureBoot enabled - Please report this message to [email protected].
BootCurrent: 0016
Timeout: 0 seconds
BootOrder: 0016,0000,0014,0015,0017,0018,0019
Boot0000* Windows Boot Manager    HD(1,GPT,f801f9a4-f861-46bc-977e-fde0871d3e80,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...H................
Boot0010  Setup    FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu    FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0012  Diagnostic Splash    FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  OilDiagApp    FvFile(f8397897-e203-4a62-b977-9e7e5d94d91b)
Boot0014* NVMe:    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a4)
Boot0015* ATA HDD:    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot0016* USB HDD:    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0017* PCI LAN:    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0018* USB FDD:    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0019* USB CD:    VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot001A* Lenovo Recovery System    File(\EFI\Microsoft\Boot\lrsBootMgr.efi)


============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________


Partitions info (1/3): _________________________________________________________


Partitions info (2/3): _________________________________________________________


Partitions info (3/3): _________________________________________________________


fdisk -l (filtered): ___________________________________________________________

Disk sda: 116.06 GiB, 124623257600 bytes, 243404800 sectors
Disk identifier: 7F710194-A624-43FA-9BA2-5155CFB1273A
        Start       End   Sectors   Size Type
sda1       64   5902403   5902340   2.8G Microsoft basic data
sda2  5902404   5910899      8496   4.1M EFI System
sda3  5914624 243404736 237490113 113.2G Linux filesystem

parted -lm (filtered): _________________________________________________________

sda:125GB:scsi:512:512:gpt:General USB Flash Disk:;
1:32.8kB:3022MB:3022MB::ISO9660:hidden, msftdata;
2:3022MB:3026MB:4350kB::Appended2:boot, esp;
3:3028MB:125GB:122GB:ext4::;
sdb:-512.00B:scsi:512:512:unknown:ATA ST1000LM035-1RK1:;

blkid (filtered): ______________________________________________________________

NAME   FSTYPE   UUID                                 PARTUUID                             LABEL                           PARTLABEL
sda    iso9660  2023-07-11-16-54-30-00                                                    Linux Mint 21.2 Cinnamon 64-bit
├─sda1 iso9660  2023-07-11-16-54-30-00               7f710194-a624-43fa-9ba3-5155cfb1273a Linux Mint 21.2 Cinnamon 64-bit ISO9660
├─sda2 vfat     8D6C-A9F8                            7f710194-a624-43fa-9ba0-5155cfb1273a ESP                             Appended2
└─sda3 ext4     c8936ba5-1fd2-471b-a494-4383de6ad657 883cda82-8843-364a-a9fe-285abeb90266 writable                       
sdb                                                                                                                       

Mount points (filtered): _______________________________________________________

                                                             Avail Use% Mounted on
/dev/disk/by-label/writable[/install-logs-2024-02-18.0/log] 105.2G   0% /var/log
/dev/sda1                                                        0 100% /cdrom

Mount options (filtered): ______________________________________________________

/dev/disk/by-label/writable[/install-logs-2024-02-18.0/log] ext4            rw,relatime
/dev/sda1                                                   iso9660         ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8

======================== Unknown MBRs/Boot Sectors/etc =========================

Unknown MBR on /dev/sdb





Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the boot.
 
1708228429286.png


@wizardfromoz

This image is from the code I pasted in my previous post. Other that this information is about my USB drive, I'm not sure exactly what I'm looking. But I did notice 2.8G Microsoft basic data.
Generated with Boot Repair.
I haven't tried to do anything with it.
EFI is for window. right?
Could the 2.8G Microsoft basic date possibly have anything to do with my problem?
If so, maybe partitioning the hard drive with a different format would work.
And maybe the USB should be formatted too?
 
Last edited:
If I'm running Live Linux from the USB Drive, not the hard drive, can I format the hard drive using "Disks"?

1708229064847.png



The hard drive doesn't show up in GParted

1708229196877.png
 
Sherri is a Cat said:
can I format the hard drive using "Disks"?
Click to expand...

Maybe.

When I saw this the other day, I was curious about the size it displayed in Disks, the drive is only 1 TB, and yet it shows as kazillions of TB, more like it is Exabytes or Petabytes or something (I lose track after Terabytes).

If you want to try it, you will first need to form a Partition Table on it, and then format a partition under that.

Give me a minute and I'll check a couple of things.
 
wizardfromoz said:
Maybe.

When I saw this the other day, I was curious about the size it displayed in Disks, the drive is only 1 TB, and yet it shows as kazillions of TB, more like it is Exabytes or Petabytes or something (I lose track after Terabytes).

If you want to try it, you will first need to form a Partition Table on it, and then format a partition under that.

Give me a minute and I'll check a couple of things.
Click to expand...

I want you to see something I noticed....
I'm going to post new screen shots in a second
 
I should say "and no, that's not partition image"
 
Since I'm not so familiar with Linux it's going to take me a little more time to show you some screen shots and where I found all the information.

I'll write everything I've noticed 1st, in a different post
 
Basically what I've noticed comes down to this.

Microsoft is mentioned in the UEFI, the USB I running Live linux from and the hdd.
But.....

The 3 GB usb I formatted with GParted says noting about Microsoft
 
I hope you don't mind all of my ideas, this is how I learn stuff. And who knows? Maybe something I notice would trigger something you know
 
Should You Disable Secure Boot?

"If you plan on dual booting a modern Windows OS.....– along with either some Linux distro....you might have to disable Secure Boot since Secure Boot can block the second OS from booting"
 
Always a good idea - I never use it.
 
That secure boot thing was the problem I ran into when I was installing XP on my ASUS. I had to enter Legacy BIOS to do it.
 
Maybe that bad sector has something to do with secure boot since Linux isn't signed by a key loaded into UEFI, Windows is the only OS that that "key works with"..
 
You must log in or register to reply here.

Members online

Total: 689 (members: 4, guests: 685)

Latest posts

Top