Sudden Bad Sectors and no Ubuntu on HDD











up vote
0
down vote

favorite












I have tried to downgrade from 18.10 to 16.04 LTS with Bootable USB.
That USB was a bit of a problem as I had tried few times to rip Kali Linux and had troubles formatting it to make another ISO image. After few tries, managed to format it and then downloaded 16.04 LTS and successfully made it bootable.



After I started the installation from the USB,
on the screen I didn't see the current 18.10 version, but instead only the option to "Erase and install 16.04LTS". That was strange, as normally it will offer me to install it next to the Ubuntu 18.10 I already have.



However, I proceeded with "Erase disk and install Ubuntu 16.04 LTS".
Then an error appeared that could not write on disk and installation terminated.



Now I am on a live Ubuntu and some bad sectors appeared, didn't have them before. Also I can not get in to the BIOS (my lap top is Sony Vaio VPCEH).
On startup I have the Vaio screen for 1-2 seconds and then the black screen. f12 and F2 doesn't get me anywhere, no access to the BIOS



Please if someone can have a quick look on the fsck output and let me know if everything is normal or there is something weird that can be fixed. (In "normal" I mean that my HDD is fucked up and I will have to replace it) as currently I can not write Ubuntu on it.



ubuntu@ubuntu:~$ fsck
fsck from util-linux 2.31.1
ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# fdisk -l
Disk /dev/loop0: 1.8 GiB, 1864450048 bytes, 3641504 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/loop1: 86.9 MiB, 91099136 bytes, 177928 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/loop2: 34.7 MiB, 36323328 bytes, 70944 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/loop3: 140.9 MiB, 147722240 bytes, 288520 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/loop4: 2.3 MiB, 2433024 bytes, 4752 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/loop5: 13 MiB, 13619200 bytes, 26600 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/loop6: 14.5 MiB, 15196160 bytes, 29680 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/loop7: 3.7 MiB, 3887104 bytes, 7592 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/sda: 298.1 GiB, 320072933376 bytes, 625142448 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: 0xe88107f2


