Mounting RAM Disks as "-notremovable"

I am replacing my G5 (10.5) Xserve with a late 2008 Xserve (10.6). This server is primarily a web server, with a small amount of mail traffic.
I keep my 'webfolder' on a RAM disk. All of my pages are dymanic php/mysql, so they can't be cached. But reading from RAM is so fast, you'd never know it.
This is the command I used in 10.5 to create a 1 GB RAM disk at boot:
[code]/usr/sbin/diskutil erasevolume HFS+ "web-ram" `/usr/bin/hdiutil attach -notremovable -nomount ram://2200000`[/code]
Not the "notremovable", that flag makes the system treat the mounted disk image (or in this case, the RAM disk), like a real physical disk, and not a mounted disk image. When you use this flag, the ram disk will actually show up with a regular hard drive icon. Without this flag, it shows up as a white disk image.
But this flag doesn't work in 10.6. According to the man page, it's still there. But when I use it, I get permissions errors. I am using it with sudo (from the command line, or as root via lanuchdeamons). As I look closer at my errors, It appears that what might be happening is that the diskutil command is being run as root, but the hdiutil command inside of it, is not.
Anyway this is about more than just the icon. When the ram disk is mounted as a real disk, its harder to eject, which is good because it's my web folder and I don't want it going anywhere. AND when its mounted that way, I can use time machine to back it up. Which works out to be a great system for that.

So I was originally suspecting that there was a problem with `hdiutil`, but now I'm starting to think (based partly on error messages) that `hdiutil` creates the disk ok, but newfs_hfs is unable to write to this disk to format it. But only when it's -notremovable.
I hope someone has any clues about this? It's quite a sticking point.

Similar Messages

DVD-Ram disks won't mount on Dual 450 - help!

I've got a particular and pressing problem. I'm an audio engineer among other things. I have a lot of files archived temporarily on DVD-Ram disks from my old Dual 450. I have to retrieve some files pronto but suddenly the DVD-Ram disk won't mount. The drive spits out the disk as soon as I insert it. It will mount CDs but not these DVD-Ram disks. Please help. I need to back these up off of thse old disks. But more urgently I have pending sessions that require I get some files from these disks. This happens both under OS 9.1 and 10.2.8 the last revisions of this computer I did. But it used to work until a year or so ago.
I have so far repaired permissions, used Disk Warrior and sprayed around the dusty drive with compressed air. It seems that perhapos a mechanism is loose springing the disk out when it's not immediately recognized as a CD or DVD-R.
Help!

Probably your best bet is to dismantle the drive and try manually cleaning the lenses, which has made a difference for some users.
Other option is to replace the drive with a new one capable of reading (but not necessarily writing) DVD-RAM media. LG-4163B is one such drive, Pioneer DVR-110 can also read DVD-RAM. These drives are under $40 online in the US.

Internal hard drive does not mount in disk utility

My internal hard drive no longer mounts in Disk Utility. It is grayed out. I have extraordinarily frequent spinning beach ball/freezes, in Safari or Apple Mail. The most recent symptom: upon rebooting or just starting up, I see flashing black on the display. This has been occuring for more than six months. Of course, I have made total and frequent backup's. I bought new RAM, but have not yet installed it, and I susect this might help. I have done repeted troubleshooting many times each: Apple's Disk Doctor, Repaired Permissions, Reinstalled the Mac OS, safe boot, Alsoft's Disk Warrior, Apple's longer Harware Test, etc. I have worked as a new user, too. All tests done report that all is well. What od you thnk the problem is? Must I drive 1.5 hrs. each way to the Genius Bar at my nearest Apple Store? Might I try to erase the hard drive as a fix? I hate to do this, only as a last resort, as it is so time-consuming. Should I just update my Mac OS? Please advise, out there, if anyone can offer any advice, I would be greatly appreciative.

The list of issues you posted probably would not get shorter if you attempt to 'upgrade them' away, as usually that kind of effort is not effective yet may expose more of the same problems while not necessarily revealing the original weakness. Another OS X installed over a set of problems seldom helps.
How full is the hard disk drive? If it is too full, or has been very busy in use several years, it may be time to replace the HDD and perhaps put a larger capacity one in the computer. And if the main computer hardware checks out OK (tested under a variety of duration and stress tests) then also consider a RAM upgrade if the device is not already at the maximum capacity.
When was the last time the hard disk drive was devoid of content, maybe wiped -- erased and reformatted by a third party disk utility or have a utility overwrite the entire HDD with zeros? This used to be a common tech service in the course of a major effort to restore a Mac. Or Defragment?
If you can do the latter, this could help resolve bad sectors and remove old data or corruption on the hard drive. Or get a new HDD and before committing a new OS X install & apps to it (or a re-clone of a complete backup) test the drive and be sure it is ready for use. Not all new drives are perfectly ready; some need to get exercise first.
I'd bet on a new hard disk drive of larger capacity (also note spin RPM rate and data speeds) and a full RAM upgrade.
If you have a backup clone on an external hard disk drive (in a boot-capable enclosure) you could really go to town and before you erase the main/only hard drive, make a backup clone and test its ability to boot the Mac. Or put the old drive and content in a suitable boot capable enclosure of the kind with its own power supply, and deal with it later.
Then consider a later version OS X -- whatever most recent version that model can support... {edited}
Good luck & happy computing!

How to erase DVD-Ram disk

I have a half dozen DVD-Ram disks (from my now-dead DVR). They mount on the Desktop and I can see the contents (VRO and associated files). I am exploring the various Toast, Streamclip (etc.) options to play/rescue the files. Once that is done, how can I erase (and rewrite/reuse) the disks? Neither Toast 8 nor Disk Utility seem happy with formatting/erasing this media. Any ideas?
~ Keri

