Hi,
With my 11.4 m6 kde 64bit install I get error when trying to access my external MyBook drive. Anyone else having issues with external drives with this release?
It also does something to the drive where I have to completely shut it down manually before any other operating system can see it.
I am using MyPassport without any problem. Do you have hal still installed?
(KDE 4.6 is hal-les)
To find it out as root please enter this into the terminal
zypper info hal
Is Hal not supposed to be installed I saw it load on boot. Does it need to be removed from this release?
I will have to do another install to check this out.
I tested my new USB-3.0 Fantec external hard drive with my new ASUS USB-3.0 PCI-e card with 11.4 M6, so I can say that works (with a 64-bit openSUSE-11.4 KDE4 liveCD). I also tested some USB-2.0 memory sticks (with both 32-bit and 64-bit openSUSE-KDE4 and 32-bit LXDE). I have not (yet) tested my external USB-2.0 nor Firewire hard drives with 11.4 M6.
Typically, when users have a problem with an exernal hard drive, to help our ‘experts’ give an assessment, WHEN the external USB drive is plugged in, the users will type as a regular user:
lsusb
and as root
fdisk -l
and also possibly put on a pastebin site the appropriate part from the dmesg, and advise as the exact desktop in use, where the install came from (DVD ? liveCD ? installed from liveCD ? etc … ). Without that its hard for anyone to make an assessment.
Having stated that, helping debug USB questions is beyond my expertise, especially if one has to dive into the innards of udev.
“M6 sees the completed removal of the HAL hardware abstraction layer, to be replaced with the more up-to-date and actively maintained udev, udisks and upower suite. HAL was already scheduled for removal in 11.3, but it was retained while the last few software packages which depend on it were ported to udev and company.”
Ok next go around with it (next few days) I will post the errors and info.
I just had a few hickups with 11.4 m6 however overall it seemed like a great system! I curious how gnome runs and will try that next probably.
Thank you.
I use a “My Passport”; mounts, reads, writes, <yada, yada> and unmounts safely. I also have several USB/HD caddies, same results: all OK.
The drive is hooked up fire wire:
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000bdcde
Device Boot Start End Blocks Id System
/dev/sdb1 63 594437129 297218533+ 7 HPFS/NTFS
/dev/sdb2 594437130 623113154 14338012+ 7 HPFS/NTFS
/dev/sdb3 623113155 1953520064 665203455 7 HPFS/NTFS
fdisk in 11.4 shows the above for the drive however I can not access it in 11.4 m6 kde. Works fine in 11.3.
Hmmm … I have not tested Firewire yet, and I have 4 external firewire drives (Seagates and Maxtors). I’ll test 11.4 M6 with firewire later this week.
Cool, thanks oldcpu.
Here are the errors I am getting when trying to open my MyBook with firewire 11.4 M6
An error occurred while accessing ‘101.4 GiB Removable Media’, the system responded: org.freedesktop.UDisks.Error.FilesystemDriverMissing: Error mounting: mount: /dev/sdf3 is not a valid block device
An error occurred while accessing ‘MyBook Files’, the system responded: org.freedesktop.UDisks.Error.Failed: Error mounting: mount exited with exit code 17: Error opening ‘/dev/sdf2’: No such device or address
Failed to mount ‘/dev/sdf2’: No such device or address
Either the device is missing or it’s powered down, or you have
SoftRAID hardware and must use an activated, different device under
/dev/mapper/, (e.g. /dev/mapper/nvidia_eahaabcc1) to mount NTFS.
Please see the ‘dmraid’ documentation for help.
My 1TB Seagate with Firefire works with the 64-bit openSUSE-11.4 M6 (build 1034) liveCD. After booting I plug the external firewire drive in, and I obtain notification it has been plugged in. Here is the relevant dmesg section:
383.217815] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
383.757393] firewire_core: created device fw1: GUID 002037020031f038, S400
383.769898] scsi8 : SBP-2 IEEE-1394
384.059476] firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries)
392.741806] scsi 8:0:0:0: Direct-Access Seagate FreeAgent XTreme 4113 PQ: 0 ANSI: 4
392.742028] sd 8:0:0:0: Attached scsi generic sg3 type 0
392.748683] sd 8:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
392.753818] sd 8:0:0:0: [sdb] Write Protect is off
392.753822] sd 8:0:0:0: [sdb] Mode Sense: 1c 00 00 00
392.757296] sd 8:0:0:0: [sdb] Cache data unavailable
392.757300] sd 8:0:0:0: [sdb] Assuming drive cache: write through
392.771713] sd 8:0:0:0: [sdb] Cache data unavailable
392.771717] sd 8:0:0:0: [sdb] Assuming drive cache: write through
392.801135] sdb: sdb1
392.893749] sd 8:0:0:0: [sdb] Cache data unavailable
392.893760] sd 8:0:0:0: [sdb] Assuming drive cache: write through
392.893763] sd 8:0:0:0: [sdb] Attached SCSI disk
and from “fdisk -l”
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x844f0716
Device Boot Start End Blocks Id System
/dev/sdb1 63 1953520064 976760001 7 HPFS/NTFS
and from “df -Th”
/dev/sdb1 fuseblk 932G 932G 320M 100% /media/FreeAgent Drive
So this appears it could be specific to your hardware and 11.4.
I recommend you write a bug report on this
Edit - YES, my drive IS full 
After booting I plug the external firewire drive in
That is the key phrase. If I boot with it no joy. If it is off on boot and then I plug fire wire in it works fine. Go figure.
Where do you bug 11.4 builds?
Ahhh … I always boot with the drive disconnected and OFF. I’ve never tried booting with the drive ON. With it being an NTFS drive, I am concerned if I do not properly unmount it first that I could cause problems (forcing a boot to MS-Windows to fix).
There is guidance for raising bugs on all openSUSE versions (including 11.4 which may be called factory in some cases) here: openSUSE:Submitting bug reports - openSUSE You can use your openSUSE user name and password when logging on to bugzilla. After you raise a bug report, please check in on it from time to time to see if there is a resolution. Sometimes the packager will ask for information, and the flag on the bug report status will change to “NEED INFO”. When that is the case, if possible provide the information, and then be certain to CLEAR the “NEED INFO” flag.
Thank you for any contributions here.
Ok thanks. 
About the drive I was wondering because it has always worked perfectly on boot with 11.3 and the problem just cropped up on 11.4.
Thank you for feedback.