USB disks no longer mount, unknown filesystem

Ran a routine weekly update on an arch box this morning, didn't think anything of it as usual. Until Thunar started spitting errors at me whenever I tried to mount a USB device. gvfs makes the devices appear in the left pane for one-click mounting... usually.
A partition on the hard drive attached has started telling me I don't have permissions to mount it any more - never had issues before, I'm in storage so I don't see why.
The other issue comes with a USB hard drive, and when trying to mount it as above, Thunar throws this at me:
Error mounting /dev/sdb1 at /run/media/pip/HD-PVU2: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid-100,shortname=mixed,dmask=0077,utf8=1,showexec" "/dev/sdb1" "/run/media/pip/HD-PVU2"' exited with non-zero exit status 32: mount: unknown filesystem type 'vfat'
Searching both pacman and AUR gave me no packages to do with vfat filesystems, and the wiki article "USB Storage Devices" provided no solutions at all.
Using XFCE4 DE on 32-bit Arch. All packages have been updated to latest versions as of the time of this post.

I probably experience the same kind of problem as you guys. I'm using udisksvm to mount USB drives and when I plug one, I get something like that:
$ udisksvm
Automounting for non optical devices enabled
Added object : /org/freedesktop/UDisks2/drives/Intenso_Basic_10011100031138
Added object : /org/freedesktop/UDisks2/block_devices/sdb
Added object : /org/freedesktop/UDisks2/block_devices/sdb1
Automounting /dev/sdb1...
Mounting failed with error:
GDBus.Error:org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform operation
traydvm for /org/freedesktop/UDisks2/block_devices/sdb1 now running with pid : 2694
/usr/lib/python2.7/site-packages/gi/types.py:47: Warning: g_variant_unref: assertion `value->ref_count > 0' failed
return info.invoke(*args, **kwargs)
$ udisksvm
Automounting for non optical devices enabled
Added object : /org/freedesktop/UDisks2/drives/Nokia_S60_359557013658840
Added object : /org/freedesktop/UDisks2/block_devices/sdb
Added interface on object : /org/freedesktop/UDisks2/block_devices/sdb
Automounting /dev/sdb...
Mounting failed with error:
GDBus.Error:org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform operation
traydvm for /org/freedesktop/UDisks2/block_devices/sdb now running with pid : 3025
/usr/lib/python2.7/site-packages/gi/types.py:47: Warning: g_variant_unref: assertion `value->ref_count > 0' failed
return info.invoke(*args, **kwargs)
And the device is not mounted automatically. I have the packages dosfstools, ntfs-3g, systemd-sysvcompat installed (I use systemd). Mounting manually from console works well.

Similar Messages

[SOLVED] mount: unknown filesystem type 'ext2'

I probably have the most complicated first-time arch setup that you'll ever hear a n00b post. XD
I just finished setting up an encrypted arch box with a usb boot drive (it contains the key-file), but when I go to boot, the system reports the following:
mount: unknown filesystem type 'ext2'
Of all the things to break! Ext2???!
This is for the default boot mode, when boot into the fallback initramfs mode, the arch box boots up fine (although it takes 2 whole minutes). I think that the issue is that I'm missing a module in my mkinitcpio.conf file.
/etc/fstab file:
UUID=1245ASDF / btrfs discard,autodefrag,compress=lzo,rw,relatime,ssd,space_cache 0 0
UUID=2245ASDF /boot ext2 rw,noatime 0 2
UUID=3245ASDF none swap defaults 0 0
/etc/mkinitcpio.conf file:
HOOKS="base btrfs udev autodetect modconf block encrypt lvm2 filesystems keyboard fsck"
/etc/default/grub file:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda:enc cryptkey=/dev/sdb2:ext2:/keyfile crypto=sha512:twofish-xts-plain64:512:0:"
Last edited by a-jamesregan (2015-04-13 19:15:48)

Wow, there was literally a note about the exact issue I was having on the wiki...
https://wiki.archlinux.org/index.php/Mkinitcpio#MODULES
Note: If using reiser4, it must be added to the modules list. Additionally, if you will be needing any file system during the boot process that is not live when you run mkinitcpio — for example, if your LUKS encryption key file is on an ext2 file system but no ext2 file systems are mounted when you run mkinitcpio — that file system module must also be added to the MODULES list. See Dm-crypt/System configuration#cryptkey for more details.
PS: How do I mark an issue as solved?
Last edited by a-jamesregan (2015-04-13 10:28:20)

BTRFS not mounting (unknown filesystem type)

Hi everyone,
From a USB drive I have been trying to install Arch in the fashion given in https://wiki.archlinux.org/index.php/In … Btrfs_root, I have upgraded the system to the newest kernel (3.3.6) and using the instructions created 2 partitions on /dev/sda. One being for Grub to boot the system, and the other being the btrfs.
I have been unable to mount the btrfs device (/dev/sda2), I keep getting the error
[root@archiso ~]# mount -o defaults,noatime /dev/sda2 /mnt/btrfs-root
mount: unknown filesystem type 'btrfs'
mount, i.e. util-linux is the newest version 2.21.1
any help is really appreciated

Well, I think the problem is caused by the loaded kernel being unable to find it's modules (the btrfs module included) because they got uninstalled when you upgraded the kernel package. You could try manually loading the module with modprobe (using -f if you get errors regarding versions), but I can't recommend that course of action, nor can I guarantee that it will fix your mounting problem.

Mount: unknown filesystem type 'LVM2_member'

I recently did a pacman -Syu with some consequences. I still had grub1 running and it was automatically upgraded to grub2, which is fine, but apparently grub-install was run on the mbr (I really think that was very inappropriate as that did break my system). Anyhow, on to chroot, I update /etc/default/grub as I have an LVM on top of an encrypted root and add this:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda5:VGarch"
and this to mkinitcpio.conf:
HOOKS="base udev autodetect fsck modconf block encrypt lvm2 filesystems"
then update both:
mkinitcpio -p linux
grub-mkconfig -o /boot/grub/grub.conf
and then update again for good measure while we're still in the chroot. However, upon reboot I get the ominous error message:
mount: unknown filesystem type ‘LVM2_member’
EDIT: i moved fsck behind filesystems in hooks with no effect
Last edited by thoth (2013-07-03 01:31:06)