Ah,... makes sense. Thanks! And here's what it says [below].
So, it seems to say I cannot "erase" ... but I can "overwrite" (??), which is splitting a hair finer would have occurred to me.
Okay. Then, how would I "overwrite" the files -- what application could I use to do this? Toast? Other??
~ Keri
MATSHITA DVD-R UJ-845E:
Firmware Revision: DMP2
Interconnect: ATAPI
Burn Support: Yes (Apple Shipped/Supported)
Cache: 2048 KB
Reads DVD: Yes
CD-Write: -R, -RW
DVD-Write: -R, -RW, +R, +RW
Burn Underrun Protection CD: Yes
Burn Underrun Protection DVD: Yes
Write Strategies: CD-TAO, CD-SAO, DVD-DAO
Media:
Media Type: DVD-RAM
Blank: Yes
Erasable: No
Overwritable: Yes
Appendable: Yes

Internal hard drive fails to mount in Disk Utility.

My internal hard drive fails to mount in Disk Utility for the past year, so I cannot verify it. However, it does mount in Disk Warrior. (1) I am concerned that it will not mount within the Apple software, and what that bodes for my computer. (2) I also have MANY spinning beach balls daily and have to use the power button to reboot. I just bought extra Crucial RAM and have yet to install it. Somehow, I don't think it wil help my issue # 1 though. Please advise, anyone out there! Thank you.

No, there are never any errors like that. Also, I have upgraded the Mac OS from 10.5 to 10.6.8. That did nothing. I backed up my Users = Christina folders to a good, 15 year old Firewire 800 La Cie 1 TB external hard drive. I also tested using the Apple Hardware test, which showed no problems, and Alsoft's Disk Warrior and defragged, and fixed a very minor issure re directory count, probably resulting from many improper shutdowns lately due to frozen spinning beach balls. None of these procedures alleviated the issues, and I still have the same issues: mainly that super-frequent spinning beach ball. Do you think I ought to install that new RAM sitting here finally? Perhaps it is a lack of RAM??I only have 2 lousy GB's of RAM after all! Thank you so very much for a reply.
Message was edited by: Flamingcreatures

Disk Utility to format DVD-RAM disk

I have swapped out my Combo drive and installed an LG GSA-4163b so that I can burn, write to, DVD-RAM disks.
I have installed Patchburn which now allows me to burn CD's and all manner of DVD's but DVD-RAM disks will not mount.
DVD-RAM disk is recognized by Disk Utility but I cannot figure out how to make Disk Utility format the DVD-RAM disk. How do I do this.
Thanks,
Doug

