Your message dated Fri, 20 Jun 2008 17:09:23 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Kernel from Debian 3.1 no longer supported
has caused the Debian Bug report #301489,
regarding kernel is unable to mount file system on raid0 device
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
301489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=301489
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: kernel-image-2.6.8-2-64-smp
Version: 2.6.8-6
Severity: grave
Seen on an A500 SMP system, it works fine with an A500 kernel found
at ftp.parisc-linux.org.
http://cvs.parisc-linux.org/download/linux-2.6/autobuild/a500_defconfig/palinux-a500-defconfig-2.6.8.1-pa11_0-2_all.deb
Just rebooting with this kernel (or vmlinux-2.6.11-pa2-a500_defconfig,
vmlinux-2.6.12-rc1-pa1-a500_defconfig) sucessfully mounts the file system.
All modules loaded.
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
Starting raid devices:
md: md0 stopped.
md: bind<sdb9>
md: bind<sda5>
md: raid0 personality registered as nr 2
md0: setting max_sectors to 128, segment boundary to 32767
raid0: looking at sda5
raid0: comparing sda5(15802240) with sda5(15802240)
raid0: END
raid0: ==> UNIQUE
raid0: 1 zones
raid0: looking at sdb9
raid0: comparing sdb9(15802240) with sda5(15802240)
raid0: EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 31604480 blocks.
raid0 : conf->hash_spacing is 31604480 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 8 bytes for hash.
mdadm: /dev/md0 has been started with 2 drives.
done.
Checking all file systems...
fsck 1.35 (28-Feb-2004)
/dev/sdb5: clean, 21431/488640 files, 619977/976636 blocks
/dev/sdb7: clean, 3646/977280 files, 95489/1953020 blocks
/dev/sdb8: clean, 30041/304608 files, 411790/608764 blocks
fsck.ext3: Invalid argument while trying to open /dev/md1
/dev/md1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the
superblock
is corrupt, and you might try running e2fsck with an alternate
superblock:
e2fsck -b 8193 <device>
fsck failed. Please repair manually.
CONTROL-D will exit from this shell and continue system startup.
--- End Message ---
--- Begin Message ---
Version: 2.6.8-99+rm
You reported a bug against the Linux kernel (version 2.6.8) that was
shipped with Debian 3.1 (sarge). Since Debian 3.1 is no longer
supported and the kernel has changed so much that it would be very
difficult to verify every outstanding bug from 2.6.8, I'm hereby
closing your bug report.
If you still see this issue with the kernel from the upcoming release
of Debian (lenny, version 5.0), then please me know and I'll be happy
to reopen this bug report.
Thanks.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