Post the entire kernel command line you are using (/proc/cmdline).
Note that the upgrade to grub2 will not have automatically installed grub to disk. So if you have not installed grub to disk, you need to do that in order to configure it correctly.
i.e. grub-install was *not* run on the mbr as part of the package upgrade.
See /var/lib/pacman/local/grub-2.00.5043-2/install.
But your config file for the old grub will have been moved to a .pacsave when that package was removed by pacman.
Last edited by cfr (2013-07-07 23:28:53)

Mounting problem, mount: unknown filesystem type 'vfat'

Can't mount vfat partition.
Mounting problem, mount: unknown filesystem type 'vfat'

takavar wrote:sorry for the necromancy, but this is the top result on Google search with no answer.
I am going to close this thread because (a) the thread is more than two years old, abd (b) may or may not be related to your problem.
Please open a new thread detailing your problem. Define what is "Solved" by rebooting. Does the drive mount during a reboot? Tell us how you are trying to mount the drive, and provide us your /etc/fstab. You may want to share the the output of sudo fdisk -l /dev/sda
If you still think it relevant. provide a link back to this thread.
Thanks

USB disk won't mount on startup (have tried everything)

Hi!
I'm having big problems getting my USB disk to mount on startup.:(
It used to work perfectly by having 'mount /dev/sdc1 /media/disk' in rc.local (and umount in local.shutdown) but recently it started saying that 'filesystem type must be defined' (or something like that). So I changed the line to 'mount -t ext3 /dev/sdc1 /media/disk' but now I get a message that '/dev/sdc1 does not exist'.
So I decided to get this fixed in fstab once and for all.
I checked the designations of the disks with 'fdisk -l' and noticed that the USB disk would alternate between /dev/sdc, /dev/sde and /dev/sdd quite random on every reboot. In other words I couldn't mount it in fstab by using one of those paths cause I'd get the same problem with '/dev/sdc or -e or -d does not exist'. I figured the sollution must be to mount the disk by using UUID. I checked the uuid's and got the following (as you can see the USB disk is on this reboot registered as '/dev/sde'):
bash-3.2$ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 2009-02-07 11:56 6cf5e803-429a-44c3-bcf9-0f007df623f3 -> ../../sda1
lrwxrwxrwx 1 root root 10 2009-02-07 11:56 8ef6be20-ee30-4a00-8946-56a4d94a7245 -> ../../sda3
lrwxrwxrwx 1 root root 10 2009-02-07 11:56 947b3b86-8501-4011-9da2-4de45eb4ed60 -> ../../sda2
lrwxrwxrwx 1 root root 10 2009-02-07 11:56 94911fb3-def7-4440-b6a5-5e09f91b19f6 -> ../../sde1
lrwxrwxrwx 1 root root 10 2009-02-07 11:56 acd197d3-f63e-48f9-88de-41eff1b3b425 -> ../../sda4
lrwxrwxrwx 1 root root 10 2009-02-07 11:56 b6745703-bde6-44ef-865d-d09501ecc8ab -> ../../sdb1
I other words the UUID of the disk should be '94911fb3-def7-4440-b6a5-5e09f91b19f6' so I added that to the fstab file, but I still get the same error that the disk doesn't exist. How is this possible? Isn't the UUID supposed to be the same no matter what? When the disk is clearly labeled with this UUID every time I check it why can't it be used in fstab??
Here's my fstab (I've commented out the lines that I've been trying out):
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 ro,user,noauto,unhide 0 0
/dev/dvd /mnt/dvd udf ro,user,noauto,unhide 0 0
/dev/sda1 /boot ext2 defaults 0 1
/dev/sda2 / ext3 defaults 0 1
/dev/sda3 /var reiserfs defaults 0 1
/dev/sda4 /home ext3 defaults 0 1
/dev/sdb1 /extra ext3 defaults 0 1
#/dev/sdc1 /media/disk defaults 0 0
#UUID=94911fb3-def7-4440-b6a5-5e09f91b19f6 /media/disk defaults 0 0
What am I doing wrong here? I've also tried to use different options like 'rw,auto,exec' but it won't work.

