[SOLVED] mount: /dev/sda3 is already mounted or /mnt busy
Hello all, I've spent several hours researching this to no avail. I'm trying to mount my partitions, first with my root partition (/dev/sda3) mounted at /mnt. It seems no matter what partition I try to mount it gives me the same error: mount: /dev/sda3 is already mounted or /mnt busy. I've tried the fuser command and killed all process associated with this device but new processes seem to pop up making it busy once more.
Hopefully somebody has some knowledge of what could be causing this one.
Thanks, and I hope to resurrect an Arch workstation once more!
-Aaron
Last edited by guitarxperience (2012-10-09 14:52:21)
guitarxperience wrote:
ewaller wrote:
guitarxperience wrote:
I'd love to post that but can you tell me how to post it when I'm running the install on another computer. ...I just don't know if there's a way to route the output to a URL or something after-all it is connected to the internet. But there is no browser as far as I know.
Why, yes!
community/wgetpaste 2.20-1 [installed]
A script that automates pasting to a number of pastebin services
ewaller@odin:~ 1004 %ls -l | wgetpaste
Your paste can be seen here: https://gist.github.com/3842491
ewaller@odin:~ 1005 %
Looks like a groovy tool.. Can you tell me how to get it on my installation setup? Don't seem to have apt-get available or anything like that to install things.
Oh yeah this is Arch so I would use pacman. The community database along with core and extra does not exist... when i run pacman.
Similar Messages
-
Mount fat32 on x86: already mounted or busy
hi. i suppose mounting fat32 on x86 is well-documented, but i'm having trouble, so i'd appreciate some help.
im dual booting with solaris 10 and xp. my partitions are as follows:
1st physical drive
[boot sector] 55 MB
[c:] label XP (NTFS)
solaris partitions...
2nd physical drive
[d:] label Data (FAT32) (about 17 GB)
i'd like to mount my FAT32 drive. according to man mount and man pcfs, i thought i'd do seomething like:
bash-3.00# mount -F pcfs /dev/dsk/c1t0d0p0:d /mnt/data
which yields:
mount: /dev/dsk/c1t0d0p0:d is already mounted or /mnt/data is busy
theres nothign in the /mnt/data folder. as far as i can tell, the drive isn't mounted. am i naming hte wrong device? im reading this "device-special:logical drive" stuff and i guess it's not making sense. i've included some more info below.
hopefully after this i can mount the drive in the vfstab, but if not i suppose ill be back.
bash-3.00# iostat -nxp
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
3.6 1.0 30.5 4.5 0.0 0.0 2.9 4.9 0 2 c0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 5.7 0 0 c0d1
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 fd0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t0d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c1t1d0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 unknown:vold(pid507)
bash-3.00# mount
/ on /dev/dsk/c0d0s0 read/write/setuid/devices/intr/largefiles/logging/xattr/oner ror=panic/dev=1980000 on Sun Feb 19 20:27:38 2006
/devices on /devices read/write/setuid/devices/dev=4380000 on Sun Feb 19 20:27:24 2006
/system/contract on ctfs read/write/setuid/devices/dev=43c0001 on Sun Feb 19 20:27:24 2006
/proc on proc read/write/setuid/devices/dev=4400000 on Sun Feb 19 20:27:24 2006
/etc/mnttab on mnttab read/write/setuid/devices/dev=4440001 on Sun Feb 19 20:27:24 2006
/etc/svc/volatile on swap read/write/setuid/devices/xattr/dev=4480001 on Sun Feb 19 20:27:24 2006/system/object on objfs read/write/setuid/devices/dev=44c0001 on Sun Feb 19 20:27:24 2006
/lib/libc.so.1 on /usr/lib/libc/libc_hwcap1.so.1 read/write/setuid/devices/dev=1980000 on Sun Feb 19 20:27:37 2006
/dev/fd on fd read/write/setuid/devices/dev=4680001 on Sun Feb 19 20:27:38 2006
/tmp on swap read/write/setuid/devices/xattr/dev=4480002 on Sun Feb 19 20:27:38 2006
/var/run on swap read/write/setuid/devices/xattr/dev=4480003 on Sun Feb 19 20:27:39 2006
/export/home on /dev/dsk/c0d0s7 read/write/setuid/devices/intr/largefiles/logging/xattr/oner ror=panic/dev=1980007 on Sun Feb 19 20:27:44 2006
thanks!!!thanks martin
i think i was trying to mount a SCSI drive instead of IDE that I have... thanks for clearing that up. i was also frustrated with teh :c part, I think I forgot about the 1st partition part.
im under the impression that c0d0p1:c is my first physical drive, which is NTFS because of:
bash-3.00# mount -F pcfs /dev/dsk/c0d0p1 /mnt/data
mount: /dev/dsk/c0d1p1:c is not a DOS filesystem.
but then why would c0d1p1 also yield:
bash-3.00# mount -F pcfs /dev/dsk/c0d1p1 /mnt/data
mount: /dev/dsk/c0d0p1, c0d0p2 is not a DOS filesystem.
then again c0d0p0, c0d0p2, and c0d1p0 yields the same...
is there a way to list the devices present, or do i have to throw knives at the wind? does anyone understand the naming schema of cN and dN? man pcfs and man mount don't help a whole lot.
i dont see anything helpful in the vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c0d0s1 - - swap - no -
/dev/dsk/c0d0s0 /dev/rdsk/c0d0s0 / ufs 1 no -
/dev/dsk/c0d0s7 /dev/rdsk/c0d0s7 /export/home ufs 2 yes -
/devices - /devices devfs - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
swap - /tmp tmpfs - yes -
i also found thsi script that output the devices... but it doesnt see any fat32 partitions =(
bash-3.00# for f in /dev/rdsk/* ; do echo "$f = $(fstyp $f 2>/dev/null )"; done
/dev/rdsk/c0d0p0 =
/dev/rdsk/c0d0p1 =
/dev/rdsk/c0d0p2 =
/dev/rdsk/c0d0p3 =
/dev/rdsk/c0d0p4 =
/dev/rdsk/c0d0s0 = ufs
/dev/rdsk/c0d0s1 =
/dev/rdsk/c0d0s10 =
/dev/rdsk/c0d0s11 =
/dev/rdsk/c0d0s12 =
/dev/rdsk/c0d0s13 =
/dev/rdsk/c0d0s14 =
/dev/rdsk/c0d0s15 =
/dev/rdsk/c0d0s2 =
/dev/rdsk/c0d0s3 =
/dev/rdsk/c0d0s4 =
/dev/rdsk/c0d0s5 =
/dev/rdsk/c0d0s6 =
/dev/rdsk/c0d0s7 = ufs
/dev/rdsk/c0d0s8 =
/dev/rdsk/c0d0s9 =
/dev/rdsk/c0d1p0 =
/dev/rdsk/c0d1p1 =
/dev/rdsk/c0d1p2 =
/dev/rdsk/c0d1p3 =
/dev/rdsk/c0d1p4 =
/dev/rdsk/c0d1s0 =
/dev/rdsk/c0d1s1 =
/dev/rdsk/c0d1s10 =
/dev/rdsk/c0d1s11 =
/dev/rdsk/c0d1s12 =
/dev/rdsk/c0d1s13 =
/dev/rdsk/c0d1s14 =
/dev/rdsk/c0d1s15 =
/dev/rdsk/c0d1s2 =
/dev/rdsk/c0d1s3 =
/dev/rdsk/c0d1s4 =
/dev/rdsk/c0d1s5 =
/dev/rdsk/c0d1s6 =
/dev/rdsk/c0d1s7 =
/dev/rdsk/c0d1s8 =
/dev/rdsk/c0d1s9 =
/dev/rdsk/c1t0d0p0 =
/dev/rdsk/c1t0d0p1 =
/dev/rdsk/c1t0d0p2 =
/dev/rdsk/c1t0d0p3 =
/dev/rdsk/c1t0d0p4 =
/dev/rdsk/c1t0d0s0 =
/dev/rdsk/c1t0d0s1 =
/dev/rdsk/c1t0d0s10 =
/dev/rdsk/c1t0d0s11 =
/dev/rdsk/c1t0d0s12 =
/dev/rdsk/c1t0d0s13 =
/dev/rdsk/c1t0d0s14 =
/dev/rdsk/c1t0d0s15 =
/dev/rdsk/c1t0d0s2 =
/dev/rdsk/c1t0d0s3 =
/dev/rdsk/c1t0d0s4 =
/dev/rdsk/c1t0d0s5 =
/dev/rdsk/c1t0d0s6 =
/dev/rdsk/c1t0d0s7 =
/dev/rdsk/c1t0d0s8 =
/dev/rdsk/c1t0d0s9 =
/dev/rdsk/c1t1d0p0 =
/dev/rdsk/c1t1d0p1 =
/dev/rdsk/c1t1d0p2 =
/dev/rdsk/c1t1d0p3 =
/dev/rdsk/c1t1d0p4 =
/dev/rdsk/c1t1d0s0 =
/dev/rdsk/c1t1d0s1 =
/dev/rdsk/c1t1d0s10 =
/dev/rdsk/c1t1d0s11 =
/dev/rdsk/c1t1d0s12 =
/dev/rdsk/c1t1d0s13 =
/dev/rdsk/c1t1d0s14 =
/dev/rdsk/c1t1d0s15 =
/dev/rdsk/c1t1d0s2 =
/dev/rdsk/c1t1d0s3 =
/dev/rdsk/c1t1d0s4 =
/dev/rdsk/c1t1d0s5 =
/dev/rdsk/c1t1d0s6 =
/dev/rdsk/c1t1d0s7 =
/dev/rdsk/c1t1d0s8 =
/dev/rdsk/c1t1d0s9 =
/dev/rdsk/c2t0d0p0 = fstyp: cannot stat or open </dev/rdsk/c2t0d0p0>
/dev/rdsk/c2t0d0p1 = fstyp: cannot stat or open </dev/rdsk/c2t0d0p1>
/dev/rdsk/c2t0d0p2 = fstyp: cannot stat or open </dev/rdsk/c2t0d0p2>
/dev/rdsk/c2t0d0p3 = fstyp: cannot stat or open </dev/rdsk/c2t0d0p3>
/dev/rdsk/c2t0d0p4 = fstyp: cannot stat or open </dev/rdsk/c2t0d0p4>
/dev/rdsk/c2t0d0s0 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s0>
/dev/rdsk/c2t0d0s1 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s1>
/dev/rdsk/c2t0d0s10 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s10>
/dev/rdsk/c2t0d0s11 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s11>
/dev/rdsk/c2t0d0s12 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s12>
/dev/rdsk/c2t0d0s13 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s13>
/dev/rdsk/c2t0d0s14 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s14>
/dev/rdsk/c2t0d0s15 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s15>
/dev/rdsk/c2t0d0s2 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s2>
/dev/rdsk/c2t0d0s3 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s3>
/dev/rdsk/c2t0d0s4 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s4>
/dev/rdsk/c2t0d0s5 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s5>
/dev/rdsk/c2t0d0s6 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s6>
/dev/rdsk/c2t0d0s7 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s7>
/dev/rdsk/c2t0d0s8 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s8>
/dev/rdsk/c2t0d0s9 = fstyp: cannot stat or open </dev/rdsk/c2t0d0s9>
thanks again for your help -
Mount: /dev/sda2 already mounted or /u01 busy
Installed new OELinux4.7 with disk partitions but unable to to mount these
[oracle@localhost sbin]$ ./fdisk -l (give no results)
[root@localhost /]# mount /dev/sda3 /u01
mount: /dev/sda3 already mounted or /u01 busy
[root@localhost /]# cd /sbin
*[root@localhost sbin]# ./fdisk -l*
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 19 152586 83 Linux
/dev/sda2 20 2630 20972857+ 8e Linux LVM
/dev/sda3 2631 5241 20972857+ 8e Linux LVM
/dev/sda4 5242 60801 446285700 5 Extended
/dev/sda5 5242 7852 20972826 8e Linux LVM
/dev/sda6 7853 10463 20972826 8e Linux LVM
/dev/sda7 10464 13074 20972826 8e Linux LVM
*[root@localhost sbin]# df -h*
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol01
20G 3.5G 16G 19% /
/dev/sda1 145M 15M 123M 11% /boot
none 3.0G 0 3.0G 0% /dev/shm
/dev/mapper/VolGroup00-LogVol02
20G 78M 19G 1% /home
[root@localhost /]# mount /dev/sda2 /u01
mount: /dev/sda2 already mounted or /u01 busy
[root@localhost /]#On a system without LVM, a filesystem is created inside a partition. fdisk is used to list partitions on disks. Because the filesystems are inside the partitions, you can use the name of parition to mount it.
On a system with LVM, a filesystem is created inside a logical volume, not in a partition. The partitions (fdisk -l) are used as physical volumes (pvdisplay), which are added to a volume group (vgdisplay), in which a logical volume can be created (lvdisplay). In the logical volume a filesystem is created. Because of this, only the logical volumes can be used to mount the filesystem.
LVM adds an abstraction layer between filesystems and partitions. This is extremely handy because it's easy to add a disk (which is made physical volume) to a volume group which makes space available, which can be added to any logical volume in the volume group. When that's done, the filesystem in the logical volume can be enlarged with resize2fs, even online. Without LVM, it's not possible or very hard at best to do that. -
"none already mounted or /dev/pts busy" udev 050-2
Just did a clean install on a new hard drive. Using udev. Haven't made any changes from default, except added "devfs=nomount" to the grub boot line.
I get this error message during boot up:
"none already mounted or /dev/pts busy"
when I issue "mount" command, I do not see /dev/pts listed. If I try "mount /dev/pts" I get the same complaint "none already mounted or /dev/pts busy"
1. What is pts? Why would it be busy?
2. How do I solve this complaint?
Thank you,
John R
[edit] was directed to bugs.archlinux.org, a report exists there.johnr wrote:What is pts? Why would it be busy?
Is this line in your /etc/fstab?:
/dev/pts devpts defaults 0 0 -
[SOLVED] Mount /dev/sda4 (recycled) /home, when booting
Dear Archlinux users,
I reinstalled Archlinux with the goal to reuse my /home partition which is on /dev/sda4.
What i did was i reinstalled Archlinux with the netinstall cd, i formatted /dev/sda1/2/3 (/boot swap /root) and kept the /dev/sda4 /home folder partition.
When i boot it does not automatically mount the /dev/sda4 to /home.
How can i mount /dev/sda4 to /home at boot automatically?
Thanks for helping
I had to add the rule to /etc/fstab
#/etc/sda4 /home etx4 defaults 0 1
Sorry for the inconvenience
Last edited by verbin (2012-07-10 21:41:31)Dear Archlinux users,
I reinstalled Archlinux with the goal to reuse my /home partition which is on /dev/sda4.
What i did was i reinstalled Archlinux with the netinstall cd, i formatted /dev/sda1/2/3 (/boot swap /root) and kept the /dev/sda4 /home folder partition.
When i boot it does not automatically mount the /dev/sda4 to /home.
How can i mount /dev/sda4 to /home at boot automatically?
Thanks for helping
I had to add the rule to /etc/fstab
#/etc/sda4 /home etx4 defaults 0 1
Sorry for the inconvenience
Last edited by verbin (2012-07-10 21:41:31) -
[Solved] Inconsistency in device naming concerning mount/fstab
This is not a problem that needs to be solved, but rather a gap in my understanding of a mechanism.
I have several partitions mounted in my fstab, they are identified by UUID.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump><pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
UUID=0767c51a-0ba8-405e-ac98-106182fe4d83 /tmp ext4 noexec,rw,noatime,nodiratime 0 2
UUID=0ba14b78-1b36-4857-92ae-8b1ca41264b6 /boot ext2 defaults 0 1
UUID=4eb07abb-25b0-4683-badf-8d556b536d9c / ext4 defaults 0 1
UUID=e3fe5429-379b-4b6d-a01e-e30aa85784e2 /home ext4 defaults 0 1
UUID=e7fda340-ca00-4c4c-b42e-cfba13a3abbe swap swap defaults 0 0
UUID=e3ae11a4-b602-4ea2-bbf7-8c8c9dea52a6 /mnt/Esther ext4 defaults,rw,noatime,nodiratime 0 2
UUID=55525a1b-386b-4390-8f47-b078b0b2c06e /mnt/Ballamb ext4 defaults,rw,noatime,nodiratime 0 2
UUID=b71cfb8d-a4eb-4ded-a65b-fbc2db102332 /mnt/Galbadia ext4 defaults,rw,noatime,nodiratime 0 2
When all drives are mounted, they show up as mounted by device name (/dev/sd*), only / is displayed as mounted by UUID.
$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=386283,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
/dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c on / type ext4 (rw,relatime,barrier=1,data=ordered)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
/dev/sdc2 on /tmp type ext4 (rw,noexec,noatime,nodiratime)
/dev/sda1 on /boot type ext2 (rw)
/dev/sda4 on /home type ext4 (rw)
/dev/sdb1 on /mnt/Esther type ext4 (rw,noatime,nodiratime)
/dev/sdc1 on /mnt/Ballamb type ext4 (rw,noatime,nodiratime)
/dev/sdd1 on /mnt/Galbadia type ext4 (rw,noatime,nodiratime)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfs-fuse-daemon on /home/xy/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=xy)
$ df -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
udev 10M 0 10M 0% /dev
run 10M 192K 9,9M 2% /run
/dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c 68G 8,5G 56G 14% /
shm 1,5G 4,0K 1,5G 1% /dev/shm
/dev/sdc2 289G 194M 274G 1% /tmp
/dev/sda1 251M 17M 222M 7% /boot
/dev/sda4 849G 62G 745G 8% /home
/dev/sdb1 1,8T 1,5T 223G 88% /mnt/Esther
/dev/sdc1 1,1T 223G 810G 22% /mnt/Ballamb
/dev/sdd1 1,8T 390G 1,4T 23% /mnt/Galbadia
Now I feel the urge to know why. Neither the mount nor the fstab manfile gave me insight on this one. So, what's behind this?
Last edited by Awebb (2011-10-08 17:51:26)Now I feel stupid for not searching properly. Solved. Thanks, karol.
EDIT: So, in other words, if the UUID is passed by Grub, it shows as UUID in the system,
http://projects.archlinux.org/mkinitcpi … 3afd7e0001
So it was solved about a year ago? Well...
Last edited by Awebb (2011-05-29 14:12:06) -
[SOLVED] ERROR: Unable to find root device '/dev/sda3'
Earlier I updated the kernel to my arch system and found this error while trying to boot. I hate to post this because there are so many topics like it, but I've been looking for hours for a solution to this problem and can't find one.
Here is the output:
Booting 'Arch Linux'
root (hd0,1)
Filesystem type is ext2fs, partition type 0x83
kernet /vmlinuz-linux root=/dev/sda3 ro
[Linux-bzImage, setup=0x4200, size=0x2ff2d0]
initrd /initrd @ 0xfd17000, 0x2c878c bytes]
Probing EDD (edd=off to disable)... ok
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
:: Starting udevd...
done.
Waiting 10 seconds for device /dev/sda3 ...
ERROR: device '/dev/sda3' not found. skipping fsck.
ERROR: Unable to find root device '/dev/sda3'.
You are being dropped to a recovery shell
type 'exit' to try and continue booting
sh: can't access tty; job control turned off
My partition layout is like this:
swap: /dev/sda1
boot: /dev/sda2
root: /dev/sda3
extended: /dev/sda4
home: /dev/sda5
I have two hard drives, but i'm sure /dev/sda is the one with my OS.
Here are some things I've tried:
This was at the very bottom of the pacman wiki
# mkdir /mnt/arch
# mount /dev/sdaX /mnt/arch (your root partition)
# cd /mnt/arch
# mount -t proc proc proc/
# mount -t sysfs sys sys/
# mount -o bind /dev dev/
# mount /dev/sdaX boot/ (your /boot partition) #This step is not needed if you do not have a separate boot partition
# chroot .
# pacman -Syu udev mkinitcpio
# mkinitcpio -p linux
I've also tried performing the above, downgrading the kernel, updating my mirrorlist, reinstalling the kernel, and rebooting as mentioned here.
I've alsa tried a few other things that I've read, but can no longer remember.
Any help would be greatly appreciated! Thanks.
Last edited by colton7909 (2012-05-25 02:09:36)Thank colton
Same problem here, but on a mac book (not mine eyh )
So, for those how have the problem (or need a live usb for mac or uefi systems),
1) with a 32bits system
- download gparted live cd
- use it for the step 3
2) with a 64bits system:
- you need the gparted live cd too: mount it and copy the EFI directory somewhere; then umount it;
- download a 64bits system (system rescue cd, as colton said is enough, follow the instructions for installation on their website first);
- mount you live usb, install the 64bits system;
- copy EFI system on the key
- edit the grub.cfg in EFI/boot/ , add the following before the other entries:
menuentry "System Rescue" {
set gfxpayload=keep
linux /syslinux/altker64 nomodeset efi
initrd /syslinux/initram.igz
3) repairing...
- boot the broken computer with the live usb
- mount the partition on which your system is (e.g. /dev/sda1 on /mnt)
- chroot it, init the system as needed (mount /dev, /proc, etc. the easier way is using init scripts)
% chroot /mnt /bin/bash
% /etc/rc.sysinit
% mkinitcpio -p linux -
Can't mount /dev/hdc during install?
Hi,
I've inherited a Dell Precision 410 computer (PIII, perhaps 6 years old?). It currently has
an older version of RedHat installed and I'm attempting to install Arch. The Arch CD boots
and loads vmlinuz and goes through screenfulls of initialization info. It gets down
to loading the add-on modules and pauses; then it comes back and says
"Can't mount /dev/hdc -- (Empty media?)" and drops me at the "#" prompt with the
message to enter "loaddisk /dev/hdc" if I need extra modules. I attempt that and I
get the same "Can't mount hdc" message. I can enter "/arch/setup" and get the
initial menu, but since no modules are loaded my network card is not working, etc.
How can the bootup and menus work, but yet /dev/hdc (which is the CDROM itself)
not be mountable? If I boot the old Redhat, I see the link "/dev/cdrom --> /dev/hdc".
If I start Gnome and insert the Arch CD, it automounts (under /dev/hdc) and
I can browse the CD contents (including the add-ons folder) and see all the files.
I have used the same CD to install Arch on another non-Dell computer so I believe
the media is OK.
Clues as to how/why /dev/hdc is causing a problem during vmlinuz startup?
Thanks in advance,
Roggie BooneProblem solved ... looks like it was either a defective CDROM drive or just one
that the kernel did not recognize. I salvaged a Lite-On drive from another
computer and Arch was able to mount it as /dev/hdc during the install.
Roggie -
X4100 mount command for second drive shows device already mounted
I have a new x4100 system and I created a new partition and ext3 filesystem on the second drive. When I try to use that partition I get the error:
mount: /dev/sdb1 already mounted
Since this is a new system, that partition has never been used and I can't see anywhere that the device is in use. I tried the same thing on other systems and I get the same error. Has anyone seen this problem and if so how was it resolved?
thanksPost Unix/Terminal queries to its forum under OS X Technologies.
-
Mounting /dev/hda1 on home/ftp/c failed on NI-8196 PXI controller.
Hi folks,
I am having some problems in recognising a PXI controller ( NI-8196
) and a field point unit on my host MAX. I know both of them are
on the same subnet. I have Labview RT running on the PXI controller. I
don't know which version though.
The problem is while setting up the IP configuration for the PXI
controller in the MAX. It doesnt take the IP from either the DHCP
server or when I use static IP's. I have already checked the Switch
settings on the controller. All of them are OFF. The BIOS option for
the IP reset has been disabled too, still the controller boots up with
0.0.0.0
While booting up it gives me the error: " mounting
/dev/hda1 on home/ftp/c failed: Invalid Arguement. Booting in
safe mode. "
With the field point unit, the MAX doesnt recognise it on the network. it doesn't show up under the REMOTE SYSTEMS panel.
My MAX version is 4.0, Labview version on the host is 8.0
Any help will be greatly appreciated.
Thank you,
SandeepFor the PXI chassis, I would start by trying a reformat. RT Disk Utilities in MAX>> Create format and boot disks.
For the fieldpoint Try using this document. http://zone.ni.com/devzone/conceptd.nsf/webmain/49e7983a1c47a3af86256a3a005b4a3e?OpenDocument -
[kinda solved, hd broken]Salvaged hard drive mounted as read-only
My old netbook died recently (if a guy in a shady computer store in Edinburgh tells you that "this adapter will surely work" -- what ever you do, don't believe him). Got a new netbook, and an external usb hd case for the old hard drive in the hope of salvaging it.
The old hd seems to have survived, as it mounts just fine and all my old partitions show up (home folder, root, swap...). However, I cannot change the permissions of the files using thunar as root, nor can I copy them to my internal hd --probably because the drive is mounted as read-only. The /home partition, which is the one I'm interested in copying things from, is formated in ext4.
I'm guessing I should change something in my fstab, though I'm not sure what exactly. What's weird though is that the drive does not show up when I run sudo fdisk -l, nor does it show in gparted (which is run as root, of course) -- meaning I don't know what rule I should put in my fstab file, as I dont know what mount point to apply it to. I use xfce on my current laptop, but seeing as the problem persists when I try on my partners ubuntu laptop I figure that the DE hasn't got much to do with it.
I guess I could open up the computer, put in the old hard drive and change some configs, install drivers etc. to make my new computer boot properly from it. Does seem like a drag though, so I figured I'd try asking here first. I suspect this is a fairly common problem, but my google-fu does not appear to be strong enough as I've failed to find a solution on my own.
Last edited by caligo (2010-07-19 20:09:01)karol wrote:'mount: /dev/sdd2: cannot read superblock' is quite different from mounting read-only - I'd call it read ... NOT!
I hope you have some sort of backup.
Yes, "cannot read" is indeed a more disheartening message... When trying to copy the files through thunar, I can see them but not move or open them -- and trying to change the permissions results in an error message about the file system being "read-only".
itsbrad212 wrote:# fsck /dev/sdd2
results in
Attempt to read block from filesystem resulted in short read
The thing might indeed be dead...
I have backups of all the important things -- just wanted to save some recent random files and a bunch of wallpapers, but I think I'll survive the loss. Thanks for the help guys. Might try to format the whole thing, see if its just the data that's corrupted or of the harware is busted as well. -
Hi
After upgrading to osx 10.9.3, my external hard drive was not able to mount, but it can be mounted without issue in osx 10.6, how do I solve it? it was formatted by disk utility.
Thanks
PTFrom the menu bar, select
▹ System Preferences ▹ Energy Saver ▹ Power Adapter
and uncheck the box labeled Put the hard disk(s) to sleep when possible, if it's checked.
If the drive has more than one interface (USB, FireWire, Thunderbolt, eSATA), try one of the other interfaces.
Check that the data cable is securely inserted at both ends.
Try a different cable.
If you're connecting the drive through a hub, connect it directly to a built-in port on the Mac.
If you're connecting it directly, try a different port.
Disconnect all other devices on the bus, or as many as possible.
Test the drive with another Mac. Test another drive with this Mac.
If the drive is bus-powered, but has an AC adapter, connect the adapter.
Start up in Recovery mode and launch Disk Utility. Is the drive recognized?
Start up in Safe Mode and test.
Reset the NVRAM.
Reset the System Management Controller.
If the drive doesn't work under any of the above conditions, and if another drive does work with the same Mac, then the drive has failed. You may be able to salvage the mechanism by removing it from the enclosure and installing it in another one, or in a drive dock. -
IS Windows 7 already Mounted on BOot camp in OS x Mountain Lion
Hi GUys
i just wanted to ask that is the Windows 7 64 bit already mounted on BOOT CAMP in OS X mounation lion............... if it is do i need to buy a Disk for windows 7 Just in caseOf course you have to buy it. And then you have to install it. did you really think you'd get it for free?
-
Root.sh diskgroup already mounted in another lock name space
I have successfully installed oracle grid infrastructure 11.2.0.3 and have created an oracle database on an asm instance on top of it.
I installed the database as a RAC database on a single node db-test-mi-1, postponing the addition of a second node at a later time.
Now I have a second node db-test-mi-2, that I need to add to to the database.
I have successfully performed
cluvfy stage -pre nodeadd -n db-test-mi-2 -verbose
without any errors.
When I try to extend grid infrastructure to the new node, with
./addNode.sh "CLUSTER_NEW_NODES={db-test-mi-2}" "CLUSTER_NEW_VIRTUAL_HOSTNAMES={db-test-mi-2-vip}"
it works fine, but the script /oracle/app/11.2.0/grid/root.sh, from the grid home of the second node, generates an error
ORA-15032: not all alterations performed
ORA-15017: diskgroup "DATADG" cannot be mounted
ORA-15003: diskgroup "DATADG" already mounted in another lock name space
This is because of course the ASM instance on the first node is locking the disk group.
How can I extend ASM to the second node??
Any hel greatly appreciatedHi,
Please refer
Troubleshooting 11.2 Grid Infrastructure root.sh Issues (Doc ID 1053970.1)
Thanks,
Rajasekhar -
After boot can't mount SDS file systems on 3300 mount: cannot mount /dev/md
Hi
I have a SUNW,Netra-440 with two SE 3300 SCSI each with two controllers. The server was working fine but after a boot, it can not see the metadevices stored in the 3300.
I have tried restarting the SE3300 and a boot -r from ok prompt but I still can see those disks or partitions.
Metaset Import
metaset: log01: setname "appvol": no such set
mount all SVM filesystems for group appvol
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d101
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d102
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d103
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d104
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d105
mount: No such device
mount: cannot mount /dev/md/appvol/dsk/d106
metaset: log01: setname "dbvol": no such set
mount all SVM filesystems for group dbvol
mount: No such device
mount: cannot mount /dev/md/dbvol/dsk/d107
mount: No such device
mount: cannot mount /dev/md/dbvol/dsk/d108
i can see the devices in /dev/md/appvol but i can't mount them.
Any ideas what this could be? using metaset shows nothing, metastat -s dbvol hangs.
Am I missing some patch or am I missing something here? is the SE3300 damaged? or is it a problem with SDS (solstice). I have solaris 9.
The system was working fine until we had to boot and power off to perform power tests in the rack.
thanks
Ryck
this is the output of prtdiag
root@log01 >prtdiag
System Configuration: Sun Microsystems sun4u Netra 440
System clock frequency: 177 MHZ
Memory size: 8GB
==================================== CPUs ====================================
E$ CPU CPU Temperature
CPU Freq Size Implementation Mask Die Amb. Status Location
0 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
1 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
2 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
3 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
================================= IO Devices =================================
Bus Freq Slot + Name +
Type MHz Status Path Model
pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1c,600000/scsi@1
pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1c,600000/scsi@1,1
pci 66 MB pci108e,abba (network) SUNW,pci-ce
okay /pci@1c,600000/network@2
pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1d,700000/scsi@1
pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1d,700000/scsi@1,1
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@0
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@1
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@2
pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
okay /pci@1d,700000/pci@2/network@3
pci 33 MB isa/su (serial)
okay /pci@1e,600000/isa@7/serial@0,3f8
pci 33 MB isa/su (serial)
okay /pci@1e,600000/isa@7/serial@0,2e8
pci 33 MB isa/rmc-comm-rmc_comm (seria+
okay /pci@1e,600000/isa@7/rmc-comm@0,3e8
pci 33 PCI0 SUNW,XVR-100 (display) SUNW,375-3290
okay /pci@1e,600000/SUNW,XVR-100
pci 33 MB pciclass,0c0310 (usb)
okay /pci@1e,600000/usb@a
pci 33 MB pciclass,0c0310 (usb)
okay /pci@1e,600000/usb@b
pci 33 MB pci10b9,5229 (ide)
okay /pci@1e,600000/ide@d
pci 66 MB pci108e,abba (network) SUNW,pci-ce
okay /pci@1f,700000/network@1
pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1f,700000/scsi@2
pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
okay /pci@1f,700000/scsi@2,1
============================ Memory Configuration ============================
Segment Table:
Base Address Size Interleave Factor Contains
0x0 2GB 4 BankIDs 0,1,2,3
0x1000000000 2GB 4 BankIDs 16,17,18,19
0x2000000000 2GB 4 BankIDs 32,33,34,35
0x3000000000 2GB 4 BankIDs 48,49,50,51
Bank Table:
Physical Location
ID ControllerID GroupID Size Interleave Way
0 0 0 512MB 0,1,2,3
1 0 1 512MB
2 0 1 512MB
3 0 0 512MB
16 1 0 512MB 0,1,2,3
17 1 1 512MB
18 1 1 512MB
19 1 0 512MB
32 2 0 512MB 0,1,2,3
33 2 1 512MB
34 2 1 512MB
35 2 0 512MB
48 3 0 512MB 0,1,2,3
49 3 1 512MB
50 3 1 512MB
51 3 0 512MB
Memory Module Groups:
ControllerID GroupID Labels Status
0 0 C0/P0/B0/D0
0 0 C0/P0/B0/D1
0 1 C0/P0/B1/D0
0 1 C0/P0/B1/D1
1 0 C1/P0/B0/D0
1 0 C1/P0/B0/D1
1 1 C1/P0/B1/D0
1 1 C1/P0/B1/D1
2 0 C2/P0/B0/D0
2 0 C2/P0/B0/D1
2 1 C2/P0/B1/D0
2 1 C2/P0/B1/D1
3 0 C3/P0/B0/D0
3 0 C3/P0/B0/D1
3 1 C3/P0/B1/D0
3 1 C3/P0/B1/D1
root@log01 >Hi,
thanks for your answer.
Yes format displays the physical devices, but metadb -i only shows the internal disks of the netra 440, not the ones in the 3320. metadb -s dbvol -i doesnt show anything.
metaset which is supposed to show me the metadevices, says the program is not registered.
cat /etc/lvm/md.tab has the configuration but since the scsi can be seen, the devices aren't mounted.
Any suggestions?
Cheers
Oscar
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootdisk
/pci@1f,700000/scsi@2/sd@0,0
1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootmirr
/pci@1f,700000/scsi@2/sd@1,0
2. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare1
/pci@1f,700000/scsi@2/sd@2,0
3. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare2
/pci@1f,700000/scsi@2/sd@3,0
4. c2t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> appvol
/pci@1c,600000/scsi@1/sd@8,0
5. c2t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol01
/pci@1c,600000/scsi@1/sd@9,0
6. c2t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol02
/pci@1c,600000/scsi@1/sd@a,0
7. c2t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol03
/pci@1c,600000/scsi@1/sd@b,0
8. c2t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol04
/pci@1c,600000/scsi@1/sd@c,0
9. c2t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol05
/pci@1c,600000/scsi@1/sd@d,0
10. c3t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol06
/pci@1c,600000/scsi@1,1/sd@8,0
11. c3t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1
/pci@1c,600000/scsi@1,1/sd@9,0
12. c3t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2
/pci@1c,600000/scsi@1,1/sd@a,0
13. c3t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3
/pci@1c,600000/scsi@1,1/sd@b,0
14. c3t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotAPP
/pci@1c,600000/scsi@1,1/sd@c,0
15. c3t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDB
/pci@1c,600000/scsi@1,1/sd@d,0
16. c4t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> APPVOLm
/pci@1d,700000/scsi@1/sd@8,0
17. c4t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@9,0
18. c4t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@a,0
19. c4t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@b,0
20. c4t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@c,0
21. c4t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1/sd@d,0
22. c5t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> d6Mirr
/pci@1d,700000/scsi@1,1/sd@8,0
23. c5t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1M
/pci@1d,700000/scsi@1,1/sd@9,0
24. c5t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2M
/pci@1d,700000/scsi@1,1/sd@a,0
25. c5t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3M
/pci@1d,700000/scsi@1,1/sd@b,0
26. c5t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1d,700000/scsi@1,1/sd@c,0
27. c5t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDBm
/pci@1d,700000/scsi@1,1/sd@d,0
root@log01 >metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a p luo 16400 8192 /dev/dsk/c1t0d0s7
a p luo 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7
a p luo 16400 8192 /dev/dsk/c1t1d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
root@log01 >
root@log01 >metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a p luo 16400 8192 /dev/dsk/c1t0d0s7
a p luo 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7
a p luo 16400 8192 /dev/dsk/c1t1d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
root@log01 >metadb -s appvol -i
metadb: log01: setname "appvol": no such set
root@log01 >metaset
metaset: log01: metad client create: RPC: Program not registered
root@log01 >cat /etc/lvm/md.tab
# Copyright 2002 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# ident "@(#)md.tab 2.4 02/01/29 SMI"
# md.tab
# metainit utility input file.
dbvol/d57 1 1 c2t12d0s0
dbvol/d58 1 1 c4t12d0s0
dbvol/d4 -m dbvol/d57 dbvol/d58 1
dbvol/d55 1 1 c2t11d0s0
dbvol/d56 1 1 c4t11d0s0
dbvol/d3 -m dbvol/d55 dbvol/d56 1
dbvol/d61 1 1 c3t8d0s0
dbvol/d62 1 1 c5t8d0s0
dbvol/d6 -m dbvol/d61 dbvol/d62 1
dbvol/d59 1 1 c2t13d0s0
dbvol/d60 1 1 c4t13d0s0
dbvol/d5 -m dbvol/d59 dbvol/d60 1
dbvol/d53 1 1 c2t10d0s0
dbvol/d54 1 1 c4t10d0s0
dbvol/d2 -m dbvol/d53 dbvol/d54 1
###dbvol/d51 1 1 c2t9d0s0
dbvol/d52 1 1 c4t9d0s0
#dbvol/d1 -m dbvol/d51 dbvol/d52 1
dbvol/d1 -m dbvol/d52 1
# SOFT Partitions
dbvol/d129 -p dbvol/d5 -o 19933376 -b 526336
dbvol/d128 -p dbvol/d5 -o 19407008 -b 526336
dbvol/d127 -p dbvol/d5 -o 18880640 -b 526336
dbvol/d126 -p dbvol/d5 -o 10489952 -b 8390656
dbvol/d125 -p dbvol/d5 -o 2099264 -b 8390656
dbvol/d123 -p dbvol/d4 -o 4724864 -b 133120
dbvol/d122 -p dbvol/d4 -o 4460640 -b 264192
dbvol/d121 -p dbvol/d4 -o 4196416 -b 264192
dbvol/d120 -p dbvol/d4 -o 32 -b 4196352
dbvol/d119 -p dbvol/d3 -o 30972032 -b 526336
dbvol/d118 -p dbvol/d3 -o 10489952 -b 20482048
dbvol/d117 -p dbvol/d3 -o 4196416 -b 6293504
dbvol/d116 -p dbvol/d3 -o 32 -b 4196352
dbvol/d115 -p dbvol/d2 -o 8925408 -b 526336
dbvol/d114 -p dbvol/d2 -o 8399040 -b 526336
dbvol/d113 -p dbvol/d2 -o 7872672 -b 526336
dbvol/d112 -p dbvol/d2 -o 7346304 -b 526336
dbvol/d111 -p dbvol/d2 -o 5247072 -b 2099200
dbvol/d110 -p dbvol/d2 -o 1050688 -b 4196352
dbvol/d109 -p dbvol/d2 -o 32 -b 1050624
dbvol/d108 -p dbvol/d1 -o 33554496 -b 1572864
dbvol/d107 -p dbvol/d1 -o 32 -b 33554432
dbvol/d124 -p dbvol/d5 -o 32 -b 2099200
dbvol/d138 -p dbvol/d4 -o 38416608 -b 133120
dbvol/d137 -p dbvol/d3 -o 31498400 -b 264192
dbvol/d136 -p dbvol/d4 -o 21637312 -b 16779264
dbvol/d135 -p dbvol/d4 -o 4858016 -b 16779264
dbvol/d134 -p dbvol/d6 -o 69212288 -b 23070720
dbvol/d133 -p dbvol/d6 -o 46141536 -b 23070720
dbvol/d132 -p dbvol/d6 -o 23070784 -b 23070720
dbvol/d131 -p dbvol/d6 -o 32 -b 23070720
dbvol/d130 -p dbvol/d5 -o 20459744 -b 526336
root@log01 >metadb -s dbvol -i
metadb: log01: setname "dbvol": no such set
root@log01 >\
Maybe you are looking for
-
I would really appreciate some help with my search & results page that is now throwing up the following error: Warning: mysql_free_result() expects parameter 1 to be resource, null given in...... line (the line number refers to the following code: my
-
Error while running procedure for refreshing AWS
Hello There, I am using a procedure which consists the script of refreshing the analytic workspace. I call this procedure from Business objects data services for automatic refresh. It used to work perfectly until the recent changes implemented. The i
-
When I try to print from a web page using Firefox, the page usually does not print in the correct format and I always get extra blank pages. Usually the first page that comes out it blank. I'm using a HP d135 All-in-one printer. This problem does not
-
Quarter to months drilldown problem
Hi, I need to create a repprt in which i need to calculate net sales for a quarter. and then when i drilldown on the quarter i should get monthly figures. Can someone please tell me how to implement this. Thanks
-
Hey I got the N95 and I once used a toothpick to remove some dust between the cover and screen(edges) so now when I look carefull under the cover in sun light I could see that I scratched the rubber in between and the metal behind shows just about 1c