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.

Similar Messages

[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.

Mount: can't find /dev/sda2/mnt in /etc/fstab

I'm trying to install Arch on a virtualbox virtual machine to become familiar with it before I install it on my main system. I've created 4 partitions, dev/sda1=1007kB boot partition, dev/sda2/= 4gb root partition which I am trying to mount, dev/sda3=swap which I've already configure and dev/sda4=1792MB Home which I haven't mounted. I've formatted sda2 and sda4 in ext4, but whenever I run
mount /dev/sda2/mnt
I get an error message saying
mount: can't find /dev/sda2/mnt in /etc/fstab
I've tried to view fstab with the less command but I only got a bunch of tildes (~). I'm fairly new to linux so keeping the explanations simple would be appreciated.

The above post should fix the immediate issue you are posting about - but there is another issue:
VEL0CITY wrote:dev/sda1=1007kB boot partition
Is that a typo? Because that's not big enough for a boot partition. The kernel itself is 3-4 times that size. 100MB is a common starting suggestion for /boot. I can do with quite a bit less than 100MB, but not that much less.

QFS problem: Error: mount_samfs: mount() error: Device busy

Hi:
I setup the QFS on my two nodes sun cluster 3.2 environment. Everything works fine. But when i reboot both nodes, the QFS system cann't be mounted. it shows following error:
Error: mount_samfs: mount() error: Device busy
Following is my setup procedure:
*2. Create the mcf file (on both nodes)*
#cd /etc/opt/SUNWsamfs/
#vi mcf
# Equipment Eq Eq Family Device Additional
# Identifier Ord Type Set State Parameters
archive 2 ma archive on shared
/dev/did/dsk/d5s4 20 mm archive on
/dev/did/dsk/d5s3 21 mr archive on
*3. Create the hosts file (on both nodes)*
#cd /etc/opt/SUNWsamfs/
#vi hosts.archive
#HostName NetworkInterface ServerPriority Unused Server
xenon 172.16.0.129 1 0 server
arsenic 172.16.0.130 1 0
*4. modify the /etc/vfstab file (on both nodes)*
#vi /etc/vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
archive - /archive samfs - no shared,notrace
*5. create the mount point (on both nodes)*
#mkdir /archive
#chmod 755 archive
*6. create the file system (on the server node)*
[root@xenon:/etc/opt/SUNWsamfs #]samd config
Configuring SAM-FS
[root@xenon:/etc/opt/SUNWsamfs #]sammkfs -S -a 64 archive
Building 'archive' will destroy the contents of devices:
/dev/did/dsk/d5s4
/dev/did/dsk/d5s3
Do you wish to continue? [y/N]y
total data kilobytes = 68525248
total data kilobytes free = 68525184
total meta kilobytes = 1044224
total meta kilobytes free = 1043680
*7. mount the file system*
on server side
[root@xenon:/etc/opt/SUNWsamfs #]mount /archive
[root@xenon:/etc/opt/SUNWsamfs #]chown �R oracle:dba /archive
On client side
[root@arsenic:/etc/opt/SUNWsamfs #]mount /archive
mount_samfs: Configuring file system
*8. Create the QFS metadata server (MDS) resource group for high availability.*
From xenon do:
# clresourcetype register SUNW.qfs
# clresourcegroup create -p nodelist=xenon,arsenic archive-rg
# clresource create -t SUNW.qfs -g archive-rg -p QFSFileSystem=/archive archive-rs
# clresourcegroup online -emM archive-rg
Actually, i did not do the step 8 (Create the QFS metadata server (MDS) resource group for high availability).
then i reboot both nodes, the QFS failed to be mounted
I found one doc is related to my problem.
http://sunsolve.sun.com/search/document.do?assetkey=1-25-90055
It suggests to restart the samfs-qfs Resource Group to fix the problem. But the problem is i haven't setup the "samfs-qfs Resource Group ".
How can i do now? any advices?
Many many thanks!
Larry chen
Edited by: chenjg00 on Nov 13, 2007 12:38 PM

It looks like you have the wrong entries in your hosts.archive file.
On a cluster, these should always reference the clusternode-priv names, e.g.
-bash-3.00# cat hosts.rac_data
pgyruss1 clusternode1-priv 1 0 server
pgyruss2 clusternode2-priv 1 0
These resolve to slight different addresses to the ones you are using and that might be the cause of your problem.
-bash-3.00# getent hosts clusternode1-priv
172.16.4.1 clusternode1-priv
Try that and see if it works. You might have to fiddle about a bit and may need to run "samd config" again.
Tim
---

[SOLVED] Trying to install Arch Linux from harddisk using /dev/sda2

Hi
I'm trying to install Arch using my swap partition, following this wiki entry: https://wiki.archlinux.org/index.php/Ha … stallation
What I've done:
Downloaded ISO: archlinux-2010.05-netinstall-i686.iso
Command: swapoff /dev/sda2
Command: fdisk /dev/sda and changed the system type to 83 (Linux) on /dev/sda2
Now it looks like:
Command (m for help): p
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00017e5b
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1060289 530144+ 83 Linux
/dev/sda2 1060290 3164804 1052257+ 83 Linux
/dev/sda3 3164805 105579179 51207187+ 83 Linux
/dev/sda4 105579180 488392064 191406442+ 83 Linux
It complained about device was busy, but it still seemed to have changed the system type, so I did partprobe as it wrote.
WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.
[root@swamp ~]# partprobe
<no output>
Next I did:
[root@swamp ~]# dd if=archlinux-2010.05-netinstall-i686.iso of=/dev/sda2
327680+0 records in
327680+0 records out
167772160 bytes (168 MB) copied, 4.3025 s, 39.0 MB/s
[root@swamp ~]# mkdir /mnt/sda2
[root@swamp ~]# mount /dev/sda2 /mnt/sda2
mount: warning: /mnt/sda2 seems to be mounted read-only.
[root@swamp ~]# ls -al /mnt/sda2
total 150466
dr-xr-xr-x 3 root root 240 May 16 15:54 .
drwxr-xr-x 6 root root 4096 Nov 5 01:40 ..
dr-xr-xr-x 3 root root 556 May 16 15:52 boot
-r--r--r-- 1 root root 448 May 16 15:54 isomounts
-r--r--r-- 1 root root 8192 May 16 15:54 overlay.sqfs
-r--r--r-- 1 root root 154058752 May 16 15:54 root-image.sqfs
And unmounted it again.
The wiki page says to type: fsck -f /dev/sda2fsck, but I get no such file while trying to open sda2fsck.
[root@swamp ~]# fsck -f /dev/sda2fsck
fsck from util-linux-ng 2.18
e2fsck 1.41.12 (17-May-2010)
fsck.ext2: No such file or directory while trying to open /dev/sda2fsck
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Can I ignore the above and continue modifying grub?
Thanks :-)
Last edited by valvet (2010-11-08 14:49:07)

fsck -f /dev/sda2fsck makes no sense because /dev/sda2fsck is not a deivce. If the wiki says that, then it is wrong. It's only doing a fsck anyway so probably not really needed. If you are just formatting th swap partition then use, mkfs.ext{234}.
edit:
from the wiki
# fsck -f /dev/sda2fsck 1.40.8 (13-Mar-2008)
e2fsck 1.40.8 (13-Mar-2008)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda2: 243/78936 files (8.2% non-contiguous), 310519/314880 blocks
The first like should just be
# fsck -f /dev/sda2
Last edited by sand_man (2010-11-05 06:46:01)

Bad magic number in super-block while trying to open /dev/sda2

hello,
So I've a linux partition, and then I wanted to install a Windows copy. I've only 1 HDD with differents partition into it:
sda5 (swap)
sda6 /user
sda7/var
sda8 / (which contain the boot and root of course)
sda3 /home
sda2 NTFS (windows xp)
So, as I had linux installed before windows, I had to make my sda2 NTFS (87) under my cfdisk. Then, I went to install windows, everything worked fine, windows booted with his boot system, but I had to restore grub with my archlinux live cd:
grub> find /boot/grub/stage1
grub>root (hd0,7)
grub>setup (hd0)
everything worked successfully, my grub loaded till while booting archlinux I got this error:
couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sda2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
What I tried is to run the e2fsck -b 8193 /dev/sda2 but right after that, I thought about it, this isn't linux partition so of course, the superblock isn't the same as they are ntfs type from widnows?
I've read on some forum but unfortunately didn't solve my problem, if anyone has any suggestion before I format the NTFS partition, I'd really appreciate it.
best regards, maz

what I think it happened, is that after installing windows your partitions numbers got twisted a bit. What you have to do is to edit /etc/fstab, and check out your linux and swap partitions mounting entries, I believe you just have to change the number of /dev/sda[number] coresponding to your linux partition in fstab
If you can't solve it, post the output of
fdisk -l
and
cat /etc/fstab
Last edited by I'mGeorge (2011-07-21 20:53:31)

[UPDATED] Setting up RAID 1 consisting of ramdisk and /dev/sda2

I'm not quite sure which board this question belongs to, so I'll post it in the newbie section, as I feel like one right now.
I need help with setting up my root partition as a RAID 1 of a ramdisk and a partition on my disk.
I have a very fresh arch install (2014-03-20) running on a this system:
512M /dev/sda1 vfat -> /boot (boot- and uefi-partition)
12G /dev/sda2 ext4 -> /
104.5G /home
64G RAM
My wish is to run / as a RAID 1 of the 12G /dev/sda2 ext4 and a 12G Ramdisk ext4.
I have read this great post on doing exactly this and the entire thread it is posted in, concerning running Arch entirely in RAM. But, to the best of my understanding, the use of a simple block device in RAM such as /dev/rd/0 has since been deprecated. I have been able to set them up manually with:
$ sudo mknod -m 660 /dev/rd b 1 1
But when I try to zero out the space I need on the device I'm unable to write more than 16 Mb of data to the device.
$ sudo dd if=/dev/zero of=/dev/rd bs=1K count=12288k
dd: error writing ‘/dev/rd’: No space left on device
16385+0 records in
16384+0 records out
16777216 bytes (17 MB) copied, 0.0222693 s, 753 MB/s
Likewise, I'm unable to set up a ext4fs larger than 16M on the device.
From what I have understood, this 16 M limit comes from the ramdisk_size kernel param during boot or from the rd_size param when loading the rd kernel module. Only problem is, the kernel param ramdisk_size=12582912 doesn't seem to help me and there doesn't seem to be any rd module in the arch kernel.
So my questions for now:
* Is there some other way than rd_size and ramdisk_size to set maximum ramdisk size to 12G?
* Am I doing something wrong?
Last edited by Hrafnahnef (2014-04-01 14:07:57)

This may not be what you want, but I managed to mount a ramdisk as the root /.
I was not interested to tried setting up such an array, as it seems to me that the ramdisk method is more flexible than the array method. By flexibility, I mean that the size of the ramdisk can be changed between reboots, but the array cannot -- I don't think that an array can be expanded or shrinked once created. Also, the disk is not needed to be accessed once the ramdisk is ready; and you can choose what folders of the root hierarchy to be copied into RAM.

[Solved] Cant use second partition /dev/sda2

sudo mount /dev/sda2 /mnt
this works and i see lost+found of the /dev/sda2
but i cant write or add folders to /dev/sda2
"Error creating directory: Permission denied"
and it disapears from the file manager side panel
this happend when i was using thunar in xfce
and again when using pcmanfm in openbox
Last edited by Shockwave0 (2013-11-12 08:27:26)

as user with sudo
[shockwave@ArchLinux ~]$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ext4 aff5b1d2-0452-467f-81e7-dc3b2298101e /
├─sda2 ext4 backup b8c96528-bdce-4a7b-9d0b-b215e9332242 /mnt
└─sda3 swap 1519cef9-0d8d-4ea4-b9d5-cc94b09cd59a
sr0 iso9660 ARCH_201311 2013-11-01-08-10-26-00 /run/media/shock
[shockwave@ArchLinux ~]$
[shockwave@ArchLinux ~]$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=2023684k,nr_inodes=505921,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=25,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/sr0 on /run/media/shockwave/ARCH_201311 type iso9660 (ro,nosuid,nodev,relatime,uid=1000,gid=100,iocharset=utf8,mode=0400,dmode=0500,uhelper=udisks2)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
/dev/sda2 on /mnt type ext4 (rw,relatime,data=ordered)
Last edited by Shockwave0 (2013-11-07 01:14:05)

[SOLVED] Slow "dev-sda2.device" at boot...

First of all, hello everyone. This is my first post on Arch Linux forums, so don't hesitate to correct me if I am doing something wrong.
I have been trying to reduce the boot time on my HDD;
-Using readahead
-Quiet boot
I have managed to reduce the boot time dramatically, but there is a problem, which is a task on boot called dev-sda2.device and it takes more than 6 seconds
systemd-analyze
Startup finished in 1.226s (firmware) + 123ms (loader) + 5.340s (kernel) + 11.205s (userspace) = 17.895s
systemd-analyze blame
6.283s dev-sda2.device
1.728s systemd-readahead-collect.service
1.728s systemd-readahead-replay.service
1.215s wicd.service
656ms systemd-udevd.service
487ms [email protected]
443ms systemd-udev-trigger.service
438ms systemd-vconsole-setup.service
381ms systemd-sysctl.service
380ms boot.mount
378ms systemd-journald.service
259ms kmod-static-nodes.service
244ms systemd-remount-fs.service
202ms sys-kernel-config.mount
200ms dev-mqueue.mount
199ms sys-kernel-debug.mount
180ms tmp.mount
179ms dev-hugepages.mount
134ms systemd-tmpfiles-setup-dev.service
64ms [email protected]
53ms systemd-user-sessions.service
49ms systemd-logind.service
43ms wpa_supplicant.service
25ms systemd-random-seed.service
24ms systemd-readahead-done.service
23ms systemd-tmpfiles-setup.service
5ms systemd-journal-flush.service
5ms systemd-update-utmp.service
4ms alsa-restore.service
3ms [email protected]
2ms [email protected]
2ms [email protected]
1ms [email protected]
1ms systemd-backlight@backlight:intel_backlight.service
systemd-analyze critical-chain
graphical.target @11.205s
└─multi-user.target @11.205s
└─wicd.service @9.989s +1.215s
└─basic.target @9.986s
└─sockets.target @9.985s
└─dbus.socket @9.985s
└─sysinit.target @9.861s
└─systemd-update-utmp.service @9.855s +5ms
└─systemd-tmpfiles-setup.service @9.830s +23ms
└─local-fs.target @9.829s
└─boot.mount @9.447s +380ms
└─[email protected] @8.959s +487ms
└─dev-sda1.device @8.959s
As you can see, dev-sda2.device takes too long and I have no idea what it is. I have been searching it for two days, and found only one topic here, which didn't help me, so I am posting this topic.
-I updated my system today.
-UEFI
-Gummiboot
I know that 17 seconds is a very fast boot, but I want to make it faster. Why not if I can?
Thanks...
EDIT: Updating the system again fixed this.
Last edited by atahanacar (2015-05-19 10:35:31)

What file system are you using, and what is the mount point for /dev/sda2?
there could be some mount options depending on your filesystem, that could slow down/speed up mounting.
depending on mount point, using x-systemd.automount option could help.
I actually have similar issue where mounting of my /home on btrfs takes 6-7s of my 18s boot time and I haven't found a solution. Most of the time I just suspend/hibernate my laptop anyway, so it's not such a big issue for myself.

"Unable to find root device /dev/sda2"

Hi!
After an update - seemingly unsuccessfull - I get dropped into a recovery shell. The messages are:
/usr/lib/suspend/resume: /usr/lib/libpng14: version `PNG14_0`not found (required by /usr/lib/libsplshrender.so.1)
ERROR: unable to find root device '/dev/sda2'
I read that now I'm supposed to run a LiveCD and chroot something... can someone please be a little more specific here? I don't want to lose that system and I have no idea why it doesn't find my disk anymore. I just performed a pacman4 uprade, but it seems pacman4 is rather immature, leaving a system unuseable like that.
There is no sdaX in /dev any more. And I have very little experience with recovering Arch Linux. Until now
Best,
wishi

I have some wild problems here
1.) I used an Arch Live CD, did the chroot trick from the wiki (https://wiki.archlinux.org/index.php/Ch … nging_Root) and rebuild my initcpio (https://wiki.archlinux.org/index.php/Mkinitcpio). That ends successfull, and says it adds hooks for sata etc.
-> But I had to remove the udev hook: http://bbs.archbang.org/viewtopic.php?pid=11304 - I guess that's the reason why it still doesn't find my /dev/sda2 - I'm not sure this is related though.
2.) I ran pacman -Qk to ensure everything is sane. No errors. I reinstalled linux and udev two minutes ago. No change.
But I don't see how I can fix this. What's that voodoo with some udev hooks wandering around? The new kernel is 3.2.5-1 ARCH.

Cant mount /dev/sda2 /mnt

hello,everybody
I'm a beginner
I want to install ArchLinux in my Dell notebook ,the sda1 had installed window xp,i want to make a dual system .
I burn a Arch Linux ISO cd and enter the live system,then the questions are coming....
After partitioning the drive by cfdisk tool,i cant mount the sda2 on the /mnt
the error code list this :
SQUASHFS error: Cant find a SQUASHFS superblock on sda2
EXT4-fs(sda2) : cant find ext4 filesystem
What's meaning ? I have partition the drive like this .Please other Linuxer help me or tell me how to solve this problem
cfdisk
name flags partType fsType size(MB)
sda1 Primary ntfs 30000
sda2 Boot Primary Linux 100
sda3 Primary Linux 10000
sda5 Logical Linux swap 2000
sda6 Logical Linux 70000

After you partitioned the drive, did you put filesystems on the partitions? Follow the steps in the Beginners' Guide, and use mkfs to put filesystems on the partitions. If sda2 is your boot partition, it's not the partition you want to mount at /mnt (you should mount your root partition there). Read the Guide.
https://wiki.archlinux.org/index.php/Beginners'_Guide
Last edited by 2ManyDogs (2012-12-16 04:48:46)

DEV- QAS : Obligatory transport target for business system not found

Hi guys!
I have read all the other threads about this subject, but since I still have no success, I´m feeling obligated to ask you for a help (deadline approaching fast!)
I´m trying to transport a Communication Channel, from DEV environment to QAS. I'm having the 'usual' error:
Import failed because of business system transfer of object Communication Channel * | SIGA | SOAP_SYNC_SENDER: Obligatory transport target for business system SIGA not found in System Landscape Directory
Here were my steps:
Keep in mind that in DEV, everything was up and running: Software Component, Product, Technical System and Business System for this name "SIGA".
1 - In DEV, I created a new Technical System, named "SIGA_QAS", pointing to my QAS server. (Keeping in mind I already had a "SIGA" pointing to my DEV server.)
2 - Still in DEV, I did create two groups: GROUP_DEV and GROUP_QAS, one points to INTEGRATION_SERVER_DX1 (DEV) and the other INTEGRATION_SERVER_QX1 (QAS).
3 - Still in DEV, I created the Business System called "SIGA_QAS" also, pointing to my QAS server.
4 - Still in DEV, I went inside both Business Systems and put: "SIGA_QAS" as TARGET BS of "SIGA" (which automatically puts "SIGA" as SOURCE BS of "SIGA_QAS")
If I look at my QAS SLD, I can see all of these objects already there, since my BASIS team did activate the 'sync' between these two environments. So, I dont need to create anything 'new' in my QAS SLD, all the objects are there, same as DEV SLD.
If I try to EXPORT/IMPORT a simple Communication Channel (using file system or even CTS - I tried both) I get the error mentioned above.
But this is 'wierd' for me, since the error says: "business system SIGA not found in System Landscape Directory", but it is there, in both SLDs.
Am I missing something here?
Thanks!
Ricardo Sancio Lóra
Brazil

Hi,
If you not tried this then try it. Delete the Business System SIGA from Integration Directory in your QAS system and then again import the business system from SLD. Acitvate the changes and then import the CC from Dev to QAS.
Regards,
Sarvesh

Error mounting an encrypted volume [solved]

On mounting an internal drive, which is encrypted (but isnt a system drive) I received the following error:
[root@kaminari /etc]# cryptsetup luksOpen /dev/sda2 data
Enter passphrase for /dev/sda2:
device-mapper: remove ioctl failed: Device or resource busy
But the device does get opened:
[root@kaminari /etc]# dmsetup ls
base-root (253, 3)
md2crypt (253, 0)
base-usr (253, 2)
base-var (253, 1)
data (253, 5)
base-home (253, 4)
[root@kaminari /etc]# dmsetup info data
Name: data
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 0
Event number: 0
Major, minor: 253, 5
Number of targets: 1
So I tried to mount it:
mount: /dev/sda2 already mounted or /mnt/data busy
Yet I cant find it. So thought I would reboot to reset everything as such. and this time it didnt error with "remove ioctl failed", but again I cant actually mount it.
[root@kaminari ~]# cryptsetup luksOpen /dev/sda2 data
Enter passphrase for /dev/sda2:
[root@kaminari ~]# mount -t ext3 /dev/sda2 /mnt/data
mount: /dev/sda2 already mounted or /mnt/data busy
[root@kaminari ~]# dmsetup ls
base-root (253, 3)
md2crypt (253, 0)
base-usr (253, 2)
base-var (253, 1)
data (253, 5)
base-home (253, 4)
Some info:
[root@kaminari ~]# cat /etc/mtab
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=506032,mode=755 0 0
/dev/mapper/base-root / ext3 rw,noatime,commit=0 0 0
devpts /dev/pts devpts rw 0 0
shm /dev/shm tmpfs rw,nosuid,nodev 0 0
/dev/mapper/base-home /home ext3 rw,noatime,commit=0 0 0
/dev/mapper/base-usr /usr ext3 rw,noatime,commit=0 0 0
/dev/mapper/base-var /var ext3 rw,noatime,commit=0 0 0
/dev/md1 /boot ext3 rw,noatime,commit=0 0 0
fusectl /sys/fs/fuse/connections fusectl rw 0 0
gvfs-fuse-daemon /home/rob/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=noodle 0 0
[root@kaminari ~]# cat /etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
/dev/mapper/base-home /home ext3 defaults,noatime 0 1
/dev/mapper/base-root / ext3 defaults,noatime 0 1
/dev/mapper/base-usr /usr ext3 defaults,noatime 0 1
/dev/mapper/base-var /var ext3 defaults,noatime 0 1
/dev/md1 /boot ext3 defaults,noatime 0 1
[root@kaminari ~]# lvscan
ACTIVE '/dev/base/var' [6.84 GiB] inherit
ACTIVE '/dev/base/usr' [19.53 GiB] inherit
ACTIVE '/dev/base/root' [1.95 GiB] inherit
ACTIVE '/dev/base/home' [97.66 GiB] inherit
Knowing me, I am (as usual!) Being daft. Would someone point out where
Last edited by Fruity (2010-11-29 21:36:48)

After some messing it about, I think it may be something to do with naultilus file manager, or the gnome disk utility.
How can I stop this behavior, so the disk is left alone for me to mount and unmount as I wish through the command line.
[solved] Knew I was being dopey, was tying to mount /dev/sda2, rather than referencing the device mapper name, like /dev/mapper/foo
Last edited by Fruity (2010-11-29 21:38:21)

/dev/shm not mounted /dev busy

Recently I was trying out a boot disk I had made, and basically, I switched it off several times due to it booting the completely wrong kernel.
Now, I'm getting to the stage "Checking File systems" and then comes up [Failed]. I then get a message saying Reboot required, and that it will reboot in 15 seconds, just a few seconds before it reboots I get "/dev/shm not mounted, /dev busy" or something similar.
I've booted up my sysresccd, ran "fsck.ext4 -fcv /dev/sda2" to force a check and scan for any bad blocks, it came up clean, then I rebooted and got the same error, so I copied the kernel and system.map over to /boot to make sure there's no corruption and reinstalled initscripts and util-linux-ng, rebooted, same error.
Tried different kernels, I've checked fstab and menu.lst, no problems there, so I still don't get why I still get the same problem.
Anybody know of any fix other than reinstalling arch?
EDIT: Editing /etc/rc.sysinit and commenting out the fsck part made it work, finding out why fsck failed now.
Last edited by compgenius999 (2010-03-03 19:21:35)

anybody?

Cannot mount cgroup: already mounted or busy

I am unable to mount cgroups on a fresh boot of a recent installation, fully up-to-date.
# mkdir /cgroups
# mount -t cgroup none /cgroups
mount: none already exists of /cgroups busy
According to lxc-config, I have cgroups enabled, and `dmesg | grep -i cgroup` confirms that the relevant subsystems are initialized. I am not finding anything added to dmesg.log, kernel.log, everything.log, etc., by the mount command.
Any ideas?

I am unable to mount cgroups on a fresh boot of a recent installation, fully up-to-date.
# mkdir /cgroups
# mount -t cgroup none /cgroups
mount: none already exists of /cgroups busy
According to lxc-config, I have cgroups enabled, and `dmesg | grep -i cgroup` confirms that the relevant subsystems are initialized. I am not finding anything added to dmesg.log, kernel.log, everything.log, etc., by the mount command.
Any ideas?

Mount: /dev/sda2 already mounted or /u01 busy

Similar Messages

Maybe you are looking for