Improve /dev/sda performace
I have a Samsung SATA II HD with 80G.
Which utility should I use, hdparm or sdparm? If it's sdparm, what shoult I put on /etc/rc.sysinit to improve performace?
Last edited by pain of salvation (2007-06-22 18:52:12)
So? Thanks for the hint, I killed that section.
You don't need hdparm/sdparm at all. See, the kernel takes care of detecting the controller and loading the right modules. And those in turn will detect the drive, its capabilities and set it up accordingly. It worked like that for many many years.
Should your drive not run with DMA enabled after booting, that's most likely a driver bug or hardware issue and nothing hdparm could fix.
For special cases like adjusting power management settings or the like, use /etc/rc.local.
Similar Messages
-
[solved] usbstick problem - how to make it /dev/sda
Hi guys,
I have a following issue: sometimes it happens that my younger sister pulls out my usbstick, this causes that it becomes /dev/sdb instead of /dev/sda. The only solution I know to return usbstick to /dev/sda it to restart the computer. Do you know any other solution?There's this udev trick:
http://wiki.archlinux.org/index.php/Ude … SB_devices
it looks like it will automaticly mount the device to /mnt/usbX . If that won't work you can always modify it to create a symlink from /mnt/usbX to /mnt/usb, or just mount any /dev/sdX to /mnt/usb .
Happy Hacking -
Unable to determine the sharedness of /dev/sda, /dev/sdb, /dev/sdc on nodes
hello, pls how do i fix this issue, the two scripts ran on first node, but failed on second node, after running cluvfy this is the output:
using cluvfy for storage requirements
Verifying shared storage accessibility
Checking shared storage accessibility...
WARNING:
Unable to determine the sharedness of /dev/sda on nodes:
rac2,rac1
WARNING:
Unable to determine the sharedness of /dev/sdb on nodes:
rac2,rac1
WARNING:
Unable to determine the sharedness of /dev/sdc on nodes:
rac2,rac1
WARNING:
Unable to determine the sharedness of /dev/sdd on nodes:
rac2
Shared storage check failed on nodes "rac2,rac1".
Verification of shared storage accessibility was unsuccessful on all the nodes.
using cluvfy for system requirements
Verifying system requirement
Checking system requirements for 'crs'...
Check: Total memory
Node Name Available Required Comment
rac2 1011.13MB (1035400KB) 1GB (1048576KB) failed
rac1 1011.13MB (1035400KB) 1GB (1048576KB) failed
Result: Total memory check failed.
Check: Free disk space in "/tmp" dir
Node Name Available Required Comment
rac2 1.07GB (1119972KB) 400MB (409600KB) passed
rac1 1.09GB (1141784KB) 400MB (409600KB) passed
Result: Free disk space check passed.
Check: Swap space
Node Name Available Required Comment
rac2 2GB (2096472KB) 1.5GB (1572864KB) passed
rac1 2GB (2096472KB) 1.5GB (1572864KB) passed
Result: Swap space check passed.
Check: System architecture
Node Name Available Required Comment
rac2 i686 i686 passed
rac1 i686 i686 passed
Result: System architecture check passed.
Check: Kernel version
Node Name Available Required Comment
rac2 2.6.18-8.el5 2.6.9 passed
rac1 2.6.18-8.el5 2.6.9 passed
Result: Kernel version check passed.
Check: Package existence for "make-3.81"
Node Name Status Comment
rac2 make-3.81-1.1 passed
rac1 make-3.81-1.1 passed
Result: Package existence check passed for "make-3.81".
Check: Package existence for "binutils-2.17.50.0.6"
Node Name Status Comment
rac2 binutils-2.17.50.0.6-2.el5 passed
rac1 binutils-2.17.50.0.6-2.el5 passed
Result: Package existence check passed for "binutils-2.17.50.0.6".
Check: Package existence for "gcc-4.1.1"
Node Name Status Comment
rac2 gcc-4.1.1-52.el5 passed
rac1 gcc-4.1.1-52.el5 passed
Result: Package existence check passed for "gcc-4.1.1".
Check: Package existence for "libaio-0.3.106"
Node Name Status Comment
rac2 libaio-0.3.106-3.2 passed
rac1 libaio-0.3.106-3.2 passed
Result: Package existence check passed for "libaio-0.3.106".
Check: Package existence for "libaio-devel-0.3.106"
Node Name Status Comment
rac2 libaio-devel-0.3.106-3.2 passed
rac1 libaio-devel-0.3.106-3.2 passed
Result: Package existence check passed for "libaio-devel-0.3.106".
Check: Package existence for "libstdc++-4.1.1"
Node Name Status Comment
rac2 libstdc++-4.1.1-52.el5 passed
rac1 libstdc++-4.1.1-52.el5 passed
Result: Package existence check passed for "libstdc++-4.1.1".
Check: Package existence for "elfutils-libelf-devel-0.125"
Node Name Status Comment
rac2 elfutils-libelf-devel-0.125-3.el5 passed
rac1 elfutils-libelf-devel-0.125-3.el5 passed
Result: Package existence check passed for "elfutils-libelf-devel-0.125".
Check: Package existence for "sysstat-7.0.0"
Node Name Status Comment
rac2 sysstat-7.0.0-3.el5 passed
rac1 sysstat-7.0.0-3.el5 passed
Result: Package existence check passed for "sysstat-7.0.0".
Check: Package existence for "compat-libstdc++-33-3.2.3"
Node Name Status Comment
rac2 missing failed
rac1 missing failed
Result: Package existence check failed for "compat-libstdc++-33-3.2.3".
Check: Package existence for "libgcc-4.1.1"
Node Name Status Comment
rac2 libgcc-4.1.1-52.el5 passed
rac1 libgcc-4.1.1-52.el5 passed
Result: Package existence check passed for "libgcc-4.1.1".
Check: Package existence for "libstdc++-devel-4.1.1"
Node Name Status Comment
rac2 libstdc++-devel-4.1.1-52.el5 passed
rac1 libstdc++-devel-4.1.1-52.el5 passed
Result: Package existence check passed for "libstdc++-devel-4.1.1".
Check: Package existence for "unixODBC-2.2.11"
Node Name Status Comment
rac2 unixODBC-2.2.11-7.1 passed
rac1 unixODBC-2.2.11-7.1 passed
Result: Package existence check passed for "unixODBC-2.2.11".
Check: Package existence for "unixODBC-devel-2.2.11"
Node Name Status Comment
rac2 unixODBC-devel-2.2.11-7.1 passed
rac1 unixODBC-devel-2.2.11-7.1 passed
Result: Package existence check passed for "unixODBC-devel-2.2.11".
Check: Package existence for "glibc-2.5-12"
Node Name Status Comment
rac2 glibc-2.5-12 passed
rac1 glibc-2.5-12 passed
Result: Package existence check passed for "glibc-2.5-12".
Check: Group existence for "dba"
Node Name Status Comment
rac2 exists passed
rac1 exists passed
Result: Group existence check passed for "dba".
Check: Group existence for "oinstall"
Node Name Status Comment
rac2 exists passed
rac1 exists passed
Result: Group existence check passed for "oinstall".
Check: User existence for "nobody"
Node Name Status Comment
rac2 exists passed
rac1 exists passed
Result: User existence check passed for "nobody".
System requirement failed for 'crs'
Verification of system requirement was unsuccessful on all the nodes.
cluvfy check for node connectivity
Verifying node connectivity
Checking node connectivity...
Interface information for node "rac2"
Interface Name IP Address Subnet Subnet Gateway Default Gateway Hardware Address
eth0 192.168.2.102 192.168.2.0 0.0.0.0 192.168.2.1 00:0C:29:4D:18:BA
eth1 192.168.0.102 192.168.0.0 0.0.0.0 192.168.2.1 00:0C:29:4D:18:C4
Interface information for node "rac1"
Interface Name IP Address Subnet Subnet Gateway Default Gateway Hardware Address
eth0 192.168.2.101 192.168.2.0 0.0.0.0 192.168.2.1 00:0C:29:A5:25:87
eth1 192.168.0.101 192.168.0.0 0.0.0.0 192.168.2.1 00:0C:29:A5:25:91
Check: Node connectivity of subnet "192.168.2.0"
Source Destination Connected?
rac2:eth0 rac1:eth0 yes
Result: Node connectivity check passed for subnet "192.168.2.0" with node(s) rac2,rac1.
Check: Node connectivity of subnet "192.168.0.0"
Source Destination Connected?
rac2:eth1 rac1:eth1 yes
Result: Node connectivity check passed for subnet "192.168.0.0" with node(s) rac2,rac1.
Interfaces found on subnet "192.168.2.0" that are likely candidates for a private interconnect:
rac2 eth0:192.168.2.102
rac1 eth0:192.168.2.101
Interfaces found on subnet "192.168.0.0" that are likely candidates for a private interconnect:
rac2 eth1:192.168.0.102
rac1 eth1:192.168.0.101
WARNING:
Could not find a suitable set of interfaces for VIPs.
Result: Node connectivity check passed.
Verification of node connectivity was successful.
Verifying administrative privileges
Checking user equivalence...
Check: User equivalence for user "oracle"
Node Name Comment
rac2 passed
rac1 passed
Result: User equivalence check passed for user "oracle".
Verification of administrative privileges was successful.Hi,
Refer --- *19. Pre-Installation Tasks for Oracle Clusterware* section from the below link:
http://www.oracle.com/technology/pub/articles/hunter_rac11gr1_iscsi_2.html
See this thread also seems to be same with ur issue:
Clusterware (Unable to determine the sharedness of) in VMware 2.0x server
Regards,
Xaheer -
/dev/sda is suddenly missing and how do I retrieve?
MAKEDEV is not under Darwin why?Yann,
Thank you. We are addressing that issue.
Kind regards,
Mark
Apple Discussions -
Auto Partion fails error = /dev/sda is mounted
I booted from the cd, ran /arch/setup then began going through the setup program
at the point it is going to auto partition my harddrive it fails with /dev/sda is mounted or busy.
I checked /mnt and its not showing anything mounted.
32M for boot
512M for swap
7500 for / and homeCorrect me if I'm wrong...I'm stuck at work on a *cough* winbloze machine.
rw=read/write
auto=mount when it boots up
user=users can mount/unmount
sync=write data to the drive immediatly when saved. async writes the data whenever it gets good and ready.
0 0 means the drive will never be force checked.
Or at least one of the 0's does. can't remember for the life of me what the other means. -
Cisco Security MARS 110 error - sfdisk:Cannot open /dev/sda for reading
HI when installing the MARS ver 6.0.1 we are getting this error sfdisk:Cannot open /dev/sda for reading, but found that this a bug for that ver BUG id : CSCso92379 - Cannot open /dev/sda for reading" error seen on installing Gen1 GC
So we tried installing the ver 5.3 now also getting the same error, pls let me know is this a hardware issue or a bugIt sounds like there may either be a problem with the RAID controller [configuration] or, though unlikely a hardware failure. You'd need to check the RAID controller BIOS to see if there's a hard disk drive problem or RAID configuration problem. Also check RAID controller is damaged as disks are not recognized at all.
Rebuild the Raid and reimage the appliances. -
SATA2 HDD slow based on these hdparm -Tt /dev/sda numbers [SOLVED]
I have a EG45M-UD2H running BIOS F3 (latest one as of the time of this post). I'm noticing a pretty significant HDD speed decrease with this board vs. my old board. If I take the same Seagate 7200.12 (1 gig) HDD and benchmark it on another motherboard, the cached reads are about 7x higher.
For example, under the EG45M-UD2H:
# hdparm -Tt /dev/sda
/dev/sda:
Timing cached reads: 2692 MB in 2.00 seconds = 1346.47 MB/sec
Timing buffered disk reads: 386 MB in 3.01 seconds = 128.13 MB/sec
On another motherboard (DFI LP P35-T2R):
# hdparm -Tt /dev/sda
/dev/sda:
Timing cached reads: 14740 MB in 2.00 seconds = 7378.19 MB/sec
Timing buffered disk reads: 368 MB in 3.02 seconds = 122.04 MB/sec
The only relevant settings I see in the BIOS are:
BIOS settings: Integrated Peripherals>SATA RAID/AHCI Mode [AHCI] <-- I have also set this to disable and there is no difference
SATA Port0-3 Native Mode [Enabled or Disabled] <-- I tried both and there is no difference
Does anyone have any thoughts?
$ lsmod | grep ahci
ahci 34321 4
libata 151860 4 pata_acpi,ata_generic,ahci,pata_jmicron
Last edited by graysky (2009-12-28 19:36:50)markp1989 wrote:
sounds like hddparm may off messed up, my p45 board isnt on right now, but i loged in to my server and did a hddparm test ....
mark@torrentslave:~$ sudo hdparm -Tt /dev/sda
/dev/sda:
Timing cached reads: 2308 MB in 2.00 seconds = 1153.72 MB/sec
Timing buffered disk reads: 332 MB in 3.01 seconds = 110.25 MB/sec
mark@torrentslave:~$
the 7000mbs cache read, way to high for a sata 3gb interface, so i think the first reading is a mistake.
i dont know of any other hdd test utils apart from dding to /dev/null. but some one will probably mention one soon
Thanks for the info, markp. Can you post the output from your P45 board once you have that system powered up? To answer your question, there's bonnie++ but it takes quiet a long time to run.
EDIT: This whole issue is a non-issue -- PEBKAC. Seems as though I was misusing the -T switch:
hdparm manpage wrote:
-T
Perform timings of cache reads for benchmark and comparison purposes. This displays the speed of reading directly from the Linux buffer cache without disk access. This measurement is essentially an indication of the throughput of the processor, cache, and memory of the system under test.
Last edited by graysky (2009-12-28 19:34:45) -
Dd to /dev/sda instead of /dev/sdb, how to restore /dev/sda
Hello,
yesterday I made a mistake, I did a dd to /dev/sda:
dd if=imagefile.img of=/dev/sda
Problem is my /dev/sda is my harddisk and it should have been /dev/sdb (usbstick).
Now my computer doesn't boot anymore.
How can I restore my harddisk without losing my data? The image file I copied was around 120MB.
Did dd than only overwrite the first 120MB or is there more?
Regards,
RoelThank You guys,
my arch-linux is up and running again in aprox. 1,5h time!!
First I tried to backup the harddisk with knoppix and saw my harddisk was empty, in gparted it seemed like it was never used... I was down, down, down... I didn't give up and downloaded systemrescuecd. Testdisk rstored my partition table and I saw it was my lucky day. The first partition on my harddrive was SWAP. All my files where intact and my stupid mistake only overwrote SWAP and MBR.
Reinstall grub would do the trick, i thought... but it didn't. Wy? Testdisk allocated my partitions to hda1 and hda2. In arch I had sda1 (swap); sda2 (/) and sda3 (/home). Now when I reinstalled grub the partition table didn't correspond to the ona in arch. A little bit fiddling in menu.lst, fstab and devices.map managed me to boot my arch system from fallback. My normal boot doesn't work though, I already changed everything to the right partitions but it keeps complaining about not finding my root partition. I already tried root=/dev/hda1; /sda1 and the whole rimram.
Can somebody tell me what's the problem?
It is probably my initrd file, isn't it? -
[SOLVED] Arch is on /dev/sdb but I want to remove /dev/sda
Hi. I've got 3 drives in my tower: sda, sdb and sdc. Arch is installed on sdb, but I want to physically remove the drive at sda. When I unplug the drive I get the syslinux menu at boot, but it ends up saying something like
"Root device mounted successfully, but /sbin/init does not exist....You're on your own", and it doesn't boot. If I plug the drive back in, it boots fine.
I'm not sure what's happening here, but I think it has something to do with the fact that I'm unplugging sda, then sdb/sdc get re-mapped to sda/sdb, or something like that. Right now my syslinux.cfg looks like this (note the APPEND root=/dev/sdb1 rw)
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sdb1 rw
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sdb1 rw
INITRD ../initramfs-linux-fallback.img
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL poweroff
MENU LABEL Poweroff
COM32 poweroff.c32
And fstab looks like this
# /dev/sdb1
UUID=54ece8c2-8998-4203-b2f8-66cb682e4bf0 / ext4 rw,relatime,data=ordered 0 1
# /dev/sdb2
#UUID=81fa4eea-4503-4fc5-8418-1fab3e753413 none swap defaults 0 0
I'm tempted to change sdb to sda in syslinux.cfg, and change the UUID=... to /dev/sda1 in fstab, but I don't want to screw with anything boot related since it's a really bad time for me to end up with a system that won't boot.
Am I on the right track here?
If I go ahead and make those changes, unplug the drive and end up with a system that won't boot, can I just go in there with a live-cd, change them back and expect it to boot as before...is that safe?
Last edited by Pacopag (2014-09-05 15:26:39)...by not reading the docs carefully enough...
So you're saying to change my APPEND root=UUID=54ece8c2-8998-4203-b2f8-66cb682e4bf0
in syslinux.cfg
And I should be able to boot with my other drives unplugged?
Last edited by Pacopag (2014-09-05 15:16:27) -
Arch Linux won't boot, "working on device dev/sda..."
Everytime I try to boot Arch there is a repeating message that pops up about every 3 seconds after the 'udev' events loads. My boot gets hung on the "working on device dev/sda6 (my linux partition on my laptop) and this message just keeps popping up every few seconds, repeatedly, non-stop:
ata1.00: exeption Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000008
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: emd 60/08/600:f1:69:51/00:00:16:00:00/40
ata1.00: tag 0 ncq 4096 in
ata1.00: status: {DRDY ERR}
ata1.00: error:{UNC}
and after 3 messages like the one above this message appears:
Ext4-fs error(device sda 6) __ext4_get_inod0 ...
I'm not sure if anyone could help me but I figured I would give it a shot. I might also mention that my HDD has been having tons of issues and has loads of bad sectors, I'm just saving up for a new one but for now I'm dealing with the one I have. My HDD also clicks when these messages start coming up.
Is there any way to fix this?I might also mention that my HDD has been having tons of issues and has loads of bad sectors, I'm just saving up for a new one but for now I'm dealing with the one I have. My HDD also clicks when these messages start coming up.
LOL. That's like getting to the altar and saying to your soon-to-be-spouse "I might also mention that I'm sterile."
The ata1.00... are hardware errors. Probably drive problems, based on your belated exposition. If you haven't already run a bad sector reallocation tool, do so. The only other thing I would suggest is try the drive on another controller make sure it is only drive problems. I've seen issues on laptops that seemed to be fixed by a new drive, but the problems returned shortly after replacement. -
/dev/sda for Arch but /dev/hda for custom kernel. Why?
My laptop does not have a scsi or sata hard drive. So why does Arch's kernel view the drive as /dev/sda1 while a custom kernel views it as /dev/hda like it should?
Hmm that does not at all seem like a good explanation.
Drivers/ide suffers from many ugly and obscure problems, and re-implementing it on top of libata has been much easier than fixing the unfixable drivers/ide mess
you don't think fixing broken and ugly code is a good thing? Let me guess, you think sdxX is somehow more ugly then hdxX?
btw, if you use persistent block device naming scheme, you wouldn't need worry about naming conventions. http://wiki.archlinux.org/index.php/Per … ice_naming -
Where are /dev/sda 15 partitions?
I've got a PATA drive, and I installed arch64 half a month ago.
The problem is very easy to understand: my new ArchLinux installation can't detect /dev/sdaX where X>15.
So I can't load /dev/hda16,17,18,19.
How can I fix this?
Thanks% ls /dev/sda1?
/dev/sda10 /dev/sda11 /dev/sda12 /dev/sda13 /dev/sda14 /dev/sda15
% dmesg | grep -i piix
% lsmod | grep -i piix
% grep ^MODULES /etc/mkinitcpio.conf
MODULES="piix pata_via ata_generic"
% mkinitcpio -M
Modules autodetected:
ata_generic
libata
pata_via
sata_via
ide-core
generic
via82cxxx
8139cp
8139too
mii
via-rhine
usbcore
ehci-hcd
uhci-hcd
ext2
jbd
ext3
reiserfs
xfs
% slocate -i piix
/lib/modules/2.6.21-ARCH/kernel/drivers/ata/pata_mpiix.ko
/lib/modules/2.6.21-ARCH/kernel/drivers/ata/pata_oldpiix.ko
/lib/modules/2.6.21-ARCH/kernel/drivers/ata/ata_piix.ko
/lib/modules/2.6.21-ARCH/kernel/drivers/i2c/busses/i2c-piix4.ko
/lib/modules/2.6.21-ARCH/kernel/drivers/ide/pci/piix.ko
/var/abs/local/kvm/src/kvm-17/qemu/hw/piix_pci.c
/var/abs/local/kvm/src/kvm-17/qemu/x86_64-softmmu/piix_pci.o
/usr/src/linux-2.6.21-ARCH/include/config/ata/piix.h
/usr/src/linux-2.6.21-ARCH/include/config/blk/dev/piix.h
/usr/src/linux-2.6.21-ARCH/include/config/i2c/piix4.h
/usr/src/linux-2.6.21-ARCH/include/config/pata/mpiix.h
/usr/src/linux-2.6.21-ARCH/include/config/pata/oldpiix.h
I've got a VIA controller.
Last edited by OCCASVS (2007-05-21 14:33:25) -
Hello arch users,
I'm currently trying to improve performance on my netbook that runs arch linux.
Today I installed a custom kernel (optimized for Atom processor) and rebuilt the initramfs and I'm pretty satisfied with my boot speed.
Still there is this 'dev-sda1.device' thing in my 'systemd-analyze blame':
4.699s dev-sda1.device
1.926s systemd-journald.service
1.765s systemd-vconsole-setup.service
963ms systemd-tmpfiles-setup-dev.service
962ms systemd-journal-flush.service
844ms lightdm.service
697ms systemd-udevd.service
457ms tmp.mount
440ms udisks2.service
416ms sys-kernel-debug.mount
372ms systemd-remount-fs.service
359ms [email protected]
323ms sys-kernel-config.mount
318ms systemd-sysctl.service
318ms dev-mqueue.mount
316ms dev-hugepages.mount
301ms systemd-udev-trigger.service
294ms polkit.service
234ms systemd-random-seed.service
145ms systemd-backlight@backlight:acpi_video0.service
144ms [email protected]
139ms home.mount
126ms systemd-tmpfiles-setup.service
122ms kmod-static-nodes.service
This seems to be very time consuming. What is 'dev-sda1.device'? I tried "find . -name 'dev-sda1.device'" with no results and I searched Google...
Is it just a "virtual" name for the process which mounts /dev/sda1? (which is my / partition by the way, where /dev/sda is a HDD)
And why does it take "this long"? I would like to improve everything I canFrom 'man systemd.device':
systemd will dynamically create device units for all kernel devices that are marked with the "systemd" udev tag
(by default all block and network devices, and a few others)
These units are not present on the file system.
4.699s dev-sda1.device
I think that this time includes the fsck running time, which depends on the partition size.
On my machine, where sda3 is my root partition, I get:
$ systemd-analyze blame|grep device
3.647s dev-sda3.device
$ systemctl status dev-sda3.device
● dev-sda3.device - Hitachi_HDP725050GLA360 3
Follow: unit currently follows state of sys-devices-pci0000:00-0000:00:0e.0-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda3.device
Loaded: loaded
Active: active (plugged) since mer. 2015-04-29 10:19:21 CEST; 6h ago
Device: /sys/devices/pci0000:00/0000:00:0e.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3
$ journalctl -b|grep sda3
avril 29 10:19:18 arch64 kernel: sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
avril 29 10:19:18 arch64 kernel: EXT4-fs (sda3): mounting ext3 file system using the ext4 subsystem
avril 29 10:19:18 arch64 kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
avril 29 10:19:19 arch64 systemd-fsck[130]: /dev/sda3: clean, 206507/1313280 files, 1624052/5242880 blocks
avril 29 10:19:19 arch64 kernel: EXT4-fs (sda3): re-mounted. Opts: (null)
Since the '10:19:18' boot time to the '10:19:21' 'dev-sda3.device' activation time there is the 3.647s lapse.
The journal shows that the 'systemd-fsck[130]: /dev/sda3' is included.
Maybe preventing the fsck on this partition might reduce the activation time of your 'dev-sda1.device'.
But is 4.7s so long?
Last edited by berbae (2015-04-29 15:01:36) -
Is it possible to mount a physical disk (/dev/mapper/ disk) on one of my Oracle VM server
I have a physical disk that I can see from multipath -ll that shows up as such
# multipath -ll
3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| `- 7:0:0:49 sdcs 70:0 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
`- 10:0:0:49 sdcr 69:240 active ready running
That particular is visible in the OVMM Gui as a physical disk that I can present to one of my VMs but currently its not presented to any of them.
I have about 50 physical LUNs that my Oracle VM server can see. I believe I can see all of them from a fdisk -l, but "dm-115" (which is from the multipath above) doesnt show up.
This disk has 3 usable partitions on it, plus a Swap.
I want to mount the 3rd partition temporarily on the OVM server itself and I receive
# mount /dev/mapper/3600c0ff00012f4878be35c5401000000p3 /mnt
mount: you must specify the filesystem type
If I present the disk to a VM and then try to mount the /dev/xvdx3 partition -it of course works. (x3 - represents the 3rd partition on what ever letter position the disk shows up as)
Is this possible?Its more of the correct syntax. Like I can not seem to figure out how to translate the /dev/mapper path above into what fdisk -l shows. Perhaps if I knew how fdisk and multipath can be cross referenced I could mount the partition.
I had already tried what you suggested. Here is the output if I present the disk to a VM and then mount the 3rd partition.
# fdisk -l
Disk /dev/xvdh: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/xvdh1 * 1 13 104391 83 Linux
/dev/xvdh2 14 2102 16779892+ 82 Linux swap / Solaris
/dev/xvdh3 2103 27783 206282632+ 83 Linux
/dev/xvdh4 27784 30394 20972857+ 5 Extended
/dev/xvdh5 27784 30394 20972826 83 Linux
# mount /dev/xvdh3 /mnt <-- no error
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda3 197G 112G 75G 60% /
/dev/xvda5 20G 1011M 18G 6% /var
/dev/xvda1 99M 32M 63M 34% /boot
tmpfs 2.0G 0 2.0G 0% /dev/shm
/dev/xvdh3 191G 58G 124G 32% /mnt <-- mounted just fine
Its ext3 partition
# df -T
/dev/xvdh3
ext3 199822096 60465024 129042944 32% /mnt
Now if I go to my vm.cfg file, I can see the disk that is presented.
My disk line contains
disk = [...'phy:/dev/mapper/3600c0ff00012f4878be35c5401000000,xvdh,w', ...]
Multipath shows that disk and says "dm-115" but that does not translate on fdisk
# multipath -ll
3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| `- 7:0:0:49 sdcs 70:0 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
`- 10:0:0:49 sdcr 69:240 active ready running
I have around 50 disks on this server, but the ones of the same size from fdisk -l from the server shows me many.
# fdisk -l
Disk /dev/sdp: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdp1 * 1 13 104391 83 Linux
/dev/sdp2 14 2102 16779892+ 82 Linux swap / Solaris
/dev/sdp3 2103 27783 206282632+ 83 Linux
/dev/sdp4 27784 30394 20972857+ 5 Extended
/dev/sdp5 27784 30394 20972826 83 Linux
Disk /dev/sdab: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdab1 * 1 13 104391 83 Linux
/dev/sdab2 14 1318 10482412+ 82 Linux swap / Solaris
/dev/sdab3 1319 27783 212580112+ 83 Linux
/dev/sdab4 27784 30394 20972857+ 5 Extended
/dev/sdab5 27784 30394 20972826 83 Linux
Disk /dev/sdac: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdac1 * 1 13 104391 83 Linux
/dev/sdac2 14 2102 16779892+ 82 Linux swap / Solaris
/dev/sdac3 2103 27783 206282632+ 83 Linux
/dev/sdac4 27784 30394 20972857+ 5 Extended
/dev/sdac5 27784 30394 20972826 83 Linux
Disk /dev/sdad: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdad1 * 1 13 104391 83 Linux
/dev/sdad2 14 1318 10482412+ 82 Linux swap / Solaris
/dev/sdad3 1319 27783 212580112+ 83 Linux
/dev/sdad4 27784 30394 20972857+ 5 Extended
/dev/sdad5 27784 30394 20972826 83 Linux
Disk /dev/sdae: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdae1 * 1 13 104391 83 Linux
/dev/sdae2 14 2102 16779892+ 82 Linux swap / Solaris
/dev/sdae3 2103 27783 206282632+ 83 Linux
/dev/sdae4 27784 30394 20972857+ 5 Extended
/dev/sdae5 27784 30394 20972826 83 Linux
Disk /dev/sdaf: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdaf1 * 1 13 104391 83 Linux
/dev/sdaf2 14 2102 16779892+ 82 Linux swap / Solaris
/dev/sdaf3 2103 27783 206282632+ 83 Linux
/dev/sdaf4 27784 30394 20972857+ 5 Extended
/dev/sdaf5 27784 30394 20972826 83 Linux
Disk /dev/sdag: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdag1 * 1 13 104391 83 Linux
/dev/sdag2 14 2102 16779892+ 82 Linux swap / Solaris
/dev/sdag3 2103 27783 206282632+ 83 Linux
/dev/sdag4 27784 30394 20972857+ 5 Extended
/dev/sdag5 27784 30394 20972826 83 Linux
Disk /dev/dm-13: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/dm-13p1 * 1 13 104391 83 Linux
/dev/dm-13p2 14 2102 16779892+ 82 Linux swap / Solaris
/dev/dm-13p3 2103 27783 206282632+ 83 Linux
/dev/dm-13p4 27784 30394 20972857+ 5 Extended
/dev/dm-13p5 27784 30394 20972826 83 Linux
Disk /dev/dm-25: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/dm-25p1 * 1 13 104391 83 Linux
/dev/dm-25p2 14 1318 10482412+ 82 Linux swap / Solaris
/dev/dm-25p3 1319 27783 212580112+ 83 Linux
/dev/dm-25p4 27784 30394 20972857+ 5 Extended
/dev/dm-25p5 27784 30394 20972826 83 Linux
Disk /dev/dm-26: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/dm-26p1 * 1 13 104391 83 Linux
/dev/dm-26p2 14 2102 16779892+ 82 Linux swap / Solaris
/dev/dm-26p3 2103 27783 206282632+ 83 Linux
/dev/dm-26p4 27784 30394 20972857+ 5 Extended
/dev/dm-26p5 27784 30394 20972826 83 Linux
Disk /dev/dm-27: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/dm-27p1 * 1 13 104391 83 Linux
/dev/dm-27p2 14 1318 10482412+ 82 Linux swap / Solaris
/dev/dm-27p3 1319 27783 212580112+ 83 Linux
/dev/dm-27p4 27784 30394 20972857+ 5 Extended
/dev/dm-27p5 27784 30394 20972826 83 Linux
Disk /dev/dm-28: 439.9 GB, 439956406272 bytes
255 heads, 63 sectors/track, 53488 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/dm-28p1 * 1 13 104391 83 Linux
/dev/dm-28p2 14 2102 16779892+ 82 Linux swap / Solaris
/dev/dm-28p3 2103 27783 206282632+ 83 Linux
/dev/dm-28p4 27784 30394 20972857+ 5 Extended
/dev/dm-28p5 27784 30394 20972826 83 Linux
Disk /dev/dm-29: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/dm-29p1 * 1 13 104391 83 Linux
/dev/dm-29p2 14 2102 16779892+ 82 Linux swap / Solaris
/dev/dm-29p3 2103 27783 206282632+ 83 Linux
/dev/dm-29p4 27784 30394 20972857+ 5 Extended
/dev/dm-29p5 27784 30394 20972826 83 Linux
Disk /dev/dm-30: 439.9 GB, 439999987712 bytes
255 heads, 63 sectors/track, 53493 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/dm-30p1 * 1 13 104391 83 Linux
/dev/dm-30p2 14 2102 16779892+ 82 Linux swap / Solaris
/dev/dm-30p3 2103 27783 206282632+ 83 Linux
/dev/dm-30p4 27784 30394 20972857+ 5 Extended
/dev/dm-30p5 27784 30394 20972826 83 Linux
How to translate the /dev/mapper address into the correct fdisk, I think I can then mount it.
If I try the same command as before with the -t option it gives me this error.
# mount -t ext3 /dev/mapper/3600c0ff00012f48791975b5401000000p3 /mnt
mount: special device /dev/mapper/3600c0ff00012f48791975b5401000000p3 does not exist
I know I am close here, and feel it should be possible, I am just missing something.
Thanks for any help -
UPDATE: /dev/sdc shows up, but no such device. How to remove/reset?
UPDATE:
Please read second post for current problem, although first still applies for the most part.
Original:
=========
Sorry, I couldn't figure out a good title hopefully this is fine.
My problem: I bought a laptop with 2 hard drive bays, I bought a regular HDD and a SDD. They both showed up fine and I initially "just installed" with the regular process via ArchBoot. Everything good still. I decided I wasn't happy with the setup and was actually thinking about getting 2 SSD's instead of the regular HDD so I took out the HDD so I could do an install with just the SDD (while I wait on another SDD to arrive). This went fine, too. I put /tmp and /var/log in tmpfs, etc. But then I realized I should put /var/cache somewhere else since I do a lot of updating and custom packages very frequently. This is where the problem starts:
1. I put in a 4GB SD Multi-Card into the little multi-card reader slot in the front. It showed up as mmblk(..) and I reformatted it as ext4. I rebooted (always like to see logs on initial boot up, etc) and the SD Multi-Card showed up as /dev/sdb instead of /dev/mmblk(..) (while the SSD was /dev/sda). I didn't think too much of it and pointed /boot and / at /dev/sda1 and /dev/sda2 while I pointed /var/cache to /dev/sdb1. Rebooted and everything seemed to work.
2. I second guess myself and wanted to put the regular HDD back in (since it's 500GB) and I have a lot of movies/music I want to watch that will currently fill up the 240GB SSD I had ordered for the second bay (there's a small 60GB SSD for / and /boot stuff that I won't be writing to much). So I put the HDD back in, remove the SD card (since it's no longer necessary) and go through the install process again. ... It cannot find the drive. It keeps complaining that /dev/sdb cannot be read. The logs show nothing except that it sees /dev/sdb but nothing else as with /dev/sda where it goes through identifying name, type, and attaching it.
END RESULT PROBLEM: I can put any drive (the SSD or the HDD) into any of the two hard-drive bays and only /dev/sda gets read. It shows /dev/sdb no matter what, but it cannot read medium. Everytime I boot it will show /dev/sda and /dev/sdb even if I only insert one drive into ANY bay. I try to gdisk or fdisk /dev/sdb and it says medium cannot be read. The only time I get /dev/sdb to read is when I insert that stupid SD Multi-Card. Okay, fine. So I insert both drives into both bays as well as the SD Multi-Card. It still only shows /dev/sda and /dev/sdb.. no /dev/sdc.
So, something keeps making my computer think /dev/sdb HAS to be the multi-card. I used gdisk to erase any GPT tables on every drive and clear the MBR but this still persists. I even inserted my original Windows HDD into the computer and tried reformatting every drive, hoping it would somehow fix it, to no avail--also tried to "dd" all the drives. "dd" cannot read /dev/sdb either. The drives themselves all appear to work fine, it's just that for some reason my computer WANTS /dev/sdb as the SD Multi-Card and nothing else can go there, or after it (e.g. /dev/sdc..). I see /sys/block/sdb/{files} but I KNOW there's no /dev/sdb if I only insert one drive. What the heck. :{ This folder and the /dev/sdb show up on every LiveCD I tried.
EXAMPLE ONE:
Bay 1: SSD
Bay 2: HDD
MCR: <nothing>
/dev/sda shows SSD
/dev/sdb cannot find/read medium
EXAMPLE TWO:
Bay 1: HDD
Bay 2: <nothing>
MCR: <nothing>
/dev/sda shows HDD
/dev/sdb still shows up, cannot find/read medium
EXAMPLE THREE:
Bay 1: <nothing>
Bay 2: SSD
MCR: <nothing>
/dev/sda shows SSD
/dev/sdb still shows up, cannot find/read medium
EXAMPLE FIVE:
Bay 1: HDD
Bay 2: <nothing>
MCR: SDMulti-Card
/dev/sda shows HDD
/dev/sdb shows SDMulti-Card
EXAMPLE SIX:
Bay 1: HDD
Bay 2: SSD
MCR: SDMulti-Card
/dev/sda shows HDD
/dev/sdb shows SDMulti-Card
SSD (/dev/sdc?) NOT shown
Did I damage the BIOs or something? Because it seems no matter what I do, it only wants /dev/sdb as the SD Multi-Card, and will not "find/read/identify" any other drive as /dev/sdb or even /dev/sd{c,d,e,...}, whereas /dev/sda can be either the SSD or the HDD just fine, but they cannot be /dev/sdb or anything else. In the BIOs boot order selection it wont show both SSD and HDD drives if theyre in there at the same time, even though it used to show both before this whole SD Multi-Card fiasco. I tried resetting BIOs but it didn't seem to do anything. I'm at a loss.
Last edited by milomouse (2010-12-24 22:47:25)Original: 12-22-10. Today: 12-24-10. UPDATE:
So, by swapping the drives repeatedly and rebooting with the ArchBoot disc, using a combination of the Windows HDD, the empty HDD and the empty SSD in different positions (all conceivable), I was able to get Linux to "softreset" the devices so that I can FINALLY have both the empty HDD and the empty SSD read/identified at the same time, but only with the HDD in /dev/sda and the SSD in /dev/sdb (while that stupid SD Multi-Card slot keeps showing up, but this time as /dev/sdc). I think Linux is now confused and thinks that the SSD is a flash/SD device or something and therefore can't put it in /dev/sda anymore (after the SD card messed everything up). I guess everything is fine unless I have to switch devices for some reason or possibly have 2 SSDs where one wont read because of this.. We'll see.
My question now: is there any way to REMOVE a device? More specifically, I see /sys/block/sdc/{files} but there is obviously no device and I can't forcefully delete them with "rm -fr" -- I don't know another way. Can I set a udev rule or something to ignore it or possibly/preferably remove it so I can plug in another device later to be read as /dev/sdc instead of skipping to /dev/sdd? This would be great.
Edit: I can do:
echo 1 > /sys/block/sdc/device/delete
and it will delete for that session. But as soon as I reboot it's back. Any ideas? Udev?
Last edited by milomouse (2010-12-24 23:30:11)
Maybe you are looking for
-
How do I transfer a sound file via TCP?
I have a .wav file that I'm trying transfer via TCP. Using LV 8.5, I modified the "Sound File to Output.vi" example to send the data across a TCP connection to a client vi. But, I've encountered numerous errors along the way with trying to convert
-
Consolidated backup report for Non-RMAN
We need to prepare a consolidated backup report. need to customize it and produce a master list for production backup failures/ non prod backup failures wondering what's the options & how to do that ....
-
How to integrate a Java Application in the portal
Hi: I have developed a pure and simple Java Application just like a test, only Java, no EJB, no JSP. JUST PURE JAVA. I need to put this application in my Oracle9iAS Portal and i've found something about developing EAR and WAR. But i can't find the wa
-
Is it possible to run LabView executables under wine? Has anyone ever attempted to do this? Thanks for any information. Regards, Ken
-
I need to create a screen that wherein the user would first select parameters eg. Product code, region code, sales_manager. The user would then press a button and this must kick off a report (based on the parameters selected) that can be downloaded i