It seems I'm able to mount the disk from the terminal by doing '# sudo mount UUID=94911fb3-def7-4440-b6a5-5e09f91b19f6 /media/disk'.
But this only works when I do it manually. Adding 'mount UUID=94911fb3-def7-4440-b6a5-5e09f91b19f6 /media/disk' to rc.local only gives the error that filesystem must be defined and when it's defined I get the error that device is not found.
How can it work manually, but not in fstab or rc.local?
Here's my dmesg:
BIOS EBDA/lowmem at: 0009f800/0009f400
Linux version 2.6.28-ARCH (root@T-POWA-LX) (gcc version 4.3.3 (GCC) ) #1 SMP PREEMPT Mon Feb 2 22:22:59 UTC 2009
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
NSC Geode by NSC
Cyrix CyrixInstead
Centaur CentaurHauls
Transmeta GenuineTMx86
Transmeta TransmetaCPU
UMC UMC UMC UMC
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007fef0000 (usable)
BIOS-e820: 000000007fef0000 - 000000007fef3000 (ACPI NVS)
BIOS-e820: 000000007fef3000 - 000000007ff00000 (ACPI data)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
DMI 2.4 present.
Phoenix BIOS detected: BIOS may corrupt low RAM, working it around.
last_pfn = 0x7fef0 max_arch_pfn = 0x100000
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Scanning 0 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009f400 (usable)
modified: 000000000009f400 - 00000000000a0000 (reserved)
modified: 00000000000f0000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 000000007fef0000 (usable)
modified: 000000007fef0000 - 000000007fef3000 (ACPI NVS)
modified: 000000007fef3000 - 000000007ff00000 (ACPI data)
modified: 00000000e0000000 - 00000000f0000000 (reserved)
modified: 00000000fec00000 - 0000000100000000 (reserved)
kernel direct mapping tables up to 377fe000 @ 10000-16000
RAMDISK: 7fe0e000 - 7fedf2e4
Allocated new RAMDISK: 0055f000 - 006302e4
Move RAMDISK from 000000007fe0e000 - 000000007fedf2e3 to 0055f000 - 006302e3
ACPI: RSDP 000F8600, 0014 (r0 HP-CPC)
ACPI: RSDT 7FEF3040, 0038 (r1 HP-CPC AWRDACPI 42302E31 AWRD 0)
ACPI: FACP 7FEF30C0, 0084 (r2 HP-CPC AWRDACPI 42302E31 AWRD 0)
ACPI: DSDT 7FEF31C0, 3C55 (r1 HP-CPC AWRDACPI 1000 MSFT 100000E)
ACPI: FACS 7FEF0000, 0040
ACPI: SSDT 7FEF6F40, 01CA (r1 HP-CPC POWERNOW 1 LTP 1)
ACPI: SRAT 7FEF7180, 00A0 (r1 HP-CPC HAMMER 1 AMD 1)
ACPI: MCFG 7FEF7280, 003C (r1 HP-CPC AWRDACPI 42302E31 AWRD 0)
ACPI: APIC 7FEF6E80, 0068 (r1 HP-CPC AWRDACPI 42302E31 AWRD 0)
ACPI: Local APIC address 0xfee00000
1158MB HIGHMEM available.
887MB LOWMEM available.
mapped low ram: 0 - 377fe000
low ram: 00000000 - 377fe000
bootmap 00012000 - 00018f00
(9 early reservations) ==> bootmem [0000000000 - 00377fe000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
#2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
#3 [0000100000 - 000055b520] TEXT DATA BSS ==> [0000100000 - 000055b520]
#4 [000055c000 - 000055f000] INIT_PG_TABLE ==> [000055c000 - 000055f000]
#5 [000009f400 - 0000100000] BIOS reserved ==> [000009f400 - 0000100000]
#6 [0000010000 - 0000012000] PGTABLE ==> [0000010000 - 0000012000]
#7 [000055f000 - 00006302e4] NEW RAMDISK ==> [000055f000 - 00006302e4]
#8 [0000012000 - 0000019000] BOOTMAP ==> [0000012000 - 0000019000]
found SMP MP-table at [c00f46e0] 000f46e0
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
Normal 0x00001000 -> 0x000377fe
HighMem 0x000377fe -> 0x0007fef0
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x0007fef0
On node 0 totalpages: 523903
free_area_init_node: node 0, pgdat c0406600, node_mem_map c1000200
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3951 pages, LIFO batch:0
Normal zone: 1744 pages used for memmap
Normal zone: 221486 pages, LIFO batch:31
HighMem zone: 2318 pages used for memmap
HighMem zone: 294372 pages, LIFO batch:31
Movable zone: 0 pages used for memmap
SB4X0 revision 0x11
Ignoring ACPI timer override.
If you got timer trouble try acpi_use_timer_override
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: BIOS IRQ0 pin2 override ignored.
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 21 low level)
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
SMP: Allowing 2 CPUs, 0 hotplug CPUs
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
Allocating PCI resources starting at 80000000 (gap: 7ff00000:60100000)
PERCPU: Allocating 36864 bytes of per cpu data
NR_CPUS: 16, nr_cpu_ids: 2, nr_node_ids 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 519809
Kernel command line: root=/dev/sda2 ro quiet
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Fast TSC calibration using PIT
Detected 2188.552 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Scanning for low memory corruption every 60 seconds
Memory: 2072040k/2096064k available (2227k kernel code, 22632k reserved, 1026k data, 332k init, 1186760k highmem)
virtual kernel memory layout:
fixmap : 0xffee8000 - 0xfffff000 (1116 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
.init : 0xc0433000 - 0xc0486000 ( 332 kB)
.data : 0xc032cfd9 - 0xc042db5c (1026 kB)
.text : 0xc0100000 - 0xc032cfd9 (2227 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Calibrating delay loop (skipped), value calculated using timer frequency.. 4378.48 BogoMIPS (lpj=7295173)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Checking 'hlt' instruction... OK.
ACPI: Core revision 20080926
ACPI: Checking initramfs for custom DSDT
..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 01
Booting processor 1 APIC 0x1 ip 0x6000
Initializing CPU#1
Calibrating delay using timer specific routine.. 4379.66 BogoMIPS (lpj=7295468)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 01
Brought up 2 CPUs
Total of 2 processors activated (8757.15 BogoMIPS).
net_namespace: 768 bytes
Booting paravirtualized kernel on bare hardware
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
PCI: MCFG area at e0000000 reserved in E820
PCI: Using MMCONFIG for extended config space
PCI: Using configuration type 1 for base access
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:00.0: reg 18 io port: [0x4100-0x411f]
pci 0000:00:00.0: reg 1c 64bit mmio: [0xe0000000-0xffffffff]
pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
pci 0000:00:02.0: PME# disabled
pci 0000:00:12.0: reg 10 io port: [0xfe00-0xfe07]
pci 0000:00:12.0: reg 14 io port: [0xfd00-0xfd03]
pci 0000:00:12.0: reg 18 io port: [0xfc00-0xfc07]
pci 0000:00:12.0: reg 1c io port: [0xfb00-0xfb03]
pci 0000:00:12.0: reg 20 io port: [0xfa00-0xfa0f]
pci 0000:00:12.0: reg 24 32bit mmio: [0xfe02f000-0xfe02f1ff]
pci 0000:00:12.0: reg 30 32bit mmio: [0x000000-0x07ffff]
pci 0000:00:12.0: supports D1 D2
pci 0000:00:13.0: reg 10 32bit mmio: [0xfe02e000-0xfe02efff]
pci 0000:00:13.1: reg 10 32bit mmio: [0xfe02d000-0xfe02dfff]
pci 0000:00:13.2: reg 10 32bit mmio: [0xfe02c000-0xfe02cfff]
pci 0000:00:13.2: supports D1 D2
pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
pci 0000:00:13.2: PME# disabled
pci 0000:00:14.0: reg 10 io port: [0x500-0x50f]
pci 0000:00:14.0: reg 14 32bit mmio: [0xfe02b000-0xfe02b3ff]
HPET not enabled in BIOS. You might try hpet=force boot option
pci 0000:00:14.1: reg 10 io port: [0x00-0x07]
pci 0000:00:14.1: reg 14 io port: [0x00-0x03]
pci 0000:00:14.1: reg 18 io port: [0x00-0x07]
pci 0000:00:14.1: reg 1c io port: [0x00-0x03]
pci 0000:00:14.1: reg 20 io port: [0xf800-0xf80f]
pci 0000:01:00.0: reg 10 32bit mmio: [0xfa000000-0xfaffffff]
pci 0000:01:00.0: reg 14 64bit mmio: [0xd0000000-0xdfffffff]
pci 0000:01:00.0: reg 1c 64bit mmio: [0xfb000000-0xfbffffff]
pci 0000:01:00.0: reg 24 io port: [0xef00-0xef7f]
pci 0000:01:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
pci 0000:00:02.0: bridge io port: [0xe000-0xefff]
pci 0000:00:02.0: bridge 32bit mmio: [0xfa000000-0xfcffffff]
pci 0000:00:02.0: bridge 64bit mmio pref: [0xd0000000-0xdfffffff]
pci 0000:02:01.0: reg 10 io port: [0xdf00-0xdfff]
pci 0000:02:01.0: supports D1 D2
pci 0000:02:03.0: reg 10 io port: [0xde00-0xdeff]
pci 0000:02:03.0: reg 14 32bit mmio: [0xfdeff000-0xfdeff0ff]
pci 0000:02:03.0: reg 30 32bit mmio: [0x000000-0x00ffff]
pci 0000:02:03.0: supports D1 D2
pci 0000:02:03.0: PME# supported from D1 D2 D3hot D3cold
pci 0000:02:03.0: PME# disabled
pci 0000:02:04.0: reg 10 32bit mmio: [0xfdefe000-0xfdefe7ff]
pci 0000:02:04.0: reg 14 io port: [0xdd00-0xdd7f]
pci 0000:02:04.0: supports D2
pci 0000:02:04.0: PME# supported from D2 D3hot D3cold
pci 0000:02:04.0: PME# disabled
pci 0000:00:14.4: transparent bridge
pci 0000:00:14.4: bridge io port: [0xd000-0xdfff]
pci 0000:00:14.4: bridge 32bit mmio: [0xfde00000-0xfdefffff]
pci 0000:00:14.4: bridge 32bit mmio pref: [0xfdd00000-0xfddfffff]
bus 00 -> node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *10 11)
ACPI: PCI Interrupt Link [LNKF] (IRQs *3 4 5 6 7 10 11)
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 *11)
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled.
PCI: Using ACPI for IRQ routing
pci 0000:00:00.0: BAR 3: can't allocate resource
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:09: mem resource (0xf0000-0xf3fff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
pnp 00:09: mem resource (0xf4000-0xf7fff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
pnp 00:09: mem resource (0xf8000-0xfbfff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
pnp 00:09: mem resource (0xfc000-0xfffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
pnp 00:09: mem resource (0x0-0x9ffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
pnp 00:09: mem resource (0x100000-0x7feeffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
pnp: PnP ACPI: found 10 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: ioport range 0x228-0x22f has been reserved
system 00:01: ioport range 0x40b-0x40b has been reserved
system 00:01: ioport range 0x4d6-0x4d6 has been reserved
system 00:01: ioport range 0xc00-0xc01 has been reserved
system 00:01: ioport range 0xc14-0xc14 has been reserved
system 00:01: ioport range 0xc50-0xc52 has been reserved
system 00:01: ioport range 0xc6c-0xc6d has been reserved
system 00:01: ioport range 0xc6f-0xc6f has been reserved
system 00:01: ioport range 0xcd4-0xcdf has been reserved
system 00:01: ioport range 0x4000-0x40fe has been reserved
system 00:01: ioport range 0x4210-0x4217 has been reserved
system 00:06: ioport range 0x4d0-0x4d1 has been reserved
system 00:06: ioport range 0x800-0x87f has been reserved
system 00:08: iomem range 0xe0000000-0xefffffff has been reserved
system 00:09: iomem range 0x7ff00000-0x7fffffff has been reserved
system 00:09: iomem range 0x7fef0000-0x7fefffff could not be reserved
system 00:09: iomem range 0xffff0000-0xffffffff has been reserved
system 00:09: iomem range 0xfec00000-0xfec00fff has been reserved
system 00:09: iomem range 0xfee00000-0xfee00fff has been reserved
system 00:09: iomem range 0xfff80000-0xfffeffff has been reserved
pci 0000:00:02.0: PCI bridge, secondary bus 0000:01
pci 0000:00:02.0: IO window: 0xe000-0xefff
pci 0000:00:02.0: MEM window: 0xfa000000-0xfcffffff
pci 0000:00:02.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff
pci 0000:00:14.4: PCI bridge, secondary bus 0000:02
pci 0000:00:14.4: IO window: 0xd000-0xdfff
pci 0000:00:14.4: MEM window: 0xfde00000-0xfdefffff
pci 0000:00:14.4: PREFETCH window: 0x000000fdd00000-0x000000fddfffff
pci 0000:00:02.0: setting latency timer to 64
bus: 00 index 0 io port: [0x00-0xffff]
bus: 00 index 1 mmio: [0x000000-0xffffffff]
bus: 01 index 0 io port: [0xe000-0xefff]
bus: 01 index 1 mmio: [0xfa000000-0xfcffffff]
bus: 01 index 2 mmio: [0xd0000000-0xdfffffff]
bus: 01 index 3 mmio: [0x0-0x0]
bus: 02 index 0 io port: [0xd000-0xdfff]
bus: 02 index 1 mmio: [0xfde00000-0xfdefffff]
bus: 02 index 2 mmio: [0xfdd00000-0xfddfffff]
bus: 02 index 3 io port: [0x00-0xffff]
bus: 02 index 4 mmio: [0x000000-0xffffffff]
NET: Registered protocol family 2
Switched to high resolution mode on CPU 0
Switched to high resolution mode on CPU 1
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Unpacking initramfs... done
Freeing initrd memory: 836k freed
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
apm: disabled - APM is not SMP safe.
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 1732
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:00:00.0: MSI quirk detected; MSI disabled
pci 0000:01:00.0: Boot video device
pcieport-driver 0000:00:02.0: setting latency timer to 64
pcieport-driver 0000:00:02.0: found MSI capability
pci_express 0000:00:02.0:pcie00: allocate port service
pci_express 0000:00:02.0:pcie01: allocate port service
pci_express 0000:00:02.0:pcie03: allocate port service
aer 0000:00:02.0:pcie01: AER service couldn't init device: no _OSC support
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver4 ports, IRQ sharing disabled
input: Macintosh mouse button emulation as /class/input/input0
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
Using IPI No-Shortcut mode
registered taskstats version 1
Freeing unused kernel memory: 332k freed
SCSI subsystem initialized
libata version 3.00 loaded.
pata_acpi 0000:00:12.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
pata_acpi 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
scsi0 : pata_atiixp
scsi1 : pata_atiixp
ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf800 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf808 irq 15
ata2.00: ATAPI: HP DVD Writer 740b, ED24, max UDMA/33
ata2.00: configured for UDMA/33
scsi 1:0:0:0: CD-ROM HP DVD Writer 740b ED24 PQ: 0 ANSI: 5
sata_sil 0000:00:12.0: version 2.3
scsi2 : sata_sil
scsi3 : sata_sil
ata3: SATA max UDMA/100 mmio m512@0xfe02f000 tf 0xfe02f080 irq 22
ata4: SATA max UDMA/100 mmio m512@0xfe02f000 tf 0xfe02f0c0 irq 22
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/100
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ATA-7: WDC WD2500JS-60MHB1, 10.02E01, max UDMA/100
ata4.00: 488397168 sectors, multi 16: LBA48
ata4.00: configured for UDMA/100
scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
scsi 3:0:0:0: Direct-Access ATA WDC WD2500JS-60M 10.0 PQ: 0 ANSI: 5
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:13.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19
ehci_hcd 0000:00:13.2: EHCI Host Controller
ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:13.2: irq 19, io mem 0xfe02c000
Driver 'sd' needs updating - please use bus_type methods
sd 2:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda:<6>ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci_hcd 0000:00:13.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
ohci_hcd 0000:00:13.0: OHCI Host Controller
ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:13.0: irq 19, io mem 0xfe02e000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
ohci_hcd 0000:00:13.1: PCI INT A -> GSI 19 (level, low) -> IRQ 19
ohci_hcd 0000:00:13.1: OHCI Host Controller
ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:13.1: irq 19, io mem 0xfe02d000
sda1 sda2 sda3 sda4
sd 2:0:0:0: [sda] Attached SCSI disk
sd 3:0:0:0: [sdb] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:0:0:0: [sdb] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 3:0:0:0: [sdb] Attached SCSI disk
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 4 ports detected
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
usb 1-7: new high speed USB device using ehci_hcd and address 5
usb 1-7: configuration #1 chosen from 1 choice
rtc_cmos 00:03: RTC can wake from S4
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, 242 bytes nvram
usb 2-2: new low speed USB device using ohci_hcd and address 2
usb 2-2: configuration #1 chosen from 1 choice
8139too Fast Ethernet driver 0.9.28
8139too 0000:02:03.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
eth0: RealTek RTL8139 at 0xf8182000, 00:13:d3:88:fb:ec, IRQ 20
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
lirc_dev: IR Remote Control driver registered, major 61
lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.44 $
lirc_mceusb2: Daniel Melander <[email protected]>, Martin Blatter <[email protected]>
usbcore: registered new interface driver lirc_mceusb2
usb 3-1: new full speed USB device using ohci_hcd and address 2
C-Media PCI 0000:02:01.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
usb 3-1: configuration #1 chosen from 1 choice
input: Power Button (FF) as /class/input/input1
usb 3-1: reset full speed USB device using ohci_hcd and address 2
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input2
ACPI: Power Button (CM) [PWRB]
processor ACPI_CPU:00: registered as cooling_device0
ACPI: Processor [CPU0] (supports 8 throttling states)
processor ACPI_CPU:01: registered as cooling_device1
ACPI: Processor [CPU1] (supports 8 throttling states)
lirc_dev: lirc_register_plugin: sample_rate: 0
lirc_mceusb2[2]: Philips eHome Infrared Transceiver on usb3:2
usb 3-2: new low speed USB device using ohci_hcd and address 3
usb 3-2: configuration #1 chosen from 1 choice
usb 3-4: new full speed USB device using ohci_hcd and address 4
usb 3-4: configuration #1 chosen from 1 choice
Linux agpgart interface v0.103
usbcore: registered new interface driver hiddev
scsi 1:0:0:0: Attached scsi generic sg0 type 5
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 3:0:0:0: Attached scsi generic sg2 type 0
input: Logitech HID compliant keyboard as /class/input/input3
generic-usb 0003:046D:C30E.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech HID compliant keyboard] on usb-0000:00:13.0-2/input0
parport_pc 00:07: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,EPP]
input: Logitech HID compliant keyboard as /class/input/input4
generic-usb 0003:046D:C30E.0002: input,hidraw1: USB HID v1.10 Device [Logitech HID compliant keyboard] on usb-0000:00:13.0-2/input1
input: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) as /class/input/input5
generic-usb 0003:045E:0047.0003: input,hidraw2: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb-0000:00:13.1-2/input0
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
nvidia: module license 'NVIDIA' taints kernel.
piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x500, revision 0
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
input: PC Speaker as /class/input/input6
Initializing USB Mass Storage driver...
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
scsi5 : 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
ohci1394 0000:02:04.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21] MMIO=[fdefe000-fdefe7ff] Max Packet=[2048] IR/IT contexts=[4/8]
Error: Driver 'pcspkr' is already registered, aborting...
lp0: using parport0 (interrupt-driven).
ppdev: user-space parallel port driver
nvidia 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
nvidia 0000:01:00.0: setting latency timer to 64
NVRM: loading NVIDIA UNIX x86 Kernel Module 180.22 Tue Jan 6 09:29:08 PST 2009
EXT3 FS on sda2, internal journal
ReiserFS: sda3: found reiserfs format "3.6" with standard journal
ReiserFS: sda3: using ordered data mode
ReiserFS: sda3: journal params: device sda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda3: checking transaction log (sda3)
ReiserFS: sda3: Using r5 hash to sort names
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0010dc0000bc42b8]
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
scsi 5:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
sd 5:0:0:0: [sdc] Attached SCSI removable disk
sd 5:0:0:0: Attached scsi generic sg3 type 0
scsi 5:0:0:1: Direct-Access Generic USB CF Reader 1.01 PQ: 0 ANSI: 0
scsi 4:0:0:0: Direct-Access ST316002 3A 8.01 PQ: 0 ANSI: 0
sd 5:0:0:1: [sdd] Attached SCSI removable disk
sd 5:0:0:1: Attached scsi generic sg4 type 0
scsi 5:0:0:2: Direct-Access Generic USB SM Reader 1.02 PQ: 0 ANSI: 0
sd 4:0:0:0: [sde] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
sd 4:0:0:0: [sde] Write Protect is off
sd 4:0:0:0: [sde] Mode Sense: 03 00 00 00
sd 4:0:0:0: [sde] Assuming drive cache: write through
sd 4:0:0:0: [sde] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
sd 4:0:0:0: [sde] Write Protect is off
sd 4:0:0:0: [sde] Mode Sense: 03 00 00 00
sd 4:0:0:0: [sde] Assuming drive cache: write through
sde: sde1
sd 4:0:0:0: [sde] Attached SCSI disk
sd 4:0:0:0: Attached scsi generic sg5 type 0
usb-storage: device scan complete
sd 5:0:0:2: [sdf] Attached SCSI removable disk
sd 5:0:0:2: Attached scsi generic sg6 type 0
scsi 5:0:0:3: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
sd 5:0:0:3: [sdg] Attached SCSI removable disk
sd 5:0:0:3: Attached scsi generic sg7 type 0
usb-storage: device scan complete
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
eth0: no IPv6 routers present
kjournald starting. Commit interval 5 seconds
EXT3 FS on sde1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
TCP(wget:15427): Application bug, race in MSG_PEEK.
TCP(wget:18681): Application bug, race in MSG_PEEK.
TCP(wget:4122): Application bug, race in MSG_PEEK.
TCP(wget:4275): Application bug, race in MSG_PEEK.
TCP(wget:19451): Application bug, race in MSG_PEEK.

Disk won't mount - Unknown USB Device (Link in Compliance Mode)

I have an HP Envy DV7 (dv7-7243cl ) with Windows 8 Pro x64. My Western Digital 2 terabyte My Book USB3.0 external drive periodically won't mount ( sometimes it will, sometimes it won't). The drive has its own power source.
When this happens Windows device manager shows - Unknown USB Device (Link in Compliance Mode). This can happen if the system is up and running and I plug the drive into the USB port or on system startup where the drive is already plugged in.
Any clue how to fix this?
Other details:
Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz
12 Gig memory
Intel(R) HD Graphics 4000
System board 181C 52.24
Bios F.26

