Skip to main content
12 events
when toggle format what by license comment
Jul 17 at 18:38 comment added pbies @Olivier we all need to "safely remove hardware" or use SysInternals sync64.exe -r.
Jul 17 at 14:36 comment added Olivier I actually just faced the same problem with an external 500 GB hard drive. It seems that the retailer took the drive straight from a sleeping computer with a Windows OS and put it into the external box before selling the whole thing to me...
Mar 26, 2022 at 18:02 history edited pbies CC BY-SA 4.0
added 66 characters in body
Mar 22, 2022 at 13:42 vote accept nonick66
Mar 22, 2022 at 13:41 comment added nonick66 I restart the super-block and everything seems OK. I think the problem is solved. The disk is up and running normally now. I found this link to help me solve it too. Thank you all for your help, and sorry for all the noob comments.
Mar 22, 2022 at 11:19 comment added nonick66 @TomYan yep, your right, sorry about that. I did find this: { FS Error count: 89794 First error time: Wed Aug 18 15:49:58 2021 First error function: ext4_lookup First error line #: 1708 First error inode #: 87687171 First error err: EFSCORRUPTED Last error time: Tue Mar 22 10:26:52 2022 Last error function: ext4_validate_block_bitmap Last error line #: 390 Last error err: EFSCORRUPTED }
Mar 22, 2022 at 11:06 comment added Tom Yan @nonick66 Neither of them is supposed to be run on /dev/sda but /dev/sda1 (according to your dmesg screenshot, the drive is partitioned and has one partition, which is not the same as "partitionless" btw).
Mar 22, 2022 at 10:46 comment added nonick66 I found out that it's a problem with the e2fsck. I tried dumpe2fs -h /dev/sda but it can't be found { /dev/sda contém dados "DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 4294967295 sectors, extended partition table (last)" }
Mar 20, 2022 at 15:40 comment added nonick66 Ok, thank you very much to all, I'll give it a try and get back to you.
Mar 20, 2022 at 14:44 comment added pbies @nonick66 even new drives can fail. Check SMART attributes for this drive. Fsck in case of errors of the file system may mess around with some files.
Mar 20, 2022 at 14:32 comment added nonick66 The drive is about 3 months old! I actually have two drives with the same problem! Should I run the e2fsck and will this destroy my data?
Mar 20, 2022 at 14:03 history answered pbies CC BY-SA 4.0