package mdadm 2.6.7.1-1ubuntu15 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mdadm
Hello,
The failure that on /dev/sda is no superblock is correct, because it is an USB stick with the ubuntu desktop edition live version. I want to setup an RAID1 array on /dev/sdb and /dev/sdc.
Regards, Rudolf
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: mdadm 2.6.7.1-1ubuntu15
ProcVersionSign
Uname: Linux 2.6.32-24-generic i686
AptOrdering:
mdadm: Install
postfix: Install
mdadm: Configure
postfix: Configure
Architecture: i386
Date: Fri Dec 24 08:14:55 2010
ErrorMessage: Unterprozess installiertes post-installati
LiveMediaBuild: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
MDadmExamine.
MDadmExamine.
MDadmExamine.
MDadmExamine.
MachineType: ASUSTeK Computer INC. 900A
ProcCmdLine: noprompt cdrom-detect/
ProcMDstat:
Personalities :
unused devices: <none>
SourcePackage: mdadm
Title: package mdadm 2.6.7.1-1ubuntu15 failed to install/upgrade: Unterprozess installiertes post-installati
dmi.bios.date: 09/24/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0607
dmi.board.
dmi.board.name: 900A
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 900A
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 368986, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.