Tech Support Guy banner
Cancel

Second hard drive issue

2615 Views 35 Replies 2 Participants Last post by  saikee, 
O
Now working on a second computer which already has Ubuntu 6.06 installed. Have partitioned and formatted a second (larger) hard drive with partitions:

Device Boot Start End Blocks Id System
/dev/hdb1 1 1217 9775521 83 Linux
/dev/hdb2 1218 1340 987997+ 82 Linux swap / Solaris
/dev/hdb3 1341 18362 136729215 83 Linux
/dev/hdb4 18363 19929 12586927+ 83 Linux
Click to expand...
1 is boot, 3 is for /home, and 4 will be changed to fat32. 6.06 is installed

and have booted the original drive which has the following partition structure:

Device Boot Start End Blocks Id System
/dev/hda1 * 1 3570 28675993+ 7 HPFS/NTFS
/dev/hda2 3571 4711 9165082+ 83 Linux
/dev/hda3 4712 4998 2305327+ 82 Linux swap / Solaris
Click to expand...
The NTFS partition is corrupted, so this drive needs repartitioning and reinstalling.

After the reboot, I first tried to use the File Browser with the idea that I would simply copy the home directory from hda2 to hdb3, repart/reinstall hda with a structure more like hdb, copy /home back to the hda /home partition. However when I click on any partition, the Browser gives the message

Unable to mount the selected volume
Click to expand...
with details as:

error: device /dev/hda[2-3] (or hdb[1-4])* is not removable
error: could not execute pmount
Click to expand...
*(the "hda[2-3] (or hdb[1-4])" is my way of indicating that this is true for both drives and all linux partitions, although it will show the filesystem and home directories in hda2)

Here is fstab:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda2 / ext3 defaults,errors=remount-ro 0 1
/dev/hda3 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
Click to expand...
This newbie has suddenly jumped in over his head. I imagine that I need to figure out how to mount the hdb drive, but why is it giving the same message for hda?

Or am I not seeing a larger problem? Any guidance will be appreciated.
Save
Like
Status
Not open for further replies.
1 - 20 of 36 Posts
O
Since my last post, I have gotten answers to most of the issues raised, which included recognition on my part that I had not correctly identified hda1 as a fat32 partition, so that went away. Next was learning that one does not mount an entire drive, only partitions.

I took the new drive to the office to replace the current drive of one of the computers there. I say replace though it is more like a "weaning off of the old drive onto the new one".

I replaced the old drive (Ubuntu 5.04)with the new one as the master (as far as the cable connectors go), but it wouldn't boot, so I just installed 6.10 again which only took a few minutes, and that went perfectly. However. unfortunately I did so without plugging the old drive in again (on the slave connector), so now when I want to choose which drive I want to boot from, the computer just automatically boots from the drive that has the "master" cable connector (both drives set to cable select and both are on the same cable).

I would like grub to give me a choice between the two. Why does my computer not see both at boot? I suspect that grub will somehow need to be reinstalled-is this possible without a total reinstall?
See less See more
Save
Like
O
You don't need to re-install any system but need to change the partition reference of the two above-mentioned system files. A re-install can get you out of the difficulty at the expense that you don't learn anything from it.
Click to expand...
Good counsel. Will try the edit and see what happens and will post results. Thanks.

I have already learned that all devices to be installed by grub (i.e., listed as a choice during bootup) need to be in place at the time of Ubuntu installation. Somehow I had expected that during the normal boot process that Ubuntu would look for other hdd's, but that is apparently not the case.
Save
Like
O
Saikee, that was a very interesting exercise. Here is what I got:

to the geometry commands:
drive 0x80: ....more...(prob not relevant)
Partition number: 2 Filesystem type is fat, partition type 0xc
Partition number: 4 Filesystem type is fat, partition type 0xb
Partition number: 5 Filesystem type is ext2fs, partition type 0x83
Click to expand...
to the find command:
Selected disk does not exist
Click to expand...
to the config command:
(hd0,5) [not surprising, given the results of the geometry command]

One thing that caught my eye was the fs type for part. 4. This must be a logical partition and should it be fat, given that part 5 is ext2fs, and would not ext3 be a better choice for the linux partition (or is ext2fs the way ext3 is represented)?