Hi Douglas,
should work pretty straight forward:
* Open Disk Utility
* Select the disc in the column on the left
* click Erase (select Quick Erase if you don't want to zero out the disk)
* Click Erase to start the process
HTH,
Koinseb
Message was edited by: Koinseb

How do I mount a disk image that won't open?

I have an external drive Samsung 500 GB that was failing. I think my MacBook Air (10.6.8) caused it to fail because it wouldn't allow me to eject the disk even though I forced quit all programs. I eventually had to just unplug the drive and this caused the external disk to fail as it had not been ejected properly. Not my fault. It's the MBA's fault for not letting me eject the disk. Now the Samsung disk won't mount properly and I get a message that the drive is failing and I should save the data.
Anyhow, I used the free version of Data Rescue 3 to try and save the data on the failing Samsung 500 GB drive and move it onto a brand new Toshiba 1 TB drive.
I was unable to use the normal scanning function of Data Rescue 3 as the hardware of the drive was too damaged, and so I used the clone function on Data Rescue 3 to clone the data onto a non-failing hard drive, with the intent of restoring the data later.
I am not sure if I was successful in making the disk image. It hung up at the 99.6% point for about 12 hours when I decided to give up on it, and I shut down Data Rescue so I could eject the hard disks.
However, it would not let me do it. I tried force ejecting but still I could not eject the disks.
I ended up just unplugging the drives. I think the Samsung drive died almost completely then because it made a whole lot of clicking noises after that (it was only making a few clicking noises before that).
Anyhow, I plugged the Toshiba 1 TB drive into the computer again and used Data Rescue to scan the drive with the disk image on it to see if I could detect files on that drive.
It opened up the structure and I was able to see that most or all of the files were there (abbout 450GB of data) just from seeing the information about the files in the structure tree - the labels of the files (file type labels such as jpg, mp4 etc) and the size of the files, although I could not open up the files to check all of them.
I tested out the restore function of Data Rescue by downloading one file (<10MB) file. I am using the free version and can download one file for free to test things out.
It worked and I was able to save that file onto a second external drive (Western Digital 500 GB) I had plugged in. I had bought this drive just to do the data rescue.
So I think the files are salvageable and the disk image is OK.
However, when I tried to open the disk image in Disk Utility, by opening it as the source and choosing the WD drive as the destination I could not open it. I got an error message. I can't remember what the message was.
I tried just opening the disk image in Finder by just clicking on the disk image but it won't mount.
Is that because my hard drive doesn't have enough space? My Desktop on the MBA only has 12 GB free and the WD drive has only 500 GB on it even though the disk image is about 501 GB.
I don't know why the disk image is that size when the failing Samsung drive only had 450 GB of data on it.
Anyway, what should I do to mount the disk image?
I want to mount the disk image so that I can copy or move the files from it to another external drive so that I can save those files.
Is it because the WD is only 500 GB or does it mean there's a problem with the disk image I made?
Should I try Carbon Clone Copy? I use that to make backups of my MBA internal HDD though I have never used it for opening or making disk images.
I have never dealt with disk images before except for dmg files of applications downloaded from the internet.
I am trying to avoid using Data Rescue 3 as I have to pay for it and if there is a free option, such as Disk Utility, CCC or other, I want to try it to restore the data in the disk image.
Sadly, I think the Samsung drive is ruined beyong repair as it's making a lot of clicking sounds and doesn't mount properly in Disk Image and I get a message that it's beyond repair or something like that in Disk Utility.
So I am relying on the disk image I made on the Toshiba drive to restore my files.
(I think it was the last movie file that caused the problem because it was when I was trying to copy it onto the Samsung external drive, all the problems began - hanging up when copying it, not being able to eject the Samsung disk, causing hardware issues on Samsung disk and getting warning messages on Disk Utility.)
BTW, I learned how to eject a drive when it won't eject the normal way, I have to use command window and type in commands, but that's another post ....
Any advice?
I am thinking of going out and buying a second 1 TB external drive so that I have a disk with enough space to open the 501GB disk image on it, just in case that was the sole problem.
However, I am not sure that is the case, and I think there may be a problem with the disk image or I am not going the right way about opening it.
Thanks for any advice.

I think I've found the solution to this problem.
http://superuser.com/questions/19426/im-unable-to-mount-a-dmg-getting-a-no-mount able-filesystems-error
I am following the instructions here:
I ran into a similar situation. I did what simonair suggested and I received a message in Terminal that Volume mounted successfully. However It did not help me access the mounted Volume neither was I able to confirm the mounted Volume. Nor was I able to mount the image using Disk Drill or even scan through. Nothing succeeded.
Here is what I did to solve my problem. I see that in this post some suggested that we should convert name.dmg to writable file. I used the command from Terminal to convert but was not successful. INSTEAD alternatively, I used Disk Utility, attached the Volume (yes I got the same message again, ''no mountable system files'' however, Disk Utility nevertheless attached the image, which I was able to do before anyways. This time, I selected it and then clicked New image, and then selected image format read/write, not the compressed option. I created a new image. This time this image was writable however, it still would not mount using Simonair's solution. However, this time I was able to scan it with Disk Drill with exact file locations and folder hierarchy as I had. Recovering all from thereon was a breeze. Just remember: when you create new image of an attached volume and chose not compressed but read/write, you need to have a disk with exact amount of space that totals the total space allocated within that name.dmg file (not the amount of space the data takes). Mine was huge, and luckily I had an external disk with enough space to do that and it took about 5 hours for about 400GB of disk allocation. Good luck.
And so far it seems to be working. Even though the volume is grayed out on the left side of Disk Utility, I am still able to select it as the source for making a new disk image. I chose Read and Write and no compression.
The only thing I might be doing differently is that instead of choosing the disk image as the source, I chose the volume as the source. The volume is grayed out, but the disk image is not.
It seems to be working all right. Keep my fingers crossed.
If this doesn't work, I will use Data Recovery 3 as a last resort.

[SOLVED] Suspend to ram / disk not working in newer kernels

Hi all,
this puzzles me for a while:
My desktop system was able to suspend to ram / disk flawlessly in older kernels. It stopped working with 3.3. The suspend seems to work, the machine goes to standby. But when I try to resume, the machines is on but the screen stays black. Neither the console is working nor can I ssh into it. Only hard reset gets me out here
I did investigate and found many tips and hints which all led to nowhere. I even changed my filesystem back from btrfs to ext4 and my VGA module from proprietary nvidia to nouveau.
When this all failed I got to the idea to burn several install disks. One of the official 2011.08.19 (kernel 3.0.3) and one of the snapshots 2012.06.05_04-00-01 (kernel 3.3.7) and 2012.07.17_04-00-01 (kernel 3.4.4). I guess these can not be compromised by some hosed installation. I started one by one and issued the follwing command:
echo mem > /sys/power/state
which suspends the machine successfully in all three cases. With 2011.08.19 the resume is working but the other two fail. Some more info about the hardware:
1. lspci output
harvey@obelix ~ $ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
00:05.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 3 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.3 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT] (rev a1)
02:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
03:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
03:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
3f:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
3f:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
3f:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
3f:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
3f:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
3f:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
3f:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
3f:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
3f:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
3f:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
3f:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)
2. lsmod output of 2012.07.17_04-00-01:
harvey@obelix ~ $ lsmod
Module Size Used by
fuse 68768 0
tun 15297 0
rfcomm 33627 8
bnep 8793 2
nfsd 246714 2
exportfs 3665 1 nfsd
btusb 11764 0
joydev 9991 0
bluetooth 190551 22 bnep,btusb,rfcomm
rfkill 15604 2 bluetooth
snd_hda_codec_realtek 60409 1
snd_hda_intel 24053 3
snd_hda_codec 94305 2 snd_hda_codec_realtek,snd_hda_intel
microcode 12185 0
i7core_edac 17477 0
snd_hwdep 6300 1 snd_hda_codec
i2c_i801 8180 0
iTCO_wdt 12813 0
snd_pcm 74958 2 snd_hda_codec,snd_hda_intel
r8169 49386 0
coretemp 5654 0
edac_core 36656 3 i7core_edac
iTCO_vendor_support 1929 1 iTCO_wdt
serio_raw 4653 0
pcspkr 1899 0
snd_page_alloc 7185 2 snd_pcm,snd_hda_intel
snd_timer 18966 1 snd_pcm
mii 4123 1 r8169
snd 58997 12 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 5410 1 snd
acpi_cpufreq 5933 0
mperf 1235 1 acpi_cpufreq
evdev 9754 4
processor 26567 1 acpi_cpufreq
vboxnetadp 18387 0
vboxnetflt 16743 0
vboxdrv 1791382 2 vboxnetadp,vboxnetflt
nfs 276056 1
nfs_acl 2359 2 nfs,nfsd
lockd 62987 2 nfs,nfsd
auth_rpcgss 32327 2 nfs,nfsd
sunrpc 184998 12 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
fscache 41059 1 nfs
aes_x86_64 7508 64
cryptd 8741 0
aes_generic 26138 1 aes_x86_64
xts 3101 32
gf128mul 6050 1 xts
dm_crypt 16496 4
dm_mod 70918 9 dm_crypt
sr_mod 14823 0
cdrom 35648 1 sr_mod
hid_logitech 16560 0
ff_memless 4690 1 hid_logitech
usbhid 36430 1 hid_logitech
hid 85285 2 hid_logitech,usbhid
sd_mod 29239 7
pata_jmicron 2480 0
usb_storage 44760 0
pata_acpi 3408 0
ata_piix 23160 5
crc32c_intel 1987 0
ahci 20549 0
libahci 20023 1 ahci
ata_generic 3295 0
libata 167611 6 ahci,pata_acpi,libahci,ata_generic,ata_piix,pata_jmicron
scsi_mod 132974 4 usb_storage,libata,sd_mod,sr_mod
uhci_hcd 23372 0
xhci_hcd 81440 0
ehci_hcd 40994 0
usbcore 147533 8 btusb,uhci_hcd,usb_storage,ehci_hcd,usbhid,xhci_hcd
usb_common 954 1 usbcore
floppy 58615 0
nouveau 784289 3
button 4502 1 nouveau
video 11307 1 nouveau
mxm_wmi 1425 1 nouveau
wmi 8475 2 mxm_wmi,nouveau
i2c_algo_bit 5391 1 nouveau
drm_kms_helper 33051 1 nouveau
ttm 64288 1 nouveau
drm 208926 5 ttm,drm_kms_helper,nouveau
i2c_core 20369 5 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau
ext4 424175 4
crc16 1359 2 ext4,bluetooth
jbd2 73919 1 ext4
mbcache 5977 1 ext4
3. /var/log/pm-suspend.log of a not working suspend
Initial commandline parameters:
Tue Jul 17 11:21:18 CEST 2012: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux obelix 3.4.5-1-ARCH #1 SMP PREEMPT Mon Jul 16 21:35:54 CEST 2012 x86_64 GNU/Linux
Module Size Used by
rfcomm 33627 8
bnep 8793 2
nfsd 246714 2
exportfs 3665 1 nfsd
ext4 424175 3
jbd2 73919 1 ext4
mbcache 5977 1 ext4
btusb 11764 0
bluetooth 190551 22 bnep,btusb,rfcomm
crc16 1359 2 ext4,bluetooth
joydev 9991 0
rfkill 15604 2 bluetooth
snd_hda_codec_realtek 60409 1
microcode 12185 0
coretemp 5654 0
serio_raw 4653 0
snd_hda_intel 24053 5
snd_hda_codec 94305 2 snd_hda_codec_realtek,snd_hda_intel
pcspkr 1899 0
snd_hwdep 6300 1 snd_hda_codec
snd_pcm 74958 3 snd_hda_codec,snd_hda_intel
snd_page_alloc 7217 2 snd_pcm,snd_hda_intel
r8169 49386 0
i7core_edac 17477 0
snd_timer 18966 1 snd_pcm
edac_core 36656 3 i7core_edac
mii 4123 1 r8169
snd 58997 15 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
iTCO_wdt 12813 0
i2c_i801 8180 0
soundcore 5410 1 snd
iTCO_vendor_support 1929 1 iTCO_wdt
acpi_cpufreq 5933 0
mperf 1267 1 acpi_cpufreq
evdev 9754 4
processor 26567 1 acpi_cpufreq
vboxnetadp 18387 0
vboxnetflt 16743 0
vboxdrv 1791382 2 vboxnetadp,vboxnetflt
nfs 276056 1
nfs_acl 2359 2 nfs,nfsd
lockd 62987 2 nfs,nfsd
auth_rpcgss 32327 2 nfs,nfsd
sunrpc 184998 12 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
fscache 41059 1 nfs
btrfs 710578 1
libcrc32c 1002 1 btrfs
zlib_deflate 20436 1 btrfs
aes_x86_64 7508 64
cryptd 8741 0
aes_generic 26138 1 aes_x86_64
xts 3101 32
gf128mul 6050 1 xts
hid_logitech 16560 0
ff_memless 4690 1 hid_logitech
dm_crypt 16496 4
dm_mod 70918 9 dm_crypt
sr_mod 14823 0
cdrom 35648 1 sr_mod
usbhid 36430 1 hid_logitech
usb_storage 44760 0
hid 85285 2 hid_logitech,usbhid
sd_mod 29239 7
pata_jmicron 2480 0
pata_acpi 3408 0
ata_piix 23160 5
ata_generic 3295 0
uhci_hcd 23404 0
crc32c_intel 1987 1
ahci 20549 0
libahci 20023 1 ahci
libata 167611 6 ahci,pata_acpi,libahci,ata_generic,ata_piix,pata_jmicron
xhci_hcd 81472 0
ehci_hcd 41026 0
scsi_mod 132974 4 usb_storage,libata,sd_mod,sr_mod
usbcore 147565 8 btusb,uhci_hcd,usb_storage,ehci_hcd,usbhid,xhci_hcd
usb_common 954 1 usbcore
floppy 58615 0
nouveau 784321 3
button 4502 1 nouveau
video 11307 1 nouveau
mxm_wmi 1425 1 nouveau
wmi 8475 2 mxm_wmi,nouveau
i2c_algo_bit 5391 1 nouveau
drm_kms_helper 33051 1 nouveau
ttm 64320 1 nouveau
drm 208958 5 ttm,drm_kms_helper,nouveau
i2c_core 20369 5 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau
total used free shared buffers cached
Mem: 8173500 884060 7289440 0 3764 405872
-/+ buffers/cache: 474424 7699076
Swap: 8386556 0 8386556
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /etc/pm/sleep.d/90alsa suspend suspend:
/etc/pm/sleep.d/90alsa suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
Kernel modesetting video driver detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Tue Jul 17 11:21:18 CEST 2012: performing suspend
This seems to be a kernel bug. Any input?
Harvey
Last edited by Harey (2012-08-06 13:51:49)

