| Autor |
Nachricht |
|
|
Titel: boot error after install - kernel panic: unknown-block(0,0)
 Verfasst am: 28.10.2006, 19:55 Uhr
|
|
Anmeldung: 21. Dez 2005
Beiträge: 18
|
|
After running 2005.03 for a year, I became jealous of all you folks who are able to use h2's du script and I decided to upgrade to 2006.RC4.
That was 2 weeks ago.
I keep getting an error on boot that looks like this:
kernel panic not syncing:VFS unable to mount rootfs on unknown-block(0,0)
I have read through previous posts (mostly German) and have tried several suggestions: Burn using SAO or DAO, burn using slow speeds (4x and 8x), use different media (I tried 2 burners at different speeds running different burning software, both on Win32 and Linux). I am still getting the same error.
I also tried memtest and testcd, both with no luck.
I am wondering if it is a problem from my setup when first partitiioned sda. I partitioned sda1 with 100MB for /boot, made sda2 swap, and sda3 for the root file system.
# /etc/fstab: static file system information.
/dev/sda3 / ext3 defaults,errors=remount-ro 0 1
/dev/hdc1 /storage/oldboot ext2 defaults 0 2
/dev/hdc3 /storage ext3 defaults 0 2
/dev/sda1 /boot ext2 defaults 0 2
/dev/hdc2 none swap sw 0 0
/dev/sda2 none swap sw 0 0
/dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0
I'm really stuck.
Any suggestions would help.
Thomas |
|
|
| |
|
|
|
 |
