LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 07-23-2014, 06:24 PM   #1
New2Linux2
Member
 
Registered: Jan 2004
Location: Arizona
Distribution: Debian
Posts: 153

Rep: Reputation: 43
No filesystem could mount root and then a kernel panic Debian 7.5.0 PowerPC


I just finished installing debian 7.5.0 PowerPC on an IBM eServer P5 with 4 U320 SCSI hard drives. This is a clean install with no prior OS, no version of VIOS or AIX and not using an IBM HMC.

After getting Debian to install, on first boot into the OS, I get a kernel panic.
Code:
Please wait, loading kernel...
   Elf64 kernel loaded...
Loading ramdisk...
ext2: i/o error 2133571364 in read
ramdisk loaded at 01700000, size: 8192 Kbytes
OF stdout device is: /vdevice/vty@30000001
Preparing to boot Linux version 3.2.0-4-powerpc64 (debian-kernel@lists.debian.org) (gcc 

version 4.6.3 (Debian 4.6.3-11) ) #1 SMP Debian 3.2.57-3
Detected machine type: 0000000000000101
Max number of cores passed to firmware: 16 (NR_CPUS = 32)
Calling ibm,client-architecture-support... not implemented
command line: root=UUID=1d82c29b-5695-47a8-a85f-5114665b0ef7 ro
memory layout at init:
  memory_limit : 0000000000000000 (16 MB aligned)
  alloc_bottom : 0000000001f00000
  alloc_top    : 0000000008000000
  alloc_top_hi : 00000001f0000000
  rmo_top      : 0000000008000000
  ram_top      : 00000001f0000000