Another life-sign. The issue is still unsolved but I've come a little further. It seems to be a combination of more failures. The first one is USB hardware. I have a usb keyboard-mouse combo from Logitech (comfort cordless desktop). The USB bus does not wake up correctly when resuming from suspend. So my keyboard is unsuable. I put in a file /etc/pm/sleep.d/20_custom-ehci_hcd with the following content:
BUSES="0000:00:1a.7 0000:00:1d.7"
case "${1}" in
hibernate|suspend)
# Switch USB buses off
for bus in $BUSES; do
echo -n $bus | tee /sys/bus/pci/drivers/ehci_hcd/unbind
done
resume|thaw)
# Switch USB buses back on
for bus in $BUSES; do
echo -n $bus | tee /sys/bus/pci/drivers/ehci_hcd/bind
done
esac
The bus IDs were taken from /sys/bus/pci/drivers/ehci_hcd
When I start pm-suspend from a console (no X started) this seems to reanimate my keyboard while the screen stays black (with backlight on). I can type and reboot. Also I can ssh into the machine from my laptop.
Concerning the blank screen there seems to be a bug in both the proprietary nvidia modules as well as the nouveau driver. The nvidia folks have issued a new beta driver which seems to at least minimize the failures. This all concerns the nv50-family of nvidias cards. I have a GF8600GT which is one of these
I'll wait for this driver and then restart my testing. Until then - no suspend/hibernate
EDIT: Today's nvidia 304.32 is solving my issues - I can sleep again
Harvey
Last edited by Harey (2012-08-06 13:52:51)

