Hard drive Ubuntu can see but that my system doesn't see at boot anymore
by HannemanThrashKing from LinuxQuestions.org on (#5K0WG)
Well I can't explain this, and this is rather annoying, it's an emptied 1TB drive, that is 5 years old, it's not about to die per diagnostics...which I can do once I boot in a live session, that drive was to install Ubuntu Mate on, but right now I got no space on any other drives, well I have an old 200gb WD drive that will just not die but it is only regular old SATA, not SATA 6gb/s like this one....which doesn't show up at boot where my ASUS mobo will not list it in the drives anymore all of a sudden, after a forced power-down of a live session by a power failure (I have a voltage protection power bar, a good one, and all is saying that my PSU is in top shape still (it's 4 years old).
How can Ubuntu see it and the system not? Which is bad, when I hit Delete to enter the mobo's bios or UEFI or whatever, it's not a "BIOS" I think, it's a fancy looking, mouse-using GUI that I get. I have to go in there so that my memory works at the speed it should. Anyways, in the list of drives, last time before I booted back, boot priority and such, it's not seen either.
I installed testdisk, which has always been quite the saviour when it came to hard drive issues, and all of a sudden, that whole drive I had partitioned as a Primary partition in ext4, testdisk tells me it not seen as wheter P or L, it's got a star next to it, so it lost it's Primary Partition tag I put on it with gParted. I know it doesn't have an MBR, but it should be listed in the drives at boot like all the others shouldn't it? I mean it also lists my Pioneer BD-R. It's always been seen as sdb but now it's sdd, because Ubuntu sees it!
I never saw such a crazy problem with a hard drive before, but I had testdisk write-in the information that it is a Primary partition and now I can't use the drive anymore because testdisk says I need to reboot it and I can't mount it no more, but it still sees it, I'll see what happens when I boot back.
I'll give you a peak of a terminal command to list all of my drives...internal and external :
Code:sudo lshw -C disk
*-disk
description: SCSI Disk
product: EZAZ-00GGJB0
vendor: WDC WD20
physical id: 0.0.0
bus info: scsi@8:0.0.0
logical name: /dev/sdf
version: 0106
serial: 00000000000000000000
size: 1863GiB (2TB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: ansiversion=6 guid=b53648e4-c450-4e79-b448-f7fe152f8f9f logicalsectorsize=512 sectorsize=512
*-disk
description: SCSI Disk
product: DataTraveler 3.0
vendor: Kingston
physical id: 0.0.0
bus info: scsi@7:0.0.0
logical name: /dev/sdc
version: PMAP
serial: EE03D85155E9
size: 115GiB (124GB)
capabilities: removable
configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512
*-medium
physical id: 0
logical name: /dev/sdc
size: 115GiB (124GB)
capabilities: partitioned partitioned:dos
configuration: signature=f844846e
*-disk
description: SCSI Disk
product: Expansion
vendor: Seagate
physical id: 0.0.0
bus info: scsi@6:0.0.0
logical name: /dev/sdb
version: 0708
serial: NA8K6MSK
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512 signature=628822a0
*-cdrom
description: DVD-RAM writer
product: BD-RW BDR-209M
vendor: PIONEER
physical id: 0
bus info: scsi@1:0.0.0
logical name: /dev/cdrom
logical name: /dev/cdrw
logical name: /dev/dvd
logical name: /dev/dvdrw
logical name: /dev/sr0
version: 1.50
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=nodisc
*-disk:0
description: ATA Disk
product: WDC WD2000JD-22H
vendor: Western Digital
physical id: 1
bus info: scsi@3:0.0.0
logical name: /dev/sda
version: 2D08
serial: WD-WCAL81786689
size: 186GiB (200GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=00095704
*-disk:1
description: ATA Disk
product: ST1000DM003-1CH1
physical id: 2
bus info: scsi@4:0.0.0
logical name: /dev/sdd
version: CC47
serial: W1D45DY8
size: 931GiB (1TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=4096 signature=d88eb14d
*-disk:2
description: ATA Disk
product: WDC WD10EFRX-68J
vendor: Western Digital
physical id: 3
bus info: scsi@5:0.0.0
logical name: /dev/sde
version: 1A01
serial: WD-WCC1U0505191
size: 931GiB (1TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=4096 signature=000ee848
*-disk
description: SCSI Disk
product: Expansion
vendor: Seagate
physical id: 0.0.0
bus info: scsi@9:0.0.0
logical name: /dev/sdg
version: 1805
serial: NA87MBQP
size: 931GiB (1TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=6 logicalsectorsize=512 sectorsize=4096 signature=000b3352It's this one : ST1000DM003-1CH1. Disks info tells me things about pre-fail in some cases, but it does with almost anything older than a year, the undying 200gb drive could be used, but, I already don't have SSD's (internally) as you can see, so I'm not gonna be slowing things down by not using a 6gb/s drive like that Seagate drive, the eternal 200gb WD from 2005 is fine for storage, I've seen 2 hard drives die after that one, they don't make em like they used to when there was more than 2 good companies making hdds and there was no quality levels/colour levels.
Anyways, if I don't see it at reboot in the drive list on the first screen where memory,keyboards, mouses, hubs, external drives and internal drives are listed and where I can press Delete to get into the gui....you tell me what it is BIOS or UEFI, the motherboard is this model :
ASUSTeK model: M5A97 LE R2.0 v: Rev 1.xx
serial: <superuser/root required> UEFI: American Megatrends v: 2701
date: 03/24/2016
Which is the last firmware update version (03/24/2016), I bought it in 2017 so I only had to apply it once easily back when I still dual-booted (when win7 wasn't dead).
The only thing bothering me is that Disks sees 78 bad blocks which is more than all other drives, where it's 20 tops on the old 200gb WD and none on the others.
I will update this post after I had a reboot, but now that I have a live session going on the 256gb usb key and everything is setup as I like it, I usually just use it this way (except for last week when I was ready to finally install it permanently, ubuntu mate 20.04 that is, the kernel the usb key loads must be getting old). But if anybody has an idea of how in the **** my motherboard itself claims the Seagate internal drive isn't there anymore but Ubuntu not only sees it, but can mount it, have files copied to it etc, even though there were no longer any flags on it, I'd like to know. Also, seems like lba flag should be checked right? Otherwise I'm stumped here, but I wanted to use it to install 20.04 and be done with always-overdue-to-crash live sessions or the annoying power failures we've been experiencing so often around here since the last few years, that often "brownout", as in, it comes back right when it cuts but then fails again which is bad when I forget to turn off the PSU even with a voltage variation protection power bar, I hear.
Sorry if the post is a bit long, I don't want details to be missed and getting questions about things I didn't ask about so I provided everything I could here.
Have a good day everyone! Stay safe from the bug, everyone imagines it's practically gone during the summer, but that's when I got it last year, wasn't too bad, just going on and on...like this post, lol.
How can Ubuntu see it and the system not? Which is bad, when I hit Delete to enter the mobo's bios or UEFI or whatever, it's not a "BIOS" I think, it's a fancy looking, mouse-using GUI that I get. I have to go in there so that my memory works at the speed it should. Anyways, in the list of drives, last time before I booted back, boot priority and such, it's not seen either.
I installed testdisk, which has always been quite the saviour when it came to hard drive issues, and all of a sudden, that whole drive I had partitioned as a Primary partition in ext4, testdisk tells me it not seen as wheter P or L, it's got a star next to it, so it lost it's Primary Partition tag I put on it with gParted. I know it doesn't have an MBR, but it should be listed in the drives at boot like all the others shouldn't it? I mean it also lists my Pioneer BD-R. It's always been seen as sdb but now it's sdd, because Ubuntu sees it!
I never saw such a crazy problem with a hard drive before, but I had testdisk write-in the information that it is a Primary partition and now I can't use the drive anymore because testdisk says I need to reboot it and I can't mount it no more, but it still sees it, I'll see what happens when I boot back.
I'll give you a peak of a terminal command to list all of my drives...internal and external :
Code:sudo lshw -C disk
*-disk
description: SCSI Disk
product: EZAZ-00GGJB0
vendor: WDC WD20
physical id: 0.0.0
bus info: scsi@8:0.0.0
logical name: /dev/sdf
version: 0106
serial: 00000000000000000000
size: 1863GiB (2TB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: ansiversion=6 guid=b53648e4-c450-4e79-b448-f7fe152f8f9f logicalsectorsize=512 sectorsize=512
*-disk
description: SCSI Disk
product: DataTraveler 3.0
vendor: Kingston
physical id: 0.0.0
bus info: scsi@7:0.0.0
logical name: /dev/sdc
version: PMAP
serial: EE03D85155E9
size: 115GiB (124GB)
capabilities: removable
configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512
*-medium
physical id: 0
logical name: /dev/sdc
size: 115GiB (124GB)
capabilities: partitioned partitioned:dos
configuration: signature=f844846e
*-disk
description: SCSI Disk
product: Expansion
vendor: Seagate
physical id: 0.0.0
bus info: scsi@6:0.0.0
logical name: /dev/sdb
version: 0708
serial: NA8K6MSK
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512 signature=628822a0
*-cdrom
description: DVD-RAM writer
product: BD-RW BDR-209M
vendor: PIONEER
physical id: 0
bus info: scsi@1:0.0.0
logical name: /dev/cdrom
logical name: /dev/cdrw
logical name: /dev/dvd
logical name: /dev/dvdrw
logical name: /dev/sr0
version: 1.50
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=nodisc
*-disk:0
description: ATA Disk
product: WDC WD2000JD-22H
vendor: Western Digital
physical id: 1
bus info: scsi@3:0.0.0
logical name: /dev/sda
version: 2D08
serial: WD-WCAL81786689
size: 186GiB (200GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=00095704
*-disk:1
description: ATA Disk
product: ST1000DM003-1CH1
physical id: 2
bus info: scsi@4:0.0.0
logical name: /dev/sdd
version: CC47
serial: W1D45DY8
size: 931GiB (1TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=4096 signature=d88eb14d
*-disk:2
description: ATA Disk
product: WDC WD10EFRX-68J
vendor: Western Digital
physical id: 3
bus info: scsi@5:0.0.0
logical name: /dev/sde
version: 1A01
serial: WD-WCC1U0505191
size: 931GiB (1TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=4096 signature=000ee848
*-disk
description: SCSI Disk
product: Expansion
vendor: Seagate
physical id: 0.0.0
bus info: scsi@9:0.0.0
logical name: /dev/sdg
version: 1805
serial: NA87MBQP
size: 931GiB (1TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=6 logicalsectorsize=512 sectorsize=4096 signature=000b3352It's this one : ST1000DM003-1CH1. Disks info tells me things about pre-fail in some cases, but it does with almost anything older than a year, the undying 200gb drive could be used, but, I already don't have SSD's (internally) as you can see, so I'm not gonna be slowing things down by not using a 6gb/s drive like that Seagate drive, the eternal 200gb WD from 2005 is fine for storage, I've seen 2 hard drives die after that one, they don't make em like they used to when there was more than 2 good companies making hdds and there was no quality levels/colour levels.
Anyways, if I don't see it at reboot in the drive list on the first screen where memory,keyboards, mouses, hubs, external drives and internal drives are listed and where I can press Delete to get into the gui....you tell me what it is BIOS or UEFI, the motherboard is this model :
ASUSTeK model: M5A97 LE R2.0 v: Rev 1.xx
serial: <superuser/root required> UEFI: American Megatrends v: 2701
date: 03/24/2016
Which is the last firmware update version (03/24/2016), I bought it in 2017 so I only had to apply it once easily back when I still dual-booted (when win7 wasn't dead).
The only thing bothering me is that Disks sees 78 bad blocks which is more than all other drives, where it's 20 tops on the old 200gb WD and none on the others.
I will update this post after I had a reboot, but now that I have a live session going on the 256gb usb key and everything is setup as I like it, I usually just use it this way (except for last week when I was ready to finally install it permanently, ubuntu mate 20.04 that is, the kernel the usb key loads must be getting old). But if anybody has an idea of how in the **** my motherboard itself claims the Seagate internal drive isn't there anymore but Ubuntu not only sees it, but can mount it, have files copied to it etc, even though there were no longer any flags on it, I'd like to know. Also, seems like lba flag should be checked right? Otherwise I'm stumped here, but I wanted to use it to install 20.04 and be done with always-overdue-to-crash live sessions or the annoying power failures we've been experiencing so often around here since the last few years, that often "brownout", as in, it comes back right when it cuts but then fails again which is bad when I forget to turn off the PSU even with a voltage variation protection power bar, I hear.
Sorry if the post is a bit long, I don't want details to be missed and getting questions about things I didn't ask about so I provided everything I could here.
Have a good day everyone! Stay safe from the bug, everyone imagines it's practically gone during the summer, but that's when I got it last year, wasn't too bad, just going on and on...like this post, lol.