instantiating rtas at 0x00000000076a1000... done
Querying for OPAL presence... not there.
boot cpu hw idx 0
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0000000003001000 -> 0x0000000003002354
Device tree struct  0x0000000003003000 -> 0x0000000003017000
[    0.000000] Using pSeries machine description
[    0.000000] Using 1TB segments
[    0.000000] Found initrd at 0xc000000001700000:0xc000000001f00000
[    0.000000] bootconsole [udbg0] enabled
[    0.000000] Partition configured for 2 cpus.
[    0.000000] CPU maps initialized for 2 threads per core
[    0.000000] Starting Linux PPC64 #1 SMP Debian 3.2.57-3
[    0.000000] -----------------------------------------------------
[    0.000000] ppc64_pft_size                = 0x1b
[    0.000000] physicalMemorySize            = 0x1f0000000
[    0.000000] htab_hash_mask                = 0xfffff
[    0.000000] -----------------------------------------------------
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.2.0-4-powerpc64 (debian-kernel@lists.debian.org) (gcc version 

4.6.3 (Debian 4.6.3-11) ) #1 SMP Debian 3.2.57-3
[    0.000000] [boot]0012 Setup Arch
[    0.000000] PCI host bridge /pci@800000020000002  ranges:
[    0.000000]   IO 0x000003fe00200000..0x000003fe002fffff -> 0x0000000000000000
[    0.000000]  MEM 0x0000040040000000..0x000004007fffffff -> 0x00000000c0000000
[    0.000000] PCI host bridge /pci@800000020000003  ranges:
[    0.000000]   IO 0x000003fe00300000..0x000003fe003fffff -> 0x0000000000000000
[    0.000000]  MEM 0x0000040080000000..0x00000400bfffffff -> 0x00000000c0000000
[    0.000000] PCI host bridge /pci@800000020000004  ranges:
[    0.000000]   IO 0x000003fe00400000..0x000003fe004fffff -> 0x0000000000000000
[    0.000000]  MEM 0x00000400c0000000..0x00000400ffffffff -> 0x00000000c0000000
[    0.000000] EEH: PCI Enhanced I/O Error Handling Enabled
[    0.000000] PPC64 nvram contains 7168 bytes
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000000 -> 0x001f0000
[    0.000000]   Normal   empty
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0: 0x00000000 -> 0x001f0000
[    0.000000] [boot]0015 Setup Done
[    0.000000] PERCPU: Embedded 13 pages/cpu @c000000000b00000 s20608 r0 d32640 u524288
[    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2003840
[    0.000000] Policy zone: DMA
[    0.000000] Kernel command line: root=UUID=1d82c29b-5695-47a8-a85f-5114665b0ef7 ro
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] freeing bootmem node 0
[    0.000000] Memory: 7982944k/8126464k available (7056k kernel code, 143520k reserved, 1312k 

data, 1922k bss, 432k init)
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  CONFIG_RCU_FANOUT set to non-default value of 32
[    0.000000]  RCU dyntick-idle grace-period acceleration is enabled.
[    0.000000] NR_IRQS:512
[    0.000000] clocksource: timebase mult[7cfc80] shift[22] registered
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [hvc0] enabled, bootconsole disabled
[    0.000000] console [hvc0] enabled, bootconsole disabled
[    0.000568] pid_max: default: 32768 minimum: 301
[    0.000747] Security Framework initialized
[    0.000759] AppArmor: AppArmor disabled by boot time parameter
[    0.002209] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[    0.007085] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.009202] Mount-cache hash table entries: 256
[    0.017257] Initializing cgroup subsys cpuacct
[    0.017279] Initializing cgroup subsys memory
[    0.017454] Initializing cgroup subsys devices
[    0.017462] Initializing cgroup subsys freezer
[    0.017470] Initializing cgroup subsys net_cls
[    0.017478] Initializing cgroup subsys blkio
[    0.017493] Initializing cgroup subsys perf_event
[    0.017613] POWER5+/++ performance monitor hardware support registered
[    0.019048] Brought up 2 CPUs
[    0.019501] devtmpfs: initialized
[    0.028995] print_constraints: dummy:
[    0.029141] NET: Registered protocol family 16
[    0.029163] IBM eBus Device Driver
[    0.033740] PCI: Probing PCI hardware
[    0.034836] IOMMU table initialized, virtual merging enabled
[    0.073593] opal: Node not found
[    0.075062] bio: create slab <bio-0> at 0
[    0.075409] vgaarb: loaded
[    0.075673] SCSI subsystem initialized
[    0.075986] Switching to clocksource timebase
[    0.084320] NET: Registered protocol family 2
[    0.084829] IP route cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.087362] TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
[    0.090736] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[    0.091189] TCP: Hash tables configured (established 524288 bind 65536)
[    0.113098] TCP reno registered
[    0.113130] UDP hash table entries: 4096 (order: 5, 131072 bytes)
[    0.113215] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
[    0.113465] NET: Registered protocol family 1
[    0.224882] Unpacking initramfs...
[    0.486170] Initramfs unpacking failed: read error
[    0.486183] Freeing initrd memory: 8192k freed
[    0.487793] vio 30000000: Warning: IOMMU dma not supported: mask 0xffffffffffffffff, table 

unavailable
[    0.487858] vio 30000001: Warning: IOMMU dma not supported: mask 0xffffffffffffffff, table 

unavailable
[    0.487902] vio 4000: Warning: IOMMU dma not supported: mask 0xffffffffffffffff, table 

unavailable
[    0.487944] vio 4001: Warning: IOMMU dma not supported: mask 0xffffffffffffffff, table 

unavailable
[    0.487985] vio 4002: Warning: IOMMU dma not supported: mask 0xffffffffffffffff, table 

unavailable
[    0.488247] Hypercall H_BEST_ENERGY not supported
[    0.488603] audit: initializing netlink socket (disabled)
[    0.488624] type=2000 audit(1406155635.483:1): initialized
[    0.555974] HugeTLB registered 16 MB page size, pre-allocated 0 pages
[    0.555985] HugeTLB registered 16 GB page size, pre-allocated 0 pages
[    0.556549] VFS: Disk quotas dquot_6.5.2
[    0.556653] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.556801] msgmni has been set to 15609
[    0.557113] alg: No test for stdrng (krng)
[    0.557178] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    0.557191] io scheduler noop registered
[    0.557199] io scheduler deadline registered
[    0.557253] io scheduler cfq registered (default)
[    0.558263] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.604110] pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
[    0.604150] Linux agpgart interface v0.103
[    0.604387] mousedev: PS/2 mouse device common for all mice
[    0.604543] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0
[    0.604936] TCP cubic registered
[    0.605079] NET: Registered protocol family 10
[    0.606096] Mobile IPv6
[    0.606103] NET: Registered protocol family 17
[    0.606114] Registering the dns_resolver key type
[    0.606357] registered taskstats version 1
[    0.610257] rtc-generic rtc-generic: setting system clock to 2014-07-23 22:47:16 UTC 