Anyway the second drive is not being recognized, so I now need to get under the hood while booted up in the older drive. I'm at it!
See less See more
Save
Like
O
That throws me. Why would bios not see the second drive?
Save
Like
O
The old hdd is on the master connector of ide1, with nothing on the slave connector

The new hdd is on the master connector of ide2, and there is a dvdrw on the slave connector

Both hdd's are set to cable select

The cable connectors have the little raised bit in the middle that fits into a "slot" on the drive, so it would take some real effort to plug it in upside down.

I had already double checked the power connectors of all (and the one for the old hdd obviously worked as the computer booted from it), but I will triple check the new hdd when I get to the office)
Save
Like
O
I have attempted to be very careful to differentiate between master cable connectors and slave cable connectors. Hope I haven't caused any confusion. As I understand it, this is the way that "cable select" works, i.e., that the built in controls detect whether it is the end (master) connector or the interior (slave).

I was not aware that this only works if both devices are set to cable select. I would have assumed that if one was set to cable select, it would normally determine which connector it was attached to, while the other could be set to either master or slave, and assuming it was on the appropriate connector, that both devices would work correctly.

The electrical is squarely in place on the second (new) hdd, so I am baffled as to why grub isn't picking it up.
Save
Like
O
Further to the above, I am thinking that if grub takes a handoff of hardware info from bios during the boot process, that probably only applies to situations where the "install" has already occured with the hardware in place (or text files appropriately modified). In other words, grub will know when something that it is looking for is not fed to it by the bios, but can't assimilate new hardware info from bios. In this case the new drive having been installed as hda, is not passing info that grub can use. Does this sound reasonable?

Getting under the hood:

here is output from fdisk -l in the old hdd (Ubuntu 5.04):

Device Boot Start End Blocks Id System
/dev/hda1 1028 3067 16386300 f W95 Ext'd (LBA)
/dev/hda3 * 8 1027 8193150 c W95 FAT32 (LBA)
/dev/hda5 2048 3067 8193118+ b W95 FAT32
/dev/hda6 1028 2047 8193087 83 Linux
Click to expand...
here is (operational) output from sudo dmesg | grep hd* on old hdd (U 5.04):

title Ubuntu, kernel 2.6.10-6-386
root (hd0,5)
kernel /boot/vmlinuz-2.6.10-6-386 root=/dev/hda6 ro quiet splash
initrd /boot/initrd.img-2.6.10-6-386
savedefault
boot

title Ubuntu, kernel 2.6.10-6-386 (recovery mode)
root (hd0,5)
kernel /boot/vmlinuz-2.6.10-6-386 root=/dev/hda6 ro single
initrd /boot/initrd.img-2.6.10-6-386
savedefault
boot

title Ubuntu, kernel 2.6.10-5-386
root (hd0,5)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hda6 ro quiet splash
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

title Ubuntu, kernel 2.6.10-5-386 (recovery mode)
root (hd0,5)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hda6 ro single
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

title Ubuntu, kernel memtest86+
root (hd0,5)
kernel /boot/memtest86+.bin
savedefault
boot
Click to expand...
Note that items 1 & 2 above refer to:
title Ubuntu, kernel 2.6.10-6-386
Click to expand...
and the only difference between those two and the next two are
title Ubuntu, kernel 2.6.10-5-386
Click to expand...
What is the significance of the 2.5.10-6-386 and 2.5.10-5-386?

Now need to shutdown, remove old hdd, then reboot with new hdd to get like info for new drive. Will post this shortly.
See less See more
Save
Like
O
Apologies. Just realized that the second quote above is not from
sudo dmesg | grep hd* , but rather text from menu.lst

Will post again with the dmesg info for old drive shortly.

Here is info from new drive:

Disk /dev/hda: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 1 1217 9775521 83 Linux
/dev/hda2 1218 1340 987997+ 82 Linux swap / Solaris
/dev/hda3 1341 18362 136729215 83 Linux
/dev/hda4 18363 19929 12586927+ 83 Linux
Click to expand...
and from sudo dmesg | grep hd* : (sorry that it is so lengthy, but unsure what I could cut out without compromising essential info)