|
|
|
Titel: RE: boot error after install - kernel panic: unknown-block(0
Verfasst am: 28.10.2006, 20:28 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
Get rid of the /boot partition, it's not necessary any more.
Just use /, /home, and whatever other data stuff you want.
Try it that way and see how it goes, as far as I know, none of the developers use /boot any longer, so that might be the issue.
Get rid of /boot, then see if you can install and boot. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel: RE: boot error after install - kernel panic: unknown-block(0
Verfasst am: 29.10.2006, 00:38 Uhr
|
|
Anmeldung: 21. Dez 2005
Beiträge: 18
|
|
The /boot habit was something I picked up from Suse - it used /boot as part of the suspend mechanism on a laptop.
I repartitioned, deleting sda1 (boot) and sda2 (swap) the re-created sda1 for swap, leaving sd3 for everything else.
I am not really sure whether to install grub in MBR or the rootpartition, so I tried both.
MBR installation gives the same error:
Zitat:
kernel panic not syncing:VFS unable to mount rootfs on unknown-block(0,0)
Installing grub on the rootpartition gives this error:
Grub loading please wait
Error 17
When I look at the boot directory (/media/sda3/boot/) I don't see an initrd file. Is that a problem? |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: boot error after install - kernel panic: unknown-block(0
Verfasst am: 29.10.2006, 01:23 Uhr
|
|
Anmeldung: 08. Dez 2005
Beiträge: 300
|
|
| just make /boot a directory, not a separate partition. Having /boot as a separate partition is an old workaround when BIOS would not recognize drives above 528MB. Nowadays this restriction is largely moot as modern BIOS's use LBA addressing which eliminates those old restrictions for the most part, and now it is not necessary to have /boot a separate partition |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: boot error after install - kernel panic: unknown-block(0
Verfasst am: 29.10.2006, 02:09 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
I think a careful reformatting might be called for in this case. I know I not only had to reformat, but zero write, my 2005-3 64 bit install before 2005-4 would install onto it.
Try downloading the latest gparted livecd, delete all partitions, reformat, create just the /swap and the /, plus whatever data partitions you want, then see if it works.
http://gparted.sourceforge.net/livecd.php
Unless you have some reason to do so, install grub to mbr, especially if you are having some problems. But reformat it all I think, at least all of the os stuff, not the data stuff.
re suspend, with kanotix, it uses powersave, which uses your swap partition, so make sure that your swap is about 1 gigabyte large if you want that feature. The dual swap partitions with powersave did not work last time I checked. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel: RE: boot error after install - kernel panic: unknown-block(0
Verfasst am: 29.10.2006, 04:23 Uhr
|
|
Anmeldung: 17. Dez 2003
Beiträge: 16790
|
|
| RC4 has latest gparted included. |
|
|
| |
|
|
|
|
|
|
|
Titel: Re: RE: boot error after install - kernel panic: unknown-blo
Verfasst am: 29.10.2006, 11:38 Uhr
|
|
Anmeldung: 21. Dez 2005
Beiträge: 18
|
|
|
h2 hat folgendes geschrieben::
I think a careful reformatting might be called for in this case. I know I not only had to reformat, but zero write, my 2005-3 64 bit install before 2005-4 would install onto it.
For kicks I installed 2005-4 and it booted with the same error. I will zero write to the drive and try again.
The drive Kanotix sees as /dev/sda is physically 4 SCSI drives attached to an Adaptec controller in a RAID-0 array. It is the same hardware as I was using on 2005-03 but I broke the mirror and rebuilt the array before the install. The array comes up as optimal, and BIOS is seeing it as a single drive. Should not be a problem?
Thanks for the help. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: boot error after install - kernel panic: unknown
Verfasst am: 29.10.2006, 17:50 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
| loyl1, in the future, please include information that might actually help solve the problem when you initially post your question, such as the fact that you are running an extremely uncommon configuration, a Raid 0 array running through an adaptec card. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel: Re: RE: boot error after install - kernel panic: unknown-blo
Verfasst am: 04.11.2006, 20:41 Uhr
|
|
Anmeldung: 21. Dez 2005
Beiträge: 18
|
|
| [quote="loyl1"]
h2 hat folgendes geschrieben::
I think a careful reformatting might be called for in this case. I know I not only had to reformat, but zero write, my 2005-3 64 bit install before 2005-4 would install onto it.
h2,
You were right on with the re-formatting. I originally had Suse installed on the RAID 0 arrays sda and sdb. About a year ago I installed Kanotix 2005 03 to IDE drive hdc .An "fdisk -l" showed the ghost of the previous Suse install array, so I low level formatted all off the drives and it cleaned up that problem.
I should have detailed my RAID 0 setup - I guess I was just focusing in on the CD burner stuff - my bad.
After the low level formatting of each of the 4 drives, I initialized them and built the RAID 0 array. It shows optimal at boot. I booted up to the 2006 RC4 CD and partitioned sda into sda1, a 1GB swap partition and sda2 where Kanotix will be installed. I also have an IDE drive which was been used in the past as a primary drive but will now be used only for data storage.
I installed GRUB to the MBR, finished the install and rebooted.
When BIOS finishes and should make the hand off to GRUB, all I got was a blinking cursor. I used Recovery-Tools and selected Restore standard MBR on /dev/sda.
A reboot returns the original error:
kernel panic not syncing:VFS unable to mount rootfs on unknown-block(0,0).
Since I have only booted Suse but never booted Kanotix from the RAID 0, I am wondering if it is a driver issue with the Adaptec card. Here is the Adaptec output from lspci -vv:
03:02.0 RAID bus controller: Adaptec AAC-RAID (rev 01)
Subsystem: Adaptec 2120S (Crusader)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 177
Region 0: Memory at e8000000 (32-bit, prefetchable) [size=64M]
Expansion ROM at dc700000 [disabled] [size=64K]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Does anyone have any experience installing Kanotix on a hardware RAID array? |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: boot error after install - kernel panic: unknown
Verfasst am: 07.11.2006, 05:49 Uhr
|
|
Anmeldung: 21. Dez 2005
Beiträge: 18
|
|
| Does anyone have any Kanotix installation on hardware RAID advice? |
|
|
| |
|
|
|
|
|
|