(1406155636)
[    0.610282] Initializing network drop monitor service
[    0.610478] List of all partitions:
[    0.610486] No filesystem could mount root, tried:
[    0.610498] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.610509] Call Trace:
[    0.610519] [c0000001eedefc30] [c000000000013524] .show_stack+0x80/0x130 (unreliable)
[    0.610536] [c0000001eedefce0] [c0000000004bacbc] .panic+0x88/0x204
[    0.610550] [c0000001eedefd80] [c000000000678f38] .mount_block_root+0x2b0/0x2c8
[    0.610563] [c0000001eedefe50] [c00000000067913c] .prepare_namespace+0x170/0x1b0
[    0.610575] [c0000001eedefee0] [c000000000678b10] .kernel_init+0x20c/0x214
[    0.610587] [c0000001eedeff90] [c00000000001ca4c] .kernel_thread+0x54/0x70
[    0.615053] Rebooting in 180 seconds..
This has me a bit stumped. The closest I can find on here is a post from 3 years ago, so it was no help (LILO instead of GRUB). Thanks in advance.
 
Old 07-24-2014, 02:37 PM   #2
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,289

Rep: Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322Reputation: 2322
Quote:
ext2: i/o error 2133571364 in read
That was line 3 or 4. It's a bad start.
No filesystem could mount root is because
a. you don't have a module for the root filesystem in the ramdisk.
b. The ramdisk is corrupt
c. The root= bit of the kernel boot line is wrong, so it's checking the wrong place.
 
2 members found this post helpful.
Old 07-24-2014, 02:42 PM   #3
New2Linux2
Member
 
Registered: Jan 2004
Location: Arizona
Distribution: Debian
Posts: 153

Original Poster
Rep: Reputation: 43
Thanks for the info, business kid. Now for the important part: how do I fix it?

This is a clean install of Debian 7.5.0 PowerPC with no other OS on the hardware.
They don't make a liveCD for this architecture.
Do I simply wipe it and install again or is this a bug for the distro developers?
Should I try a different distro for this hardware?

Any further help would be great. Thank you.

Last edited by New2Linux2; 07-24-2014 at 02:43 PM.
 
Old 07-24-2014, 02:52 PM   #4
Pearlseattle
Member
 
Registered: Aug 2007
Location: Zurich, Switzerland
Distribution: Gentoo
Posts: 999

Rep: Reputation: 142Reputation: 142
Hi
I don't see any "proposals" after the error message "No filesystem could mount root, tried:", nor I think to see any drive-related messages above => I would think that you have in your kernel no drivers/modules that can access the storage device on which the rootfs resides.
 
Old 07-24-2014, 03:42 PM   #5
New2Linux2
Member
 
Registered: Jan 2004
Location: Arizona
Distribution: Debian
Posts: 153

Original Poster
Rep: Reputation: 43
Nevermind. I found it myself. It is a reported bug. It seems a reinstall is the fix, but selecting to only install the drivers for the detected hardware. I've been doing a generic install, which triggered this particular bug. More info here:

https://bugs.debian.org/cgi-bin/bugr...cgi?bug=719479

Thanks business kid and Pearlseattle.

Last edited by New2Linux2; 07-24-2014 at 03:44 PM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Kernel Panic: unable to mount root filesystem... Firefox54 Linux - General 11 05-31-2011 01:49 PM
Kernel Panic unable to mount root filesystem mrinal mishra Linux - Kernel 4 05-03-2006 07:47 AM
Kernel Panic: It won't mount the root filesystem (2.6.8 and 2.6.9) and LILO hates me edman007 Linux - General 4 11-13-2004 05:41 PM
2.6 Kernel Panic : won't mount root filesystem Neorio Linux - Software 2 02-26-2004 09:38 PM
Kernel Panic: won't mount root filesystem Neorio Linux - Software 4 02-05-2004 06:32 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 06:09 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration