[opensuse] Large disks in Opensuse 11
Is there a problem with 1 Tb disks (or larger) in Opensuse 11? Yesterday I bought a Western Digital Caviar Black, model WD1001FALS-00J780. I put it into an external cabinet, attached the USB cord to the computer and started Opensuse 11. The disk did not appear in Konqueror, so I went into Yast2. There was no indication that there was any disk attached, and I tried Yast (the text-based older version). There the disk came up, but Yast claimed that the disk was 2 Tb instead of 1 Tb. I started formatting, but the process stopped with no success and I could not format the disk. What is the source of the problem, and how to remedy it. I shall be thankful for all help. Cheers, Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2009-05-06 at 14:16 +0200, Per Inge Oestmoen wrote:
Is there a problem with 1 Tb disks (or larger) in Opensuse 11?
Yesterday I bought a Western Digital Caviar Black, model WD1001FALS-00J780. I put it into an external cabinet, attached the USB cord to the computer and started Opensuse 11.
The disk did not appear in Konqueror, so I went into Yast2. There was no indication that there was any disk attached, and I tried Yast (the text-based older version). There the disk came up, but Yast claimed that the disk was 2 Tb instead of 1 Tb. I started formatting, but the process stopped with no success and I could not format the disk.
I use them. They usually only support USB2, not the slower USB1, like smaller disks often do. So it must be a USB2 port that it is connected to. Do you see the disk if you type: lsusb If not, the problem is at the usb level If you see it in lsusb, do you see it in lsscsi ?
What is the source of the problem, and how to remedy it.
I shall be thankful for all help.
Cheers, Per Inge Oestmoen, Norway
-- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
On Wed, 2009-05-06 at 14:16 +0200, Per Inge Oestmoen wrote:
Is there a problem with 1 Tb disks (or larger) in Opensuse 11? The disk did not appear in Konqueror, so I went into Yast2. There was no indication that there was any disk attached, and I tried Yast (the text-based older version). There the disk came up, but Yast claimed that the disk was 2 Tb instead of 1 Tb. I started formatting, but the process stopped with no success and I could not format the disk.
I use them. They usually only support USB2, not the slower USB1, like smaller disks often do. So it must be a USB2 port that it is connected to. Do you see the disk if you type: lsusb
It would seem so: lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 046d:c043 Logitech, Inc. MX320 Laser Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 046d:c30e Logitech, Inc. UltraX Keys (X) Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
If you see it in lsusb, do you see it in lsscsi ?
No: lsscsi [1:0:0:0] disk ATA WDC WD1200JB-32E 15.0 /dev/sda [2:0:0:0] cd/dvd Optiarc DVD RW AD-7170A 1.02 /dev/sr0 [2:0:1:0] cd/dvd PIONEER DVD-ROM DVD-117 1.07 /dev/sr1 [4:0:0:0] disk ATA ST3320620NS 3.AE /dev/sdb Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2009-05-06 at 14:34 +0200, Per Inge Oestmoen wrote:
Roger Oberholtzer wrote:
On Wed, 2009-05-06 at 14:16 +0200, Per Inge Oestmoen wrote:
Is there a problem with 1 Tb disks (or larger) in Opensuse 11? The disk did not appear in Konqueror, so I went into Yast2. There was no indication that there was any disk attached, and I tried Yast (the text-based older version). There the disk came up, but Yast claimed that the disk was 2 Tb instead of 1 Tb. I started formatting, but the process stopped with no success and I could not format the disk.
I use them. They usually only support USB2, not the slower USB1, like smaller disks often do. So it must be a USB2 port that it is connected to. Do you see the disk if you type: lsusb
It would seem so:
lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 046d:c043 Logitech, Inc. MX320 Laser Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 046d:c30e Logitech, Inc. UltraX Keys (X) Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Um, which in the above is the disk? -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
On Wed, 2009-05-06 at 14:34 +0200, Per Inge Oestmoen wrote:
to. Do you see the disk if you type: lsusb It would seem so:
lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 046d:c043 Logitech, Inc. MX320 Laser Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 046d:c30e Logitech, Inc. UltraX Keys (X) Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Um, which in the above is the disk?
To tell you the truth I an not sure! But all my ports are USB 2. By the way, my kernel version is 2.6.25.20-01-default. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi On Wed, May 6, 2009 at 1:16 PM, Per Inge Oestmoen <pioe@coldsiberia.org> wrote:
Is there a problem with 1 Tb disks (or larger) in Opensuse 11?
Yesterday I bought a Western Digital Caviar Black, model WD1001FALS-00J780. I put it into an external cabinet, attached the USB cord to the computer and started Opensuse 11.
The disk did not appear in Konqueror, so I went into Yast2. There was no indication that there was any disk attached, and I tried Yast (the text-based older version). There the disk came up, but Yast claimed that the disk was 2 Tb instead of 1 Tb. I started formatting, but the process stopped with no success and I could not format the disk.
Did you try "tail -f /var/log/messages" and connect/disconnect the drive? Maybe you can see if the disk is recognized. Cheers, Ioan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ionut Vancea wrote:
On Wed, May 6, 2009 at 1:16 PM, Per Inge Oestmoen <pioe@coldsiberia.org> wrote:
Is there a problem with 1 Tb disks (or larger) in Opensuse 11? Yesterday I bought a Western Digital Caviar Black, model WD1001FALS-00J780. I put it into an external cabinet, attached the USB cord to the computer and started Opensuse 11. The disk did not appear in Konqueror, so I went into Yast2. There was no indication that there was any disk attached, and I tried Yast (the text-based older version). There the disk came up, but Yast claimed that the disk was 2 Tb instead of 1 Tb. I started formatting, but the process stopped with no success and I could not format the disk.
Did you try "tail -f /var/log/messages" and connect/disconnect the drive? Maybe you can see if the disk is recognized.
That yielded this result: siberia@linux-k9na:~> tail -f /var/log/messages tail: cannot open `/var/log/messages' for reading: Permission denied tail: no files remaining Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday May 6 2009, Per Inge Oestmoen wrote:
...
Did you try "tail -f /var/log/messages" and connect/disconnect the drive? Maybe you can see if the disk is recognized.
That yielded this result:
siberia@linux-k9na:~> tail -f /var/log/messages tail: cannot open `/var/log/messages' for reading: Permission denied tail: no files remaining
Only root can read /var/log/messages.
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:
Only root can read /var/log/messages.
I then became root, and here is the result: ---- linux-k9na:/home/siberia # tail -f /var/log/messages May 6 17:04:06 linux-k9na kernel: usb 2-2: New USB device found, idVendor=152d, idProduct=2338 May 6 17:04:06 linux-k9na kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 May 6 17:04:06 linux-k9na kernel: usb 2-2: Product: USB to ATA/ATAPI Bridge May 6 17:04:06 linux-k9na kernel: usb 2-2: Manufacturer: JMicron May 6 17:04:06 linux-k9na kernel: usb 2-2: SerialNumber: 183D203370B9 May 6 17:04:07 linux-k9na kernel: scsi 9:0:0:0: Direct-Access PQ: 0 ANSI: 2 CCS May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: [sdc] Attached SCSI disk May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: Attached scsi generic sg4 type 0 May 6 17:04:07 linux-k9na kernel: usb-storage: device scan complete May 6 17:11:20 linux-k9na su: (to root) siberia on /dev/pts/2 May 6 17:11:40 linux-k9na smartd[3371]: Device: /dev/sda, 1 Currently unreadable (pending) sectors May 6 17:15:06 linux-k9na gconfd (siberia-20011): GConf server is not in use, shutting down. May 6 17:15:06 linux-k9na gconfd (siberia-20011): Exiting ---- Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/05/06 17:17 (GMT+0200) Per Inge Oestmoen composed:
linux-k9na:/home/siberia # tail -f /var/log/messages May 6 17:04:06 linux-k9na kernel: usb 2-2: New USB device found, idVendor=152d, idProduct=2338 May 6 17:04:06 linux-k9na kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 May 6 17:04:06 linux-k9na kernel: usb 2-2: Product: USB to ATA/ATAPI Bridge May 6 17:04:06 linux-k9na kernel: usb 2-2: Manufacturer: JMicron May 6 17:04:06 linux-k9na kernel: usb 2-2: SerialNumber: 183D203370B9 May 6 17:04:07 linux-k9na kernel: scsi 9:0:0:0: Direct-Access PQ: 0 ANSI: 2 CCS May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: [sdc] Attached SCSI disk May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: Attached scsi generic sg4 type 0 May 6 17:04:07 linux-k9na kernel: usb-storage: device scan complete May 6 17:11:20 linux-k9na su: (to root) siberia on /dev/pts/2 May 6 17:11:40 linux-k9na smartd[3371]: Device: /dev/sda, 1 Currently unreadable (pending) sectors May 6 17:15:06 linux-k9na gconfd (siberia-20011): GConf server is not in use, shutting down. May 6 17:15:06 linux-k9na gconfd (siberia-20011): Exiting
Have you tried accessing it with a partitioning program yet? Until there are partitions, there is nothing for any user activity except a partitioning program to access. -- "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 Wednesday May 6 2009, Felix Miata wrote:
...
Have you tried accessing it with a partitioning program yet? Until there are partitions, there is nothing for any user activity except a partitioning program to access.
Good point. And if there are partitions but they're unformatted or formatted with a file system type not supported by installed drivers, the net effect would be similar (nothing seems to happen when the drive is attached).
... Felix Miata *** http://fm.no-ip.com/
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday May 6 2009, Randall R Schulz wrote:
On Wednesday May 6 2009, Felix Miata wrote:
...
Have you tried accessing it with a partitioning program yet? Until there are partitions, there is nothing for any user activity except a partitioning program to access.
Good point. And if there are partitions but they're unformatted or formatted with a file system type not supported by installed drivers, the net effect would be similar (nothing seems to happen when the drive is attached).
An even more esoteric possibility occurred to me: The partition type code could be one not recognized as holding a file system. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
On Wednesday May 6 2009, Felix Miata wrote:
...
Have you tried accessing it with a partitioning program yet? Until there are partitions, there is nothing for any user activity except a partitioning program to access.
Good point. And if there are partitions but they're unformatted or formatted with a file system type not supported by installed drivers, the net effect would be similar (nothing seems to happen when the drive is attached).
Indeed, if it works with Windows than maybe it has some foul NTFS filesystem installed. I usually assume that any off-the-shelf external disk is unusable until I put my own filesystem on it. If this disk was on my system I'd do the following from the command line as root. (WARNING! You can trash your system if you mess up here!!! If you don't understand commands like fdisk and mkfs be sure to read and understand the man pages. Man is your friend.) 1. Check /var/log/messages to see what /dev/sdX device it was mounted on. In this case it looks like /dev/sdc. 2. Run fdisk /dev/sdc to check the disk labeling and find what partitions are defined. If necessary I'll create a new label and partition table. See "man fdisk". 3. Create my own filesystem. If the disk will be used only on Linux boxes I'll use reiserfs. If I want both Linux and Windows to be able to use it I'll format with fat-32. Assuming that partition 1 is the one you want: For Linux only: mkreiserfs /dev/sdc1 For Linux/Windows: mkfs.vfat -F 32 /dev/sdc1 The disk should now automount when hot-plugged. If it doesn't you might try mounting it manually, as in "mount /dev/sdc1 /mnt". Once again, be careful. The command-line can byte if you're root and you mess up. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday May 6 2009, Lew Wolfgang wrote:
...
1. Check /var/log/messages to see what /dev/sdX device it was mounted on. In this case it looks like /dev/sdc.
I find the directories under /dev/disk to be most useful for identifying which /dev entry corresponds to which driver or partition. Often the entries in /dev/disk/by-id include manufacturer and model information. E.g. (Partitions elided): % ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 May 1 13:54 ata-WDC_WD3000JD-00KLB0_WD-WMAMR1684703 -> ../../sdd lrwxrwxrwx 1 root root 9 May 1 13:54 edd-int13_dev80 -> ../../sda lrwxrwxrwx 1 root root 9 May 1 13:54 edd-int13_dev81 -> ../../sdc lrwxrwxrwx 1 root root 9 May 1 13:54 edd-int13_dev82 -> ../../sdb lrwxrwxrwx 1 root root 9 May 1 13:54 edd-int13_dev83 -> ../../sdd lrwxrwxrwx 1 root root 9 May 1 13:54 ieee1394-0090a9dcdeb9a1ce:000434:0000 -> ../../sde lrwxrwxrwx 1 root root 9 May 1 13:54 scsi-20010b9ff0d0ba600 -> ../../sdc lrwxrwxrwx 1 root root 9 May 1 13:54 scsi-35005076718c08df4 -> ../../sda lrwxrwxrwx 1 root root 9 May 1 13:54 scsi-SATA_WDC_WD3000JD-00_WD-WMAMR1684703 -> ../../sdd lrwxrwxrwx 1 root root 9 May 1 13:54 scsi-SFUJITSU_MAT3073NP_AAS0P55014US -> ../../sdb
...
Regards, Lew
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/06 17:17 (GMT+0200) Per Inge Oestmoen composed:
linux-k9na:/home/siberia # tail -f /var/log/messages
Have you tried accessing it with a partitioning program yet? Until there are partitions, there is nothing for any user activity except a partitioning program to access.
Yes, by all means, read back to the start - I have tried both Yast2 and Yast, but I did not manage to get them to partition and format the 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/06 18:01 (GMT+0200) Per Inge Oestmoen composed:
Felix Miata wrote:
On 2009/05/06 17:17 (GMT+0200) Per Inge Oestmoen composed:
linux-k9na:/home/siberia # tail -f /var/log/messages
Have you tried accessing it with a partitioning program yet? Until there are partitions, there is nothing for any user activity except a partitioning program to access.
Yes, by all means, read back to the start - I have tried both Yast2 and Yast, but I did not manage to get them to partition and format the large disk.
I saw your first post before anyone else replied to it. That you tried YaST2 told me nothing. YaST2 is a multifacted configurator with many ways to not do what actually needs doing. I never use it to create partitions. The only time I see it is after partitioning when it is run by the installer, when I use it exclusively to assign mount points to existing partitions. In your OP, you discussed formatting without discussing partitioning. Formatting (as the term is used by most people; technically partitioning is a special form of formatting, but most people limit use of the term to apply to creating filesystems on previously created partitions) on a HD is never possible until after partition(s) have been created. OTOH, you could 'fdisk -l' and see if there's any sign of its presence or any partitioning on it. If you partitioned it with Vista, it may be that YaST2 does not understand what Vista did to it. If there are no partitions at all .... -- "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 2009/05/06 13:27 (GMT-0400) Felix Miata composed:
OTOH, you could 'fdisk -l' and see if there's any sign of its presence or any partitioning on it.
Or, as alternative to listing devices in /dev/disk as others have suggested, do 'cat /proc/partitions'. -- "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:
Or, as alternative to listing devices in /dev/disk as others have suggested, do 'cat /proc/partitions'.
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 8 32 2147483648 sdc The disk is sdc. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday May 6 2009, Per Inge Oestmoen wrote:
Felix Miata wrote:
Or, as alternative to listing devices in /dev/disk as others have suggested, do 'cat /proc/partitions'.
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 8 32 2147483648 sdc
The disk is sdc.
And there are no partitions. Compare it with sda[n] and sdb[n]. Where are you with this? Clearly the system has recognized the disk and integrated as much as possible into the known device configuration. Have you partitioned it? Until you do, you won't get further. Technically, of course, that's not true. You can use the unpartitioned device itself, but a terabyte is a largish file system volume (and an insane swap partition).
Per Inge Oestmoen, Norway
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 Wednesday, 2009-05-06 at 15:45 -0700, Randall R Schulz wrote:
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 8 32 2147483648 sdc
The disk is sdc.
And there are no partitions. Compare it with sda[n] and sdb[n].
Where are you with this? Clearly the system has recognized the disk and integrated as much as possible into the known device configuration.
Have you partitioned it? Until you do, you won't get further.
Technically, of course, that's not true. You can use the unpartitioned device itself, but a terabyte is a largish file system volume (and an insane swap partition).
I prefer "fdisk -l" to list partitions, it gives more information. However, I think Per said he connected the disk to a Vista machine and it worked. If the disk was already partitioned there, or even contains data, it would be a bad idea to try partitioning or formatting it in Linux. Now that I think, I remember he said he tried formatting it with YaST which saw the wrong size. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoCFoIACgkQtTMYHG2NR9XvEgCfdMqDQFhqhSvj4XLeq7opguxr TaEAoI5PX/Ul7FwWSjgXk/fb9NBAiDjw =bNUj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, May 6, 2009 at 7:00 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday, 2009-05-06 at 15:45 -0700, Randall R Schulz wrote:
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 8 32 2147483648 sdc
The disk is sdc.
And there are no partitions. Compare it with sda[n] and sdb[n].
Where are you with this? Clearly the system has recognized the disk and integrated as much as possible into the known device configuration.
Have you partitioned it? Until you do, you won't get further.
Technically, of course, that's not true. You can use the unpartitioned device itself, but a terabyte is a largish file system volume (and an insane swap partition).
I prefer "fdisk -l" to list partitions, it gives more information. However, I think Per said he connected the disk to a Vista machine and it worked. If the disk was already partitioned there, or even contains data, it would be a bad idea to try partitioning or formatting it in Linux.
Now that I think, I remember he said he tried formatting it with YaST which saw the wrong size.
- -- Cheers, Carlos E. R.
Have you guys considered the drive may have a GPT instead of a standard IBM Partition Table? They are the defacto standard for large drives and required for over 2TB drives. fdisk does NOT support them. Vista / Win 2008 does for non-boot drives. (Older does not.) Many / all Macs use GPT by default, even for the boot drive. Trouble is I don't know how to check for a GPT from Linux. (I have commercial tools I use that handle it transparently.) The linux kernel should autodetect a GPT I'm pretty sure, but who knows how often that gets tested. 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 Wednesday May 6 2009, Greg Freemyer wrote:
...
Have you guys considered the drive may have a GPT instead of a standard IBM Partition Table? They are the defacto standard for large drives and required for over 2TB drives.
fdisk does NOT support them. Vista / Win 2008 does for non-boot drives. (Older does not.)
Many / all Macs use GPT by default, even for the boot drive.
I think it became the default with the introduction of the Intel-based Macs, but I'm not sure about that.
Trouble is I don't know how to check for a GPT from Linux. (I have commercial tools I use that handle it transparently.)
You might try "file -s" (the -s means read the contents of device file rather than reporting that it is a device).
The linux kernel should autodetect a GPT I'm pretty sure, but who knows how often that gets tested.
I had the impression that my WD MyBook (1 TB) was GPT, but at the moment I'm not sure and while I have it connected to my openSUSE 11.1 box on an essentially permanent basis, I see no indication in /var/log/messages mentioning GPT. File says this: % file -s /dev/sde /dev/sde: x86 boot sector; partition 1: ID=0xaf, active, starthead 1, startsector 63, 976762584 sectors; partition 2: ID=0xa8, starthead 254, startsector 976762710, 976762458 sectors But if, as you say, fdisk doesn't support GPT, then the fact that it's happy with this drive suggests it's _not_ GPT.
Greg
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, May 6, 2009 at 7:32 PM, Randall R Schulz <rschulz@sonic.net> wrote:
But if, as you say, fdisk doesn't support GPT, then the fact that it's happy with this drive suggests it's _not_ GPT.
Quoting several messages ago: linux-k9na:/home/siberia # fdisk /dev/sdc Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel I don't call that fdisk being happy. 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 Wednesday May 6 2009, Greg Freemyer wrote:
On Wed, May 6, 2009 at 7:32 PM, Randall R Schulz wrote:
But if, as you say, fdisk doesn't support GPT, then the fact that it's happy with this drive suggests it's _not_ GPT.
Quoting several messages ago:
linux-k9na:/home/siberia # fdisk /dev/sdc Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
I don't call that fdisk being happy.
I meant my Western Digital 1 TB MyBook, not Per's recalcitrant drive.
Greg
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
I meant my Western Digital 1 TB MyBook, not Per's recalcitrant drive.
And now I have lost all contact with it. Finally I gave in, and attached it to a MacBook Pro. That machine could not detect any drive either. That disk spins and spins, but has now become completely inaccessible. Per Inge Oestmoen, Norway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/05/06 19:38 (GMT-0400) Greg Freemyer composed:
Randall R Schulz wrote:
But if, as you say, fdisk doesn't support GPT, then the fact that it's happy with this drive suggests it's _not_ GPT.
Quoting several messages ago:
linux-k9na:/home/siberia # fdisk /dev/sdc Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
I don't call that fdisk being happy.
That's it normal state when the first sector is all nulls, a common occurrence on a brand new HD with nothing yet written to it by any partitioner. ;-) -- "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:
That's it normal state when the first sector is all nulls, a common occurrence on a brand new HD with nothing yet written to it by any partitioner. ;-)
Understood. But this I fail to understand: ---- 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 ---- 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 01:58 (GMT+0200) Per Inge Oestmoen composed:
Felix Miata wrote:
That's it normal state when the first sector is all nulls, a common occurrence on a brand new HD with nothing yet written to it by any partitioner. ;-)
Understood.
But this I fail to understand:
---- 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
It simply means the device is not currently recognized. I don't know why, but I suspect any of several possibilities, among them: 1-too many attempts to connect and disconnect on a single boot 2-attempts to disconnect/connect too quickly 3-attempts to disconnect/connect too quickly while not using the same port 4-USB device failure 5-attempting to disconnect without executing a safe disconnect command of some sort 6-failed or incomplete cable connection I wouldn't give up without trying it again on a fresh boot, both with, and without it connected prior to booting. In the long run I suggest you consider a solution such as this: http://www.newegg.com/product/product.aspx?Item=N82E16817173043 I have 5 of them and have never used them in USB mode. They come with an adapter that provides an eSATA cable connection to the outside of the system, and an SATA cable to connect to an available internal SATA port. They do not support hot plug, but that is not a problem for me. OTOH, they are just as fast as any internal SATA HD directly connected to a motherboard port, which is several times faster than USB or firewire. -- "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
Greg Freemyer wrote:
Have you guys considered the drive may have a GPT instead of a standard IBM Partition Table? They are the defacto standard for large drives and required for over 2TB drives.
fdisk does NOT support them. Vista / Win 2008 does for non-boot drives. (Older does not.)
Many / all Macs use GPT by default, even for the boot drive.
Trouble is I don't know how to check for a GPT from Linux. (I have commercial tools I use that handle it transparently.)
The linux kernel should autodetect a GPT I'm pretty sure, but who knows how often that gets tested.
Good point, Greg. I've had recent experience with GPT. Yast's partitioner will create and work with them, as will the kernel once booted. The only problem was booting with grub. As long as your boot partition is non GPT there shouldn't be any problems. So Yast's partitioner might be able to work with this particular disk, if it is GPT. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-05-06 at 19:22 -0400, Greg Freemyer wrote:
Have you guys considered the drive may have a GPT instead of a standard IBM Partition Table? They are the defacto standard for large drives and required for over 2TB drives.
fdisk does NOT support them. Vista / Win 2008 does for non-boot drives. (Older does not.)
Many / all Macs use GPT by default, even for the boot drive.
Trouble is I don't know how to check for a GPT from Linux. (I have commercial tools I use that handle it transparently.)
According to the wikipedia: “A single partition type of 0xEE, encompassing the entire GPT drive, is indicated and identifies it as GPT”. <http://en.wikipedia.org/wiki/GUID_Partition_Table#Legacy_MBR_.28LBA_0.29>
The linux kernel should autodetect a GPT I'm pretty sure, but who knows how often that gets tested.
And perhaps that support was not included in openSUSE 11.0 - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoDNcMACgkQtTMYHG2NR9ViYQCePhRb+EbJpBFd6Gdlz/9IMIUe ZzAAn3jCm7qsZLRVTIpT/PAymKiAMRHy =knjJ -----END PGP SIGNATURE-----
On 2009/05/06 23:36 (GMT+0200) Per Inge Oestmoen composed:
Felix Miata wrote:
Or, as alternative to listing devices in /dev/disk as others have suggested, do 'cat /proc/partitions'.
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 8 32 2147483648 sdc
The disk is sdc.
So, you have no partitions on it, and thus you can't yet do any formatting, or "see" it normally. To "see" it currently you need a partitioning tool, so next step should be to create partitioning with such a tool. If YaST2 can't figure it out due to the largish 1T size, the USB interposition, or some bug, then use fdisk, cfdisk, parted, qparted, gparted, DFSee (the only tool I ever use to create partitions regardless of OS), Ranish, or any of several other tools designed for the task. The following one must or can operate from CD/DVD boot: http://gpartedclonz.tuxfamily.org/ http://www.ultimatebootcd.com/ http://www.dfsee.com/ http://www.knopper.net/knoppix/ (contains KDE3, fdisk, cfdisk, parted, qparted & gparted in 5.1.1 CD version) -- "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 Wednesday May 6 2009, Per Inge Oestmoen wrote:
Randall R Schulz wrote:
Only root can read /var/log/messages.
I then became root, and here is the result:
---- linux-k9na:/home/siberia # tail -f /var/log/messages May 6 17:04:06 linux-k9na kernel: usb 2-2: New USB device found, idVendor=152d, idProduct=2338 May 6 17:04:06 linux-k9na kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 May 6 17:04:06 linux-k9na kernel: usb 2-2: Product: USB to ATA/ATAPI Bridge May 6 17:04:06 linux-k9na kernel: usb 2-2: Manufacturer: JMicron May 6 17:04:06 linux-k9na kernel: usb 2-2: SerialNumber: 183D203370B9 May 6 17:04:07 linux-k9na kernel: scsi 9:0:0:0: Direct-Access PQ: 0 ANSI: 2 CCS May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: [sdc] Attached SCSI disk May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: Attached scsi generic sg4 type 0 May 6 17:04:07 linux-k9na kernel: usb-storage: device scan complete May 6 17:11:20 linux-k9na su: (to root) siberia on /dev/pts/2 May 6 17:11:40 linux-k9na smartd[3371]: Device: /dev/sda, 1 Currently unreadable (pending) sectors May 6 17:15:06 linux-k9na gconfd (siberia-20011): GConf server is not in use, shutting down. May 6 17:15:06 linux-k9na gconfd (siberia-20011): Exiting ----
[ As an aside, it's highly preferable that you inhibit line-wrapping for things like log file excerpts. I've rejoined the lines manually. ] Clearly your drive was detected and processed. What do you see when you look beneath /dev/disk? Use "ls -lR" to see it.
Per Inge Oestmoen, Norway
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Inge Oestmoen wrote:
Randall R Schulz wrote:
Only root can read /var/log/messages.
I then became root, and here is the result:
---- linux-k9na:/home/siberia # tail -f /var/log/messages May 6 17:04:06 linux-k9na kernel: usb 2-2: New USB device found, idVendor=152d, idProduct=2338 May 6 17:04:06 linux-k9na kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 May 6 17:04:06 linux-k9na kernel: usb 2-2: Product: USB to ATA/ATAPI Bridge May 6 17:04:06 linux-k9na kernel: usb 2-2: Manufacturer: JMicron May 6 17:04:06 linux-k9na kernel: usb 2-2: SerialNumber: 183D203370B9 May 6 17:04:07 linux-k9na kernel: scsi 9:0:0:0: Direct-Access PQ: 0 ANSI: 2 CCS May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: [sdc] Attached SCSI disk May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: Attached scsi generic sg4 type 0
So /dev/sdc is your 1Tb USB drive. /Per -- Per Jessen, Zürich (17.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-05-06 at 18:38 +0200, Per Jessen wrote:
May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: [sdc] Attached SCSI disk May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: Attached scsi generic sg4 type 0
So /dev/sdc is your 1Tb USB drive.
I don't thing so, because of the "sg4" thing. That's a CDrom :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoB5iIACgkQtTMYHG2NR9UksACeKFWLRil+g9rTe9S/RwCm46K0 y94AmgOoR7Sy284W9ZEXb2ZhNUNAvFY8 =/22n -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, May 6, 2009 at 3:33 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday, 2009-05-06 at 18:38 +0200, Per Jessen wrote:
May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: [sdc] Attached SCSI disk May 6 17:04:07 linux-k9na kernel: sd 9:0:0:0: Attached scsi generic sg4 type 0
So /dev/sdc is your 1Tb USB drive.
I don't thing so, because of the "sg4" thing. That's a CDrom :-?
sg is just scsi generic I have them in my dmesg output and I don't think I've connected up a usb dvd recently. 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2009-05-06 at 17:17 +0200, Per Inge Oestmoen wrote:
Only root can read /var/log/messages.
I then became root, and here is the result:
---- May 6 17:11:40 linux-k9na smartd[3371]: Device: /dev/sda, 1 Currently unreadable (pending) sectors
This is bad, very bad. Assuming the disk is good, as Vista can see it, I'd try with openSUSE 11.1 instead. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoB5aAACgkQtTMYHG2NR9UuDgCcCbhWSS0pIaqHTlxAGLEW1qjr EUMAoI0FBs1YX6PUpegCXxl22B87Zo8Z =mm2r -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Carlos E. R. -
Felix Miata -
Greg Freemyer -
Ionut Vancea -
Lew Wolfgang -
Per Inge Oestmoen -
Per Jessen -
Randall R Schulz -
Roger Oberholtzer