Well, the problem is that - as outlined in one of the articles I linked to - some USB devices will not work in Safe Mode; that may have to do with the fact the Safe Mode is only meant to be a troubleshooting tool, not a regular way of booting up. Did you have the USB devices attached while upgrading to 10.6? That would also be a problem - I unplug everything except keyboard and mouse.And, did you repair permissions after the upgrade? If not, do it now.
And, the other problem is the fact that you wait 1 - 2 years before addressing the issue; when you had it in for the last repair and it still exhibited the same problems afterwards, you should would have taken it back, possibly with some screenshots, exact notes of how/when/error messages, etc. and insisted on having it fixed or replaced.
So, I'd run the Apple Hardware Test (after you make sure that you have a complete backup) - instructions here:
http://support.apple.com/kb/HT1509
Report back with whatever messages you wind up with.

External USB HD no longer mounts

Hi - I've been using a Seagate Free Agent Desk 1TB external USB drive on my Intel iMac for a little over a year without any significant problems. Sometimes, in the past, it might come unmounted for some reason, maybe a power surge or something but would always remount without problem if shut down, etc.. About a week ago I tried to access a recent file on the external drive and nothing was there. I did a restart and got a message to the effect that "Drive not recognized, Ignore, Eject, Initialize", you know the one. I ignored. Since this time I have been unable to get the drive to mount. Nothing has been changed in the computer, no updates, or changes. The computer is kept on at all times and everything else continued to function as normal.
I have tried everything that I can think of and anything I have seen recommended i.e.: Restart, Shut Down, reset PRAM, reset SMC, USB Prober, verify & repair permissions, delete DiskUtility.plist, delete caches, etc.. About the only thing I've come across and haven't tried is to load older versions of the "drivers" using Pacifist. There didn't seem to be any really reason for that since it had been functioning fine with the current version. The disc "shows up" in System Profiler and Disc Utility but, if you try to Mount it...nothing. When an attempt is made to Verify or Repair in Disc Utility, the following messages are received: "Error: The underlying task reported failure on exit." and "1 Non HFS volume checked. 1 Volume could not be repaired because of an error.". I downloaded Boomerang to see if the demo version could tell me anything but it too recognizes the disc but, when it scans it, seems to hang up at 0%.
This drive is mostly used for back ups so I don't really want to have to invest in data recovery / expensive recovery programs. My impression, since the drive seems to "be there", is that the "Header File" (or some such) has just gotten corrupted and, if it could be reset, everything would be OK. Unfortunately, I can't seem to find a way to do that. If anyone has any other ideas, I would love to hear them before I have to resort to reformatting. As I said, it's mostly just back ups but I know I'm going to loose something important that I've forgotten about so I hate to just wipe it all.
Thanks in advance,
Kevin King