(Disk /dev/sda: 298.1 GiB is where 18.10 was installed



Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1 2048 625141759 625139712 298.1G 83 Linux


Disk /dev/sdb: 3.8 GiB, 4089446400 bytes, 7987200 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: 0x663eb4c4

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 3815135 3815136 1.8G 0 Empty
/dev/sdb2 3737268 3741939 4672 2.3M ef EFI (FAT-12/16/32)


Disk /dev/sdc: 3.8 GiB, 4089446400 bytes, 7987200 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: 0x8d505a86

Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 7987199 7985152 3.8G b W95 FAT32
root@ubuntu:/home/ubuntu# fsck /dev/sda
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda is in use.
e2fsck: Cannot continue, aborting.


root@ubuntu:/home/ubuntu# fsck /dev/sda
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda is in use.
e2fsck: Cannot continue, aborting.


root@ubuntu:/home/ubuntu# fdisk -l^C
root@ubuntu:/home/ubuntu#









share|improve this question









New contributor




brkroot is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1




    Sorry it's not clear. You wanted to move to 16.04 LTS, downloaded 16.04 LTS and when it booted it said 18.04 LTS & looked strange. Did you verify the ISO before writing? (or was 18.04 a typo?). I also don't see any [useful] fsck output (on one you didn't specify it what device to fsck, the other was mounted) and it only checks for logical file-system errors anyway, and I'd be checking the integrity of your hdd/sdd electronics (smartctl) and then mechanics/storage (badblocks) etc and not partition table (fdisk) or fs (fsck) first too.
    – guiverc
    2 days ago












  • I had Ubuntu 18.10 and tried to install Ubuntu 16.04 LTS. And I have downloaded the file from the ubuntu main page. Thank you for looking into this. I will have get familiar with smartctl and badblocks and will get back with some outputs. ( I can't remember what was the error while installing it, as it was noting particular. It just suggested to create CD/DVD iso file at lower speed)
    – brkroot
    2 days ago

















up vote
0
down vote

favorite












I have tried to downgrade from 18.10 to 16.04 LTS with Bootable USB.
That USB was a bit of a problem as I had tried few times to rip Kali Linux and had troubles formatting it to make another ISO image. After few tries, managed to format it and then downloaded 16.04 LTS and successfully made it bootable.



After I started the installation from the USB,
on the screen I didn't see the current 18.10 version, but instead only the option to "Erase and install 16.04LTS". That was strange, as normally it will offer me to install it next to the Ubuntu 18.10 I already have.



However, I proceeded with "Erase disk and install Ubuntu 16.04 LTS".
Then an error appeared that could not write on disk and installation terminated.



Now I am on a live Ubuntu and some bad sectors appeared, didn't have them before. Also I can not get in to the BIOS (my lap top is Sony Vaio VPCEH).
On startup I have the Vaio screen for 1-2 seconds and then the black screen. f12 and F2 doesn't get me anywhere, no access to the BIOS



Please if someone can have a quick look on the fsck output and let me know if everything is normal or there is something weird that can be fixed. (In "normal" I mean that my HDD is fucked up and I will have to replace it) as currently I can not write Ubuntu on it.



ubuntu@ubuntu:~$ fsck
fsck from util-linux 2.31.1
ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# fdisk -l
Disk /dev/loop0: 1.8 GiB, 1864450048 bytes, 3641504 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/loop1: 86.9 MiB, 91099136 bytes, 177928 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/loop2: 34.7 MiB, 36323328 bytes, 70944 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/loop3: 140.9 MiB, 147722240 bytes, 288520 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/loop4: 2.3 MiB, 2433024 bytes, 4752 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/loop5: 13 MiB, 13619200 bytes, 26600 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/loop6: 14.5 MiB, 15196160 bytes, 29680 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/loop7: 3.7 MiB, 3887104 bytes, 7592 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/sda: 298.1 GiB, 320072933376 bytes, 625142448 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: 0xe88107f2


(Disk /dev/sda: 298.1 GiB is where 18.10 was installed



Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1 2048 625141759 625139712 298.1G 83 Linux


Disk /dev/sdb: 3.8 GiB, 4089446400 bytes, 7987200 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: 0x663eb4c4

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 3815135 3815136 1.8G 0 Empty
/dev/sdb2 3737268 3741939 4672 2.3M ef EFI (FAT-12/16/32)


Disk /dev/sdc: 3.8 GiB, 4089446400 bytes, 7987200 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: 0x8d505a86

Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 7987199 7985152 3.8G b W95 FAT32
root@ubuntu:/home/ubuntu# fsck /dev/sda
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda is in use.
e2fsck: Cannot continue, aborting.


root@ubuntu:/home/ubuntu# fsck /dev/sda
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda is in use.
e2fsck: Cannot continue, aborting.


root@ubuntu:/home/ubuntu# fdisk -l^C
root@ubuntu:/home/ubuntu#









share|improve this question









New contributor




brkroot is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1




    Sorry it's not clear. You wanted to move to 16.04 LTS, downloaded 16.04 LTS and when it booted it said 18.04 LTS & looked strange. Did you verify the ISO before writing? (or was 18.04 a typo?). I also don't see any [useful] fsck output (on one you didn't specify it what device to fsck, the other was mounted) and it only checks for logical file-system errors anyway, and I'd be checking the integrity of your hdd/sdd electronics (smartctl) and then mechanics/storage (badblocks) etc and not partition table (fdisk) or fs (fsck) first too.
    – guiverc
    2 days ago












  • I had Ubuntu 18.10 and tried to install Ubuntu 16.04 LTS. And I have downloaded the file from the ubuntu main page. Thank you for looking into this. I will have get familiar with smartctl and badblocks and will get back with some outputs. ( I can't remember what was the error while installing it, as it was noting particular. It just suggested to create CD/DVD iso file at lower speed)
    – brkroot
    2 days ago















up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have tried to downgrade from 18.10 to 16.04 LTS with Bootable USB.
That USB was a bit of a problem as I had tried few times to rip Kali Linux and had troubles formatting it to make another ISO image. After few tries, managed to format it and then downloaded 16.04 LTS and successfully made it bootable.



After I started the installation from the USB,
on the screen I didn't see the current 18.10 version, but instead only the option to "Erase and install 16.04LTS". That was strange, as normally it will offer me to install it next to the Ubuntu 18.10 I already have.



However, I proceeded with "Erase disk and install Ubuntu 16.04 LTS".
Then an error appeared that could not write on disk and installation terminated.



Now I am on a live Ubuntu and some bad sectors appeared, didn't have them before. Also I can not get in to the BIOS (my lap top is Sony Vaio VPCEH).
On startup I have the Vaio screen for 1-2 seconds and then the black screen. f12 and F2 doesn't get me anywhere, no access to the BIOS



Please if someone can have a quick look on the fsck output and let me know if everything is normal or there is something weird that can be fixed. (In "normal" I mean that my HDD is fucked up and I will have to replace it) as currently I can not write Ubuntu on it.



ubuntu@ubuntu:~$ fsck
fsck from util-linux 2.31.1
ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# fdisk -l
Disk /dev/loop0: 1.8 GiB, 1864450048 bytes, 3641504 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/loop1: 86.9 MiB, 91099136 bytes, 177928 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/loop2: 34.7 MiB, 36323328 bytes, 70944 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/loop3: 140.9 MiB, 147722240 bytes, 288520 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/loop4: 2.3 MiB, 2433024 bytes, 4752 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/loop5: 13 MiB, 13619200 bytes, 26600 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/loop6: 14.5 MiB, 15196160 bytes, 29680 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/loop7: 3.7 MiB, 3887104 bytes, 7592 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/sda: 298.1 GiB, 320072933376 bytes, 625142448 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: 0xe88107f2


(Disk /dev/sda: 298.1 GiB is where 18.10 was installed



Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1 2048 625141759 625139712 298.1G 83 Linux


Disk /dev/sdb: 3.8 GiB, 4089446400 bytes, 7987200 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: 0x663eb4c4

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 3815135 3815136 1.8G 0 Empty
/dev/sdb2 3737268 3741939 4672 2.3M ef EFI (FAT-12/16/32)


Disk /dev/sdc: 3.8 GiB, 4089446400 bytes, 7987200 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: 0x8d505a86

Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 7987199 7985152 3.8G b W95 FAT32
root@ubuntu:/home/ubuntu# fsck /dev/sda
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda is in use.
e2fsck: Cannot continue, aborting.


root@ubuntu:/home/ubuntu# fsck /dev/sda
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda is in use.
e2fsck: Cannot continue, aborting.


root@ubuntu:/home/ubuntu# fdisk -l^C
root@ubuntu:/home/ubuntu#









share|improve this question









New contributor




brkroot is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I have tried to downgrade from 18.10 to 16.04 LTS with Bootable USB.
That USB was a bit of a problem as I had tried few times to rip Kali Linux and had troubles formatting it to make another ISO image. After few tries, managed to format it and then downloaded 16.04 LTS and successfully made it bootable.



After I started the installation from the USB,
on the screen I didn't see the current 18.10 version, but instead only the option to "Erase and install 16.04LTS". That was strange, as normally it will offer me to install it next to the Ubuntu 18.10 I already have.



However, I proceeded with "Erase disk and install Ubuntu 16.04 LTS".
Then an error appeared that could not write on disk and installation terminated.



Now I am on a live Ubuntu and some bad sectors appeared, didn't have them before. Also I can not get in to the BIOS (my lap top is Sony Vaio VPCEH).
On startup I have the Vaio screen for 1-2 seconds and then the black screen. f12 and F2 doesn't get me anywhere, no access to the BIOS



Please if someone can have a quick look on the fsck output and let me know if everything is normal or there is something weird that can be fixed. (In "normal" I mean that my HDD is fucked up and I will have to replace it) as currently I can not write Ubuntu on it.



ubuntu@ubuntu:~$ fsck
fsck from util-linux 2.31.1
ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# fdisk -l
Disk /dev/loop0: 1.8 GiB, 1864450048 bytes, 3641504 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/loop1: 86.9 MiB, 91099136 bytes, 177928 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/loop2: 34.7 MiB, 36323328 bytes, 70944 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/loop3: 140.9 MiB, 147722240 bytes, 288520 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/loop4: 2.3 MiB, 2433024 bytes, 4752 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/loop5: 13 MiB, 13619200 bytes, 26600 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/loop6: 14.5 MiB, 15196160 bytes, 29680 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/loop7: 3.7 MiB, 3887104 bytes, 7592 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/sda: 298.1 GiB, 320072933376 bytes, 625142448 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: 0xe88107f2


(Disk /dev/sda: 298.1 GiB is where 18.10 was installed



Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1 2048 625141759 625139712 298.1G 83 Linux


Disk /dev/sdb: 3.8 GiB, 4089446400 bytes, 7987200 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: 0x663eb4c4

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 3815135 3815136 1.8G 0 Empty
/dev/sdb2 3737268 3741939 4672 2.3M ef EFI (FAT-12/16/32)


Disk /dev/sdc: 3.8 GiB, 4089446400 bytes, 7987200 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: 0x8d505a86

Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 7987199 7985152 3.8G b W95 FAT32
root@ubuntu:/home/ubuntu# fsck /dev/sda
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda is in use.
e2fsck: Cannot continue, aborting.


root@ubuntu:/home/ubuntu# fsck /dev/sda
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda is in use.
e2fsck: Cannot continue, aborting.


root@ubuntu:/home/ubuntu# fdisk -l^C
root@ubuntu:/home/ubuntu#






boot partitioning mount hard-drive fsck






share|improve this question









New contributor




brkroot is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




brkroot is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 2 days ago





















New contributor




brkroot is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 days ago









brkroot

13




13




New contributor




brkroot is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





brkroot is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






brkroot is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1




    Sorry it's not clear. You wanted to move to 16.04 LTS, downloaded 16.04 LTS and when it booted it said 18.04 LTS & looked strange. Did you verify the ISO before writing? (or was 18.04 a typo?). I also don't see any [useful] fsck output (on one you didn't specify it what device to fsck, the other was mounted) and it only checks for logical file-system errors anyway, and I'd be checking the integrity of your hdd/sdd electronics (smartctl) and then mechanics/storage (badblocks) etc and not partition table (fdisk) or fs (fsck) first too.
    – guiverc
    2 days ago












  • I had Ubuntu 18.10 and tried to install Ubuntu 16.04 LTS. And I have downloaded the file from the ubuntu main page. Thank you for looking into this. I will have get familiar with smartctl and badblocks and will get back with some outputs. ( I can't remember what was the error while installing it, as it was noting particular. It just suggested to create CD/DVD iso file at lower speed)
    – brkroot
    2 days ago
















  • 1




    Sorry it's not clear. You wanted to move to 16.04 LTS, downloaded 16.04 LTS and when it booted it said 18.04 LTS & looked strange. Did you verify the ISO before writing? (or was 18.04 a typo?). I also don't see any [useful] fsck output (on one you didn't specify it what device to fsck, the other was mounted) and it only checks for logical file-system errors anyway, and I'd be checking the integrity of your hdd/sdd electronics (smartctl) and then mechanics/storage (badblocks) etc and not partition table (fdisk) or fs (fsck) first too.
    – guiverc
    2 days ago












  • I had Ubuntu 18.10 and tried to install Ubuntu 16.04 LTS. And I have downloaded the file from the ubuntu main page. Thank you for looking into this. I will have get familiar with smartctl and badblocks and will get back with some outputs. ( I can't remember what was the error while installing it, as it was noting particular. It just suggested to create CD/DVD iso file at lower speed)
    – brkroot
    2 days ago










1




1




Sorry it's not clear. You wanted to move to 16.04 LTS, downloaded 16.04 LTS and when it booted it said 18.04 LTS & looked strange. Did you verify the ISO before writing? (or was 18.04 a typo?). I also don't see any [useful] fsck output (on one you didn't specify it what device to fsck, the other was mounted) and it only checks for logical file-system errors anyway, and I'd be checking the integrity of your hdd/sdd electronics (smartctl) and then mechanics/storage (badblocks) etc and not partition table (fdisk) or fs (fsck) first too.
– guiverc
2 days ago






Sorry it's not clear. You wanted to move to 16.04 LTS, downloaded 16.04 LTS and when it booted it said 18.04 LTS & looked strange. Did you verify the ISO before writing? (or was 18.04 a typo?). I also don't see any [useful] fsck output (on one you didn't specify it what device to fsck, the other was mounted) and it only checks for logical file-system errors anyway, and I'd be checking the integrity of your hdd/sdd electronics (smartctl) and then mechanics/storage (badblocks) etc and not partition table (fdisk) or fs (fsck) first too.
– guiverc
2 days ago














I had Ubuntu 18.10 and tried to install Ubuntu 16.04 LTS. And I have downloaded the file from the ubuntu main page. Thank you for looking into this. I will have get familiar with smartctl and badblocks and will get back with some outputs. ( I can't remember what was the error while installing it, as it was noting particular. It just suggested to create CD/DVD iso file at lower speed)
– brkroot
2 days ago






I had Ubuntu 18.10 and tried to install Ubuntu 16.04 LTS. And I have downloaded the file from the ubuntu main page. Thank you for looking into this. I will have get familiar with smartctl and badblocks and will get back with some outputs. ( I can't remember what was the error while installing it, as it was noting particular. It just suggested to create CD/DVD iso file at lower speed)
– brkroot
2 days ago

















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






brkroot is a new contributor. Be nice, and check out our Code of Conduct.










 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1093374%2fsudden-bad-sectors-and-no-ubuntu-on-hdd%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes








brkroot is a new contributor. Be nice, and check out our Code of Conduct.










 

draft saved


draft discarded


















brkroot is a new contributor. Be nice, and check out our Code of Conduct.













brkroot is a new contributor. Be nice, and check out our Code of Conduct.












brkroot is a new contributor. Be nice, and check out our Code of Conduct.















 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1093374%2fsudden-bad-sectors-and-no-ubuntu-on-hdd%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How did Captain America manage to do this?

迪纳利

南乌拉尔铁路局