[17179569.184000] BIOS-provided physical RAM map:
[17179569.184000] DMA zone: 4096 pages, LIFO batch:0
[17179569.184000] Normal zone: 126960 pages, LIFO batch:31
[17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
[17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
[17179569.184000] Kernel command line: root=/dev/hda1 ro quiet splash
[17179569.184000] PID hash table entries: 2048 (order: 11, 8192 bytes)
[17179569.184000] Using pmtmr for high-res timesource
[17179570.252000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[17179570.252000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[17179570.268000] Memory: 510056k/524224k available (1910k kernel code, 13596k reserved, 1069k data, 308k init, 0k highmem)
[17179570.268000] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[17179570.348000] Mount-cache hash table entries: 512
[17179570.348000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[17179570.348000] CPU: L2 Cache: 512K (64 bytes/line)
[17179570.348000] Checking 'hlt' instruction... OK.
[17179570.364000] SMP alternatives: switching to UP code
[17179570.364000] checking if image is initramfs... it is
[17179571.044000] CPU0: AMD Athlon(tm) stepping 00
[17179571.188000] Brought up 1 CPUs
[17179571.220000] PCI: Probing PCI hardware (bus 00)
[17179571.372000] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
[17179571.420000] pnp: 00:00: ioport range 0x4080-0x40ff has been reserved
[17179571.420000] pnp: 00:00: ioport range 0x4400-0x447f has been reserved
[17179571.420000] pnp: 00:00: ioport range 0x4200-0x427f has been reserved
[17179571.420000] pnp: 00:00: ioport range 0x4280-0x42ff has been reserved
[17179571.420000] pnp: 00:01: ioport range 0x5000-0x503f has been reserved
[17179571.420000] pnp: 00:01: ioport range 0x5100-0x513f has been reserved
[17179571.460000] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[17179571.460000] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[17179571.460000] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[17179571.460000] TCP: Hash tables configured (established 16384 bind 8192)
[17179571.460000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[17179571.460000] Initializing Cryptographic API
[17179571.460000] io scheduler noop registered
[17179571.460000] io scheduler anticipatory registered
[17179571.460000] io scheduler deadline registered
[17179571.460000] io scheduler cfq registered (default)
[17179571.844000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
[17179571.848000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[17179571.848000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[17179571.852000] Using IPI No-Shortcut mode
[17179573.488000] ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [APSI] -> GSI 22 (level, high) -> IRQ 177
[17179573.896000] NFORCE2-U400R: chipset revision 163
[17179573.896000] ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
[17179573.896000] ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
[17179574.184000] hda: Maxtor 6Y160P0, ATA DISK drive
[17179575.876000] hdd: _NEC DVD_RW ND-3550A, ATAPI CD/DVD-ROM drive
[17179575.944000] hda: max request size: 512KiB
[17179575.952000] hda: 320173056 sectors (163928 MB) w/7936KiB Cache, CHS=19929/255/63, UDMA(133)
[17179575.952000] hda: cache flushes supported
[17179575.952000] hda: hda1 hda2 hda3 hda4
[17179575.984000] hdd: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
[17179576.380000] usbcore: registered new driver hub
[17179576.380000] ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
[17179576.380000] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 21 (level, high) -> IRQ 185
[17179576.380000] ohci_hcd 0000:00:02.0: OHCI Host Controller
[17179576.380000] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
[17179576.420000] ohci_hcd 0000:00:02.0: irq 185, io mem 0xec103000
[17179576.476000] usb usb1: configuration #1 chosen from 1 choice
[17179576.476000] hub 1-0:1.0: USB hub found
[17179576.476000] hub 1-0:1.0: 4 ports detected
[17179576.580000] ACPI: PCI Interrupt 0000:00:02.1 -> Link [APCG] -> GSI 20 (level, high) -> IRQ 193
[17179576.580000] ohci_hcd 0000:00:02.1: OHCI Host Controller
[17179576.580000] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
[17179576.608000] ohci_hcd 0000:00:02.1: irq 193, io mem 0xec104000
[17179576.664000] usb usb2: configuration #1 chosen from 1 choice
[17179576.664000] hub 2-0:1.0: USB hub found
[17179576.664000] hub 2-0:1.0: 4 ports detected
[17179576.768000] ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 21 (level, high) -> IRQ 185
[17179576.768000] ehci_hcd 0000:00:02.2: EHCI Host Controller
[17179576.768000] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
[17179576.768000] ehci_hcd 0000:00:02.2: debug port 1
[17179576.768000] PCI: cache line size of 64 is not supported by device 0000:00:02.2
[17179576.768000] ehci_hcd 0000:00:02.2: irq 185, io mem 0xec105000
[17179576.768000] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[17179576.768000] usb usb3: configuration #1 chosen from 1 choice
[17179576.768000] hub 3-0:1.0: USB hub found
[17179576.768000] hub 3-0:1.0: 8 ports detected
[17179576.920000] EXT3-fs: mounted filesystem with ordered data mode.
[17179577.324000] usb 3-1: new high speed USB device using ehci_hcd and address 2
[17179577.868000] usb 3-1: new high speed USB device using ehci_hcd and address 3
[17179578.412000] usb 3-1: new high speed USB device using ehci_hcd and address 4
[17179578.932000] usb 3-1: new high speed USB device using ehci_hcd and address 5
[17179579.524000] ohci_hcd 0000:00:02.0: wakeup
[17179579.908000] usb 1-2: new full speed USB device using ohci_hcd and address 3
[17179580.132000] usb 1-2: configuration #1 chosen from 1 choice
[17179584.944000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[17179584.948000] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[17179585.564000] agpgart: Detected NVIDIA nForce2 chipset
[17179586.320000] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 20 (level, high) -> IRQ 193
[17179586.528000] 8139too Fast Ethernet driver 0.9.27
[17179586.640000] eth0: RealTek RTL8139 at 0xe08a6000, 00:50:70:d6:7c:1c, IRQ 201
[17179586.640000] eth0: Identified 8139 chip type 'RTL-8101'
[17179586.660000] 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
[17179586.932000] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[17179587.220000] ts: Compaq touchscreen protocol output
[17179587.712000] EXT3 FS on hda1, internal journal
[17179588.768000] EXT3 FS on hda3, internal journal
[17179588.768000] EXT3-fs: mounted filesystem with ordered data mode.
[17179599.328000] eth0: no IPv6 routers present
[17179603.828000] Bluetooth: Core ver 2.8
[17179603.828000] Bluetooth: HCI device and connection manager initialized
[17179603.828000] Bluetooth: HCI socket layer initialized
[17179603.852000] Bluetooth: L2CAP ver 2.8
[17179603.852000] Bluetooth: L2CAP socket layer initialized
[17179603.880000] Bluetooth: RFCOMM socket layer initialized
[17179603.880000] Bluetooth: RFCOMM TTY layer initialized
[17179603.880000] Bluetooth: RFCOMM ver 1.7
Click to expand...


and finally, from menu.lst:
title Ubuntu, kernel 2.6.17-10-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/hda1 ro quiet splash
initrd /boot/initrd.img-2.6.17-10-generic
quiet
savedefault
boot

title Ubuntu, kernel 2.6.17-10-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.17-10-generic
boot

title Ubuntu, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
quiet
boot
Click to expand...
I take it I should change (hd0,0) to (hd1,0) in all instances above? (Not doing this yet, just looking for reassurance/guidance)

OK, now back to old drive
See less See more
Save
Like
O
And back to the old drive, here is dmesg:

DMA zone: 4096 pages, LIFO batch:1
Normal zone: 126960 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
Kernel command line: root=/dev/hda6 ro quiet splash
PID hash table entries: 2048 (order: 11, 32768 bytes)
Using pmtmr for high-res timesource
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 511772k/524224k available (1437k kernel code, 11860k reserved, 753k data, 224k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: AMD Athlon(tm) stepping 00
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
PCI: Probing PCI hardware (bus 00)
** PCI interrupts are no longer routed automatically. If this
** causes a device to stop working, it is probably because the
** workaround, the "pci=routeirq" argument restores the old
** behavior. If this argument makes the device work again,
** please email the output of "lspci" to [email protected]
** so I can fix the driver.
pnp: 00:00: ioport range 0x4080-0x40ff has been reserved
pnp: 00:00: ioport range 0x4400-0x447f has been reserved
pnp: 00:00: ioport range 0x4200-0x427f has been reserved
pnp: 00:00: ioport range 0x4280-0x42ff has been reserved
pnp: 00:01: ioport range 0x5000-0x503f has been reserved
pnp: 00:01: ioport range 0x5100-0x513f has been reserved
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch ([email protected])
Initializing Cryptographic API
Serial: 8250/16550 driver $Revision: 1.90 $ 54 ports, IRQ sharing enabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2-U400R: chipset revision 163
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 6Y080P0, ATA DISK drive
elevator: using anticipatory as default io scheduler
hda: max request size: 128KiB
hda: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63, UDMA(133)
hda: cache flushes supported
/dev/ide/host0/bus0/target0/lun0: p1 < p5 p6 > p3
hdd: _NEC DVD_RW ND-3550A, ATAPI CD/DVD-ROM drive
EXT3-fs: mounted filesystem with ordered data mode.
EXT3 FS on hda6, internal journal
hdd: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache
ts: Compaq touchscreen protocol output
device-mapper: 4.3.0-ioctl (2004-09-30) initialised: [email protected]
agpgart: Detected NVIDIA nForce2 chipset
usbcore: registered new driver hub
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 21 (level, high) -> IRQ 21
ohci_hcd 0000:00:02.0: PCI device 10de:0087 (nVidia Corporation)
ohci_hcd 0000:00:02.0: irq 21, pci mem 0xec103000
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
ACPI: PCI interrupt 0000:00:02.1 -> GSI 20 (level, high) -> IRQ 20
ohci_hcd 0000:00:02.1: PCI device 10de:0087 (nVidia Corporation)
ohci_hcd 0000:00:02.1: irq 20, pci mem 0xec104000
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
usb 1-1: new full speed USB device using ohci_hcd and address 2
ACPI: PCI interrupt 0000:00:02.2[C] -> GSI 21 (level, high) -> IRQ 21
ehci_hcd 0000:00:02.2: PCI device 10de:0088 (nVidia Corporation)
ehci_hcd 0000:00:02.2: irq 21, pci mem 0xec105000
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: USB 2.0 initialized, EHCI 1.00, driver 26 Oct 2004
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 8 ports detected
usb 3-1: new high speed USB device using ehci_hcd and address 2
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 20 (level, high) -> IRQ 20
usb 3-1: new high speed USB device using ehci_hcd and address 3
cpci_hotplug: CompactPCI Hot Plug Core version: 0.2
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pciehp: add_host_bridge: status 5
pciehp: Fails to gain control of native hot-plug
ohci_hcd 0000:00:02.0: wakeup
usb 1-2: new full speed USB device using ohci_hcd and address 3
ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 22 (level, high) -> IRQ 22
ata1: no device found (phy stat 00000000)
ata2: no device found (phy stat 00000000)
pciehp: add_host_bridge: status 5
pciehp: Fails to gain control of native hot-plug
8139too Fast Ethernet driver 0.9.27
eth0: RealTek RTL8139 at 0xd000, 00:50:70:d6:7c:1c, IRQ 17
eth0: Identified 8139 chip type 'RTL-8101'
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: no IPv6 routers present
Click to expand...


Whoooops, completely forgot about fstab. Here is:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda6 / ext3 defaults,errors=remount-ro 0 1
/dev/hdc /media/cdrom0 udf,iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
Click to expand...
I surmise that fstab in new drive will need editing to change hda to hdb wherever it appears?

Thnaks for wading through all of the above and for any further guidance.
Save
Like
O
Will only get to that office late this afternoon, but will try to sort out the ide jumpers correctly and advise back. Thanks.
Save
Like
O
You were right yet again. Here is fdisk:

Disk /dev/hda: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 1028 3067 16386300 f W95 Ext'd (LBA)
/dev/hda3 * 8 1027 8193150 c W95 FAT32 (LBA)
/dev/hda5 2048 3067 8193118+ b W95 FAT32
/dev/hda6 1028 2047 8193087 83 Linux

Partition table entries are not in disk order

Disk /dev/hdb: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 1 1217 9775521 83 Linux
/dev/hdb2 1218 1340 987997+ 82 Linux swap / Solaris
/dev/hdb3 1341 18362 136729215 83 Linux
/dev/hdb4 18363 19929 12586927+ 83 Linux
Click to expand...
dmesg:

ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
Kernel command line: root=/dev/hda6 ro quiet splash
PID hash table entries: 2048 (order: 11, 32768 bytes)
Using pmtmr for high-res timesource
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 511772k/524224k available (1437k kernel code, 11860k reserved, 753k data, 224k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: AMD Athlon(tm) stepping 00
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
PCI: Probing PCI hardware (bus 00)
** PCI interrupts are no longer routed automatically. If this
** causes a device to stop working, it is probably because the
** workaround, the "pci=routeirq" argument restores the old
** behavior. If this argument makes the device work again,
** please email the output of "lspci" to [email protected]
** so I can fix the driver.
pnp: 00:00: ioport range 0x4080-0x40ff has been reserved
pnp: 00:00: ioport range 0x4400-0x447f has been reserved
pnp: 00:00: ioport range 0x4200-0x427f has been reserved
pnp: 00:00: ioport range 0x4280-0x42ff has been reserved
pnp: 00:01: ioport range 0x5000-0x503f has been reserved
pnp: 00:01: ioport range 0x5100-0x513f has been reserved
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch ([email protected])
Initializing Cryptographic API
Serial: 8250/16550 driver $Revision: 1.90 $ 54 ports, IRQ sharing enabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2-U400R: chipset revision 163
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 6Y080P0, ATA DISK drive
hdb: Maxtor 6Y160P0, ATA DISK drive
elevator: using anticipatory as default io scheduler
hda: max request size: 128KiB
hda: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63, UDMA(133)
hda: cache flushes supported
/dev/ide/host0/bus0/target0/lun0: p1 < p5 p6 > p3
hdb: max request size: 1024KiB
hdb: 320173056 sectors (163928 MB) w/7936KiB Cache, CHS=19929/255/63, UDMA(133)
hdb: cache flushes supported
/dev/ide/host0/bus0/target1/lun0: p1 p2 p3 p4
hdc: _NEC DVD_RW ND-3550A, ATAPI CD/DVD-ROM drive
EXT3-fs: mounted filesystem with ordered data mode.
EXT3 FS on hda6, internal journal
hdc: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache
ts: Compaq touchscreen protocol output
device-mapper: 4.3.0-ioctl (2004-09-30) initialised: [email protected]
agpgart: Detected NVIDIA nForce2 chipset
usbcore: registered new driver hub
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 21 (level, high) -> IRQ 21
ohci_hcd 0000:00:02.0: PCI device 10de:0087 (nVidia Corporation)
ohci_hcd 0000:00:02.0: irq 21, pci mem 0xec103000
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
ACPI: PCI interrupt 0000:00:02.1 -> GSI 20 (level, high) -> IRQ 20
ohci_hcd 0000:00:02.1: PCI device 10de:0087 (nVidia Corporation)
ohci_hcd 0000:00:02.1: irq 20, pci mem 0xec104000
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
usb 1-1: new full speed USB device using ohci_hcd and address 2
ACPI: PCI interrupt 0000:00:02.2[C] -> GSI 21 (level, high) -> IRQ 21
ehci_hcd 0000:00:02.2: PCI device 10de:0088 (nVidia Corporation)
ehci_hcd 0000:00:02.2: irq 21, pci mem 0xec105000
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: USB 2.0 initialized, EHCI 1.00, driver 26 Oct 2004
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 8 ports detected
usb 3-1: new high speed USB device using ehci_hcd and address 2
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 20 (level, high) -> IRQ 20
usb 3-1: new high speed USB device using ehci_hcd and address 3
cpci_hotplug: CompactPCI Hot Plug Core version: 0.2
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pciehp: add_host_bridge: status 5
pciehp: Fails to gain control of native hot-plug
ohci_hcd 0000:00:02.0: wakeup
ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 22 (level, high) -> IRQ 22
usb 1-2: new full speed USB device using ohci_hcd and address 4
ata1: no device found (phy stat 00000000)
ata2: no device found (phy stat 00000000)
pciehp: add_host_bridge: status 5
pciehp: Fails to gain control of native hot-plug
8139too Fast Ethernet driver 0.9.27
eth0: RealTek RTL8139 at 0xd000, 00:50:70:d6:7c:1c, IRQ 17
eth0: Identified 8139 chip type 'RTL-8101'
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: no IPv6 routers present
Click to expand...


and fstab:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda6 / ext3 defaults,errors=remount-ro 0 1
/dev/hdc /media/cdrom0 udf,iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
Click to expand...
I have just noticed that there is no /swap partition on the old drive, and

why is hda6 causing an error=remount-ro message? Does:
Partition table entries are not in disk order
Click to expand...
from fdisk have anything to do with this?

At this point, I am thoroughly confused, :confused: but think that fsab will need one or more lines to point to /dev/hdb1 to allow it to be included in the grub screen and possibly hdb3 which is the large partition provided for my /home? I believe all mount points are already set up.
See less See more
Save
Like
O
geometry:

hda:
Partition number: 2 Filesystem type is fat, partition type 0xc
Partition number: 4 Filesystem type is fat, partition type 0xb
Partition number: 5 Filesystem type is ext2fs, partition type 0x83

and
hdb:
Partition number: 0 Filesystem type is ext2fs, partition type 0x83
Partition number: 1 Filesystem type is unknown, partition type 0x82
Partition number: 2 Filesystem type is ext2fs, partition type 0x83
Partition number: 3 Filesystem type is unknown, partition type 0x83
Click to expand...
booting from hda

Partition hdb1 is / on this drive

Not sure how to get fstab from hdb without reconnecting drives and booting from hdb, If I can get there via the shell, will need your guidance. Or can disconnect and boot from hdb as you suggest.

(For what it might be worth, my post yesterday at 11:32 has output from this drive for dmesg and menu.lst. Don't know if any info in these will give you what you might otherwise seek from the fstab? Please keep in mind that in that post it shows as hda since I booted from it, but it is now hdb since it booted from the old drive)
Save
Like
O
from my previous post:

booting from hda
Click to expand...
I don't know why you say "partition hdb1 is / on this drive" as your fstab does not indicate any of the partition from hdb would be mounted.
Click to expand...
I was just giving information. When I formatted this drive (which we are now seeing as hdb), I set the first partition as "/", the second as /swap and the third as /home.

The "missing" fstab is at:

/mnt/hdb1/etc/fstab

Here is fstab from that location:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda1
UUID=f8456a64-1ceb-4a82-9631-fd825e7c5d86 / ext3 defaults,errors=remount-ro 0 1
# /dev/hda3
UUID=5f298ac6-32e7-4d4f-8bf5-a87c81af39b0 /home ext3 defaults 0 2
# /dev/hda4
UUID=45AA-D8FB /media/hda4 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/hda2
UUID=e781d5c4-d2a9-4b57-84de-915a7ed0ee17 none swap sw 0 0
/dev/hdd /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/hdc /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/ /media/floppy0 auto rw,user,noauto 0 0
Click to expand...
Here is /mnt/hdb1/boot/grub/menu.lst:

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=f8456a64-1ceb-4a82-9631-fd825e7c5d86 ro
# kopt_2_6=root=/dev/hda1 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## ## End Default Options ##

title Ubuntu, kernel 2.6.17-10-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/hda1 ro quiet splash
initrd /boot/initrd.img-2.6.17-10-generic
quiet
savedefault
boot

title Ubuntu, kernel 2.6.17-10-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.17-10-generic
boot

title Ubuntu, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
quiet
boot

### END DEBIAN AUTOMAGIC KERNELS LIST
Click to expand...
and /boot/grub/menu.lst:

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default optons below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda6 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,5)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## nonaltoption boot targets option
## This option controls options to pass to only the
## primary kernel menu item.
## You can have ONLY one nonaltoptions line
# nonaltoptions=quiet splash

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## ## End Default Options ##

title Ubuntu, kernel 2.6.10-6-386
root (hd0,5)
kernel /boot/vmlinuz-2.6.10-6-386 root=/dev/hda6 ro quiet splash
initrd /boot/initrd.img-2.6.10-6-386
savedefault
boot

title Ubuntu, kernel 2.6.10-6-386 (recovery mode)
root (hd0,5)
kernel /boot/vmlinuz-2.6.10-6-386 root=/dev/hda6 ro single
initrd /boot/initrd.img-2.6.10-6-386
savedefault
boot

title Ubuntu, kernel 2.6.10-5-386
root (hd0,5)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hda6 ro quiet splash
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

title Ubuntu, kernel 2.6.10-5-386 (recovery mode)
root (hd0,5)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/hda6 ro single
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot

title Ubuntu, kernel memtest86+
root (hd0,5)
kernel /boot/memtest86+.bin
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda3
title Microsoft Windows XP Professional
root (hd0,2)
savedefault
makeactive
chainloader +1
Click to expand...
I stopped back at the office en route to a business meeting to post this and will stop again on the way back to reboot the second system and answer questions/post results as you might need. I can delete the remarks to shorten the posts if you do not need them-pls advise.

Many thanks.
See less See more
Save
Like
O
When I boot from the second system, what info can I obtain that will be helpful?
Save
Like
O
a panic
Click to expand...
Sounds exciting indeed! In the event that I encounter a situation that appears to be a panic, what is the recovery procedure please?
Save
Like
O
As I begin to implement your guidance, I see some questions:

The red bits are the actual alterations required.
Click to expand...
In the post above, the red bits show only as

/dev/hdb1 /
Click to expand...
in the entire line of:
/dev/hdb1 / ext3 defaults,errors=remount-ro 0 1
Click to expand...
Since the second part of that line does not appear in the existing file text, I expect that the entire line should be added, and the same is true of all four lines that begin with red text. Please confirm.

The current text in the fstab file is:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda1
UUID=f8456a64-1ceb-4a82-9631-fd825e7c5d86 / ext3 defaults,errors=remount-ro 0 1
# /dev/hda3
UUID=5f298ac6-32e7-4d4f-8bf5-a87c81af39b0 /home ext3 defaults 0 2
# /dev/hda4
UUID=45AA-D8FB /media/hda4 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/hda2
UUID=e781d5c4-d2a9-4b57-84de-915a7ed0ee17 none swap sw 0 0
/dev/hdd /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/hdc /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/ /media/floppy0 auto rw,user,noauto 0 0
Click to expand...
So my question is, assuming that I should add the lines:
/dev/hdb1 / ext3 defaults,errors=remount-ro 0 1

/dev/hdb3 /home ext3 defaults 0 2

/devhdb4 /media/hda4 vfat defaults,utf8,umask=007,gid=46 0 1

/dev/hdb2 none swap sw 0 0
Click to expand...
in their entirety, does it matter whether they are added at the end of the file or do they need to go above the line?:
/dev/hdd /media/cdrom0 udf,iso9660 user,noauto 0 0
Click to expand...
Secondly, by:
manually boot up the Ubuntu in hdb
Click to expand...
do you mean that I should shut down and manually change the cable config, or that I should use the manual technique of entering "C" while grub is showing, as you instructed above?

Finally,
If things work out the lines you manually boot up the Ubuntu in hdb are the commands needed to be put inside the /boot/grub/menu.lst of hda6 (in hda),
Click to expand...
My understanding is that these lines be should be added (and if placement is important, please advise where, as above) to the existing text rather than modifying any existing lines. If this is incorrect, please advise.

Thank you for your patient guidance on this. I can see light at the end of the tunnel and this certainly is the learning experience you predicted.
See less See more
Save
Like
O
All the changes made, I hope!

Now rebooting with fingers crossed.

Be back shortly. :D
Save
Like
O
Woo Hoo! It worked!

When I restarted and the grub loader came up, I noticed that my line for the hdb disk came up (It is "Ubuntu 6.10"), I just clicked on it and up it came.

I was expecting to enter "C" during grub and add those lines, but it wasn't necessary. So I went back and re-read the last few of your posts and realized that the "C" process was what you meant by manually booting from hdb? Also now understand the question about cheating, which I now realize that I did.

Now also realize that you thought by my quoting you with "a panic" that you thought I had actually encountered one. However, no I had not, but was just trying to get ready for it if it happened.

Sooooo, I went back and restarted, following your instructions and up it came up again. (Even copied down the print response to each line so that I can prove that I did it.) Hot damn!

I do realize that without your help, I would have needed a month of Sundays to figure any of this out. So hopefully some of it will stick!

I do have a new question now which I will put up here as it would take too long to start a new thread and give enough background to be understood. When one is dual booting, as in this case, and I want to use Nautilus to view a file on the other hdd, how do I do it? I reckon that the other drive must be mounted manually now?

Once that is done, will the other drive show up in Nautilus or will the system just put an icon on the desktop?

Apologies for this very basic question, but my poor head is spinning from all this and I may need a real ale before it is going to clear up.

Thanks again.
See less See more
Save
Like
O
Thank you most sincerely.
Save
Like
1 - 20 of 36 Posts
Status
Not open for further replies.
Tech Support Guy
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!
Full Forum Listing
Explore Our Forums
Hardware Virus & Other Malware Removal Off Topic Lounge Thread Games & Discussion Networking
Top