Have you tried another cable and have you attempted to connect it to another computer? If neither solution works then yes the drive has probably failed. I'd recommend possibly investing in a higher quality drive something like a:
OWC (www.macsales.com) Mercury Elite Pro series
or
Lacie Quadra D2 series
or
G-Tech G series
all are high quality products with similar features and build quality. Personally I use Lacie however I wouldn't hesitate with either of the others.
Roger

[Solved]Wont boot after installing syslinux; unknown filesystem 'swap'

After installing syslinux to be my boot manager I can no longer boot into Arch, I can however boot into Windows 7. When I try to boot into Arch I get the following error.
Loading ../vmlinuz-linux......
Loading ../initramfs-linux.img......ready.
Probing EDD (edd=off to disable)... ok
Decompressing Linux... Parsing ELF... done
Booting the kernel.
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
:: performing fsck on '/dev/sda3'
fsck: fsck.swap: not found
fsck: error 2 while executing fsck.swap for /dev/sda3
ERROR: fsck failed on 'dev/sda3'
:: mounting '/dev/sda3' on real root
mount: unknown filesystem type 'swap'
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs /]#
What's going on?
Last edited by slughappy1 (2012-07-05 22:50:35)

loafer wrote:Can you post your syslinux.cfg please.
Surely
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 1 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux-fallback.img
LABEL windows
MENU LABEL Windows7
COM32 chain.c32
APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com

