[opensuse] Re: Large disks in Opensuse 11
Per Inge Oestmoen a écrit :
jdd wrote:
Why will not opensuse 11 read it and let me format it? Or do I do something wrong in Yast?
probably. Your drive seems to be /dev/sda what gives "fdisk /dev/sda" (with the disk plugged in :-) option "p" to see the partitions. this is harm free as long as you don't save "typing w". Quit with option "q" or Control C is safe jdd -- http://www.dodin.net http://valerie.dodin.org http://news.opensuse.org/2009/04/13/people-of-opensuse-jean-daniel-dodin/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
jdd wrote:
Per Inge Oestmoen a écrit :
Why will not opensuse 11 read it and let me format it? Or do I do something wrong in Yast?
probably.
And hopefully, as well.
Your drive seems to be /dev/sda
sdc.
what gives "fdisk /dev/sda" (with the disk plugged in :-)
This: ---- linux-k9na:/home/siberia # fdisk /dev/sdc Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel with disk identifier 0x5a02840f. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. The number of cylinders for this disk is set to 267349. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) ---- Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Inge Oestmoen wrote:
sdc.
what gives "fdisk /dev/sda" (with the disk plugged in :-)
This:
---- linux-k9na:/home/siberia # fdisk /dev/sdc Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Assuming you know the disk is empty, you now continue with creating a partition - for instance just one primary taking up the whole disk. Then you create a filesystem on it. Next you time you unplug/plug the drives, openSUSE will ask if you want to mount it automagically. /also Per -- Per Jessen, Zürich (10.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Per Inge Oestmoen wrote:
what gives "fdisk /dev/sda" (with the disk plugged in :-) This: linux-k9na:/home/siberia # fdisk /dev/sdc Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Assuming you know the disk is empty, you now continue with creating a partition - for instance just one primary taking up the whole disk. Then you create a filesystem on it. Next you time you unplug/plug the drives, openSUSE will ask if you want to mount it automagically.
But that is precisely what is impossible. I go into the partitioner of YaST, and the disk is recognized. I choose to make one large partion, and to format with FAT since the disk is to be accessed by a number of different operating systems apart from my own Linux machines. Then I get this following error message: http://www.coldsiberia.net/text/partition_failure.jpg I then choose OK, and go back to the main YaST screen, where YaST claims that my disk is 2 Tb instead of 1 Tb which is the real size. I can go no further. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Inge Oestmoen wrote:
Per Jessen wrote:
Per Inge Oestmoen wrote:
what gives "fdisk /dev/sda" (with the disk plugged in :-) This: linux-k9na:/home/siberia # fdisk /dev/sdc Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Assuming you know the disk is empty, you now continue with creating a partition - for instance just one primary taking up the whole disk. Then you create a filesystem on it. Next you time you unplug/plug the drives, openSUSE will ask if you want to mount it automagically.
But that is precisely what is impossible.
I go into the partitioner of YaST, and the disk is recognized. I choose to make one large partion, and to format with FAT since the disk is to be accessed by a number of different operating systems apart from my own Linux machines.
Then I get this following error message:
Which says something about a problem and error -1013 when trying to set the disk label to MSDOS. Like others have suggested, a 1Tb FAT filesystem is probably not a good idea, but it might work, I don't know.
I then choose OK, and go back to the main YaST screen, where YaST claims that my disk is 2 Tb instead of 1 Tb which is the real size. I can go no further.
Next step is to 1) report the problem (bugzilla.novell.com) and 2) create the filesystem manually. Assuming your drive is still /dev/sdc: fdisk /dev/sdc delete all existing partitions. create new primary, use all the space. toggle partition type to 'b' = W95 FAT32. (I'm not sure about 'b'). w(rite) new partition table mkfs -t vfat /dev/sdc1 mount /dev/sdc1 /mnt /Per -- Per Jessen, Zürich (17.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Next step is to 1) report the problem (bugzilla.novell.com) and 2) create the filesystem manually.
Assuming your drive is still /dev/sdc:
fdisk /dev/sdc delete all existing partitions. create new primary, use all the space. toggle partition type to 'b' = W95 FAT32. (I'm not sure about 'b'). w(rite) new partition table
mkfs -t vfat /dev/sdc1
mount /dev/sdc1 /mnt
The command fdisk /dev/sdc resulted in the disk becoming inaccessible, and I had to turn it off and on again. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Inge Oestmoen wrote:
The command fdisk /dev/sdc resulted in the disk becoming inaccessible,
Then I think you've got a hardware problem. What exactly did fdisk say? Which errors? Did it just hang? How do you know that the disk became inaccessible? /Per -- Per Jessen, Zürich (19.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Per Inge Oestmoen wrote:
The command fdisk /dev/sdc resulted in the disk becoming inaccessible,
Then I think you've got a hardware problem. What exactly did fdisk say? Which errors? Did it just hang? How do you know that the disk became inaccessible?
I got this: ---- linux-k9na:/home/siberia # fdisk /dev/sdc Unable to open /dev/sdc ---- And then: ---- linux-k9na:/home/siberia # cat /proc/partitions major minor #blocks name 8 0 117220824 sda 8 1 8225248 sda1 8 2 5566522 sda2 8 3 12289725 sda3 8 4 91136745 sda4 8 16 312571224 sdb 8 17 2104483 sdb1 8 18 20972857 sdb2 8 19 289491300 sdb3 ---- The disk just disappeared. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Inge Oestmoen wrote:
Per Jessen wrote:
Per Inge Oestmoen wrote:
The command fdisk /dev/sdc resulted in the disk becoming inaccessible,
Then I think you've got a hardware problem. What exactly did fdisk say? Which errors? Did it just hang? How do you know that the disk became inaccessible?
I got this:
---- linux-k9na:/home/siberia # fdisk /dev/sdc
Unable to open /dev/sdc ----
It would have been nice to see the output from dmesg right after this, but if fdisk cannot access the disk, you have a hardware problem. /Per -- Per Jessen, Zürich (20.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Per Inge Oestmoen wrote:
Which errors? Did it just hang? How do you know that the disk became inaccessible?
I got this:
---- linux-k9na:/home/siberia # fdisk /dev/sdc
Unable to open /dev/sdc ----
It would have been nice to see the output from dmesg right after this, but if fdisk cannot access the disk, you have a hardware problem.
Here is the most recent dmesg: http://www.coldsiberia.net/text/dmesg_07052009.txt Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, May 7, 2009 at 8:43 AM, Per Inge Oestmoen <pioe@coldsiberia.org> wrote:
Per Jessen wrote:
Per Inge Oestmoen wrote:
Which errors? Did it just hang? How do you know that the disk became inaccessible?
I got this:
---- linux-k9na:/home/siberia # fdisk /dev/sdc
Unable to open /dev/sdc ----
It would have been nice to see the output from dmesg right after this, but if fdisk cannot access the disk, you have a hardware problem.
Here is the most recent dmesg:
Every time you reboot the dmesg data is reset to null. Your link appears to be to a dmesg shortly after booting up. It contains nothing relevant to your issue. Also, dmesg only reports a limited amount of data going back a limited amount of time. In general you want to trigger the fault, then immediately capture the dmesg. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Inge Oestmoen wrote:
Per Jessen wrote:
Per Inge Oestmoen wrote:
Which errors? Did it just hang? How do you know that the disk became inaccessible?
I got this:
---- linux-k9na:/home/siberia # fdisk /dev/sdc
Unable to open /dev/sdc ----
It would have been nice to see the output from dmesg right after this, but if fdisk cannot access the disk, you have a hardware problem.
Here is the most recent dmesg:
This one doesn't seems to show the USB device being connected/discovered at all - there's certainly no mention of a disk drive with SCSI emulation etc. Can I suggest the following: disconnect USB drive reboot system connect USB drive, do a dmesg and post the output on coldsiberia try 'fdisk /dev/sdX' where X is the driver letter assigned as per dmesg output. Assuming this fails, do a dmesg and post the output on coldsiberia, but separately. (if it doesn't fail, you have some sort of intermittent problem, again indicative of a hardware issue). /Per -- Per Jessen, Zürich (23.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Can I suggest the following:
disconnect USB drive reboot system connect USB drive, do a dmesg and post the output on coldsiberia try 'fdisk /dev/sdX' where X is the driver letter assigned as per dmesg output. Assuming this fails, do a dmesg and post the output on coldsiberia, but separately. (if it doesn't fail, you have some sort of intermittent problem, again indicative of a hardware issue).
First one dmesg after attaching the drive, this is a new one just made now: http://www.coldsiberia.net/text/dmesg_07052009.txt Thereafter i tried fdisk: ---- linux-k9na:/home/siberia # fdisk /dev/sdc Unable to read /dev/sdc ---- Then I made another dmesg: http://www.coldsiberia.net/text/dmesg_07052009_2.txt Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday May 7 2009, Per Inge Oestmoen wrote:
Per Jessen wrote:
First one dmesg after attaching the drive, this is a new one just made now:
http://www.coldsiberia.net/text/dmesg_07052009.txt
Thereafter i tried fdisk:
---- linux-k9na:/home/siberia # fdisk /dev/sdc
Unable to read /dev/sdc ----
Then I made another dmesg:
I direct you to kdiff3. These lines appear in the second dmesg output: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1b:11:61:73:6f:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:1f:5b:c3:11:c4:08:00 SRC=192.168.0.153 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=58772 OPT (94040000) PROTO=2 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.125 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1b:11:61:73:6f:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:1f:5b:c3:11:c4:08:00 SRC=192.168.0.153 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=42257 OPT (94040000) PROTO=2 Uniform Multi-Platform E-IDE driver ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx st: Version 20080221, fixed bufsize 32768, s/g segs 256 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1b:11:61:73:6f:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.125 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1b:11:61:73:6f:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:1f:5b:c3:11:c4:08:00 SRC=192.168.0.153 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=35487 OPT (94040000) PROTO=2 The long lines with MAC= refer to your network adaptor. The others are for you IDE bus, presumably for an optical drive. It's odd it would show up here and now, though. Did you insert an CD or DVD between the first and the second dmesg? You said this drive works with Windows. Is that Windows running on the same machine as the Linux system that's giving you trouble? If not, perhaps your (Linux) machine's BIOS is the source of the problem. Also, there's more information in /var/log/messages than you get from dmesg. Follow Felix's other advice: Try a program _not_ known to fail.
Per Inge Oestmoen, Norway
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
On Thursday May 7 2009, Per Inge Oestmoen wrote:
Per Jessen wrote:
First one dmesg after attaching the drive, this is a new one just made now:
http://www.coldsiberia.net/text/dmesg_07052009.txt
Thereafter i tried fdisk:
---- linux-k9na:/home/siberia # fdisk /dev/sdc
Unable to read /dev/sdc ----
Then I made another dmesg:
I direct you to kdiff3. These lines appear in the second dmesg output:
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1b:11:61:73:6f:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:1f:5b:c3:11:c4:08:00 SRC=192.168.0.153 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=58772 OPT (94040000) PROTO=2 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.125 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1b:11:61:73:6f:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:1f:5b:c3:11:c4:08:00 SRC=192.168.0.153 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=42257 OPT (94040000) PROTO=2 Uniform Multi-Platform E-IDE driver ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx st: Version 20080221, fixed bufsize 32768, s/g segs 256 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1b:11:61:73:6f:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.0.125 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:1b:11:61:73:6f:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:1f:5b:c3:11:c4:08:00 SRC=192.168.0.153 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=35487 OPT (94040000) PROTO=2
The long lines with MAC= refer to your network adaptor. The others are for you IDE bus, presumably for an optical drive. It's odd it would show up here and now, though. Did you insert an CD or DVD between the first and the second dmesg?
No, nothing was done except for the attempt to access the external disk - the WD Caviar 1 Tb.
You said this drive works with Windows. Is that Windows running on the same machine as the Linux system that's giving you trouble? If not, perhaps your (Linux) machine's BIOS is the source of the problem.
The Windows machine was in the shop where I bought the hard drive - I went there because this is the first disk I have been unable to partition and format ever. It is also the biggest, since I have hitherto only used 500 Gb disks. My motherboard is the Asus P4P-800E deluxe. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Inge Oestmoen wrote:
Per Jessen wrote:
Can I suggest the following:
disconnect USB drive reboot system connect USB drive, do a dmesg and post the output on coldsiberia try 'fdisk /dev/sdX' where X is the driver letter assigned as per dmesg output. Assuming this fails, do a dmesg and post the output on coldsiberia, but separately. (if it doesn't fail, you have some sort of intermittent problem, again indicative of a hardware issue).
First one dmesg after attaching the drive, this is a new one just made now:
OK, that's great - usb 2-2: new high speed USB device using ehci_hcd and address 4 usb 2-2: configuration #1 chosen from 1 choice usb 2-2: New USB device found, idVendor=152d, idProduct=2338 usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 usb 2-2: Product: USB to ATA/ATAPI Bridge usb 2-2: Manufacturer: JMicron usb 2-2: SerialNumber: 152D203380B6 Initializing USB Mass Storage driver... scsi8 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning scsi 8:0:0:0: Direct-Access PQ: 0 ANSI: 2 CCS Uh, your drive did not identify itself - the line above should have looked more like this: scsi 11:0:0:0: Direct-Access TOSHIBA USB 3.5"-HDD 100 PQ: 0 ANSI: 2 This is from a 500Gb Toshiba drive - the key is "TOSHIBA USB 3.5"-HDD 100", I don't know why your drive only produced blanks. After that I have this: sd 11:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 11:0:0:0: [sdc] Write Protect is off sd 11:0:0:0: [sdc] Mode Sense: 38 00 00 00 sd 11:0:0:0: [sdc] Assuming drive cache: write through sd 11:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 11:0:0:0: [sdc] Write Protect is off sd 11:0:0:0: [sdc] Mode Sense: 38 00 00 00 sd 11:0:0:0: [sdc] Assuming drive cache: write through We are not getting much closer to solving your problem, but your system definitely has trouble talking to the drive. /Per -- Per Jessen, Zürich (25.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Inge Oestmoen wrote:
Per Jessen wrote:
Per Inge Oestmoen wrote:
Which errors? Did it just hang? How do you know that the disk became inaccessible?
I got this:
---- linux-k9na:/home/siberia # fdisk /dev/sdc
Unable to open /dev/sdc ----
It would have been nice to see the output from dmesg right after this, but if fdisk cannot access the disk, you have a hardware problem.
Here is the most recent dmesg:
You are running fdisk as root, right? Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Lew Wolfgang wrote:
You are running fdisk as root, right?
Of course. Per Inge Oestmoen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/05/07 13:45 (GMT+0200) Per Inge Oestmoen composed:
The command fdisk /dev/sdc resulted in the disk becoming inaccessible, and I had to turn it off and on again.
Stop messing with what you know isn't working (fdisk and yast) and try something else: cfdisk parted qparted gparted ... winxp vista Do all them cause the disk to become inaccessible too? Also, there's now an exFAT to consider, though I suspect that's best reserved for solid state media rather than HDs. -- "A fool gives full vent to his anger, but a wise man keeps himself under control." Proverbs 29:11 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata wrote:
On 2009/05/07 13:45 (GMT+0200) Per Inge Oestmoen composed:
The command fdisk /dev/sdc resulted in the disk becoming inaccessible, and I had to turn it off and on again.
Stop messing with what you know isn't working (fdisk and yast) and try something else:
cfdisk parted qparted gparted ... winxp vista
I have no regular access to Windows XP or Vista machines. cfdisk does not work either. The fact that the disk drops out at irregular intervals is disturbing. A MacBook Pro with OSX 10.5.6 does not see the disk either. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Inge Oestmoen wrote:
I have no regular access to Windows XP or Vista machines.
cfdisk does not work either.
The fact that the disk drops out at irregular intervals is disturbing.
A MacBook Pro with OSX 10.5.6 does not see the disk either.
Despite Randall's insistence that 'All this stuff about "directly connected" is a bunch of distinctions without differences' I suggest that if it is at all possible, you should remove the drive from the case and try to temporarily directly connect the drive to a SATA cable on your motherboard. That way you may determine if the problem is with the disk or with the cabinet/USB system. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday May 7 2009, Dave Howorth wrote:
Per Inge Oestmoen wrote:
I have no regular access to Windows XP or Vista machines.
cfdisk does not work either.
The fact that the disk drops out at irregular intervals is disturbing.
A MacBook Pro with OSX 10.5.6 does not see the disk either.
Despite Randall's insistence that 'All this stuff about "directly connected" is a bunch of distinctions without differences' I suggest that if it is at all possible, you should remove the drive from the case and try to temporarily directly connect the drive to a SATA cable on your motherboard.
I didn't know we were diagnosing hardward problems that could be anywhere between the CPU and the drive. Per O. repeatedly said that this drive and all the connecting hardware worked with Windows. That suggests that hardware is not the source of the problem.
That way you may determine if the problem is with the disk or with the cabinet/USB system.
Cheers, Dave
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
On Thursday May 7 2009, Dave Howorth wrote: I didn't know we were diagnosing hardward problems that could be anywhere between the CPU and the drive. Per O. repeatedly said that this drive and all the connecting hardware worked with Windows. That suggests that hardware is not the source of the problem.
That way you may determine if the problem is with the disk or with the cabinet/USB system.
(1) I don't think he said that it worked with Windows. He said it could be detected but then Linux has also been able to detect it. (2) I didn't say it was a hardware problem did I? :) I do think it is a possibility though, as is firmware, as is software. Separating the components will help to isolate the source of the trouble. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/05/07 16:07 (GMT+0100) Dave Howorth composed:
Randall R Schulz wrote:
On Thursday May 7 2009, Dave Howorth wrote:
I didn't know we were diagnosing hardward problems that could be anywhere between the CPU and the drive. Per O. repeatedly said that this drive and all the connecting hardware worked with Windows. That suggests that hardware is not the source of the problem.
http://lists.opensuse.org/opensuse/2009-05/msg00377.html suggests that it is a hardware problem. http://lists.opensuse.org/opensuse/2009-05/msg00461.html and http://lists.opensuse.org/opensuse/2009-05/msg00245.html and http://lists.opensuse.org/opensuse/2009-05/msg00268.html don't provide clear explanation of doz behavior, but http://lists.opensuse.org/opensuse/2009-05/msg00416.html does, at least for that point in time whenever it was.
That way you may determine if the problem is with the disk or with the cabinet/USB system.
(1) I don't think he said that it worked with Windows. He said it could be detected but then Linux has also been able to detect it.
(2) I didn't say it was a hardware problem did I? :) I do think it is a possibility though, as is firmware, as is software. Separating the components will help to isolate the source of the trouble.
I think any time spent doing trying further partitioning attemps prior to trying the HD separately is a waste. One thing to try: Is there a SATA I compatibility jumper available on the WD? If so, try changing it from whatever it is now to the other setting. Is there any documentation for the USB enclosure that mentions its capabilities? Is it SATA II? Maybe the enclosure only supports SATA I mode while your WD is SATA II? Another point: Are you always using the same motherboard USB port? I'd figure out which if any are EHCI (2.0) and which are other (1.x), and be sure to only connect it to EHCI (2.0), preferably the same one if you have a way to determine if it works correctly at all times with other 2.0 devices. -- "A fool gives full vent to his anger, but a wise man keeps himself under control." Proverbs 29:11 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata wrote:
http://lists.opensuse.org/opensuse/2009-05/msg00377.html suggests that it is a hardware problem.
http://lists.opensuse.org/opensuse/2009-05/msg00461.html and http://lists.opensuse.org/opensuse/2009-05/msg00245.html and http://lists.opensuse.org/opensuse/2009-05/msg00268.html don't provide clear explanation of doz behavior, but http://lists.opensuse.org/opensuse/2009-05/msg00416.html does, at least for that point in time whenever it was.
I think any time spent doing trying further partitioning attemps prior to trying the HD separately is a waste.
One thing to try: Is there a SATA I compatibility jumper available on the WD? If so, try changing it from whatever it is now to the other setting. Is there any documentation for the USB enclosure that mentions its capabilities? Is it SATA II? Maybe the enclosure only supports SATA I mode while your WD is SATA II?
The enclosure is described as SATA I and SATA II compliant, and here it is: http://www.akasa.com.tw/akasa_english/spec_page/storage/spec_ak_enp2sata_sl.... I might try to change a jumper position anyway to see if it helps, but I have more faith that a direct installment of the disk in the PC might do the trick. One might suggest that the Asus P4P800 deluxe has trouble reading 1 Tb disks, but since the MacBook Pro could not either that possibility can be ruled out.
Another point: Are you always using the same motherboard USB port? I'd figure out which if any are EHCI (2.0) and which are other (1.x), and be sure to only connect it to EHCI (2.0), preferably the same one if you have a way to determine if it works correctly at all times with other 2.0 devices.
No, I alternate between the six ports available. All of them give consistent USB 2.0 speeds with all the devices I have used, including several 500 Gb hard drives, one 250 Gb hard drive, several card readers and my digital cameras EOS 1D III and EOS 40D. But none of them will function with this new large disk. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/05/07 17:47 (GMT+0200) Per Inge Oestmoen composed:
The enclosure is described as SATA I and SATA II compliant, and here it is:
http://www.akasa.com.tw/akasa_english/spec_page/storage/spec_ak_enp2sata_sl....
After all this time and trouble you have not tried the eSATA interface? Is that because you have no eSATA port? You can get a eSATA/SATA combo cable, or an adapter like I described upthread regarding the enclosures I use. Just be sure to connect and power on prior to booting if any of the hardware does not support eSATA-only features.
I might try to change a jumper position anyway to see if it helps, but I have more faith that a direct installment of the disk in the PC might do the trick.
I'd try the combo cable first if you don't have to wait to get one.
One might suggest that the Asus P4P800 deluxe has trouble reading 1 Tb disks, but since the MacBook Pro could not either that possibility can be ruled out.
I doubt it has anything to do directly with the size but rather with the capability of the enclosure's USB connectivity. On reading that web page I see a conflict between the features and specifications regarding the maximum eSATA transfer rate. That reduces my expectation of the competence of the hardware. -- "A fool gives full vent to his anger, but a wise man keeps himself under control." Proverbs 29:11 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday May 7 2009, Felix Miata wrote:
On 2009/05/07 17:47 (GMT+0200) Per Inge Oestmoen composed:
The enclosure is described as SATA I and SATA II compliant, and here it is:
> http://www.akasa.com.tw/akasa_english/spec_page/storage/spec_ak_enp2sata_sl....
After all this time and trouble you have not tried the eSATA interface? Is that because you have no eSATA port? You can get a eSATA/SATA combo cable, or an adapter like I described upthread regarding the enclosures I use. Just be sure to connect and power on prior to booting if any of the hardware does not support eSATA-only features.
Wait... Per O. has a SATA drive and he's using an adaptor that makes it appear as USB? Why, indeed! That's just silly. I assume there's _some_ reason for it, but you really should not try to avoid using SATA, you should prefer it!
...
Felix Miata
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata wrote:
On 2009/05/07 17:47 (GMT+0200) Per Inge Oestmoen composed:
The enclosure is described as SATA I and SATA II compliant, and here it is: http://www.akasa.com.tw/akasa_english/spec_page/storage/spec_ak_enp2sata_sl....
After all this time and trouble you have not tried the eSATA interface? Is that because you have no eSATA port? You can get a eSATA/SATA combo cable, or an adapter like I described upthread regarding the enclosures I use. Just be sure to connect and power on prior to booting if any of the hardware does not support eSATA-only features.
I have no eSATA ports on my motherboard.
I might try to change a jumper position anyway to see if it helps, but I have more faith that a direct installment of the disk in the PC might do the trick.
I'd try the combo cable first if you don't have to wait to get one.
Such a cable came with the enclosure, but without any ports to plug it into it will be of little help.
One might suggest that the Asus P4P800 deluxe has trouble reading 1 Tb disks, but since the MacBook Pro could not either that possibility can be ruled out.
I doubt it has anything to do directly with the size but rather with the capability of the enclosure's USB connectivity. On reading that web page I see a conflict between the features and specifications regarding the maximum eSATA transfer rate. That reduces my expectation of the competence of the hardware.
Maybe. I have two things to try out then: To change the jumper position on the hard drive and see if it helps, granted that there is such a jumper. If still no joy, I proceed with placing the whole disk into the PC instead. This is my first external disk that could not be easily formatted with my SuSE 11.0. Why is yet to determine. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/05/07 18:15 (GMT+0200) Per Inge Oestmoen composed:
Felix Miata wrote:
After all this time and trouble you have not tried the eSATA interface? Is that because you have no eSATA port? You can get a eSATA/SATA combo cable, or an adapter like I described upthread regarding the enclosures I use. Just be sure to connect and power on prior to booting if any of the hardware does not support eSATA-only features.
I have no eSATA ports on my motherboard.
I just looked at the first Google hit for Asus P4P-800E deluxe and it does indeed have one pair of SATA (RAID) ports. I've yet to encounter SATA RAID ports that could not be operated in non-RAID mode. Maybe there was more than one variant of Asus P4P-800E deluxe made and you got the short end of the deal? What is your output from lspci? Maybe you need to enable the SATA in your BIOS. -- "A fool gives full vent to his anger, but a wise man keeps himself under control." Proverbs 29:11 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata wrote:
On 2009/05/07 18:15 (GMT+0200) Per Inge Oestmoen composed:
I have no eSATA ports on my motherboard.
I just looked at the first Google hit for Asus P4P-800E deluxe and it does indeed have one pair of SATA (RAID) ports. I've yet to encounter SATA RAID ports that could not be operated in non-RAID mode. Maybe there was more than one variant of Asus P4P-800E deluxe made and you got the short end of the deal?
Yes, on the inside. But I need external hard drives to be attached to external ports.
What is your output from lspci? Maybe you need to enable the SATA in your BIOS.
I already use SATA disks - inside the machine. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday May 7 2009, Per Inge Oestmoen wrote:
...
I already use SATA disks - inside the machine.
Is FireWire (IEEE 1394) an option? My WD MyBook has FireWire, eSATA _and_ USB. I'm using its FireWire interface.
Per Inge Oestmoen, Norway
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
On Thursday May 7 2009, Per Inge Oestmoen wrote:
I already use SATA disks - inside the machine.
Is FireWire (IEEE 1394) an option? My WD MyBook has FireWire, eSATA _and_ USB. I'm using its FireWire interface.
Unfortunately not, since the enclosures I use only have USB and eSATA interfaces. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, May 7, 2009 at 1:48 PM, Per Inge Oestmoen <pioe@coldsiberia.org> wrote:
Randall R Schulz wrote:
On Thursday May 7 2009, Per Inge Oestmoen wrote:
I already use SATA disks - inside the machine.
Is FireWire (IEEE 1394) an option? My WD MyBook has FireWire, eSATA _and_ USB. I'm using its FireWire interface.
Unfortunately not, since the enclosures I use only have USB and eSATA interfaces.
Per, eSata and Sata use exactly the same voltages, signals. You can buy an adapter cable for about $10 that is sata on one end an eSata on the other. The eSata end should come on a bracket so you can permanently mount the adaptor cable in your chassis. Then you just connect a normal eSata cable to it and to your eSata enclosure. All in all a one time $10 expense. And eSata is much faster than USB2.0 But you don't have to do that for now, just put the drive inside the computer and connect it via sata directly and see if the problem goes away. If it does you likely have a bad enclosure. If you still have problems, then likely have a bad drive. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday May 7 2009, Greg Freemyer wrote:
...
But you don't have to do that for now, just put the drive inside the computer and connect it via sata directly and see if the problem goes away. If it does you likely have a bad enclosure. If you still have problems, then likely have a bad drive.
Felix said there are two internal SATA connectors and Per O. said he had SATA disks (plural) inside, to presumably both SATA ports are in use. But it would probably help the diagnostic situation to try connecting the troublesome drive to the SATA port at least temporarily.
Greg
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
Felix said there are two internal SATA connectors and Per O. said he had SATA disks (plural) inside, to presumably both SATA ports are in use.
But it would probably help the diagnostic situation to try connecting the troublesome drive to the SATA port at least temporarily.
Yes, I have to take out one disk and insert the one that creates all these headaches. If the problem then disappears, it has been isolated to the USB chain of transmission. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday May 7 2009, Per Inge Oestmoen wrote:
Randall R Schulz wrote:
Felix said there are two internal SATA connectors and Per O. said he had SATA disks (plural) inside, to presumably both SATA ports are in use.
But it would probably help the diagnostic situation to try connecting the troublesome drive to the SATA port at least temporarily.
Yes, I have to take out one disk and insert the one that creates all these headaches. If the problem then disappears, it has been isolated to the USB chain of transmission.
I did some searching and found some references (more like allusions) to there being external drive enclosures that impose capacity limits on the drives they support. I couldn't find anything very definitive, but if it is a real issue, it may be what you're encountering. I still wouldn't rule out the BIOS as a source of problems, but if that's the case, I'd still say there's a good chance the SATA ports won't be affected.
Per Inge Oestmoen, Norway
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/05/07 19:28 (GMT+0200) Per Inge Oestmoen composed:
I need external hard drives to be attached to external ports.
In http://lists.opensuse.org/opensuse/2009-05/msg00381.html I explained this is not a problem for me. Just put in an adapter, and enjoy the full speed of SATA externally, and without any USB compatibility issues. e.g. http://www.microbarn.com/details.aspx?rid=101818&source=froogle -- "A fool gives full vent to his anger, but a wise man keeps himself under control." Proverbs 29:11 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-05-07 at 07:53 -0700, Randall R Schulz wrote:
I didn't know we were diagnosing hardward problems that could be anywhere between the CPU and the drive. Per O. repeatedly said that this drive and all the connecting hardware worked with Windows. That suggests that hardware is not the source of the problem.
Yes, but windows on a different machine, one at the shop he bought the device. We don't know if windows on the same machine works because he doesn't have windows there. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoDOP4ACgkQtTMYHG2NR9X4YgCfdM8q7Dn39zhUAHzOMHe0gsD6 eNEAmwetkpcXizbiWJuR+UGUpxvIzOFQ =JZIu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday May 7 2009, Carlos E. R. wrote:
On Thursday, 2009-05-07 at 07:53 -0700, Randall R Schulz wrote:
I didn't know we were diagnosing hardward problems that could be anywhere between the CPU and the drive. Per O. repeatedly said that this drive and all the connecting hardware worked with Windows. That suggests that hardware is not the source of the problem.
Yes, but windows on a different machine, one at the shop he bought the device. We don't know if windows on the same machine works because he doesn't have windows there.
I wasn't clear on that. I thought when I asked him whether the working setup (with Windows) was using the same cables and / or hubs as the non-working (Linux) case that the answer was "yes."
-- Cheers, Carlos E. R.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-05-07 at 12:59 -0700, Randall R Schulz wrote:
Yes, but windows on a different machine, one at the shop he bought the device. We don't know if windows on the same machine works because he doesn't have windows there.
I wasn't clear on that. I thought when I asked him whether the working setup (with Windows) was using the same cables and / or hubs as the non-working (Linux) case that the answer was "yes."
I thought that, too, until I saw one message that clarified the issue. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoDRu0ACgkQtTMYHG2NR9UbCgCggNfdEr497BTDfY0yHcMxTZN6 fbgAn0LK01CBRJqR6+Tm8jxNOrMAGX42 =rEYs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
On Thursday May 7 2009, Carlos E. R. wrote:
Yes, but windows on a different machine, one at the shop he bought the device. We don't know if windows on the same machine works because he doesn't have windows there.
I wasn't clear on that. I thought when I asked him whether the working setup (with Windows) was using the same cables and / or hubs as the non-working (Linux) case that the answer was "yes."
I brought the whole thing to the shop, and there Vista recognized the drive when in its enclosure. The USB cable also was the same. Interestingly, that aforementioned MacBook Pro with OSX 10.5.6 could not detect the drive at all. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Howorth wrote:
Per Inge Oestmoen wrote:
I have no regular access to Windows XP or Vista machines. cfdisk does not work either. The fact that the disk drops out at irregular intervals is disturbing. A MacBook Pro with OSX 10.5.6 does not see the disk either.
Despite Randall's insistence that 'All this stuff about "directly connected" is a bunch of distinctions without differences' I suggest that if it is at all possible, you should remove the drive from the case and try to temporarily directly connect the drive to a SATA cable on your motherboard. That way you may determine if the problem is with the disk or with the cabinet/USB system.
Yes, and that is what I will have to do next if everything else fails. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/05/07 16:17 (GMT+0200) Per Inge Oestmoen composed:
Felix Miata wrote:
cfdisk parted qparted gparted ... winxp vista
I have no regular access to Windows XP or Vista machines.
No friends or neighbors with doz? That's rather unusual, unless you have neither friends nor neighbors.
cfdisk does not work either.
:-(
The fact that the disk drops out at irregular intervals is disturbing.
Quite. :-( How old is the system? What I/O chipset does it have? Maybe your motherboard's USB system is the real problem. You could try installing a well-supported USB card in a PCI slot to see.
A MacBook Pro with OSX 10.5.6 does not see the disk either.
Well, probably not your motherboard then. :~(
Per Inge Oestmoen, Norway
How far is that from Hageland? If close, maybe my friendly web carpenter friend can try to do NTFS for you in Windows. Probably now it is time to contact WD support, or take it back to the vendor for refund or exchange. -- "A fool gives full vent to his anger, but a wise man keeps himself under control." Proverbs 29:11 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday May 7 2009, Per Inge Oestmoen wrote:
...
I then choose OK, and go back to the main YaST screen, where YaST claims that my disk is 2 Tb instead of 1 Tb which is the real size. I can go no further.
What information is presented by "hwinfo --disk" for this device?
Per Inge Oestmoen, Norway
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Carlos E. R. -
Dave Howorth -
Felix Miata -
Greg Freemyer -
jdd -
Lew Wolfgang -
Per Inge Oestmoen -
Per Jessen -
Randall R Schulz