i have a 1TB western digital portable hard drive. i have just tried plugging into suse machine…nothing. i have just tried plugging it into another machine, which has windows on it…nothing. the drive light comes on and i can hear the disk spinning.
this will be my second WD drive to fail :mad: this 1TB drive has nearly 800GB of stuff on it, most of which is backed up…but that’s not the point is it.
When it’s physically attached to the OpenSuSE box, what’s the output
of ‘fdisk -l’? Do you see a /dev/sdb or the like with the approximate
size? This might tell us if the device node(s) are being created for it.
menesofmemphis [at] gmail [dot] com
“Unity and humility is the lesson all of history teaches.”
well, this is very strange indeed. it turns out someone dropped the drive. i unplugged the drive. ran the tail command to show logs, it showed several (i didn’t count, roughly 6-7 though) lines of the device giving I/O errors at sector x (where x is a large number). i then replugged the device and it connected fine and showed. to start with it was not appearing in /dev as normal as /dev/sdb1. i opened some stuff and some files would not work (i thought maybe corrupted) but i unplugged it then replugged it and all data seems fine
however, one thing puzzles me a lot, a friends pc on windows simply detected the drive, and that was it, it did not install the drivers, i could not read the drive, in fact, no windows pc seems to (i have tried another vista machine without success); so the only machine which is able to read (and write) to the drive is my own suse linux box - which is windows free of course.
why on earth could only suse see and read/write from it? this is so strange, maybe you clever people have some ideas.
thanks for getting back. i believe the drive was turned off when dropped; i definitely know it was not connected to a machine, but it may have been plugged in. how do i run a disk check, from what i used to think the best way for disk check is using the install dvd, but on 10.3 i believe this is broken? are there any command line tools (or GUI??) which i can use once i use umount to unmount it, as it’s probably best to scan the drive whilst unmounted.
ah, will upload the avatar soon, forgot about that. not similar problem, that last one was a good drive, but it got locked out badly. this one, someone dropped it and it only seems to work under linux. not too much of an issue as i only use linux now, but if a friend of mine wants to borrow some stuff etc they can’t. new drive ordered at the expense of the person who dropped it lol.
which avatar to load…the linux inside one or the old tux doing something to a windows logo…hmmm lol
it’s not too much of an issue now since the person has ordered a new one for me, so since i can still use it for linux, i can transfer my stuff onto the next one hopefully. but…before i do so, what do you guys reckon regarding format? it comes as fat32 but…well that’s not that great, should i stick with vfat, or go ext3?
Actually it’ll be wise to choose your FS based on usage. For example, if you’re going to store lots of big files on it, then I’d suggest using XFS as it can deal better with those files than Ext3 can. XFS is also generally faster and has a lower fragmentation level than Ext3. Also XFS has a higher throughput than Ext3.
FAT32 is common on external drives. It may be for broad compatibility, but I’ve also seen software with such drives which only supports FAT32. In my experience - YMMV - it’s not been a problem reformatting with another filesystem, but you may lose the sw utilties that came with it. The biggest pain with FAT32 is the 4GB file size limitation. With a 1 TB drive, on some Windows systems in order to see the entire drive or even to just recognize it, can require an oem driver or a drive overlay.
If you want it usable with both Linux and W$, you can format it as NTFS on a W$ machine and then on SuSE use the ntfs-3g driver. If you will only use it on Linux, and you will not have a lot of very large files, ext3 is probably best.