AezDropZz
Posts: 29
Joined: Tue Dec 23, 2014 2:16 pm

Raspbian image not booting

Tue Jan 03, 2017 6:42 pm

Hello,

So i've been running a Samba-server with MINIDLNA on my pi for the best part of a year (I guess). But a week or two ago it ran into some problems where it does not want to boot anymore. So I've plugged the pi into a monitor and got the following screen (pictures might not be sharp, but should be readable). I have tried cloning the image to a new SD-card, but with the same result. Inserting an SD-card with a brand new image seems to boot just fine, so the problem seems to be with the image of my server. Does anyone have any clue as to what might have happened and how I could possibly solve this?

I have tried googling the error, but I could not find a similar problem that was solvable without entering commands (since I can't enter any).

Since it has been a while setting this pi up, I would lose massive amounts of time trying to figure out how to remake the image from scratch... The biggest problem is that the pi refuses to boot, so I can't retrieve any config-files or whatsoever.


Images:
https://drive.google.com/open?id=0B8l80 ... 2lNR1lBTnc
https://drive.google.com/open?id=0B8l80 ... kVTY3lFNEE
https://drive.google.com/open?id=0B8l80 ... 0ZZNWZoMm8

From what I can make out of the errors, it seems to be some sort of login-problem? I could of course be totally wrong about this :)

User avatar
DougieLawson
Posts: 39121
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: Raspbian image not booting

Tue Jan 03, 2017 7:45 pm

Those errors tend to suggest your SDCard has reached a point where it's worn out and due to fail drastically.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

Criticising any questions is banned on this forum.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

AezDropZz
Posts: 29
Joined: Tue Dec 23, 2014 2:16 pm

Re: Raspbian image not booting

Tue Jan 03, 2017 8:09 pm

Should it not have been solved then by burning a copy of the image to a brand new SD-card? Or am I not understanding what you mean?

User avatar
DougieLawson
Posts: 39121
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: Raspbian image not booting

Tue Jan 03, 2017 8:20 pm

You need to buy a new SDCard and consider tossing the old/fake/worn out one in the bin.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

Criticising any questions is banned on this forum.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

AezDropZz
Posts: 29
Joined: Tue Dec 23, 2014 2:16 pm

Re: Raspbian image not booting

Tue Jan 03, 2017 8:22 pm

That is what I did, but the new card gave the exact same error after cloning the image to it.
Then I tried flashing a brand new image to the new card (instead of the cloned image) and it worked fine.
Both old and new card are Kingston class 10, 32 gig.

drgeoff
Posts: 10765
Joined: Wed Jan 25, 2012 6:39 pm

Re: Raspbian image not booting

Tue Jan 03, 2017 9:09 pm

It looks like you have corrupted files and/or a corrupted file system on the old card. Copying to a new card won't repair them.

AezDropZz
Posts: 29
Joined: Tue Dec 23, 2014 2:16 pm

Re: Raspbian image not booting

Tue Jan 03, 2017 10:46 pm

And there is no way for me to fix this or recover most of the data and settings?

User avatar
DougieLawson
Posts: 39121
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: Raspbian image not booting

Tue Jan 03, 2017 10:51 pm

Build a fresh copy of NOOBS/Raspbian or plain Raspbian on the new SDCard.

Get a USB SDCard reader so you can mount the trashed card.

Run
for i in a1 a2 a5 a6; do sudo fsck -f -y /dev/sd$i;done
then try to mount the partitions after the fsck has completed so you can rescue your valuable data & programs.
Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

Criticising any questions is banned on this forum.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

AezDropZz
Posts: 29
Joined: Tue Dec 23, 2014 2:16 pm

Re: Raspbian image not booting

Wed Jan 04, 2017 8:40 am

I have tried your command and it does not want to work for me:

Code: Select all

fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
fsck.ext2: No such file or directory while trying to open /dev/sda1
Possibly non-existent device?
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
fsck.ext2: No such file or directory while trying to open /dev/sda2
Possibly non-existent device?
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
fsck.ext2: No such file or directory while trying to open /dev/sda5
Possibly non-existent device?
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
fsck.ext2: No such file or directory while trying to open /dev/sda6
Possibly non-existent device?
I tried four different SD-cards (two with a RPi-OS, two with 'normal' data) and two different card readers, I can always detect the readers but no SD-cards. To check detection i disconnected the reader and executed the command:

Code: Select all

sudo dmesg -C
Then I reconnected the reader with an sd-card in it and execute the following command:

Code: Select all

sudo dmesg
For the 'broken' SD-card with my important files, the readout was the following (which clearly shows the 32 gig SD-card):

Code: Select all

