Error mounting a USB disk
After last upgrade, I am getting this error when trying to mount an external hard disk.
If I try it using dolphin, it says
"An error occured while accessing 'disk name', the system responded: An unspecified error has occurred.: Not Authorized"
with
udisks --mount
I am getting the same error too.
If I use these with sudo (gksu/kdesu) it works just fine.
My user is part of storage group. Also made changes in
/usr/shre/polkit-1/actions/org.freedesktop.udisks.policy
to allow_inactive.
<allow_inactive>yes</allow_inactive>
I figured it out.
xinit is tasked with two jobs: finding a client to run, and finding a server to run it on.
The default behavior of xinit is to first look for commandline arguments that tell it what to do, e.g.:
xinit /usr/bin/awesome -- /usr/bin/X
This tells it to run awesome wm using the X server located at /usr/bin/X.
Failing commandline arguments, xinit then looks in your home directory for files .xinitrc and .xserverrc. If they exist, xinit will execute these files for the responsibility of the client and server, respectively.
If these do not exist, then xinit uses defaults built-in to the xinit program (launches xterm with /usr/bin/X). This is where startx differs. Under the same circumstance, startx will also search the /etc/X11/xinit directory for system wide xinitrc and xserverrc files. In all other ways startx is the same program, such that if you provide server arguments to startx then it will preference that over the default xserverrc, and thus you'll have the same problem.
All of this boils down to the appropriate X server arguments. The system wide xserverrc located in /etc/X11/xinit/xserverrc checks if the environment variable XDG_VTNR has been set (the current virtual terminal number, set by pam_systemd), and if it is then to use that same terminal number for the next X session by running:
exec /usr/bin/X vt$XDG_VTNR
So, there's three solutions:
Use startx instead of xinit
Make a symlink to the default xserverrc file in your home directory. This works because xinit still checks your home directory for xinitrc and xserverrc, just not the system wide files.
Make your own xserverrc that will do the correct thing, and put it in your home directory.
Last edited by Whef (2012-11-11 04:34:27)
Similar Messages
-
Do I Need To Remount/Keep Mounted Airport USB Disk?
I have a Lacie HD connect to airport extreme and have mounted it on my desktop, designated it as m y Time Machine destination, and am in the process of the first 130gb back up. My question: do I have to have the Lacie mounted, on my desktop, for TM to find it/work in subsequent back up?
Thanks.yes
-
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? -
Can't mount 4Tb USB 3.0 drive on a Sparc T5-8 control domain
Hello,
I'm trying to mount a 4Tb USB 3.0 disk drive on a Sun Sparc T5-8 running Solaris 11. It is also the LDOM primary and control domain.
I've verified that hal, dbus and rmvolmgr are running:
# svcs hal dbus rmvolmgr
STATE STIME FMRI
online Jan_29 svc:/system/dbus:default
online 16:21:51 svc:/system/hal:default
online 16:21:51 svc:/system/filesystem/rmvolmgr:default
but the server can't detect the drive:
# rmformat -l
Looking for devices...
No removables found.
# echo | format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t5000CCA022659884d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900> solaris
/scsi_vhci/disk@g5000cca022659884
/dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD0/disk
1. c0t5000CCA022666330d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900> solaris
/scsi_vhci/disk@g5000cca022666330
/dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD1/disk
2. c0t5000CCA0166F4D08d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900> solaris
/scsi_vhci/disk@g5000cca0166f4d08
/dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD2/disk
3. c0t5000CCA022665404d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900> solaris
/scsi_vhci/disk@g5000cca022665404
/dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD3/disk
4. c1t0d0 <drive not available>
/pci@300/pci@1/pci@0/pci@4/pci@0/pci@6/usb@0/storage@3/disk@0,0
Specify disk (enter its number): Specify disk (enter its number): ^C
I verified the drive is good because I can mount it on a Sun T4 server running Solaris10 and was able to mount and see the data.
Any ideas why the Sparc T5 can't access the drive? I've also tried restarting hal and rmvolmgr, but issue still persist.
Any assistance is appreciated as we need to access customer's data on the drive as soon as possible.
Thanks,Hi,
since your posting is a couple of weeks old I don't know if you already managed to get the disk working.
You might want to consider one of the following options to get it working as the problem is seen when the disk drive draws more power as the USB port can deliver.
1) use USB EXTENSION Y CABLE
2) use external USB hub with power supply
3) use USB disk with external power supply
For more details you might want to review
(Doc ID 1572327.1) Solaris might be Unable to Mount certain USB Disks because of Overcurrent on USB Port
regards
Walter -
IBM x31 pcmanfm LXDE usb disk and sound issue
How can I auto mount external USB disk
my daemon list looks like this
DAEMONS=(@syslog-ng @hal @network @net-profiles @netfs @crond @fam slim)
and modules look like this
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(e100 eepro100 mii slhc rt2x00lib rt2x00pci rt61pci ac97_bus snd-mixer-oss snd-pcm-oss snd-page-alloc snd-pcm snd-timer snd snd-ac97-codec snd-intel8x0 snd-intel8x0m soundcore vboxdrv)
Also I am not able to hear no sound, I am in the audio group and ive seen channels through alsamixer
anyone else having issues
Last edited by venky80 (2009-01-22 04:16:08)Hello Eugene,
Interesting - possible - coincidence. I just posted about a similar seeming issue here:
<http://discussions.apple.com/thread.jspa?messageID=10425731#10425731>
Notice that I've checked Disk Utility's repairs report as well as the System Log with Console: both show mention of USB related items.
This may not have anything to do with your issue but I thought it worth mentioning. -
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. -
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: 0Hi ,
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. -
Hello all,
Doubt this issue relates to a recent and ugly issue but sharing anyways (resolved thanks to a user here: LaPastenague)
Time Capsule won't backup if Modem (Motorola SB6121) attached
This was on Feb 10th resolved. Few days later I upgraded to Yosemite. Backups were working fine since.
Yesterday I happen to notice my last backup was 5 days ago. I looked in the console logs and saw:
2/25/15 3:55:06.127 PM com.apple.backupd[2777]: Attempting to mount network destination URL: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.778 PM com.apple.backupd[2777]: NAConnectToServerSync failed with error: 2 (No such file or directory) for url: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.792 PM com.apple.backupd[2777]: Backup failed with error 19: The backup disk could not be resolved, or there was a problem mounting it.
2/25/15 3:57:18.808 PM com.apple.prefs.backup.remoteservice[2021]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
I called Apple. Their front line was clueless. He suggested resetting the TC (latest "tower" model btw") which then a backup kicked off YEAH
But the next hour it failed
Called Apple again, this time to Sr Advisor. He suggested factory reset of the TC and set up again. Also first backup worked then rest failed
Third call to Apple useless also. He was asking questions I didn't feel relevant. He also was asking me to reset the TC which I told him was done 2 hours prior. He asked me to reboot which I could NOT at that time.
I begged him to collect data to submit to engineering, which will take days to get a reply.
So I thought I would throw this out to the community....
TC Is NEW (replaced from last issue). Mac is 8 months old (iMac 27"), Os is Yosemite, TC also new (latest model)
Thanks...Yosemite is problematic on two fronts.. Networking and Time Machine.. so the combo of doing both with a Time Capsule is like bugs on bugs.
Here is my standard list.. but your problem maybe difficult to resolve.. and my suggestion is simple.. until Apple get their act together and fix TM.. buy Carbon Copy Cloner and use that for your backup. It is solid and reliable.. even better if you use USB drive plugged into the computer and do a bootable clone.. because then you have a backup that is able to be tested for full functionality 2min after the end of the backup.
This also starts from a factory reset.. but the reason for it is to change the configuration which is much more easily handled with factory reset to begin.. the instructions are there.. because this is my standard reply.. this is not uncommon!!
Factory reset universal
Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
Setup the TC again.
ie Start from a factory reset. No files are lost on the hard disk doing this.
Then redo the setup from the computer with Yosemite.
1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
eg TCgen5 and TCwifi for basestation and wireless respectively.
Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
5. Mount the TC disk in the computer manually.
In Finder, Go, Connect to server from the top menu,
Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
You might need to do some more work on the Mac itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
Tell us how you go.
Someone posted a solution.. See this thread.
Macbook can't find Time Capsule anymore
Start from the bottom and work up.. What I list here is good network practice changes but I have avoided Yosemites bug heaven.
This user has had success and a few others as well.
RáNdÓm GéÉzÁ
Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/ -
Time Machine Error Message: "The backup disk image could not be mounted"
I just installed Time Capsule and the initial back up was going smoothly. Now
all I get is a and the Error message "The backup disk image could not be mounted". Can anyone help me troubleshoot this problem? Thanks.This works, if there is no corruption in the sparse image. But after weeks of backups, my sparse image on a USB disk attached to an Airport Extreme was corrupted.
I am right now repairing it by connecting the USB disk directly and using disk utility. It recovered the file system and is not rebuilding the B-Tree. I hope that works, otherwise it will have to be disk warrior...
On Time Capsule, I have heard folks having success with attaching the image, and then repairing it:
hdiutil attach -nomount -readwrite /path/to/sparse/image
Your mileage may vary, but you do not have a lot to lose in this circumstance...
This functionality should really be in the Airport or Time Capsule, or at least Disk Utility or Airport Utility. -
Hi,
How can I mount automatically an usb disk after boot?
Any suggestion would be appreciated.
ThanksRead this fine article and use it to set up a udev rule, to specifically name the device. (Otherwise you may never know where it pops up in the disk naming scheme.)
Also note -- after reading the article -- there are plenty of examples of rules in /etc/udev/ files that may further help. -
Write errors (-50) when I try to create new files or folders on my Airport Extreme USB disk. Restarting the Airport Extreme seems to solve the issue. Any idea why this occurring? It doesn't seem to be OS specific, meaning I can't write to the drive from a Windows PC or a MacBook Pro.
Although, I would consider it rare, it is quite possible that this drive is just not 100% compatible with the AirPorts. Typically, in these cases, the AirPort will not even recognize the drive at all ... or it will, but not allow you to access it. I actually haven't come across a case where you can read but not write to a drive consistently or vice versa ... except from Windows-based computers. Sorry!
-
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. -
Can't mount USB disk with the atribute of fix and read-only
Hello All,
I have a usb disk which is set as fix(non-removalbe) and read-only. I tried to connect it to Macbook version 10.4.11 ,but it failed to mount the disk. However, connecting to 10.5.X and windows XP work fine. I am wondering is it a bug specifically in 10.4.11 only ? Could I get any patch for this problem ?
Thanks,
YingHI Ying and Welcome to Apple Discussions ...
Try repairing disk permissions.
Quit any open applications/programs. Launch Disk Utility. (Applications/Utilities) Select MacintoshHD in the panel on the left, select the FirstAid tab. Click: Repair Disk Permissions. When it's finished from the Menu Bar, Quit Disk Utility and restart your Mac.
Carolyn -
EXT4 errors while mounting a USB in initramfs on a specific computer
Hi,
I'm having trouble booting a newly installed Archlinux on a USB key on an old HP Compaq computer.
I am getting EXT4 errors in the regular initramfs, but they blink really fast on the screen so I can't read them properly.
It boots fine with the fallback initramfs, and dmesg shows that there are no problems while mounting.
The system boots without any problem on both initramfs with QEMU on my Windows.
My mkinitcpio.conf :
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect block filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems fsck keyboard"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
I'm really puzzled about this, since I initially thought that the HP Compaq simply had problems with my USB key, but since it boots fine with the fallback initramfs, I think that it is the initramfs' fault, but it is the default one, so I currently have no clues about this.
I've also checked the USB key multiple times with fsck, and that doesn't seem to be the cause of the problem.The thing is, the block module and the filesystem module are both loaded in my regular initramfs, and the presence of ext4 errors while mounting my USB key (it uses ext4) signifies that the system is actually using the right tool to do what it's supposed to.
The system has been installed via VirtualBox so the autodetect module may have messed things up. Going to recreate an initramfs image without it.
EDIT : It worked, sorry for bothering you guys, I could've found it sooner.
Anyway, as a note for others, if you plan on installing on a USB key to use it on other computers, remove the autodetect module from the initramfs, otherwise the required modules won't always be there.
Last edited by FreeSalad (2014-03-10 15:56:22) -
Invalid file name error while copying some packages to USB disk.
Hi
I am trying to create my custom local repository by copying all the packages from /var/cache/pacman/pkg to /run/media/anand/SJCE_EEE/custompkgs on my USB storage device. But I get the following errors for some packages:
cp: cannot create regular file ‘/run/media/anand/SJCE_EEE/custompkgs/graphite-1:1.0.3-1-i686.pkg.tar.xz’: Invalid argument
cp: cannot create regular file ‘/run/media/anand/SJCE_EEE/custompkgs/hsqldb-java-1:1.8.0.10-2-any.pkg.tar.xz’: Invalid argument
cp: cannot create regular file ‘/run/media/anand/SJCE_EEE/custompkgs/libmythes-1:1.2.3-1-i686.pkg.tar.xz’: Invalid argument
cp: cannot create regular file ‘/run/media/anand/SJCE_EEE/custompkgs/libshout-1:2.3.0-1-i686.pkg.tar.xz’: Invalid argument
cp: cannot create regular file ‘/run/media/anand/SJCE_EEE/custompkgs/phonon-1:4.6.0-2-i686.pkg.tar.xz’: Invalid argument
cp: cannot create regular file ‘/run/media/anand/SJCE_EEE/custompkgs/rasqal-1:0.9.29-1-i686.pkg.tar.xz’: Invalid argument
cp: cannot create regular file ‘/run/media/anand/SJCE_EEE/custompkgs/redland-1:1.0.15-3-i686.pkg.tar.xz’: Invalid argument
cp: cannot create regular file ‘/run/media/anand/SJCE_EEE/custompkgs/redland-storage-virtuoso-1:1.0.15-3-i686.pkg.tar.xz’: Invalid argument
cp: cannot create regular file ‘/run/media/anand/SJCE_EEE/custompkgs/vi-1:050325-2-i686.pkg.tar.xz’: Invalid argument
cp: cannot create regular file ‘/run/media/anand/SJCE_EEE/custompkgs/xf86-video-ati-1:6.14.6-1-i686.pkg.tar.xz’: Invalid argument
But other packages copy properly to the USB storage device. If I remove : from the file names of packages mentioned above they copy properly. Is this because of the FAT32 file system on my USB disk?
The above mentioned packages copy properly to my home directory which is ext4 file system.
Any suggestions to correct this?
Thanks in advance.
Anandrsamurti, you asked the moderators to do this:
Please remove : from package file names due to the problems reported in this post. Such packages cannot be copied to FAT32 file systems.
This is up to you. Just "Edit" the post by yourself and mark this section deleted. (See the BBCode help for this.)
And please leave an according comment stating something like the quote above there. It would be valuable information.
Maybe you are looking for
-
I have a script that exports each individual page to a pdf with each page having it's own metadata. It works fine except for on small thing. The keyword array looks like this in the final PDF. ; "Keyword1, Keyword2, Keyword3 How do I get rid of the s
-
After you plug an Apple USB SuperDrive into an iMac, what must you do to view or to burn DVD videos?
-
Trouble using getLong to get an Oracle Number(8,2) field from ResultSet
I am having trouble using getLong to get an Oracle Number(8,2) field from ResultSet. The error message starts with: java.lang.ExceptionInInitializerError: [exception was kaffe.utilNotImplemented] at oracle.jdbc.dbaccess.DBConversion.NumberBytesToLong
-
How does one update iOS and what is iOS.. Thank you..
how do you update iOS. And what is that anyway. I had to update FaceTime in order to use it and now I cannot send any pictures from ipad camera. Thanks for any help..
-
ATi Extension is corrupted?
Hi guys, I was watching a movie when the screen went crazy and froze. It kept flickering, and everything on my screen was jagged. I restarted the computer, forced, and after the logo and wheel, the screen turned white pixelated (right after the blue