Suspend to ram/disk stopped working overnight

My suspend to ram/disk used to work fine, but overnight, it stopped. It is not an update issue since, I was able to suspend after the last update. I decided to update today hoping that it is going to solve the problem, but the problem persist.
Here is what happens:
$ sudo pm-suspend
or
$ sudo pm-hibernate
The computer suspends faster than usual, as if it does not take the time to complete the suspend procedure. When I turn the computer on, it starts to boot instead of resuming from suspend. In the case of hibernate, this is clearly obvious. Normally it is suppose to take 10-30 s. to save the memory data to the swap, but this time the computer shuts fast (1-2s.), and I doubt that all the data is saved to swap.
Here are the logs for each case (/var/log/pm-suspend.log):
suspend to ram:
Initial commandline parameters:
Sat Aug 25 23:16:03 EDT 2012: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux gateway 3.4.9-1-ARCH #1 SMP PREEMPT Wed Aug 15 18:59:31 CEST 2012 x86_64 GNU/Linux
Module Size Used by
xt_recent 7901 3
xt_tcpudp 2471 51
ip6table_mangle 1684 0
ipt_MASQUERADE 1738 1
nf_nat_ftp 1668 0
iptable_nat 4024 1
nf_nat 15100 3 nf_nat_ftp,ipt_MASQUERADE,iptable_nat
nf_conntrack_ipv4 6871 20 nf_nat,iptable_nat
nf_defrag_ipv4 1339 1 nf_conntrack_ipv4
xt_TCPMSS 3439 5
xt_LOG 11943 48
ipt_REJECT 2281 0
iptable_mangle 1584 0
xt_multiport 1758 0
xt_state 1295 17
xt_limit 2041 51
xt_conntrack 3329 0
nf_conntrack_ftp 6261 1 nf_nat_ftp
nf_conntrack 61584 8 nf_nat_ftp,ipt_MASQUERADE,nf_nat,xt_state,xt_conntrack,nf_conntrack_ftp,iptable_nat,nf_conntrack_ipv4
ip6table_filter 1396 1
ip6_tables 18198 2 ip6table_filter,ip6table_mangle
iptable_filter 1456 1
ip_tables 16946 3 iptable_filter,iptable_mangle,iptable_nat
x_tables 16954 17 ip6table_filter,ip6table_mangle,xt_recent,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_state,xt_conntrack,xt_LOG,xt_multiport,iptable_filter,xt_TCPMSS,ipt_REJECT,iptable_mangle,ip6_tables,iptable_nat
adt7475 20329 0
hwmon_vid 3196 1 adt7475
arc4 1410 2
sg 25344 0
st 35573 0
uas 8823 0
rtl8187 52559 0
mxm_wmi 1425 0
wmi 8475 1 mxm_wmi
shpchp 26305 0
pci_hotplug 23564 1 shpchp
eeprom_93cx6 2175 1 rtl8187
serio_raw 4653 0
i2c_algo_bit 5391 0
ttm 64320 0
drm_kms_helper 33051 0
drm 208958 2 ttm,drm_kms_helper
tpm_tis 9074 0
tpm 13765 1 tpm_tis
tpm_bios 5121 1 tpm
video 11307 0
b43 353506 0
snd_hda_codec_realtek 60726 1
iTCO_wdt 12813 0
iTCO_vendor_support 1929 1 iTCO_wdt
snd_hda_intel 24053 0
snd_hda_codec 94305 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 6300 1 snd_hda_codec
snd_pcm 74958 2 snd_hda_codec,snd_hda_intel
snd_page_alloc 7217 2 snd_pcm,snd_hda_intel
snd_timer 18966 1 snd_pcm
snd 58997 6 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 5410 1 snd
nvidia 11182217 0
sky2 49219 0
microcode 12345 0
i2c_i801 8180 0
ssb 48803 1 b43
pcspkr 1899 0
evdev 9754 11
firewire_ohci 31709 0
intel_agp 10936 0
firewire_core 51552 1 firewire_ohci
intel_gtt 14047 1 intel_agp
crc_itu_t 1363 1 firewire_core
thermal 7959 0
fan 2426 0
button 4502 0
pcmcia 35785 2 b43,ssb
bcma 22757 1 b43
mmc_core 82070 2 b43,ssb
coretemp 5654 0
i2c_core 20369 6 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,adt7475,nvidia
mac80211 395712 2 b43,rtl8187
cfg80211 170255 3 b43,mac80211,rtl8187
rfkill 15604 1 cfg80211
pcmcia_core 12253 1 pcmcia
vboxnetadp 18387 0
vboxnetflt 16871 0
vboxdrv 1792216 2 vboxnetadp,vboxnetflt
acpi_cpufreq 5933 0
mperf 1299 1 acpi_cpufreq
processor 26567 1 acpi_cpufreq
nfs 276152 0
nfs_acl 2359 1 nfs
lockd 62987 1 nfs
auth_rpcgss 32327 1 nfs
sunrpc 185190 4 nfs,auth_rpcgss,lockd,nfs_acl
fscache 41059 1 nfs
ext4 424871 6
crc16 1359 1 ext4
jbd2 73919 1 ext4
mbcache 5977 1 ext4
aes_x86_64 7508 40
cryptd 8741 0
aes_generic 26138 1 aes_x86_64
xts 3101 20
gf128mul 6050 1 xts
dm_crypt 16496 5
dm_mod 70918 11 dm_crypt
sr_mod 14823 0
cdrom 35648 1 sr_mod
sd_mod 29239 8
usbhid 36462 0
hid 85541 1 usbhid
usb_storage 44760 0
pata_jmicron 2480 0
pata_acpi 3408 0
ata_piix 23160 7
ata_generic 3295 0
uhci_hcd 23436 0
libata 167611 4 pata_acpi,ata_generic,ata_piix,pata_jmicron
scsi_mod 132736 7 sg,st,uas,usb_storage,libata,sd_mod,sr_mod
ehci_hcd 41026 0
usbcore 147661 7 uas,uhci_hcd,rtl8187,usb_storage,ehci_hcd,usbhid
usb_common 954 1 usbcore
floppy 58615 0
vfat 10119 0
fat 49739 1 vfat
nls_cp437 5953 0
total used free shared buffers cached
Mem: 4052416 174372 3878044 0 20828 36868
-/+ buffers/cache: 116676 3935740
Swap: 5122680 0 5122680
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend:
/usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/50netcfg suspend suspend:
/usr/lib/pm-utils/sleep.d/50netcfg suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
Unloading kernel module rfkill...Done.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /etc/pm/sleep.d/90alsa suspend suspend:
/etc/pm/sleep.d/90alsa suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
nVidia binary video drive detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Sat Aug 25 23:16:04 EDT 2012: performing suspend
hibernate:
Initial commandline parameters:
Sat Aug 25 22:13:46 EDT 2012: Running hooks for hibernate.
Running hook /usr/lib/pm-utils/sleep.d/00logging hibernate hibernate:
Linux gateway 3.4.9-1-ARCH #1 SMP PREEMPT Wed Aug 15 18:59:31 CEST 2012 x86_64 GNU/Linux
Module Size Used by
xt_recent 7901 3
xt_tcpudp 2471 51
ip6table_mangle 1684 0
ipt_MASQUERADE 1738 1
nf_nat_ftp 1668 0
iptable_nat 4024 1
nf_nat 15100 3 nf_nat_ftp,ipt_MASQUERADE,iptable_nat
nf_conntrack_ipv4 6871 20 nf_nat,iptable_nat
nf_defrag_ipv4 1339 1 nf_conntrack_ipv4
xt_TCPMSS 3439 5
xt_LOG 11943 48
ipt_REJECT 2281 0
iptable_mangle 1584 0
xt_multiport 1758 0
xt_state 1295 17
xt_limit 2041 51
xt_conntrack 3329 0
nf_conntrack_ftp 6261 1 nf_nat_ftp
nf_conntrack 61584 8 nf_nat_ftp,ipt_MASQUERADE,nf_nat,xt_state,xt_conntrack,nf_conntrack_ftp,iptable_nat,nf_conntrack_ipv4
ip6table_filter 1396 1
ip6_tables 18198 2 ip6table_filter,ip6table_mangle
iptable_filter 1456 1
ip_tables 16946 3 iptable_filter,iptable_mangle,iptable_nat
x_tables 16954 17 ip6table_filter,ip6table_mangle,xt_recent,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_state,xt_conntrack,xt_LOG,xt_multiport,iptable_filter,xt_TCPMSS,ipt_REJECT,iptable_mangle,ip6_tables,iptable_nat
adt7475 20329 0
hwmon_vid 3196 1 adt7475
sg 25344 0
st 35573 0
uas 8823 0
rtl8187 52559 0
mxm_wmi 1425 0
wmi 8475 1 mxm_wmi
shpchp 26305 0
pci_hotplug 23564 1 shpchp
eeprom_93cx6 2175 1 rtl8187
serio_raw 4653 0
i2c_algo_bit 5391 0
ttm 64320 0
drm_kms_helper 33051 0
drm 208958 2 ttm,drm_kms_helper
tpm_tis 9074 0
tpm 13765 1 tpm_tis
tpm_bios 5121 1 tpm
video 11307 0
nvidia 11182217 0
arc4 1410 2
snd_hda_codec_realtek 60726 1
snd_hda_intel 24053 0
snd_hda_codec 94305 2 snd_hda_codec_realtek,snd_hda_intel
b43 353506 0
ssb 48803 1 b43
snd_hwdep 6300 1 snd_hda_codec
snd_pcm 74958 2 snd_hda_codec,snd_hda_intel
snd_page_alloc 7217 2 snd_pcm,snd_hda_intel
snd_timer 18966 1 snd_pcm
snd 58997 6 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 5410 1 snd
sky2 49219 0
pcmcia 35785 2 b43,ssb
bcma 22757 1 b43
i2c_i801 8180 0
iTCO_wdt 12813 0
iTCO_vendor_support 1929 1 iTCO_wdt
thermal 7959 0
fan 2426 0
button 4502 0
firewire_ohci 31709 0
mmc_core 82070 2 b43,ssb
firewire_core 51552 1 firewire_ohci
intel_agp 10936 0
intel_gtt 14047 1 intel_agp
crc_itu_t 1363 1 firewire_core
i2c_core 20369 6 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,adt7475,nvidia
pcspkr 1899 0
microcode 12345 0
evdev 9754 11
coretemp 5654 0
mac80211 395712 2 b43,rtl8187
cfg80211 170255 3 b43,mac80211,rtl8187
rfkill 15604 1 cfg80211
pcmcia_core 12253 1 pcmcia
vboxnetadp 18387 0
vboxnetflt 16871 0
vboxdrv 1792216 2 vboxnetadp,vboxnetflt
acpi_cpufreq 5933 0
mperf 1299 1 acpi_cpufreq
processor 26567 1 acpi_cpufreq
nfs 276152 0
nfs_acl 2359 1 nfs
lockd 62987 1 nfs
auth_rpcgss 32327 1 nfs
sunrpc 185190 4 nfs,auth_rpcgss,lockd,nfs_acl
fscache 41059 1 nfs
ext4 424871 6
crc16 1359 1 ext4
jbd2 73919 1 ext4
mbcache 5977 1 ext4
aes_x86_64 7508 40
cryptd 8741 0
aes_generic 26138 1 aes_x86_64
xts 3101 20
gf128mul 6050 1 xts
dm_crypt 16496 5
dm_mod 70918 11 dm_crypt
usbhid 36462 0
sr_mod 14823 0
hid 85541 1 usbhid
sd_mod 29239 8
cdrom 35648 1 sr_mod
pata_jmicron 2480 0
usb_storage 44760 0
pata_acpi 3408 0
uhci_hcd 23436 0
ata_piix 23160 7
ata_generic 3295 0
libata 167611 4 pata_acpi,ata_generic,ata_piix,pata_jmicron
scsi_mod 132736 7 sg,st,uas,usb_storage,libata,sd_mod,sr_mod
ehci_hcd 41026 0
usbcore 147661 7 uas,uhci_hcd,rtl8187,usb_storage,ehci_hcd,usbhid
usb_common 954 1 usbcore
floppy 58615 0
vfat 10119 0
fat 49739 1 vfat
nls_cp437 5953 0
total used free shared buffers cached
Mem: 2054092 156900 1897192 0 20680 36788
-/+ buffers/cache: 99432 1954660
Swap: 5122680 0 5122680
/usr/lib/pm-utils/sleep.d/00logging hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave hibernate hibernate:
/usr/lib/pm-utils/sleep.d/00powersave hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub hibernate hibernate:
/usr/lib/pm-utils/sleep.d/01grub hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/01laptop-mode hibernate hibernate:
/usr/lib/pm-utils/sleep.d/01laptop-mode hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth hibernate hibernate:
/usr/lib/pm-utils/sleep.d/49bluetooth hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/50netcfg hibernate hibernate:
/usr/lib/pm-utils/sleep.d/50netcfg hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules hibernate hibernate:
Unloading kernel module rfkill...Done.
/usr/lib/pm-utils/sleep.d/75modules hibernate hibernate: success.
Running hook /etc/pm/sleep.d/90alsa hibernate hibernate:
/etc/pm/sleep.d/90alsa hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock hibernate hibernate:
/usr/lib/pm-utils/sleep.d/90clock hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq hibernate hibernate:
/usr/lib/pm-utils/sleep.d/94cpufreq hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/95led hibernate hibernate:
/usr/lib/pm-utils/sleep.d/95led hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler hibernate hibernate:
nVidia binary video drive detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/99video hibernate hibernate:
/usr/lib/pm-utils/sleep.d/99video hibernate hibernate: success.
Sat Aug 25 22:13:48 EDT 2012: performing hibernate
This seems to be too few information to pin point the exact cause of the problem.
What should I do to troubleshoot this problem ?

