| Summary: | fsck.ext2: Bad magic number in super-block while trying to open /dev/loop1 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | claire robinson <eeeemail> |
| Component: | Installer | Assignee: | Anne Nicolas <ennael1> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | 3alpha1 3beta4 | ||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
ddebug.log.gz
ddebug.log.tar.gz |
||
Created attachment 2737 [details]
ddebug.log.gz
claire robinson
2012-09-03 14:45:29 CEST
Whiteboard:
(none) =>
3alpha1 Is it still happening with alpha 2 release?
Manuel Hiebel
2012-10-20 20:25:04 CEST
Keywords:
(none) =>
NEEDINFO ping ? i'll do a beta dvd install and check this and bug 9284 valid 3beta4 Keywords:
NEEDINFO =>
(none) Created attachment 3734 [details]
ddebug.log.tar.gz
from 3beta4 default kde i586 install dvd
claire robinson
2013-04-11 11:56:34 CEST
Summary:
Mga3 alpha1 DVD fsck.ext2: Bad magic number in super-block while trying to open /dev/loop1 =>
DVD fsck.ext2: Bad magic number in super-block while trying to open /dev/loop1
claire robinson
2013-04-11 11:56:58 CEST
Summary:
DVD fsck.ext2: Bad magic number in super-block while trying to open /dev/loop1 =>
fsck.ext2: Bad magic number in super-block while trying to open /dev/loop1 @eeeemail@gmail.com Please look at current status & update when you get a chance. Thanks. old stuff Status:
NEW =>
RESOLVED |
Mga3 alpha1 DVD i586 default KDE installation from a USB stick. Checking /root/drakx/ddebug.log showed this, not sure if it is expected or a bug. * running: losetup /dev/loop1 /mnt/root/drakx/replay_install.img * mounting /dev/loop1 on /mnt/root/aif-mount as type ext2, options * running: fsck.ext2 -a /dev/loop1 fsck.ext2: Bad magic number in super-block while trying to open /dev/loop1 /dev/loop1: 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> * mounting /dev/loop1 on /mnt/root/aif-mount as type vfat, options I'll attach the full ddebug.log