# Apparently deleted my boot partition (and/or more) **URL:** \ **Category:** Newbie\ **Created:** [December 10, 2022, 3:55am UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696 "2022-12-10T03:55:14Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![jmainhard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/j/ed8c4c/32.png) [@jmainhard](https://forum.endeavouros.com/u/jmainhard)\ **Post date:** [December 10, 2022, 3:55am UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/1 "2022-12-10T03:55:14Z")
Hi to everyone! (Posting from Live ISO 😅) This week when I forcefully restarted after a freeze I got something like the next block - if I remember correctly on `/dev/sda2` -. ([source](https://askubuntu.com/questions/697190)) ```bash fsck from util-linux 2.26.2 /dev/sda6 contains a file system with errors, check forced. /dev/sda6: Inodes that were part of a corrupted orphan linked list found. /dev/sda6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck exited with status code 4 The root filesystem on /dev/sda6 requires a manual fsck # [...] (initramfs) _ ``` So I followed what is suggested in the source linked before which is yes to all without knowing much what I was doing (Hoping to always learn from mistakes and decisions like that haha). Something like the next `fsck /dev/sda2` and got prompted several times for errors, I answered yes to every prompt. After that I rebooted and I got a message from the computer that it couldn’t recognize any boot media. Right after that I enter the UEFI to see the same, I have no Boot media, only this: ```uefi # (Boot menu) EFI Hard Drive (ST1000LM035-1RK172) EFI PXE Network ``` I tried to Chroot with a live ISO - from the [Grub incident](https://forum.endeavouros.com/t/the-latest-grub-package-update-needs-some-manual-intervention/30689) of august more or less as I learned -. Tried to mount (please check): ```auto [liveuser@eos-2022.09.10 ~]$ sudo lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS loop0 squashfs 4.0 0 100% /run/archiso/airootfs sda ├─sda1 vfat FAT32 NO_LABEL B303-E0D5 ├─sda2 ext4 1.0 296fc2f2-67e8-468b-b86b-8231bf911b58 └─sda3 swap 1 swap c52dec28-c60f-429f-a5d3-53bda411f9c2 sdb iso9660 Joliet Extension EOS_202209 2022-09-10-10-51-40-00 ├─sdb1 iso9660 Joliet Extension EOS_202209 2022-09-10-10-51-40-00 0 100% /run/archiso/bootmnt ``` ```auto [liveuser@eos-2022.09.10 ~]$ sudo mount /dev/sda2 /mnt mount: /mnt: can't read superblock on /dev/sda2. dmesg(1) may have more information after failed mount system call. ``` And got this log from `journalctl -k`: [https://clbin.com/oo1Ii](https://clbin.com/oo1Ii) **From this I would like to ask to any that can help me:** 1. I am doing the chroot process correctly? (Actually I fell I don’t understand it so well like the last time from [here](https://discovery.endeavouros.com/system-rescue/arch-chroot-for-efi-uefi-systems/2021/03/)) 2. Is there a way I could recover my previous data or installation, I actually deleted it or its just corrupted (or both)? 3. What are my next steps # More info ## Context For more context, I was finishing a Job for college - with a lot of things opened - and usually what happens is my system can’t hold it no more and freezes (happened a few times before). That is usually a small problem because when I restart I recover the session through something like a journal, I don’t really know whats that about but is very nice. ## Hardware From INXI (`inxi -FAZ --no-host`): [https://clbin.com/lZsBK](https://clbin.com/lZsBK) ## Thanks Relatively new Linux user here, I started with EndeavourOS less than a year ago and I wanted to take this opportunity to say that it has been a very good experience and very educational Im very thankful of this community. #arch-based-related-questions #arch-based-related-questions:kernel-hardware ---
**Author:** ![Stephane](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stephane/32/9196_2.png) [@Stephane](https://forum.endeavouros.com/u/Stephane)\ **Post date:** [December 10, 2022, 2:22pm UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/2 "2022-12-10T14:22:33Z")
you have error on ata1 ( search for ata1 in log ) ==\> first recheck cables then ==\> after with USB live iso check for smartctl ---
**Author:** ![jmainhard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/j/ed8c4c/32.png) [@jmainhard](https://forum.endeavouros.com/u/jmainhard)\ **Post date:** [December 10, 2022, 3:55pm UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/3 "2022-12-10T15:55:13Z")
Hi @Stephane thanks for your time. Rechecked cables ✅ And this is smartctl log (on every `/dev/sda`): `smartctl /dev/sda2` ```shell [liveuser@eos-2022.09.10 ~]$ sudo smartctl /dev/sda2 smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.7-arch1-1] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org ATA device successfully opened Use 'smartctl -a' (or '-x') to print SMART (and more) information ``` `$ smartctl -a /dev/sda2` (log [here](https://clbin.com/MpwRm)) `$ smartctl -a /dev/sda2` after trying to mount `/dev/sda2` log: ```shell [liveuser@eos-2022.09.10 ~]$ sudo smartctl /dev/sda2 smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.7-arch1-1] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org Short INQUIRY response, skip product id A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. ``` and with `-T permissive` (I don’t really know what it is for) ```auto [liveuser@eos-2022.09.10 ~]$ sudo smartctl -T permissive /dev/sda2 smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.7-arch1-1] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org Short INQUIRY response, skip product id ``` For whatever it’s worth I tested all the above with: - `/dev/sda` - `/dev/sda1` - `/dev/sda2` - `/dev/sda3` what would be the next step? ---
**Author:** ![Stephane](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stephane/32/9196_2.png) [@Stephane](https://forum.endeavouros.com/u/Stephane)\ **Post date:** [December 10, 2022, 4:05pm UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/4 "2022-12-10T16:05:25Z")
then retry `fsck /dev/sda2` ---
**Author:** ![jmainhard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/j/ed8c4c/32.png) [@jmainhard](https://forum.endeavouros.com/u/jmainhard)\ **Post date:** [December 10, 2022, 4:15pm UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/5 "2022-12-10T16:15:41Z")
Got this: ```shell [liveuser@eos-2022.09.10 ~]$ sudo fsck /dev/sda2 fsck from util-linux 2.38.1 e2fsck 1.46.5 (30-Dec-2021) /dev/sda2: recovering journal Error reading block 120818564 (Input/output error). Ignore error? ``` Sorry, I’m not very confident since the last time. I ignore errors? ---
**Author:** ![Stephane](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stephane/32/9196_2.png) [@Stephane](https://forum.endeavouros.com/u/Stephane)\ **Post date:** [December 10, 2022, 4:34pm UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/6 "2022-12-10T16:34:44Z")
if there data on sda2 —\> make a save then try ```auto e2fsck -f -y -v /dev/sda2 ``` ---
**Author:** ![jmainhard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/j/ed8c4c/32.png) [@jmainhard](https://forum.endeavouros.com/u/jmainhard)\ **Post date:** [December 10, 2022, 4:42pm UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/7 "2022-12-10T16:42:18Z")
How should I make a save from /dev/sda2? Something that has me worried and ignored in the first post is that I remember not so clearly, that besides ignoring errors fsck prompted me to rewrite on the blocks. Also from my [INXI](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696#hardware-3) and other programs it looks like /dev/sda2 is empty from the available space. ---
**Author:** ![jmainhard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/j/ed8c4c/32.png) [@jmainhard](https://forum.endeavouros.com/u/jmainhard)\ **Post date:** [December 10, 2022, 7:11pm UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/8 "2022-12-10T19:11:47Z")
So looks it is possible to backup a disk via `dd` ill manage to backup the data and return later to update with what you pointed out @Stephane. Thanks! ---
**Author:** ![jmainhard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/j/ed8c4c/32.png) [@jmainhard](https://forum.endeavouros.com/u/jmainhard)\ **Post date:** [December 11, 2022, 5:21pm UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/9 "2022-12-11T17:21:42Z")
Hello again. Hope you having a nice day. After doing what you pointed out I can mount sda2 and sda1 on /mnt and /mnt/boot/efi respectively and chroot into my system and see all my files in /home. From that I present the following: 1. At booting still no boot partition e.g As my first post 2. When doing `fsck /dev/sda2` (I cancel it): ```auto e2fsck 1.46.5 (30-Dec-2021) /dev/sda2 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 6164727 extent tree (at level 2) could be narrower. Optimize? /dev/sda2: e2fsck canceled. /dev/sda2: **********WARNING: Filesystem still has errors********** ``` What should I do? At this point could I run grub-install? ---
**Author:** ![Stephane](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stephane/32/9196_2.png) [@Stephane](https://forum.endeavouros.com/u/Stephane)\ **Post date:** [December 11, 2022, 6:03pm UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/10 "2022-12-11T18:03:40Z")
you can go for that ```auto sudo e2fsck -f -y -v /dev/sda2 ``` ---
**Author:** ![jmainhard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/j/ed8c4c/32.png) [@jmainhard](https://forum.endeavouros.com/u/jmainhard)\ **Post date:** [December 11, 2022, 11:31pm UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/11 "2022-12-11T23:31:51Z")
Hi again. So has been approximately 5 hours since I ran this command and its still checking “Inode” by Inode apparently. A lot of blocks like this: ```auto Unattached inode 14294363 Connect to /lost+found? yes Inode 14294363 ref count is 2, should be 1. Fix? yes ``` From looking at the last log of first running `e2fsck` Im thinking that is still a long way to go. Probably millions from this log of the last lines of [first running e2fsck (previous reply)](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/6) ```auto Error reading block 214990848 (Input/output error). Ignore error? yes Force rewrite? yes Error writing file system info: Input/output error /dev/sda2: *****FILE SYSTEM WAS MODIFIED***** ``` Sadly since I am in final exams and have no time to wait **my decision at this point is to try a fresh installation** from the bootable usb (RIP last system ☹ ). If you still there and have any advice @Stephane I would be really grateful, I would be trying to reinstall in the next hour or so. Edit: my guess is that blocks have nothing to do with inodes, sorry for that. Even in that situation the time it is taking is soo much for me, and don’t know what to expect or how much. ---
**Author:** ![jmainhard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/j/ed8c4c/32.png) [@jmainhard](https://forum.endeavouros.com/u/jmainhard)\ **Post date:** [December 12, 2022, 2:53am UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/12 "2022-12-12T02:53:56Z")
Just finished trying to run EndeavourOS installation and it failed with the same. Calamares log: ```auto Job: Check file system on partition ‘/dev/sda2’ Command: e2fsck -f -y -v /dev/sda2 2022-12-11 - 23:14:17 [6]: void Calamares::ViewManager::onInstallationFailed(const QString&, const QString&) Calamares will quit when the dialog closes. 2022-12-11 - 23:14:17 [6]: QML Component (default slideshow) deactivated 2022-12-11 - 23:14:17 [6]: void Config::doNotify(bool, bool) Notification not sent; completion: failed ``` full log : [https://termbin.com/h7cq7](https://termbin.com/h7cq7) from journalctl -k: [https://clbin.com/VBN7Z](https://clbin.com/VBN7Z) Now I’m looking forward to have back my computer as soon as possible because is urgency, either via a fresh installation or my old system. Could anyone guide me? ---
**Author:** ![Stephane](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/stephane/32/9196_2.png) [@Stephane](https://forum.endeavouros.com/u/Stephane)\ **Post date:** [December 12, 2022, 6:34am UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/13 "2022-12-12T06:34:41Z")
your disk is dead , they were report errors in journallog ==\> change disk ---
**Author:** ![jmainhard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/j/ed8c4c/32.png) [@jmainhard](https://forum.endeavouros.com/u/jmainhard)\ **Post date:** [December 12, 2022, 11:42pm UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/14 "2022-12-12T23:42:38Z")
One disk is on the way. Thanks a lot for your time @Stephane. Have a nice week! 😀 ---
**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\ **Post date:** [December 13, 2022, 12:27am UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/15 "2022-12-13T00:27:54Z")
really looks like drive failing hardware side… Only as a recommendation on rescue drives it is best to clone it to another drive or create an image of the drive and do the rescue on cloned or image not an the drive that is failing. ---
**Author:** ![jmainhard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/j/ed8c4c/32.png) [@jmainhard](https://forum.endeavouros.com/u/jmainhard)\ **Post date:** [December 13, 2022, 1:07am UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/16 "2022-12-13T01:07:54Z")
Thank you! I will apply this next time ---
**Author:** ![system](https://forum.endeavouros.com/uploads/default/original/2X/9/9ea52f9fd5ef8e609e593c362d61a36295f48be8.png) [@system](https://forum.endeavouros.com/u/system)\ **Post date:** [December 15, 2022, 1:08am UTC](https://forum.endeavouros.com/t/apparently-deleted-my-boot-partition-and-or-more/34696/17 "2022-12-15T01:08:42Z")
Closed on December 15, 2022, 1:08am UTC This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.