My linux installation is actually on a harddrive using SATA on a desktop. I decided to remove this harddrive and put it into an external usb enclosure. I booted this linux installation on my laptop. When doing suspend, it works as it should, which let me think this is probably not a software issue.
If it is a hardware malfunction, which hardware malfunction can be responsible of an incomplete suspend procedure as described earlier?

Is there no better way to mount a disk than using Disk Utility?

When an unmounted disk needs mounting, it's kind of a pain to have to load an app (Disk Utility) to mount that disk. Is there no easier way, direct from the Desktop/Dock/Finder/via a third party plugin?

After you unmount the external drive, turn the power off.
When you need it again, turn the power to the external
drive back on and the drive will mount automatically.
If you will need to access the unmounted volume again after a
short time interval, then you should just leave it mounted.
DP 1.25 MDD & 1GHz 12" PB Mac OS X (10.4.7)

Mounting Windows Disk within Single User Mode

A Windows machine I administer kacked and the users didn't back up all their data. Windows won't touch the drive, so I popped it in a 10.3.9 Mac... I can copy a handful of files and folders from the Finder, but some directories won't read -- there may be physical damage to the drive (if the kernel panics are any indication).
When I boot into Single User Mode, I can't get into the disk.... the disk(s) show up under /Volumes, but you can't actually get into them... only a file named .autodiskmounted shows up for each Windows partition. I'm guessing this is a product of the disk being formatted as a NTFS drive (I'm thinking that's probably what Windows XP Home used on this drive).
Can you mount a NTFS or FAT32 disk from Single User Mode? How?
Many thanks!