Unknown filesystem error [solved]

I just updated arch and now when I try to mount my usb harddrive I get this error:
# mount /mnt/usbdrive
mount: unknown filesystem type 'vfat'
Anyone know whats up?

I met the same problem.
the key is that the kernel is updated ( e.g. from 2.23 -> 2.24 ).
the vfat kernel module reside in difference directory (/lib/modules/XXXx-2.24/)after update.
but the kernel version in /proc is the old one , until you reboot.
if you don't reboot, when load the vfat module, the insmod will search the /lib/modules/`uname -r` , which can found nothing to load. well, what you get is nothing but some string like
# modprobe vfat
FATAL: Could not load /lib/modules/2.6.23-ARCH/modules.dep: No such file or directory.
so, you can understand why you are happy now.

Can't boot after system update: unknown filesystem type

After running a system update, including updating the kernel, I can't boot to the new kernel.
On booting, grub loads the kernel image, runs/loads udev, but then fails to mount the root partition with error:
mount: unknown filesystem type 'ext4'
I have tried reinstalling the 'linux' package via packman several times, also trying the --recursive argument to make sure all my dependencies were there, and after days of googling and tweaking my system, I'm at a loss.
Thank goodness I happened to keep a spare kernel laying around in /boot.
Thanks in advance.
Last edited by jackrabbit (2012-03-22 23:25:28)

