slayer^_^
April 26th, 2008, 08:47 AM
hi, i've got a problem with hardy heron installation, i know you can help me:
here is my partition table :
1st hard drive - sata
etx3 Linux partition
swap partition
ext3 Archive partition
2nd hard drive - ide
ntfs weendoos partition
ext3 archive partition
1) grub is mad, it gives me error 17 (can't mount the partition) because (i dunno why) it tries to boot hard drive (0,0) - but changing it to (1,0) i fix the problem.
2) Grub doesn't allow anymore me to choose to boot the weendoos partition
2) i've got that second hard drive, now hardy can see its partitions during the install process and gparted sees it still, however the installed hardy sees the hard drive as an unmountable scsi device... gparted sees its partitions but can't make any operation on...
3) on that second hard drive
what's happening? help me!
(p.s. installed 3 times , every time the same problems... the second hard drive recognized as scsi even if i updated from gutsy, my cd rom and my hardy cd are working fine... i didn't experience these problems with hardy beta)
output of sudo fdisk -l
Disco /dev/sda: 122.9 GB, 122942324736 byte
255 heads, 63 sectors/track, 14946 cylinders
Units = cilindri of 16065 * 512 = 8225280 bytes
Disk identifier: 0x90399039
Dispositivo Boot Start End Blocks Id System
/dev/sda1 * 1 1804 14490598+ 7 HPFS/NTFS
/dev/sda2 1805 14946 105563115 f W95 Esteso (LBA)
/dev/sda5 1805 14946 105563083+ 83 Linux
Disco /dev/sdb: 250.0 GB, 250059350016 byte
255 heads, 63 sectors/track, 30401 cylinders
Units = cilindri of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd624f0be
Dispositivo Boot Start End Blocks Id System
/dev/sdb1 * 1 2791 22418612 83 Linux
/dev/sdb2 2792 3041 2008092 82 Linux swap / Solaris
/dev/sdb3 3042 30401 219769168 83 Linux
if I type in the console
stormrider@stormrider-desktop:~$ sudo mount -t ext3 /dev/sda5 /media/download
it reports:
mount: the special device /dev/sda5 does not exist
output of /etc/fstab:
# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# Entry for /dev/sdb1 :
UUID=203e112a-7913-4500-b84f-bb60ba20d555 / ext3 relatime,errors=remount-ro 0 1
# Entry for /dev/sdb3 :
UUID=74b2f489-c6be-4b25-9305-976bf92e34cb /media/archivio ext3 relatime 0 2
/media/download ext3 relatime 0 2 0
/media/windows ntfs defaults,umask=007,gid=46 0 1 0
# Entry for /dev/sdb2 :
UUID=32371871-cb17-45fd-b949-f5604c47f79d none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
NOTABLY adding the "all_generic_ide" option to /boot/grub/menu.lst makes hardy recognize the partitions on the ide drive , but i experience slow system and complete lockups
argh, someone help me !
-----------
SOLUTION
-----------
Today we discovered on launchpad the final solution:
the ide cable!
the new modules absolutely require a 80-wire ide cable (the one with coloured pins), everyone of us who experienced this bug had 40-wire ide-cables...
...and of course a good cable plugging (blue plug on motherboard, gray on slave and black on master) and a correct setting of the jumpers of the hard disks (disk set as master if it is connected to the black plug of the cable, ecc ecc).
A manually setting of the dma speed and pio mode in the motherboard bios is also a good idea.
Best regards.
here is my partition table :
1st hard drive - sata
etx3 Linux partition
swap partition
ext3 Archive partition
2nd hard drive - ide
ntfs weendoos partition
ext3 archive partition
1) grub is mad, it gives me error 17 (can't mount the partition) because (i dunno why) it tries to boot hard drive (0,0) - but changing it to (1,0) i fix the problem.
2) Grub doesn't allow anymore me to choose to boot the weendoos partition
2) i've got that second hard drive, now hardy can see its partitions during the install process and gparted sees it still, however the installed hardy sees the hard drive as an unmountable scsi device... gparted sees its partitions but can't make any operation on...
3) on that second hard drive
what's happening? help me!
(p.s. installed 3 times , every time the same problems... the second hard drive recognized as scsi even if i updated from gutsy, my cd rom and my hardy cd are working fine... i didn't experience these problems with hardy beta)
output of sudo fdisk -l
Disco /dev/sda: 122.9 GB, 122942324736 byte
255 heads, 63 sectors/track, 14946 cylinders
Units = cilindri of 16065 * 512 = 8225280 bytes
Disk identifier: 0x90399039
Dispositivo Boot Start End Blocks Id System
/dev/sda1 * 1 1804 14490598+ 7 HPFS/NTFS
/dev/sda2 1805 14946 105563115 f W95 Esteso (LBA)
/dev/sda5 1805 14946 105563083+ 83 Linux
Disco /dev/sdb: 250.0 GB, 250059350016 byte
255 heads, 63 sectors/track, 30401 cylinders
Units = cilindri of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd624f0be
Dispositivo Boot Start End Blocks Id System
/dev/sdb1 * 1 2791 22418612 83 Linux
/dev/sdb2 2792 3041 2008092 82 Linux swap / Solaris
/dev/sdb3 3042 30401 219769168 83 Linux
if I type in the console
stormrider@stormrider-desktop:~$ sudo mount -t ext3 /dev/sda5 /media/download
it reports:
mount: the special device /dev/sda5 does not exist
output of /etc/fstab:
# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# Entry for /dev/sdb1 :
UUID=203e112a-7913-4500-b84f-bb60ba20d555 / ext3 relatime,errors=remount-ro 0 1
# Entry for /dev/sdb3 :
UUID=74b2f489-c6be-4b25-9305-976bf92e34cb /media/archivio ext3 relatime 0 2
/media/download ext3 relatime 0 2 0
/media/windows ntfs defaults,umask=007,gid=46 0 1 0
# Entry for /dev/sdb2 :
UUID=32371871-cb17-45fd-b949-f5604c47f79d none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
NOTABLY adding the "all_generic_ide" option to /boot/grub/menu.lst makes hardy recognize the partitions on the ide drive , but i experience slow system and complete lockups
argh, someone help me !
-----------
SOLUTION
-----------
Today we discovered on launchpad the final solution:
the ide cable!
the new modules absolutely require a 80-wire ide cable (the one with coloured pins), everyone of us who experienced this bug had 40-wire ide-cables...
...and of course a good cable plugging (blue plug on motherboard, gray on slave and black on master) and a correct setting of the jumpers of the hard disks (disk set as master if it is connected to the black plug of the cable, ecc ecc).
A manually setting of the dma speed and pio mode in the motherboard bios is also a good idea.
Best regards.