Everett
To mount a disk in 10.3.9, look at the first part of this FAQ: Resetting the System Immutable Flag in 10.3.
You will need to replace the "mount -t hfs" with "mount -t msdos", but I don't know if you would need further options.
If you can find a 10.4 system, it may be easier, since "autodiskmount" appears to work again. See: kmosx4: Resetting the System Immutable Flag in OS X 10.4

SQL 2014 cluster installation on mounting point disks error: Updating permission setting for file

Dear all,
I am attempting to install SQL 2014 fail over cluster under a physical windows 2012 R2 server which have mounting point disks.
At the finish of setup I get the following error message.
Could you please help me on this?
Thanks
The following error has occurred:
Updating permission setting for file 'E:\Sysdata!System Volume Information\.....................................' failed. The file permission setting were supposed to be set to 'D:P(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;OICI;FA;;;CO)(A;OICI;FA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)'.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: go.microsoft.com/fwlink
I am using an administrator account which have all security rights (cheched on secpol.msc mmc) needed for installation.

Hi Marco_Ben_IT,
Do not install SQL Server to the root directory of a mount point, setup fails when the root of a mounted volume is chosen for the data file directory, we must always specify
a subdirectory for all files. This has to do with how permissions are granted. If you must put files in the root of the mount point you must manually manage the ACLs/permissions. We need to create a subfolder under the root of the mount point, and install
there.
More related information:
Using Mount Points with SQL Server
http://blogs.msdn.com/b/cindygross/archive/2011/07/05/using-mount-points-with-sql-server.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Need to Increase mount point disk space

