SSD failing?

hydrurga · 07-08-2017, 08:30 AM

That SSD looks fine.

In your opening post you said that you had received an error about sdc. Now that it appears that sdc is in fact your data hdd, it looks as if your system had multiple problems.

Out of pure interest, can you please run sudo fdisk -l /dev/sda? I would just like to see how your disks are set up. We can look at the other 2 disks afterwards...

columini · 07-08-2017, 07:58 PM

well I'm not sure about sdc. I wouldn't expect a storage disk to cause boot issues, maybe I copied those infos wrong (I couldn't copy paste)

here are the results of fdisk on sda:

Code:

sudo fdisk -l /dev/sda
Disk /dev/sda: 111,8 GiB, 120034123776 bytes, 234441648 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
Disklabel type: dos
Disk identifier: 0xace274df

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sda1  *       2048   1026047   1024000   500M  7 HPFS/NTFS/exFAT
/dev/sda2       1026048 234438655 233412608 111,3G  7 HPFS/NTFS/exFAT



sudo fdisk -l /dev/sda1
Disk /dev/sda1: 500 MiB, 524288000 bytes, 1024000 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
Disklabel type: dos
Disk identifier: 0x73736572

Device      Boot      Start        End    Sectors   Size Id Type
/dev/sda1p1      1920221984 3736432267 1816210284   866G 72 unknown
/dev/sda1p2      1936028192 3889681299 1953653108 931,6G 6c unknown
/dev/sda1p3               0          0          0     0B  0 Empty
/dev/sda1p4        27722122   27722568        447 223,5K  0 Empty

Partition table entries are not in disk order.



sudo fdisk -l /dev/sda2
Disk /dev/sda2: 111,3 GiB, 119507255296 bytes, 233412608 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
Disklabel type: dos
Disk identifier: 0x6c727443

Device      Boot      Start        End    Sectors   Size Id Type
/dev/sda2p1      1970237472 3672215697 1701978226 811,6G 75 PC/IX
/dev/sda2p2      1929382413 3883035520 1953653108 931,6G 72 unknown
/dev/sda2p3               0          0          0     0B  0 Empty
/dev/sda2p4        27394442   27394879        438   219K  0 Empty

By the way, do you have any idea why my boot loading time increased that much after the "e2fsck -c /dev/sda1" command? (it gets stuck for a while on the motherboard screen right before grub)

hydrurga · 07-09-2017, 03:00 AM

Thanks, columini.

The output to sudo fdisk -l /dev/sda was all that was needed. The output to fdisk -l /dev/sda1 is nonsensical as the individual partitions themselves don't contain MBR partition tables.

Can you do the same for fdisk -l /dev/sdb and fdisk -l /dev/sdc? Many thanks.

That long boot might indicate a hardware issue. But as to why it appeared to begin after a filesystem check and repair, I have no idea to be honest.

columini · 07-09-2017, 07:35 AM

Code:

sudo fdisk -l /dev/sdb
Disk /dev/sdb: 232,9 GiB, 250059350016 bytes, 488397168 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
Disklabel type: dos
Disk identifier: 0xaa7b08bd

Device     Boot    Start       End   Sectors  Size Id Type
/dev/sdb1           2048  31250431  31248384 14,9G 82 Linux swap / Solaris
/dev/sdb2       31250432 488396799 457146368  218G 83 Linux

Code:

sudo fdisk -l /dev/sdc
Disk /dev/sdc: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
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: dos
Disk identifier: 0xb4dd95b3

Device     Boot     Start        End   Sectors   Size Id Type
/dev/sdc1            2048  976963583 976961536 465,9G 83 Linux
/dev/sdc2       976963584 1953523711 976560128 465,7G  b W95 FAT32

columini · 07-09-2017, 04:31 PM

Ok well I noticed that during boot time, my PC is making a little humming sound when it's stuck on the asrock screen for like 10-30 seconds.
So I tried switching which disk has grub on it with "sudo grub-install /dev/sdb" and "sudo update-grub" and I noticed something:

Grub found all the linux/memetest etc... almost instantly but it took it a very long time to find windows (like 10-30 minutes) and while it was looking for windows, there was the same sound that I have with the asrock screen during boot time.

So I think there's still something up with that SSD and my long boot time might be grub having a hard time to read the windows partition. Maybe I'll just reinstall windows on the HDD and forget about it.

hydrurga · 07-09-2017, 04:49 PM

I thought your Windows was on sda (it is according to your previous output anyway).

columini · 07-09-2017, 06:13 PM

Yes it is.
Windows and grub where on sda.
I switched grub to sdb to see if it would improve the boot time.

hydrurga · 07-10-2017, 05:48 AM

Quote:

Originally Posted by columini

Yes it is.
Windows and grub where on sda.
I switched grub to sdb to see if it would improve the boot time.

Ah, gotcha. I'm no expert on grub but I'm sure it's still installed on /dev/sda anyway, so there was no "switching" going on, just an additional installation of grub to /dev/sdb. Perhaps you also switched the boot order in your BIOS to boot /dev/sdb first?

Anyway, apart from that, the fact that grub takes so long to find the Windows partition is worrying. That would indicate a problem with your Windows SSD or the connections to it. Can you therefore check the connections again?

The Windows SSD was the one for which we found SMART data that looked worrying (post #13). Is it a fairly new disk? If so, you should look to get it replaced under warranty due to what you're experiencing and the SMART data. If not, you should replace it.