0

I've just got my first Raspberry Pi 4. I'm trying to install Raspbian's July 2019 version. I've read all related issues to this problem here and I can´t manage to find the problem.

I downloaded Raspbian with desktop from the official page: https://www.raspberrypi.org/downloads/raspbian/ And flashed it on my Kingston 32 gb Class 10 SD Card using balenaEtcher.

The first incovenient I got was the write speed I got while using balenaEtcher: between 600 and 800 kbps. When the flash finished "succesfully", a tiny warning, hidden under a red X said:

\.\PhysicalDrive1: Source and Destination checksums do not match

I didn't pay attention to this warning and proceeded to turn on my Pi anyway, and then I got the error in the title:

Kernel panic-not syncing: VFS: unable to mount root fs on unknown-block(179,2)

Reading other issues here, I tried editing cmdline.text by changing the rootfs and replace the 2 at the end with a 6, but this made my Pi stuck at the four raspberries without booting.

I also tried doing a filesystem check with fsck.ext4 on my PC with Linux mint but I got a message that said that the filesystem couldn't be found.

I think that the SD Card may be the problem but I just want to make sure it is before buying a new one, as they are not cheap where I live.

I don't know what else I can do. Thanks for your help.

EDIT:

Already run an H2testw, here we have the results:

Warning: Only 30869 of 30870 MByte tested.
The media is likely to be defective.
87.0 MByte OK (178293 sectors)
30.0 GByte DATA LOST (63041419 sectors)
Details:36.5 KByte overwritten (73 sectors)
0.5 KByte slightly changed (< 8 bit/sector, 1 sector)
30.0 GByte corrupted (63041345 sectors)
36.5 KByte aliased memory (73 sectors)
First error at offset: 0x0000000002f41010
Expected: 0x5899e01398821110
Found: 0x5899e01398821510
H2testw version 1.3
Writing speed: 7.95 MByte/s
Reading speed: 9.72 MByte/s
H2testw v1.4

Don't need to make any more clarifications, already bought a new card, thanks for your time.

  • I have been using different types of uSD cards, the writing speed varies from about 4Mb/s to 8/10MB/s or higher. I never saw your ridiculously low speed. – tlfong01 Aug 23 at 0:56
  • So I should probably switch my SD Card? – Sebastian Braga Aug 23 at 11:53
  • yes, get two class 10+ ones. – tlfong01 Aug 23 at 11:57
  • Why 2? I've already bought a new one, I should receive it this afternoon, but why should I get 2? They are not that cheap where I live – Sebastian Braga Aug 23 at 12:13
  • Well, I was about to suggest to use 16GB Class 10 x 2, which I think is most cost effective, unless you are doing video/image processing things. I always use two cards to swap troubleshooting. You may even consider 8GB Class 10, if it is much cheaper. Beside swap troubleshooting, it is a good idea to keep a backup copy. – tlfong01 Aug 23 at 12:18
-1

This is a quite common error reported on this site.

The root partition is damaged. IT CANNOT BE FIXED by modifying files.

The most likely cause is a faulty download - you should check the checksum BEFORE imaging.

This can also be due to a faulty card or hardware.

  • Just checked SHA256 and it is ok, so the download is not the problem. The checksum error I'm talking about is the one Etcher gives me after it finishes flashing. I'm just asking if there is anything I can do other than buying another SD card, or at least something I can do to know if that's really what's causing the problem – Sebastian Braga Aug 22 at 22:35
  • Boot from another SDCard. Mount the broken system in a USB reader and run sudo umount /dev/sda1; sudo umount /dev/sda2: sudo fsck -f -y /dev/sda1;sudo fsck -f -y /dev/sda2;sudo poweroff; swap the cards back and all should be good. – Dougie Aug 23 at 0:04
  • @Dougie the repair procedure may work for a corrupted disk, but is unlikely to work on a fresh image rejected by Etcher (before initial expansion). Every occasion I have encountered this it was due to faulty image or faulty SD Card. – Milliways Aug 23 at 4:14
  • OK then the OP should test the SDCard with H2TESTW as it's likely a fake. – Dougie Aug 23 at 8:33
  • I'm testing and so far it is fine, already copied 5,5 gb without any problems (speed always between 7,5 and 8 mbps) will update you when it finishes – Sebastian Braga Aug 23 at 12:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.