[   59.793751] usb 1-1.2: USB disconnect, device number 4
[   62.585781] usb 1-1.2: new high-speed USB device number 6 using dwc_otg
[   62.690148] usb 1-1.2: New USB device found, idVendor=11b0, idProduct=6108
[   62.690175] usb 1-1.2: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[   62.690192] usb 1-1.2: Product: FCR-HS215/1
[   62.690208] usb 1-1.2: Manufacturer: Kingston
[   62.690223] usb 1-1.2: SerialNumber: 000005525
[   62.691916] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[   62.692487] scsi host1: usb-storage 1-1.2:1.0
[   63.687479] scsi 1:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9328 PQ: 0 ANSI: 0
[   63.689159] sd 1:0:0:0: Attached scsi generic sg0 type 0
[   63.889599] scsi 1:0:0:1: Direct-Access     Generic  STORAGE DEVICE   9328 PQ: 0 ANSI: 0
[   63.891884] sd 1:0:0:0: [sda] Attached SCSI removable disk
[   63.892628] sd 1:0:0:1: Attached scsi generic sg1 type 0
[   63.897716] sd 1:0:0:1: [sdb] Attached SCSI removable disk
[   63.899484] scsi 1:0:0:2: Direct-Access     Generic  STORAGE DEVICE   9328 PQ: 0 ANSI: 0
[   63.901244] sd 1:0:0:2: Attached scsi generic sg2 type 0
[   63.905464] sd 1:0:0:2: [sdc] 61497344 512-byte logical blocks: (31.5 GB/29.3 GiB)
[   63.907285] sd 1:0:0:2: [sdc] Write Protect is off
[   63.907329] sd 1:0:0:2: [sdc] Mode Sense: 03 00 00 00
[   63.908108] scsi 1:0:0:3: Direct-Access     Generic  STORAGE DEVICE   9328 PQ: 0 ANSI: 0
[   63.909140] sd 1:0:0:2: [sdc] No Caching mode page found
[   63.909177] sd 1:0:0:2: [sdc] Assuming drive cache: write through
[   63.910636] sd 1:0:0:3: Attached scsi generic sg3 type 0
[   63.914092] sd 1:0:0:3: [sdd] Attached SCSI removable disk
[   63.921091]  sdc: sdc1 sdc2
[   63.928493] sd 1:0:0:2: [sdc] Attached SCSI removable disk
For a second SD-card with normal data, the readout was the following (which clearly shows the 1 gig SD-card):

Code: Select all

[  144.028965] usb 1-1.2: USB disconnect, device number 6
[  149.385781] usb 1-1.2: new high-speed USB device number 7 using dwc_otg
[  149.490125] usb 1-1.2: New USB device found, idVendor=11b0, idProduct=6108
[  149.490152] usb 1-1.2: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[  149.490169] usb 1-1.2: Product: FCR-HS215/1
[  149.490185] usb 1-1.2: Manufacturer: Kingston
[  149.490201] usb 1-1.2: SerialNumber: 000005525
[  149.491896] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[  149.495186] scsi host2: usb-storage 1-1.2:1.0
[  150.497515] scsi 2:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9328 PQ: 0 ANSI: 0
[  150.499160] sd 2:0:0:0: Attached scsi generic sg0 type 0
[  150.547750] scsi 2:0:0:1: Direct-Access     Generic  STORAGE DEVICE   9328 PQ: 0 ANSI: 0
[  150.550438] sd 2:0:0:0: [sda] Attached SCSI removable disk
[  150.552073] sd 2:0:0:1: [sdb] Attached SCSI removable disk
[  150.552337] sd 2:0:0:1: Attached scsi generic sg1 type 0
[  150.555235] scsi 2:0:0:2: Direct-Access     Generic  STORAGE DEVICE   9328 PQ: 0 ANSI: 0
[  150.557720] sd 2:0:0:2: Attached scsi generic sg2 type 0
[  150.563786] sd 2:0:0:2: [sdc] 2007040 512-byte logical blocks: (1.03 GB/980 MiB)
[  150.564605] scsi 2:0:0:3: Direct-Access     Generic  STORAGE DEVICE   9328 PQ: 0 ANSI: 0
[  150.566478] sd 2:0:0:2: [sdc] Write Protect is off
[  150.566585] sd 2:0:0:2: [s[code]
dc] Mode Sense: 03 00 00 00
[ 150.567688] sd 2:0:0:3: Attached scsi generic sg3 type 0
[ 150.570651] sd 2:0:0:2: [sdc] No Caching mode page found
[ 150.570748] sd 2:0:0:2: [sdc] Assuming drive cache: write through
[ 150.574595] sd 2:0:0:3: [sdd] Attached SCSI removable disk
[ 150.584077] sdc: sdc1
[ 150.591237] sd 2:0:0:2: [sdc] Attached SCSI removable disk
[/code]

Both the reader and cards were detected, yet I can't execute your command. Executing 'lsusb -t' generates the following information:

Code: Select all

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
        |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
        |__ Port 2: Dev 7, If 0, Class=Mass Storage, Driver=usb-storage, 480M
        |__ Port 4: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 4: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M

AezDropZz
Posts: 29
Joined: Tue Dec 23, 2014 2:16 pm

Re: Raspbian image not booting

Wed Jan 04, 2017 9:20 am

I think I might have solved the problem, upon further inspection it is not 'sda' but 'sdc'. Mounting the SD-card partition was possible using the following command:

Code: Select all

sudo mount /dev/sdc2 /mnt
It did give an error though, stating the partition is write-protected. Nevertheless, I was able to recover my config-files from the SD-card.

Thank you to everyone who contributed to this!

Return to “Troubleshooting”