The OP can read their partition initially though, it's only after udev that they can't.
Also, try adding "rootfstype=ext4" to your grub kernel line. Is your /boot on a separate partition or part of your / partition?

Unknown filesystem type crypto_LUKS

Hi, I have spare space on my HD so I decided to experiment with encryption following this wiki:
https://wiki.archlinux.org/index.php/dm-crypt_with_LUKS
In summary:
created boot (sda6) and root (sda7) partitions
formatted boot as ext2 and root with passphrase and then with ext4
installed the base system
generated a new initramfs as explained in the wiki:
MODULES="dm_mod ext4"
HOOKS="base udev autodetect modconf block keymap encrypt filesystems keyboard fsck"
added cryptdevice=<device>:<dmname> to kernel boot options:
linux /vmlinuz-linux cryptdevice=/dev/sda7:cryptroot root=UUID=d3505fe1-4a29-4841-8e80-e953442d8d30 ro quiet
restarted pc
On boot it asks for passphrase, but after that it stops with an error regarding crypto_LUKS; here the complete message:
A password is required to access the cryptroot volume:
Enter passphrase for /dev/sda7
fsck: fsck.crypto_LUKS: not founf
fsck: error 2 while executing fsck.crypto_LUKS for /dev/sda7
ERROR: fsck failed on '/dev/sda7'
********************* WARNING ***********************
* The root device is not configured to be mounted *
* read-write! It may be fsck'd again later. *
mount: unknown filesystem type 'crypto_LUKS'
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs /]#
Here it is my fstab: http://pastebin.archlinux.fr/474004
and lsblk output: http://pastebin.archlinux.fr/474005
Any idea about the problem?
Thanks for your time.

There are two discrepencies between your kernel parameters and fstab:
1) The kernel parameter UUID for real root differs from the UUID given for /dev/mapper/cryptroot in your fstab; if cryptroot is your real root partition, the UUIDs should be the same.
2) Your fstab instructs the system to mount the root partition as read-write, while the kernel parameters specify read-only. (the kernel parameter should be read-write, which is what the warning in the output above is about).
Change those and see if it helps.

Cannot mount USB disk in SIngle-user mode (solaris 10)

Hi all ,
I need some help please :
I can read/write to my USB disks when i'm in muti-user mode but when to I swith to single-user mode ( init S ), I cannot mount it.
in Single-user mode , i started volume management daemon :
#/etc/init.d/volgmt start
#volcheck
but i'm still not able to mount it.
I tried to mount manually:
#mount /dev/dsk/c2t0d0p0 /testpoint , i have this error: < mount : not a UFS magic number ( 0x0) , dev/dsk/c2t0d0p0 is not of this fstype.
My system recognizes the USB device though in single-user mode:
This is an output of #iostat -En
c2t0d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: BUFFALO Product: ClipDrive Revision: 2.00 Serial No:
Size:0.07GB <65339392 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0

Hi ,
thanks for your advice. My problem is resolved.
The USB drive was actually a FAT filesystem.
so I did # mount -F pcfs /dev/dsk/c2t0d0p0:c /testpoint and everything went fine
I can read/write to my USB disks when i'm in
muti-user mode but when to I swith to single-user
mode ( init S ), I cannot mount it.
in Single-user mode , i started volume management
daemon :
/etc/init.d/volgmt start
#volcheck
but i'm still not able to mount it.It probably requires other items to be started
first.
I tried to mount manually:
#mount /dev/dsk/c2t0d0p0 /testpoint , i have
this
error: < mount : not a UFS magic number ( 0x0) ,
dev/dsk/c2t0d0p0 is not of this fstype.
Looks like it's assuming UFS. If this is a pcfs
filesystem, give it the type on the mount line.
# mount -F pcfs /dev/dsk/c2t0d0p0 /testpointYeah, this was the right command, I had to specify option < -F pcfs >.
but I read somethere on this forum i had to specify :c as the drive for FAT at the end of c2t0d0p0 , so the full command was:
# mount -F pcfs /dev/dsk/c2t0d0p0:c /testpoint
>
DarrenThanks,
Sakolan.

GNOME, nautilus, devicekit-disks: mount USB disk