Hello,
I do not know whether this is the appropriate forum to post my question.
I need to increase the mount /u01 disk space . I would like to club two mounts and make one File system to a make a bigger one. I do have 2 filesystems mounted on 2 disks as following.
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c1t4d0s0 2012390 9 1952010 1% /u01
/dev/dsk/c1t14d0s0 2012390 9 1952010 1% /u09
Is there any way that I can merge these two into one filesystem to make a 4 GB filesystem of /u01 ?
Thanks

Hi
You have to install a package called Solaris DiskSuite where there is a utility called growfs which can grow your file systems that is it can add more space to your existing file system. Which OS do u have . If you have solaris 7 you have to install it from sun early access CD..If it is already installed , then you have to follow the procedure as given below.
The following example expands a nonmetadevice slice for the /u01 file system. In this example, the existing slice, /dev/dsk/c1t4d0s0, is converted to a metadevice so additional slices can be concatenated.
# metainit -f d1 2 1 c1t4d0s0 1 c1t4d0s1
# umount /u01
(Edit the /etc/vfstab file to change the entry for /u01
to the newly defined metadevice, d1.)
# mount /u01
# growfs -M /u01 /dev/md/rdsk/d1

Mount UFS disk not working

Hi,
I am new to Solaris so this may be something simple I have missed. I am having troubles mounting a MO (magnetic Optical) disk on my Solaris 9 X 86 workstation.. I have just loaded the Solaris operating system, in the workstation I have an internal MO drive connected to an internal PCI SCSI card. I know the drive is working because I can format and create a newfs on disks, then mount read and write to the disks I have just created. I mount the disk by using the following command.
# mount /dev/dsk/c0t6d0s2 /mnt/mo
When I try to mount a disk MO formatted on another Solaris system using the same command I get an error
# mount /dev/dsk/c0t6d0s2 /mnt/mo
mount: /dev/dsk/c0t6d0s2 is not this fstype
I have tried to change the fstype to autofs in the vfstab file but this would not work. I have a Linux box with the same hardware installed and I can mount both MO disks (mine and ones formatted on other systems) by using the following command:
mount -t -ufs -o ufstype=sun /dev/sda /mnt/mo
I can read and write to both MO disks in Linux (after complilng the kernel with WR support for UFS in Linux) but not in Solaris.
Can anyone give me hints as to why I can not mount the disks from other Solaris machines?
Do I need to add other file system support?
Can I do some checks on the MO disk to make sure it is compatible?
Thanks in advance for any assistance.

Thanks for your responce.
I have 2 new solaris X86 boxes which I have just built. Our customer sends us data on MO disks formatted in UFS from their solaris 8 SPARC boxes. If what you are saying is true, it may not be possiable to read the MO disks on my X86 solaris box then.
All of the disks I am trying are 512 bytes/sector (4.1GB or 2.3GB).
I have not tried Solaris 10 but if may be worth a go before I go out and buy a SPARC station.
When I do the following commands this is the output I get:
On the UFS formatted on a SPARC station
#fdisk -w /dev/rdsk/c0t6d0p0
# (returns with no errors. I also tried s2 instead of s2)
#prtvtoc /dev/rdsk/c0t6d0s2
* /dev/rdsk/c0t6d0s2 partition map
* Dimensions:
* 512 bytes/sector
* 31 sectors/track
* 4 tracks/cylinder
* 124 sectors/cylinder
* 32047 cylinders
* 32045 accessable cylinders
* Flags:
* 1: Unmountable
* 10: Read-only
* Unallocated Space
* First Second Last
* Sector Count Sector
* 124 3973456 3973579
* First Second Last
* Partition Tag Flags Sector count sector mount dir
2 5 01 0 3973580 3973579
8 1 01 0 124 123
#fstpy /dev/dsk/c0t6d0s2
Unknown_fstype (no matches)
Drive formatted on my X86 box
results were teh same exept:
# fstyp /dev/dsk/c0t6d0s2
UFS
In conclusion does this mean that we can not read the disks formatted on the SPARC boxes?
Do you know of anything else I can try?
Thanks in advance.

IPod 4G always mounts for disk use when Mac wakes from sleep

My 4G iPod is always mounting for disk use when my Mac (10.4.8, Dual 1.8 GHz G5) wakes from sleep, even though the settings for the iPod has "enable disk use" unselected. When I launch iTunes (latest version) the iPod promptly is unmounted. I have restored factory settings, I have reinstalled the computer's OS and iTunes with it.
What is going on and how can I make it normal?
Dual 1.8 GHz G5 Mac OS X (10.4.8) iTunes 7.1, iPod 4G 20GB

UPDATE:
I have started to turn off Bluetooth at night before I put my computer to sleep. I HAVE NOT HAD THE FIREWIRE RANDOM DISMOUNT PROBLEM SINCE. I do not know if this is a freak coincidence -- but so far, so much the better for my firewire drive.
Hope this helps someone else down the line... eh hem...

Mounting RAM Disks as "-notremovable"

Similar Messages

Maybe you are looking for