0 Пользователей и 1 Гость просматривают эту тему.
При запуске в recovere mode тоже самое.
Последние действия на работающей ОС:Решил изменить USplash screen и воспользовался руководством1.9.10 Как изменить USplash Screen при загрузке/завершенииСделал как написано только разве что не перезагрузился, а потом перевёл систему в спящий режим.
После этого не могу запустить систему, выскакивает то что написал в самом начале
Прошу помощи, в решении этой проблемы.
« Последнее редактирование: 09 Марта 2008, 18:04:51 от Garfeild »
я после этого переустанавливал систему, ответа не дали.
Можно загрузиться с Live CD , затем 1) sudo mount /dev/sdaX /mnt //sdaХ — раздел c Linux2) sudo chroot /mntЭтот путь chroot я нашёл тут на форуме, лично я всегда делал немного по-другому (читай: сложнее), но надеюсь этот тоже cработает.Итак, значит, вводим sudo chroot /mnt , ну и теперьa)sudo update-alternatives —config usplash-artwork.sob)sudo update-initramfs -u
Или же о просто переустановить ядро.
« Последнее редактирование: 09 Марта 2008, 04:43:50 от Sven »
Большое спасибо, помогло.
Я для себя решил, что до последнего буду бится за систему.
Система Ubuntu 9.04 установлена сразу после релиза, работала почти пол года без сбоев, все обновления ставились адекватно. Непосредственно перед возникновением проблемы ни каких пакетов не ставил и не обновлял.
подозревал, что с железом беда, возможно с материнкойM/B ASUS P5ND2-SLICPU Intel Pentium 4 630 BOX 3.0 ГГцDDR-II DIMM 512Mb х4шт
upd: тестированием памяти установлено, что 1 из 4 планок памяти сдохла, после её извлечения «Kernel panic» больше не появлялся
« Последнее редактирование: 02 Октября 2009, 20:57:37 от Flashinbrain »
Помогло на 9.10, за исключение пункта а) т.к usplash не трогал.
Вчера при попытке обновить ядро через Менеджер обновлений произошел сбой связи. Обновленное ядро не было закачано. После перезагрузки не могу попасть в систему. Грузится GRUB, потом лого Ubuntu и черный экран. Что делать? Ubuntu 9.10. На всякий случай: в интернет выхожу через USB модем.
Unable to mount root fs on unknown-block
I have the exact same problem on boot!
Pi worked perfectly on both wheezy and now raspbmc on a Scandisk SD 8gb class 10, and apple iphone charger. But suddenly, maybe caused by using Constellation as a remote for turning on/off Pi, the Pi don’t boot just as 4d1l describes.
If any one has a solution or an idea, please help! Don’t want to lose all my configurations.
I tried changing to the original distribution on a 2GB SD card in case I had scrambled Wheezy, but get a similar error:
I have used several power configurations, with i/p volts between 4.93 and 4.97V, so I dont believe I have a problem there, and in any case it was working before.
So it looks like the RPi is bricked.
Any help welcomed.
Tony
Reference my previous post, I was reading R-Pi trouble shooting on the elinux.org website. This mentions the Kernel Panic problem and suggests removing any USB devices. I have booted my device with and without USB and it makes no difference. I also just tried a bigger power supply (5V 2A Samsung) which gives 5.19V on the i/p to the polyfuse and 5.09 on the regulator side. Still get same error. So is there anyone from the R-Pi org or Element14 looking at this thread and able to respond.
OK folks. Sorry to answer my own post again, but some of you out there may still be in the same state as I was. Reading the elinux.org website again, I found a reference that low voltage on the supply or feeds from the USB ports can cause unexpected writes to the SD card (I cant currently find the reference). I was wondering if both my SD cards has experienced such a write glitch. So I rewrote the Wheezy image to my 16GB Transcend class 10 card from my Macbook and Pound shop card reader. My setup also seems to need the init file editing to force the HDMI TV o/p.
Hey presto — working Pi again.
So now I have to reload the work I was doing, since any previous code seems to be lost.
So the answer to this topic — at least for me — is to rewrite the SD card image
good luck out there
Tony
miicchhii wrote:I have the same problems on raspbian wheezy, since i used the GPIO’s over php and shellscript.
To fix this problem get a new SD card or did what «tony1tf» did.
OK folks. Sorry to answer my own post again, but some of you out there may still be in the same state as I was. Reading the elinux.org website again, I found a reference that low voltage on the supply or feeds from the USB ports can cause unexpected writes to the SD card (I cant currently find the reference). I was wondering if both my SD cards has experienced such a write glitch. So I rewrote the Wheezy image to my 16GB Transcend class 10 card from my Macbook and Pound shop card reader. My setup also seems to need the init file editing to force the HDMI TV o/p.
Hey presto — working Pi again.
So now I have to reload the work I was doing, since any previous code seems to be lost.
So the answer to this topic — at least for me — is to rewrite the SD card image
It seems my SD cars was not supported. Bought a new SD card and works like a charm.
I have the same problem when booting Xbian for the 2nd time.
My SD card is on the approved list though: 8GB SDHC Class 10 (SD10V/8GB).
you may be able to recover just by replacing the DOS partition —
the kernel , or start.elf may have got currupt somehow
How To ask Questions :- http://www.catb.org/esr/faqs/smart-questions.html
WARNING — some parts of this post may be erroneous YMMV
I was getting the same problem. I ended up doing a few things, so I’ll list them. Hope this helps.
I kicked off with SD formatter. Re formatted the SD disk. In option I selected ‘adjustment’ on.
I then reinstalled (in windows 7) raspbmc.
I did the same for Debian on a different SD card (this one was an old one that is only a class 4).
I did the next step for both SD cards.
Then saved the file.
I then unmounted the SD card(s) from windows, and put it in the raspberry pi.
Plugged in the power, and they restarted, and raspbmc re installed.
Hope this helps,
Hi i got the same / similar problem using some builds of XBMC on my pi.
I ended up in reformating everything as soon as I run into this problem.
Until recently ..
As i tried to image my xbmc XD card (8GB) using dd (e.g. dd if=/dev/sdd of=image.dd) i run into the same effect after restoring from a Delking 8 GB SD (which i took out of my Canon EOS) to a more «stable» Samsung 8GB SD (mb-ss8a).
I took the defective Samsung card to my notebook mounting it resulting in some error massages in dmesg ..
to fix this problem I checked the filesystem
fsck.ext4 /dev/mmcblk0p3
answering yes to start a fix on a not fitting file system
resize2fs /dev/mmcblk0p7 7300M
Guessing the FS to 7.3GB
Insert the SD into you Pi and try
My Pi encounter this problem twice..it runs normally for sereval days.
but, when i reboot, it crashed..
i have changed a sd card, but this problem appears again~
This is too bad..
Had the same problem. Put the SD card into my Ubuntu laptop and executed a fsck
e2fsck -f -v /dev/mmcblk0p2
Answered yes to all reported problems and my PI booted up OK.
Using a 4GB card Sandisk card pre- formatted at FAT32. Now instead of FAT 32 the card is saying its FAT16 and 17 mBytes are used out of 58Mbytes?
Not a great start
Any clues please
Just got my Pi after waiting a month. Ran into the same error even after writing the image multiple times. Turns out the SD card I was using was too slow (Class 2 SanDisk). I then tried with SanDisk class 6 (Extreme III) and it booted fine.
I had this happen after an rpi-update. When I plugged it into another Linux box, it gave me an error on /dev/sdc2, so I ran:
Fixed it right up without formatting.
I was having this same problem and I thought I’d just mention that removing my USB devices (in my case a 3rd party IR dongle and a Logitech bluetooth dongle) fixed the issue for me.
This keeps happening to me and the only (really the only) solution is format and re-install SD card.
I’ve a new Class 10 8GB SD card, it’s already the 2nd SD card and still behaves the same way.
It happens occasionally after a XBMC automatic update on boot.
I think that this equipment is not prepared for massive read/write operations and this is where this system update fails.
Since the update is a critical operation it should in my opinion check the filesystem consistency after doing it and repeat it in case there are errors.
It happened once during boot, it shows a message saying that the partition is ReadOnly and loops until I turn it off.
I always use the reboot option from RaspBMC menu and it happend yesterday again.
I also tried to fix the partition with fsck, it really found lot errors and after fixing the kernel panic message was resolved but the system does nothing but displaying a berry in the screen.
I’m running the latest standard Debian (2013-02-09-wheezy-raspbian.img) image with the latest firmware (as of this post)
EDIT: Nevermind, turns out my USB printer was causing the USB HDD to disappear completely from /dev/. The rest still stands though.
I have the same problem. I’m running XBMC on my RPi and when I plug it in, I only see the message:
I see that some of you managed to resolve the issue with «fsck». Since I’m a real noob with Linux (apart from RPi, I only have this Win7 PC), I need your help. Is there a tool for Windows with which I might try fixing the problem?
Thanks for your help.
I assume my 8GB SD card is trashed somehow?
Return to “Troubleshooting”
Analysis
The panic informs that the Linux kernel is unable to:
- Detect the partition because it does not have support for the partition type (less likely, but still possible);
- Detect the partition because the wrong device was passed in the boot loader configuration.
Synopsis
Any Gentoo Linux system on which a new kernel is being booted (or an update was made on the bootloader configuration).
Resolution
Boot with the old kernel (if available), or with a LiveCD, and open the kernel configuration:
- Ensure that the controller chipset has been configured in the Linux kernel (and in-kernel, not as a module);
- Ensure that the used file systems (such as ext2, ext3, ext4, ReiserFS, Btrfs, etc.) are configured in the Linux kernel (and built into the kernel, not as a module);
Also verify that the boot loader configuration ( for GRUB legacy and for GRUB2) refers to the correct partition:
/boot/grub/grub.confGRUB Legacy partition example
title Gentoo Linux
root (hd0,0)
kernel /kernel-3.0.4 root=/dev/sda3
When using an initramfs and upgrade to another kernel version, make sure the initramfs is recreated correctly in /boot for the new kernel version and that the boot loader configuration refers to the correct initramfs.
