LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   mount problems with second hard disk in SuSe 9.3 (https://www.linuxquestions.org/questions/linux-newbie-8/mount-problems-with-second-hard-disk-in-suse-9-3-a-360868/)

garygoldthorpe 09-06-2005 07:31 PM
mount problems with second hard disk in SuSe 9.3
 
I'm having difficulty finding out exactly how to mount the second hard disk on my SuSE 9.3 setup. I disconnected said disk before installing SuSE because of problems I'd had with it trying to boot from the wrong disk during a previous attempt at installation. I then reconnected the disk and booted up but, although the system knows that it's there, it won't automatically mount it. It doesn't appear in the Konqueror browser at all. The YaST partition tool sees the disk, but, unlike the main boot disk, does not see any of the partitions on it (I previously had SuSE 8.2, so there should be two Linux partions - one for the swap - and a Windows partition).

XP has no problems accessing the Windows partition on the second disk at all.

I can find no obvious way of mounting the disk in YaST and, although I'm aware that you can use the 'mount' command from the shell, this has no effect unless you alter the etc/fstab file in some way.

I would be grateful if anyone could help - I'm sure there is a simple solution but I just don't know what it is - the manuals do not give detailed instructions.

What I would like to know is:

(preferably) How can I mount this disk from the GUI (KDE/YaST) and make it permanent *or*

if I have to alter the fstab file, what exactly do I put in there?

I've included some information below from the etc/fstab file and from the YaST hardware probe...

FSTAB:
/dev/sda3 / reiserfs acl,user_xattr 1 1
/dev/sda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/sda2 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/cdrecorder /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/dvdram /media/dvdram subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0


###############

HARDWARE PROBE:
UniqueID=90A1.khei0j0DnI8
ParentID=H0_h.HB0oECAalsA
HWClass=disk
Model=Maxtor 6E030L0
Configured=no
Available=yes
Needed=no
Active=unknown
Bus=0x85
Slot=0x2
BaseClass=0x106
DeviceName=6E030L0
VendorName=Maxtor
RevisionName=NAR61590
Serial=E1FV1VDE
UnixDevice=/dev/hdc
UnixDeviceList=/dev/hdc /dev/disk/by-path/pci-0000:00:06.0-ide-1:0 /dev/disk/by-id/Maxtor_6E030L0_E1FV1VDE
Drivers=AMD_IDE|ide-disk
SysfsID=/block/hdc
SysfsBusID=1.0
SysfsLink=/devices/pci0000:00/0000:00:06.0/ide1/1.0
HWClassList=00002000044001
Res.Size=3,60058656,512
Res.DiskGeometry=59582,16,63,0
Res.DiskGeometry=59582,16,63,1
Res.Cache=2048

Many thanks!

CroMagnon 09-06-2005 07:50 PM
OK, I don't know anything about YaST or SUSE, so this is all going to be common command line tools.

Login as root, and use the command "fdisk /dev/hdc". Once it loads, you should be able to hit 'p' (then enter) and that will display the partition table. Make sure your partitions are the way you expect them to be. Here's an example:
Code:
  Device Boot      Start        End      Blocks  Id  System
/dev/hda1              1          31      248976  82  Linux swap / Solaris
/dev/hda2  *          32        529    4000185  83  Linux
/dev/hda3            530        1582    8458222+  7  HPFS/NTFS
This would show that hda2 was my linux partition and hda3 was my windows partition. Use 'q' to quit fdisk, then add what you need to /etc/fstab. Edit the file and add something like this for the linux partition:
Code:
/dev/hda2        /mnt/oldsuse                    ext2  defaults  0  0
obviously, change hda2 to the partition you got from fdisk, and /mnt/oldsuse should be a directory that exists for your old drive to be mounted under. Also, ext2 should be whatever the filesystem was - check 'man mount' and 'man fstab' for more information on the available options.

mayhemt 09-06-2005 08:47 PM
1. check your
$fdisk -l
if its showing the disk.....
2. check if the filesystem on that disk is supported by ur present kernel..do a
cat /proc/filesystems to get the supported filesystems
3. if that fs is not in the list...u have to recompile the kernel with that fs on....
4. But looks like its on SCSI bus..did u enable SCSI in kernel options?
4a. Or is it USB external drive? then u have to enable USB mass storage

CroMagnon 09-06-2005 09:03 PM
I don't think his drive is SCSI, the output says there is a Maxtor drive as /dev/hdc. His primary drive is /dev/sda, which I presume is a SATA drive, while his old one is a plain ATA.

mayhemt 09-06-2005 09:09 PM
nevertheless "fdisk -l" would solve the mystery

garygoldthorpe 09-07-2005 04:41 AM
Wow! You guys work fast - I didn't expect a reply so quickly.

You're right about the hard disks - the primary is a new SATA device and the old one is an ordinary ATA IDE one. They are both Maxtor brand. At the moment, I'm unsure as to what's on the Linux partitions on the old drive because of the fact that SuSE 9.3 tried to boot from it part way through the previous (abortive) installation - so it may have replaced the old filing system from 8.2 with a new one (reiserfs, perhaps). So I'll use your advice and try to find out.

Many thanks for the information.

garygoldthorpe 09-09-2005 03:46 PM
I have tried what CroMagnon kindly suggested and managed to get some useful information from the fdisk output:

Disk /dev/hdc: 30.7 GB, 30750031872 bytes
255 heads, 63 sectors/track, 3738 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 1 2248 18057028+ c W95 FAT32 (LBA)
/dev/hdc2 2249 2310 498015 82 Linux swap / Solaris
/dev/hdc3 * 2311 3738 11470410 83 Linux

I then put the following lines at the end of the fstab file:

/dev/hdc3 /mnt/oldSuSE reiserfs defaults 0 0
/dev/hdc2 /mnt/oldswap swap defaults 0 0
/dev/hdc1 /windows/E vfat defaults 0 0

When I then tried 'mount /dev/hdc1' I got the message: '/dev/hdc1 is not a valid block device'. I tried the same with hdc3 and hdc2 with the same result. Changing the 'reiserfs' entry to 'ext2' did not help either.

So next I decided to 'delete' the Linux partitions on the old drive in order to simplify things (there was nothing important on there). I didn't know how to do this from KDE/SuSE, so I used XP. Sure enough fdisk then reported:

Device Boot Start End Blocks Id System
/dev/hdc1 1 2248 18057028+ c W95 FAT32 (LBA)

same as before, but without the other partitions.

Then I tried 'mount /dev/hdc1' again but got exactly the same error message.

I have also put the same fstab lines into the mtab file, again with no effect. Fstab now reads:

/dev/sda3 / reiserfs acl,user_xattr 1 1
/dev/sda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/sda2 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/cdrecorder /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/dvdram /media/dvdram subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0
/dev/hdc1 /windows/E vfat defaults 0 0


I'm not sure what to try next!

mayhemt 09-09-2005 06:34 PM
for the oldsuse partition..dont mention ext2 or reiserfs....let the kernel autodetect the fs
/dev/hdc3 /mnt/oldsuse auto auto,user 0 0

now the kernel tweaks: these are the checks i would hav added
is automount enabled in kernel?
is loop back devices enabled? (not valid block devide prompts me to ask this)
r u sure the FAT32 fs is clean without any bad sectors? (run scandisk in dos/windows or fsck.vfat fsck.msdos in linux)
since u dont need booting from oldsuse...get a parittion software (ranish partition manager is free one)...& check the MBR on the second disk.... (if u play MBR On 1st disk..u might not boot to grub or lilo )

CroMagnon 09-10-2005 03:00 AM
OK, the MBR is not your problem, so don't mess with that. Proof: disk works under windows, and fdisk doesn't complain. automount is irrelevant, and so is loopback support (if loopback was required for filesystems, it wouldn't be an option in the kernel in the first place).

The first thing to check would be mayhemt's earlier suggestion of checking /proc/filesystems - make sure both 'vfat' and 'msdos' are in the list. If you compiled these as modules (or if SUSE did that - check under the directory in /lib/modules that matches your kernel version), make sure the relevant modules appear in an 'lsmod'. e.g if your kernel is 2.4.2, the right directory would be /lib/modules/2.4.2/kernel/fs

If that checks out ok, perhaps post the result of 'ls -l /dev/hdc1'. It should look like this:
Code:
brw-rw----  1 root disk 22, 1 May 21  2004 /dev/hdc1
I doubt this could be damaged, but it's always possible.

Also, check the output of 'dmesg' for any errors that might give us a clue about the problem.

garygoldthorpe 09-10-2005 08:09 AM
Thanks very much for the advice so far, folks.

I have found a directory called:

lib/modules/2.6.11.4-20a-default/kernel/fs

and in there are directories called 'msdos', 'vfat' and 'ntfs' among many others. Each of these directories has a corresponding '.ko' file inside (eg. 'msdos.ko').

However, if you look at the contents of 'proc/filesystems', there is no entry for msdos...

nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev sockfs
nodev debugfs
nodev pipefs
nodev futexfs
nodev tmpfs
nodev eventpollfs
nodev devpts
ext2
nodev ramfs
nodev hugetlbfs
minix
iso9660
nodev nfs
nodev nfs4
nodev mqueue
nodev rpc_pipefs
reiserfs
nodev usbfs
ntfs
vfat
nodev subfs

seeing as the filesystem on the old drive is FAT32 (vfat?), rather than old DOS, does this matter? To change this file, is it simply a question of editing and putting in a line for msdos, or is 'filesystems' an output from another program? Even if I did this though, it wouldn't really explain why I couldn't access the Linux partitions on the old drive.

Anyway, here are the outputs from ls and dmesg...

+++++++++++++++++++++

linux:~ # ls -l /dev/hdc1
brw-rw---- 1 root disk 22, 1 Mar 19 22:01 /dev/hdc1

+++++++++++++++++++++

Bootdata ok (command line is root=/dev/sda3 vga=0x317 selinux=0 splash=silent c
onsole=tty0 resume=/dev/sda2)
Linux version 2.6.11.4-20a-default (geeko@buildhost) (gcc version 3.3.5 20050117
(prerelease) (SUSE Linux)) #1 Wed Mar 23 21:52:37 UTC 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
BIOS-e820: 00000000c0000000 - 00000000d0000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
ACPI: RSDP (v000 Nvidia ) @ 0x00000000000f6fd0
ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0x000000001fff300
0
ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0x000000001fff304
0
ACPI: MCFG (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0x000000001fff7bc
0
ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0x000000001fff7b4
0
ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x000000000000000
0
On node 0 totalpages: 131056
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 126960 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
Nvidia board detected. Ignoring ACPI timer override.
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:15 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: BIOS IRQ0 pin2 override ignored.
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ9 used by override.
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Checking aperture...
CPU 0: aperture @ 4cce000000 size 32 MB
Aperture from northbridge cpu 0 too small (32 MB)
No AGP bridge found
Built 1 zonelists
Kernel command line: root=/dev/sda3 vga=0x317 selinux=0 splash=silent console=t
ty0 resume=/dev/sda2
bootsplash: silent mode.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
time.c: Using 1.193182 MHz PIT timer.
time.c: Detected 1809.281 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Memory: 508488k/524224k available (2167k kernel code, 14972k reserved, 1158k dat
a, 168k init)
Calibrating delay loop... 3588.09 BogoMIPS (lpj=1794048)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 256 (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) 64 Processor 3000+ stepping 00
checking if image is initramfs... it is
ACPI: Looking for DSDT in initrd... not found!
not found!
Using local APIC NMI watchdog using perfctr0
Using local APIC timer interrupts.
Detected 12.564 MHz APIC timer.
NET: Registered protocol family 16
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20050211
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
PCI: Transparent bridge - 0000:00:09.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK3] (IRQs *3 4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs *3 4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LPCA] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled.
ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled.
ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0, disabled.
ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled.
ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCP] (IRQs 20 21 22 23) *0, disabled.
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
TC classifier action (bugs to netdev@oss.sgi.com cc hadi@cyberus.ca)
PCI-DMA: Disabling IOMMU.
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1126357788.336:0): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
vesafb: framebuffer at 0xd0000000, mapped to 0xffffc20000080000, using 6144k, to
tal 65536k
vesafb: mode is 1024x768x16, linelength=2048, pages=1
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
bootsplash 3.1.6-2004/03/31: looking for picture...<6> silentjpeg size 57135 byt
es,<6>...found (1024x768, 36789 bytes, v3).
Console: switching to colour frame buffer device 127x44
fb0: VESA VGA frame buffer device
Real Time Clock Driver v1.12
Non-volatile memory driver v1.2
Linux agpgart interface v0.100 (c) Dave Jones
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 128000K size 1024 blocksize
loop: loaded (max 8 devices)
mice: PS/2 mouse device common for all mice
input: PC Speaker
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP established hash table entries: 32768 (order: 6, 262144 bytes)
TCP bind hash table entries: 32768 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 32768 bind 32768)
NET: Registered protocol family 1
PM: Checking swsusp image.
PM: Resume from disk failed.
ACPI wakeup devices:
HUB0 XVR0 XVR1 XVR2 XVR3 USB0 USB2 MMAC MMCI UAR1
ACPI: (supports S0 S1 S4 S5)
Freeing unused kernel memory: 168k freed
input: AT Translated Set 2 keyboard on isa0060/serio0
SCSI subsystem initialized
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
NFORCE-CK804: chipset revision 162
NFORCE-CK804: not 100% native mode: will probe irqs later
NFORCE-CK804: 0000:00:06.0 (rev a2) UDMA133 controller
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: HL-DT-ST DVDRAM GSA-4163B, ATAPI CD/DVD-ROM drive
logips2pp: Detected unknown logitech mouse model 62
input: ImExPS/2 Logitech Explorer Mouse on isa0060/serio1
hdb: CR-4804TE, ATAPI CD/DVD-ROM drive
Losing some ticks... checking if CPU frequency changed.
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: Maxtor 6E030L0, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
libata version 1.10 loaded.
sata_nv version 0.6
ACPI: PCI Interrupt Link [APSI] enabled at IRQ 23
ACPI: PCI interrupt 0000:00:07.0[A] -> GSI 23 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:00:07.0 to 64
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xC800 irq 177
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xC808 irq 177
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4063 85:7c68 86:3e01 87:4063 88:407f
ata1: dev 0 ATA-7, max UDMA/133, 398297088 sectors: LBA48
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata1: dev 0 configured for UDMA/133
scsi0 : sata_nv
ata2: no device found (phy stat 00000000)
scsi1 : sata_nv
Vendor: ATA Model: Maxtor 6L200M0 Rev: BANC
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
SCSI device sda: drive cache: write back
sda:<4>nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
sda1 sda2 sda3
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 22
ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 22 (level, low) -> IRQ 185
PCI: Setting latency timer of device 0000:00:08.0 to 64
ata3: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xDC00 irq 185
ata4: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xDC08 irq 185
ata3: no device found (phy stat 00000000)
scsi2 : sata_nv
ata4: no device found (phy stat 00000000)
scsi3 : sata_nv
hdc: max request size: 128KiB
hdc: Host Protected Area detected.
current capacity is 60052447 sectors (30746 MB)
native capacity is 60058656 sectors (30750 MB)
hdc: Host Protected Area disabled.
hdc: 60058656 sectors (30750 MB) w/2048KiB Cache, CHS=59582/16/63, UDMA(133)
hdc: cache flushes supported
hdc:hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
ide1: reset: success
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
ide1: reset: success
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 0
Buffer I/O error on device hdc, logical block 0
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
ide1: reset: success
unable to read partition table
hda: ATAPI 63X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdb: ATAPI 24X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
Attempting manual resume
PM: Checking swsusp image.
swsusp: Suspend partition has wrong signature?
PM: Resume from disk failed.
ReiserFS: sda3: found reiserfs format "3.6" with standard journal
ReiserFS: sda3: using ordered data mode
reiserfs: using flush barriers
ReiserFS: sda3: journal params: device sda3, size 8192, journal first block 18,
max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda3: checking transaction log (sda3)
reiserfs: disabling flush barriers on sda3
ReiserFS: sda3: Using r5 hash to sort names
bootsplash: status on console 0 changed to on
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Adding 1004052k swap on /dev/sda2. Priority:42 extents:1
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
parport0: PC-style at 0x378 [PCSPP,TRISTATE]
parport0: Printer, HEWLETT-PACKARD DESKJET 930C
lp0: using parport0 (polling).
i2c_adapter i2c-0: nForce2 SMBus adapter at 0x1c00
i2c_adapter i2c-1: nForce2 SMBus adapter at 0x1c40
ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21
ACPI: PCI interrupt 0000:00:04.0[A] -> GSI 21 (level, low) -> IRQ 193
PCI: Setting latency timer of device 0000:00:04.0 to 64
intel8x0_measure_ac97_clock: measured 52588 usecs
intel8x0: clocking to 46890
ieee1394: Initialized config rom entry `ip1394'
ohci1394: $Rev: 1250 $ Ben Collins <bcollins@debian.org>
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI interrupt 0000:01:0a.0[A] -> GSI 18 (level, low) -> IRQ 201
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[201] MMIO=[f2404000-f24047ff] Ma
x Packet=[4096]
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.31.
ACPI: PCI Interrupt Link [APCH] enabled at IRQ 20
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 20 (level, low) -> IRQ 209
PCI: Setting latency timer of device 0000:00:0a.0 to 64
usbcore: registered new driver usbfs
usbcore: registered new driver hub
load_module: err 0xffffffffffffffef (dont worry)
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
eth0: forcedeth.c: subsystem: 01458:e000 bound to 0000:00:0a.0
ACPI: PCI Interrupt Link [APCF] enabled at IRQ 23
ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 23 (level, low) -> IRQ 177
ohci_hcd 0000:00:02.0: OHCI Host Controller
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: irq 177, pci mem 0xf2803000
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: 10 ports detected
ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
ACPI: PCI interrupt 0000:00:02.1[B] -> GSI 22 (level, low) -> IRQ 185
ehci_hcd 0000:00:02.1: EHCI Host Controller
PCI: Setting latency timer of device 0000:00:02.1 to 64
ehci_hcd 0000:00:02.1: irq 185, pci mem 0xf2805000
ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
PCI: cache line size of 64 is not supported by device 0000:00:02.1
ehci_hcd 0000:00:02.1: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 10 ports detected
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 217
sk98lin: Network Device Driver v8.14.3.3
(C)Copyright 1999-2005 Marvell(R).
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 217
PCI: Setting latency timer of device 0000:02:00.0 to 64
eth1: Marvell Yukon 88E8053 Gigabit Ethernet Controller
PrefPort:A RlmtMode:Check Link State
ieee1394: Host added: ID:BUS[0-00:1023] GUID[000fea56008f367d]
st: Version 20041025, fixed bufsize 32768, s/g segs 256
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
BIOS EDD facility v0.16 2004-Jun-25, 2 devices found
NTFS driver 2.1.22 [Flags: R/W MODULE].
NTFS volume version 3.1.
Capability LSM initialized
ieee1394: raw1394: /dev/raw1394 device initialized
video1394: Installed video1394 module
NET: Registered protocol family 10
Disabled Privacy Extensions on device ffffffff80405f60(lo)
IPv6 over IPv4 tunneling driver
Disabled Privacy Extensions on device ffff81001b9c5800(sit0)
ip6_tables: (C) 2000-2002 Netfilter core team
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (2047 buckets, 16376 max) - 304 bytes per conntrack
bootsplash: status on console 0 changed to on
eth0: no link during initialization.
NET: Registered protocol family 17
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
ACPI: Power Button (FF) [PWRF]
ACPI: Processor [CPU0] (supports 8 throttling states)
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.00.09e)
powernow-k8: 0 : fid 0xa (1800 MHz), vid 0x6 (1400 mV)
powernow-k8: 1 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV)
cpu_init done, current fid 0xa, vid 0x6
eth0: no IPv6 routers present
drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial_generic
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
bootsplash: status on console 0 changed to on
subfs 0.9
nvidia: unsupported module, tainting kernel.
nvidia: module license 'NVIDIA' taints kernel.
ACPI: PCI interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 201
PCI: Setting latency timer of device 0000:05:00.0 to 64
NVRM: loading NVIDIA Linux x86_64 NVIDIA Kernel Module 1.0-7664 Wed May 25 22: 14:12 PDT 2005
end_request: I/O error, dev fd0, sector 0
bootsplash: status on console 0 changed to on
linux:~ #

++++++++++++++

Many thanks again for your efforts.

CroMagnon 09-10-2005 09:10 AM
Even though vfat may seem like a new filesystem, it is really just an extension on the old fat system. Unless things have changed in recent kernels, msdos is required for vfat to work (it's always possible things have changed on me). Try 'insmod msdos' and then re-cat /proc/filesystems to see if msdos shows up.

Another worry is the abundance of errors on /dev/hdc like this:
ide: failed opcode was: unknown
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }

Normally these kinds of errors pop up on drives that are failing. You could try switching the drive to the primary IDE controller, in case the error is in the connection rather than the drive itself (this would make the device /dev/hda instead of hdc).

If the above fails to get things working, I'd advise you to boot up the Windows system and save as much important data from that drive as you can, because it might not be long before it gives up completely :(

mayhemt 09-10-2005 09:42 AM
end_request: I/O error, dev hdc, sector 0
Buffer I/O error on device hdc, logical block 0
isnt that referring to MBR???

garygoldthorpe 09-10-2005 06:43 PM
success!
 
Thanks again for your contributions.

I have swapped the cables around on the motherboard and SuSE now recognises the old drive! I can now mount it with 'mount' and 'fstab'. One problem though - I had a look at the 'dmesg' output again and this time, similar error messages crop up for the optical drives, which use the same cable as before but are now plugged into the secondary connector. So I suppose this must be a problem with the motherboard socket. Having said that, both the optical drives do mount up normally and can be used by the filing system.

Perhaps we can now put this to bed as a hardware problem then? I must say though that I don't really fancy having to send the motherboard back and wait for a new one!

Sound advice chaps, well done.

PS. I've just installed SuSE 9.2 on the spare partition on the old drive - it has no problems mounting any of the storage devices and gives no error messages for the optical drives, so maybe it was a 9.3 bug after all. I know 9.3 uses a later kernel. Curious!

garygoldthorpe 09-11-2005 03:56 PM
XP shows no problems either - hardware probe says everything working fine!

CroMagnon 09-11-2005 04:13 PM
Do you have any errors in the XP event log? I don't know what 'hardware probe' is, but XP is really good at 'painting over' some hardware problems.

It's possible the IDE cable was just not seated properly at one end or the other, or that there is a problem with the secondary controller that doesn't manifest itself when dealing with lower size drives (like a CD or DVD drive). It's also possible (but I think unlikely) that the kernel on the newer system doesn't include a required patch for your IDE chipset. You could try grabbing the kernel source and compiling your own to see if you can track it down to a software fault.


All times are GMT -5. The time now is 12:28 PM.