nachdem ich mein Debiansystem total kaputtkonfiguriert hatte, wollte ich debian mittels dem installer von CC neuinstallieren
nur treten jetzt am Anfang der Installation folgende Fehler auf
Die erste Partition nimmt er anscheinend noch, aber danach funktioniert es nicht mehr, woran kann das liegen ?Error: Partition doesn't exist.
Information: Don't forget to update /etc/fstab, if necessary.
Error: Partition doesn't exist.
Information: Don't forget to update /etc/fstab, if necessary.
Error: Partition doesn't exist.
Information: Don't forget to update /etc/fstab, if necessary.
Error: Partition doesn't exist.
Information: Don't forget to update /etc/fstab, if necessary.
Error: Partition doesn't exist.
Information: Don't forget to update /etc/fstab, if necessary.
Error: Partition doesn't exist.
Information: Don't forget to update /etc/fstab, if necessary.
Error: Partition doesn't exist.
Information: Don't forget to update /etc/fstab, if necessary.
Error: Partition doesn't exist.
Information: Don't forget to update /etc/fstab, if necessary.
Error: Partition doesn't exist.
Information: Don't forget to update /etc/fstab, if necessary.
Information: Don't forget to update /etc/fstab, if necessary.
Information: Don't forget to update /etc/fstab, if necessary.
Information: Don't forget to update /etc/fstab, if necessary.
Information: Don't forget to update /etc/fstab, if necessary.
Information: Don't forget to update /etc/fstab, if necessary.
Information: Don't forget to update /etc/fstab, if necessary.
expr: syntax error
Information: Don't forget to update /etc/fstab, if necessary.
mke2fs 1.27 (8-Mar-2002)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
6024 inodes, 24066 blocks
1203 blocks (5.00%) reserved for the super user
First data block=1
3 block groups
8192 blocks per group, 8192 fragments per group
2008 inodes per group
Superblock backups stored on blocks:
8193
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
mke2fs 1.27 (8-Mar-2002)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
128768 inodes, 257040 blocks
12852 blocks (5.00%) reserved for the super user
First data block=0
8 block groups
32768 blocks per group, 32768 fragments per group
16096 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 37 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
mke2fs 1.27 (8-Mar-2002)
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition tablekjournald starting. Commit interval 5 seconds
.
mke2fs 1.2EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,3), 7 (8-Mar-2002)
internal journal
mke2fs: Device sEXT3-fs: mounted filesystem with ordered data mode.
ize reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
mke2fs 1.27 (8-Mar-2002)
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being kjournald starting. Commit interval 5 seconds
busy and in use.EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), You may need tinternal journal
o reboot
to reEXT3-fs: mounted filesystem with ordered data mode.
-read your partition table.
mke2fs 1.27 (8-Mar-2002)
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being bushda5: bad access: block=2, count=2
y and in use. Yend_request: I/O error, dev 03:05 (hda), sector 2
ou may need to rEXT3-fs: unable to read superblock
eboot
to re-read your partition table.
Setting up swapspace version 1, size = 518184960 bytes
mount: wrong fs type, bad option, bad superblock on /dev/hda5,
or thda6: bad access: block=2, count=2
oo many mounted end_request: I/O error, dev 03:06 (hda), sector 2
file systems
EXT3-fs: unable to read superblock
(could this be the IDE devihda7: bad access: block=2, count=2
ce where you in end_request: I/O error, dev 03:07 (hda), sector 2
fact use
EXT3-fs: unable to read superblock
ide-scsi so that sr0 or sda or hda8: bad access: block=2, count=2
so is needed?)
end_request: I/O error, dev 03:08 (hda), sector 2
mount: wrong fs EXT3-fs: unable to read superblock
type, bad option, bad superblock on /dev/hda6,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
mount: wrong fs type, bad option, bad superblock on /dev/hda7,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
mount: wrong fs type, bad option, bad superblock on /dev/hda8,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
Server ist von 1und1 (XXL)
MfG
Kai
