[SOLVED] Need help fixing boot up

MrEd · January 3, 2021, 9:25pm

Last night I was trying to fix badblocks on a hard drive.

Short version is now I can’t boot one of my machines.

As I’m reading

It says to ask for help in forums for manual partitions.

At this point I am here

[liveuser@eos-2020.05.08 ~]$ sudo fdisk -l
Disk /dev/sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EURX-73F
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 48E134F1-0042-11E2-8159-0050FC4B5D08

Device     Start        End    Sectors   Size Type
/dev/sda1     40 1953525127 1953525088 931.5G Linux filesystem


Disk /dev/sdb: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA MQ01ABD0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: CACF6CA8-F888-4A43-A991-C63136FF27EB

Device         Start       End   Sectors   Size Type
/dev/sdb1       2048   1026047   1024000   500M Linux filesystem
/dev/sdb2    1026048 205826047 204800000  97.7G Linux filesystem
/dev/sdb3  205826048 211970047   6144000     3G Linux filesystem
/dev/sdb4  211970048 976773119 764803072 364.7G Linux filesystem


Disk /dev/sdc: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Hitachi HDS72101
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 989378E0-17BF-11E1-812D-0050FC4B5D08

Device     Start        End    Sectors   Size Type
/dev/sdc1     34 1953525134 1953525101 931.5G Linux filesystem


Disk /dev/sdd: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: SAMSUNG HD204UI 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 29363758-0AC8-11E0-B26C-0050FC4B5D08

Device     Start        End    Sectors  Size Type
/dev/sdd1   2048 3907028991 3907026944  1.8T Linux filesystem


Disk /dev/sdf: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD2002FYPS-1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 905A9BFD-6CE6-11E8-B198-0025222805C7

Device     Start        End    Sectors  Size Type
/dev/sdf1     40 3907029127 3907029088  1.8T FreeBSD UFS


Disk /dev/sdg: 2.75 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: ST3000DM001-9YN1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 5BC445A5-6C70-11E8-ACA0-0025222805C7

Device     Start        End    Sectors  Size Type
/dev/sdg1     40 5860533119 5860533080  2.7T FreeBSD UFS


Disk /dev/sdh: 3.74 GiB, 4000317440 bytes, 7813120 sectors
Disk model: Cruzer          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x561d0d2e

Device     Boot Start     End Sectors  Size Id Type
/dev/sdh1  *        0 3593919 3593920  1.7G  0 Empty
/dev/sdh2         164  131235  131072   64M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 1.63 GiB, 1730863104 bytes, 3380592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sde: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD2002FYPS-1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1ddd54ff

Device     Boot Start        End    Sectors  Size Id Type
/dev/sde1        2048 3907028991 3907026944  1.8T 83 Linux

Before I screw something up, I thought it best to ask.

In the live boot my boot order is listed as
sdb1 is boot
sdb2 is root
sdb3 is swap
sdb4 is home

The original boot error I got was
dependency failed local files system

If someone could help with the correct procedure in getting me to boot, thankyou.

ricklinux · January 3, 2021, 9:32pm

Maybe check the boot log.

journalctl -xb

See if it’s not mounting /home or something?

MrEd · January 3, 2021, 10:20pm

It says it’s mounting from what I can tell,
but I did find the part where it says it’s waiting for a disk that’s not there and that disk is the one that had the issues.

That drive is listed in etc/fstab even though it’s been removed, does that matter?

EDIT-
It’s booting! I commented out the etc/fstab line with the bad drive in it and rebooted.

Thanks for your help. after reading that in the log made me wonder that.

ricklinux · January 3, 2021, 11:08pm

Probably should be removed then? Is it a drive that was physically removed? Or some other reason why the entry is in fstab?

MrEd · January 3, 2021, 11:18pm

It acted like that before I removed it, but removed before before it was running again.

I used badblocks on it then e2fsk which was ok I’m sure, but then reformatted with gparted and don’t know if that did something or not.

I just did all but reformat a drive on main machine and didn’t have an issue.

freebird54 · January 4, 2021, 2:12am

One thing a gparted format will do is provide the drive with a different UUID (and maybe label?) which could confuse /etc/fstab pretty quickly. I only mention this because I have done that! If the drive is fixed, get the new UUID and make a suitably altered entry in fstab…