Hi,
I recently upgraded and have now nautlius 2.28.2-1 together with devicekit-disks 009-1 installed.
As usual mounting/unmounting USB disks in nautilus stopped working. I searched the wiki, forums, bugs and google to gather information about this topic, but you know ...
When I try to mount a disk (they all show up in nautilus) nautilus pops up an error declaring me "Not Authorized". After quite some reading I think nautilus now uses devicekit-disks to actually mount my USB disks, so I tried to mount it with devicekit-disks:
[resi@nomad ~]$ devkit-disks --mount /dev/sdc
Mount failed: Not Authorized
In older versions of nautilus I used to edit some files in /etc to grant myself permissions (PolicyKit.conf), but this does not work anymore.
I found a hint and edited /usr/share/polkit-1/actions/org.freedesktop.devicekit.disks.policy (this one is coming with devicekit-disks) and modified the default for the actions org.freedesktop.devicekit.disks.filesystem-mount action:
<allow_any>yes</allow_any>
Having done so I can now mount the USB disks using nautilus, devicekit-disks or palimpsest (suffering from the same "Not Authorized" problem). Unmounting has a little flaw though, it seems like nautilus tries to eject the medium when unmounting, but then again its "Not Authorized" to do so.
However, this is the only solution I could come up with. Since the file I modified will probably be replaced without notice during the next upgrade I fear I will have to go all the way again, not remembering anymore what I did to fix this (otoh, after writing this I probably will).
And since the values in org.freedesktop.devicekit.disks.policy are declared as defaults (and by the fact it lives under /usr) I assume there has to be a site configuration file somewhere in /etc.
Where should I but my customizations? I mean, whats the proper way to do so?
Thanks,
Christoph
P.S.: I like nautilus, it makes me unhappy to use thunar/pmount/whatever to mount my disks.

me again ... this whole *kit stuff seems so odd to me.
I finally read all the devicekit, then the policykit docs, Syu-ed and have now devicekit-disks 009-3 installed.
Using polkit-actions without arguments prints a list of registered actions (known to policykit). This list was pretty short:
[resi@nomad ~]$ polkit-action
org.freedesktop.policykit.read
org.freedesktop.policykit.revoke
org.freedesktop.policykit.grant
org.freedesktop.policykit.modify-defaults
PolicyKit considers all *.policy files under /usr/share/PolicyKit/policy/, only the policykit package installs its files (well, its one file) there.
devicekit-disks (and probably some other packages providing *.policy files) seems to forget about that. So I added a symlink:
[root@nomad policy]# ln -s /usr/share/polkit-1/actions/org.freedesktop.devicekit.disks.policy /usr/share/PolicyKit/policy/
Thats not enough, the file seems to be out of date. I had to replace all auth_admin_keep defaults with auth_admin_keep_session until the file validated.
And hurray:
[resi@nomad ~]$ polkit-action
org.freedesktop.policykit.read
org.freedesktop.policykit.revoke
org.freedesktop.policykit.grant
org.freedesktop.policykit.modify-defaults
org.freedesktop.devicekit.disks.filesystem-mount
org.freedesktop.devicekit.disks.filesystem-mount-system-internal
org.freedesktop.devicekit.disks.filesystem-check
org.freedesktop.devicekit.disks.filesystem-check-system-internal
org.freedesktop.devicekit.disks.filesystem-unmount-others
org.freedesktop.devicekit.disks.filesystem-lsof
org.freedesktop.devicekit.disks.filesystem-lsof-system-internal
org.freedesktop.devicekit.disks.drive-eject
org.freedesktop.devicekit.disks.drive-detach
org.freedesktop.devicekit.disks.change
org.freedesktop.devicekit.disks.change-system-internal
org.freedesktop.devicekit.disks.drive-ata-smart-refresh
org.freedesktop.devicekit.disks.drive-ata-smart-selftest
org.freedesktop.devicekit.disks.drive-ata-smart-retrieve-historical-data
org.freedesktop.devicekit.disks.luks-unlock
org.freedesktop.devicekit.disks.luks-lock-others
org.freedesktop.devicekit.disks.linux-md
org.freedesktop.devicekit.disks.cancel-job-others
org.freedesktop.devicekit.disks.inhibit-polling
org.freedesktop.devicekit.disks.drive-set-spindown
polkit-auth shows my authorizations, thus:
[resi@nomad ~]$ polkit-auth | grep mount
org.freedesktop.devicekit.disks.filesystem-mount
org.freedesktop.devicekit.disks.filesystem-mount-system-internal
org.freedesktop.devicekit.disks.filesystem-unmount-others
It seems to me that I am authorized for all actions listed above, I guess thats because this user is in both the wheel and root groups.
However, when I try to actually mount something nothing has changed.
[resi@nomad ~]$ devkit-disks --mount /dev/sdc
Mount failed: Not Authorized
Since policykit is now properly configured I can use polkit-action or polkit-gnome-authorization to modify the default values in the way polkit expects me to (not tampering with with the *.policy files).
[resi@nomad ~]$ polkit-action --action org.freedesktop.devicekit.disks.filesystem-mount
action_id: org.freedesktop.devicekit.disks.filesystem-mount
description: Mount a device
message: Authentication is required to mount the device
default_any: yes (factory default: no)
default_inactive: yes (factory default: no)
default_active: yes
But even now mounting fails because I'm not authorized.
Back to the start, if I change the factory defaults in org.freedesktop.devicekit.disks.policy mounting succeeds.
I think there might be 2 bugs involved here:
1.) missing links to policy files in /usr/share/PolicyKit/policy/
2.) policykit fails to consider overrides for factory defaults
What do you think?

Power outtage: Can no longer mount disk?! Please help

Firmware 7.2.1 and seagate 500 gb disk. everything has been fine for a while until our power went out last night. when i woke up to check some of my overnight downloads, i could no longer mount the disk. when i clicked on my alias it said it could not mount it.
when i typed in the IP to connect, it allowed me to log in and view my available mounts, but i could not connect to it. it gave me an error code -35 (not sure what that means).
i tried plugging the disk into my laptop but i cannot seem to view the disk (though it has always done this).
please help, this is very odd and there is data i need to get off that disk. thank you.
Message was edited by: rpeters83

Odd...
Using MacDrive, i'm able to view my files on the HFS drive from windows, go figure. So i'm backing them up right now and am going to reformat the external.
Now I know to back up my stuff...twice!

USB disks no longer mount, unknown filesystem

Similar Messages

Maybe you are looking for