Solaris 10:unable to mount a solaris root file system

Hi All,
I am trying to install Solaris 10 X86 on a Proliant DL385 Server it has a Smart array 6i, I have download the driver from the HP web site, on booting up the installation CD 1, adding the device driver, it sees the device but now says it can���t mount the device. Any clues what I need to do?
Screen Output:
Unable to mount a Solaris root file system from the device
DISK: Target 0, Bios primary drive - device 0x80
on Smart Array 6i Controller on Board PCI bus 2, at Dev 4
Error message from mount::
/pci@0,0/pci1022,7450@7/pcie11,4091@4/cmdk@0,0:a: can't open - no vtoc
any assistence would be appreciated.

Hi,
I read the Message 591 (Agu 2003) and the problem is quite the same. A brief description: I have aLaptop ASUS with HDD1 60GB and a USB storage HDD (in next HDD2) 100GB. I installed Solaris 10 x86 on HDD2 (partition c2t0d0s0). At the end of installation I removed the DVD and using BIOS features I switched the boot to HDD2. All ok; I received the SUN Blue Screen and I choose the active Solaris option; but at the beginning of the boot I received the following error message
Screen Output:
Unable to mount a Solaris root file system from the device
DISK: Target 0: IC25N060 ATMR04-0 on Board ....
Error message from mount::
/pci@0,0/pci-ide2,5/ide@1/cmdk@0,0:a: can't open
any assistence would be appreciated.
Regards

Similar Messages

  • Unbootable Solaris 10 x86 installed on ZFS root file system

    Hi all,
    I have unbootable Solaris 10 x86 installed on ZFS root file system. on an IDE HDD
    The bios keep showing the msg
    DISK BOOT FAILURE , PLEASE INSERT SYSTEM BOOT DISK
    please note :
    1- the HDD is connected properly and recognized by the system
    2- GRUB don't show any messages
    is there any guide to recover the system , or detail procedure to boot system again
    Thanks,,,

    It's not clear if this is a recently installed system that is refusing to boot OR if the system was working fine and crashed.
    If it's the former, I would suggest you check the BIOS settings to make sure it's booting from the right hard disk. In any case, the Solaris 10 installation should have writting the GRUB stage1 and stage2 blocks to the beginning of the disk.
    If the system crashed and is refusing to boot, you can try to boot from a Solaris 10 installation DVD. Choose the single user shell option and see if it can find your system. You should be able to use format/devfsadm/etc to do the actual troubleshooting. If your disk is still responding, try a `zpool import` to see if there is any data that ZFS can recognize (it usually has many backup uberblocks and disk labels scattered around the disk).

  • Mounting the Root File System into RAM

    Hi,
    I had been wondering, recently, how can one copy the entire root hierarchy, or wanted parts of it, into RAM, mount it at startup, and use it as the root itself.  At shutdown, the modified files and directories would be synchronized back to the non-volatile storage. This synchronization could also be performed manually, before shutting down.
    I have now succeeded, at least it seems, in performing such a task. There are still some issues.
    For anyone interested, I will be describing how I have done it, and I will provide the files that I have worked with.
    A custom kernel hook is used to (overall):
    Mount the non-volatile root in a mountpoint in the initramfs. I used /root_source
    Mount the volatile ramdisk in a mountpoint in the initramfs. I used /root_ram
    Copy the non-volatile content into the ramdisk.
    Remount by binding each of these two mountpoints in the new root, so that we can have access to both volumes in the new ramdisk root itself once the root is changed, to synchronize back any modified RAM content to the non-volatile storage medium: /rootfs/rootfs_{source,ram}
    A mount handler is set (mount_handler) to a custom function, which mounts, by binding, the new ramdisk root into a root that will be switched to by the kernel.
    To integrate this hook into a initramfs, a preset is needed.
    I added this hook (named "ram") as the last one in mkinitcpio.conf. -- Adding it before some other hooks did not seem to work; and even now, it sometimes does not detect the physical disk.
    The kernel needs to be passed some custom arguments; at a minimum, these are required: ram=1
    When shutting down, the ramdisk contents is synchronized back with the source root, by the means of a bash script. This script can be run manually to save one's work before/without shutting down. For this (shutdown) event, I made a custom systemd service file.
    I chose to use unison to synchronize between the volatile and the non-volatile mediums. When synchronizing, nothing in the directory structure should be modified, because unison will not synchronize those changes in the end; it will complain, and exit with an error, although it will still synchronize the rest. Thus, I recommend that if you synch manually (by running /root/Documents/rootfs/unmount-root-fs.sh, for example), do not execute any other command before synchronization has completed, because ~/.bash_history, for example, would be updated, and unison would not update this file.
    Some prerequisites exist (by default):
        Packages: unison(, cp), find, cpio, rsync and, of course, any any other packages which you can mount your root file system (type) with. I have included these: mount.{,cifs,fuse,ntfs,ntfs-3g,lowntfs-3g,nfs,nfs4}, so you may need to install ntfs-3g the nfs-related packages (nfs-utils?), or remove the unwanted "mount.+" entires from /etc/initcpio/install/ram.
        Referencing paths:
            The variables:
                source=
                temporary=
            ...should have the same value in all of these files:
                "/etc/initcpio/hooks/ram"
                "/root/Documents/rootfs/unmount-root-fs.sh"
                "/root/.rsync/exclude.txt"    -- Should correspond.
            This is needed to sync the RAM disk back to the hard disk.
        I think that it is required to have the old root and the new root mountpoints directly residing at the root / of the initramfs, from what I have noticed. For example, "/new_root" and "/old_root".
    Here are all the accepted and used parameters:
        Parameter                       Allowed Values                                          Default Value        Considered Values                         Description
        root                                 Default (UUID=+,/dev/disk/by-*/*)            None                     Any string                                      The source root
        rootfstype                       Default of "-t <types>" of "mount"           "auto"                    Any string                                      The FS type of the source root.
        rootflags                         Default of "-o <options>" of "mount"        None                     Any string                                      Options when mounting the source root.
        ram                                 Any string                                                  None                     "1"                                                  If this hook sould be run.
        ramfstype                       Default of "-t <types>" of "mount"           "auto"                     Any string                                      The FS type of the RAM disk.
        ramflags                         Default of "-o <options>" of "mount"        "size=50%"           Any string                                       Options when mounting the RAM disk.
        ramcleanup                    Any string                                                   None                     "0"                                                  If any left-overs should be cleaned.
        ramcleanup_source       Any string                                                   None                     "1"                                                  If the source root should be unmounted.
        ram_transfer_tool          cp,find,cpio,rsync,unison                            unison                   cp,find,cpio,rsync                           What tool to use to transfer the root into RAM.
        ram_unison_fastcheck   true,false,default,yes,no,auto                    "default"                true,false,default,yes,no,auto        Argument to unison's "fastcheck" parameter. Relevant if ram_transfer_tool=unison.
        ramdisk_cache_use        0,1                                                              None                    0                                                      If unison should use any available cache. Relevant if ram_transfer_tool=unison.
        ramdisk_cache_update   0,1                                                              None                    0                                                     If unison should copy the cache to the RAM disk. Relevant if ram_transfer_tool=unison.
    This is the basic setup.
    Optionally:
        I disabled /tmp as a tmpfs mountpoint: "systemctl mask tmp.mount" which executes "ln -s '/dev/null' '/etc/systemd/system/tmp.mount' ". I have included "/etc/systemd/system/tmp.mount" amongst the files.
        I unmount /dev/shm at each startup, using ExecStart from "/etc/systemd/system/ram.service".
    Here are the updated (version 3) files, archived: Root_RAM_FS.tar (I did not find a way to attach files -- does Arch forums allow attachments?)
    I decided to separate the functionalities "mounting from various sources", and "mounting the root into RAM". Currently, I am working only on mounting the root into RAM. This is why the names of some files changed.
    Of course, use what you need from the provided files.
    Here are the values for the time spend copying during startup for each transfer tool. The size of the entire root FS was 1.2 GB:
        find+cpio:  2:10s (2:12s on slower hardware)
        unison:      3:10s - 4:00s
        cp:             4 minutes (31 minutes on slower hardware)
        rsync:        4:40s (55 minutes on slower hardware)
        Beware that the find/cpio option is currently broken; it is available to be selected, but it will not work when being used.
    These are the remaining issues:
        find+cpio option does not create any destination files.
        (On some older hardware) When booting up, the source disk is not always detected.
        When booting up, the custom initramfs is not detected, after it has been updated from the RAM disk. I think this represents an issue with synchronizing back to the source root.
    Inconveniences:
        Unison needs to perform an update detection at each startup.
        initramfs' ash does not parse wild characters to use "cp".
    That's about what I can think of for now.
    I will gladly try to answer any questions.
    I don't consider myself a UNIX expert, so I would like to know your suggestions for improvement, especially from who consider themselves so.
    Last edited by AGT (2014-05-20 23:21:45)

    How did you use/test unison? In my case, unison, of course, is used in the cpio image, where there are no cache files, because unison has not been run yet in the initcpio image, before it had a chance to be used during boot time, to generate them; and during start up is when it is used; when it creates the archives. ...a circular dependency. Yet, files changed by the user would still need to be traversed to detect changes. So, I think that even providing pre-made cache files would not guarantee that they would be valid at start up, for all configurations of installation. -- I think, though, that these cache files could be copied/saved from the initcpio image to the root (disk and RAM), after they have been created, and used next time by copying them in the initcpio image during each start up. I think $HOME would need to be set.
    Unison was not using any cache previously anyway. I was aware of that, but I wanted to prove it by deleting any cache files remaining.
    Unison, actually, was slower (4 minutes) the first time it ran in the VM, compared to the physical hardware (3:10s). I have not measured the time for its subsequent runs, but It seemed that it was faster after the first run. The VM was hosted on a newer machine than what I have used so far: the VM host has an i3-3227U at 1.9 GHz CPU with 2 cores/4 threads and 8 GB of RAM (4 GB ware dedicated to the VM); my hardware has a Pentium B940 at 2 GHz CPU with 2 cores/2 threads and 4 GB of RAM.
    I could see that, in the VM, rsync and cp were copying faster than on my hardware; they were scrolling quicker.
    Grub, initially complains that there is no image, and shows a "Press any key to continue" message; if you continue, the kernel panics.
    I'll try using "poll_device()". What arguments does it need? More than just the device; also the number of seconds to wait?
    Last edited by AGT (2014-05-20 16:49:35)

  • Sol10 u8 installed on a ZFS Root File System have different swap needs?

    Does Sol10 u8 installed on a ZFS Root File System have different swap needs/processes?
    Information:
    I've installed Solaris 10 (10/09 s10s_u8wos_08a SPARC, Assembled 16 September 2009) on a half dozen servers and every one of them no longer mount swap at boot.
    The install program commented out the old swap entry and created this one:
    # grep swap /etc/vfstab
    swap - /tmp tmpfs - yes -
    Everything works like a champ. I didn't discover the issue until I tried to install some patches and the install failed. It didn't fail because of lack of swap - it refused to run because it found "No swap devices configured".
    Here are the symptoms:
    # swap -s
    total: 183216k bytes allocated + 23832k reserved = 207048k used, 13600032k available
    # swap -l
    No swap devices configured
    # mount | grep swap
    /etc/svc/volatile on swap read/write/setuid/devices/xattr/dev=5ac0001 on Mon Apr 19 08:06:45 2010
    /tmp on swap read/write/setuid/devices/xattr/dev=5ac0002 on Mon Apr 19 08:07:40 2010
    /var/run on swap read/write/setuid/devices/xattr/dev=5ac0003 on Mon Apr 19 08:07:40 2010
    #

    Hi Nitabills,
    I assume that you create a zfs entry for swap with the commande zfs create -V $size
    did you launch the command :
    swap -a /dev/zvol/dsdk/$ZPOOL/swap
    Try this entry below in the vfstab :
    /dev/zvol/dsdk/$ZPOOL/swap - - swap - no -

  • Root file system 100%

    Hi,
    We are facing a proble in which our root file system is 100% because of a lot of directories being created in the /proc directory. These directories are created with numbers as their names.
    Please give some advice

    1- It should be nothing to do with proc file system.
    2- Somtimes backup command has an 'o' instead of a 0
    (zero) in /dev/rmt/"0" and a file "o" is created in
    /dev/rmt that fills entire space.
    3- If your slice is really large enough, use du -sh
    /* command in case solaris 9 (du -sk for 8) to see
    which directories are taking space.
    4- If you still find nothing and directory sizes
    don;t seem to pose any problem, umount all filesstems
    and then do a du -sh /*.
    Remember, if you have a directory (say /export/home)
    filled with stuff, and currently it is not mounted,
    It consumes space from / filesystem. When it is
    mounted later, the space shown by df -k would show
    consumed space for entire Inode table. But du -sk
    wont show those files. Indeed those are hidden untill
    you unmount the physical slice from /export/homeI had root file system 100% used
    I deleted all syslog and messages files, the best I could reclaim was 1%
    I did "du -d / |more" to discover sizes of file that may be filling up root file system.
    I discovered that in /dev/rmt the size was unusually very large about
    2.5GB
    There was a file with file name "1" in /dev/rmt which was taking all the space
    I did "rm -r 1" to removed the unwanted file and reclaimed 53% free space

  • Change ZFS root dataset name for root file system

    Hi all
    A quick one.
    I accepted the default ZFS root dataset name for the root file system during Solaris 10 installation.
    Can I change it to another name afterward without reinstalling the OS? For example,
    zfs rename rpool/ROOT/s10s_u6wos_07b rpool/ROOT/`hostname`
    zfs rename rpool/ROOT/s10s_u6wos_07b/var rpool/ROOT/`hostname`/var
    Thank you.

    Renaming the root pool is not recommended.

  • Programmatic interface to get zone's root file system

    Hi,
    I am a newcomer to solaris zones. Is there any programmatic (C API) way to know the path to root file system of a zone given its name, from the global zone?
    Thanks!

    A truss of zoneadm list -cv shows a bunch of zone related calls like:
    zone_lookup()
    zone_list()
    zone_getattr()
    Using the truss output as an example and including /usr/include/sys/zones.h and linking to libzonecfg
    (and maybe libzoneinfo) seems like a fairly straight-forward path to getting the info you are looking for.
    You could also parse /etc/zones/index
    which is (on my s10_63 machine) a colon seperated flat file containing [zone:install state:root path] that looks like:
    global:installed:/
    demo1:installed:/zones/demo1
    demo2:installed:/zones/demo2
    demo3:installed:/zones/demo3
    foo:installed:/zones/foo
    ldap1:installed:/zones/ldap1
    Neither of these methods are documented, so they are certainly subject to change or removal.
    Good luck!
    -William Hathaway

  • Problem in Reducing the root file system space

    Hi All ,
    The root file system is reached 86%. We have cleared 1 GB data in /var file system. But the root file system still showing 86%. Please note that the /var file is not seprate file system.
    I have furnished the df -h output for your reference. Please provide solution as soon as possible.
    /dev/dsk/c1t0d0s0 2.9G 2.4G 404M 86% /
    /devices 0K 0K 0K 0% /devices
    ctfs 0K 0K 0K 0% /system/contract
    proc 0K 0K 0K 0% /proc
    mnttab 0K 0K 0K 0% /etc/mnttab
    swap 30G 1.0M 30G 1% /etc/svc/volatile
    objfs 0K 0K 0K 0% /system/object
    /dev/dsk/c1t0d0s3 6.7G 3.7G 3.0G 56% /usr
    /platform/SUNW,Sun-Fire-T200/lib/libc_psr/libc_psr_hwcap1.so.1
    2.9G 2.4G 404M 86% /platform/sun4v/lib/libc_psr.so.1
    /platform/SUNW,Sun-Fire-T200/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
    2.9G 2.4G 404M 86% /platform/sun4v/lib/sparcv9/libc_psr.so.1
    fd 0K 0K 0K 0% /dev/fd
    swap 33G 3.5G 30G 11% /tmp
    swap 30G 48K 30G 1% /var/run
    /dev/dsk/c1t0d0s4 45G 30G 15G 67% /www
    /dev/dsk/c1t0d0s5 2.9G 1.1G 1.7G 39% /export/home
    Regards,
    R. Rajesh Kannan.

    I don't know if the root partition filling up was sudden, and thus due to the killing of an in-use file, or some other problem. However, I have noticed that VAST amounts of space is used up just through the normal patching process.
    After I installed Sol 10 11/06, my 12GB root partition was 48% full. Now, about 2 months later, after applying available patches, it is 53% full. That is about 600 MB being taken up by the superseded versions of the installed patches. This is ridiculous. I have patched using Sun Update Manager, which by default does not use the patchadd -d option that would not back up old patch versions, so the superseded patches are building up in /var, wasting massive amounts of space.
    Are Solaris users just supposed to put up with this, or is there some other way we should manage patches? It is time consuming and dangerous to manually clean up the old patch versions by using patchrm to delete all versions of a patch and then using patchadd to re-install only the latest revision.
    Thank you.

  • Convert ZFS root file system to UFS with data.

    Hi, I would need to covert my ZFS root file systems to UFS and boot from the other disk as a slice (/dev/dsk/c1t0d0s0)
    I am ok to split the hard disk from root pool mirror. any ideas on how this can be acheived?
    Please sugget. Thanks,

    from the same document that was quoted above in the Limitations section:
    Limitations
    Version 2.0 of the Oracle VM Server for SPARC P2V Tool has the following limitations:
    Only UFS file systems are supported.
    Only plain disks (/dev/dsk/c0t0d0s0), Solaris Volume Manager metadevices (/dev/md/dsk/dNNN), and VxVM encapsulated boot disks are supported on the source system.
    During the P2V process, each guest domain can have only a single virtual switch and virtual disk server. You can add more virtual switches and virtual disk servers to the domain after the P2V conversion.
    Support for VxVM volumes is limited to the following volumes on an encapsulated boot disk: rootvol, swapvol, usr, var, opt, and home. The original slices for these volumes must still be present on the boot disk. The P2V tool supports Veritas Volume Manager 5.x on the Solaris 10 OS. However, you can also use the P2V tool to convert Solaris 8 and Solaris 9 operating systems that use VxVM.
    You cannot convert Solaris 10 systems that are configured with zones.

  • SOLVED: kernel loads, but doesn't have a root file system

    Hi,
    The system is an Asus X202E. It does UEFI and has a GPT partition system. I've gotten through that part. And it is clear to me that the kernel loads.
    It's the next step that's giving me grief. I've tried this with two bootloaders: gummiboot and rEFInd.
    With gummiboot, the kernel panics because it can't mount the root file system. With rEFInd, it gets to the intial ramdisk and then drops me to a shell, apparently because the root file system is set to null, and it obviously can't mount that as "real root".
    Here is what I posted on the Arch mailing list, documenting that I have indeed specified the correct root (I'm copying this from the email, eliding the unfortunate line wraps):
    bridge-live# cat /boot/loader/entries/arch.conf
    Title Arch Linux
    linux /vmlinuz-linux
    initrc /initramfs-linux.img
    options root=PARTUUID=d5bb2ad1-9e7d-4c75-b9b6-04865dd77782
    bridge-live# ls -l /dev/disk/by-partuuid
    total 0
    lrwxrwxrwx 1 root root 10 Apr 15 19:26 0ab4d458-cd09-4bfb-a447-5f5fa66332e2 -> ../../sda6
    lrwxrwxrwx 1 root root 10 Apr 15 19:26 3e12caeb-1424-451c-898e-a4ff05eab48d -> ../../sda7
    lrwxrwxrwx 1 root root 10 Apr 15 19:26 432a977b-f26d-4e75-b9ee-bf610ee6f4a4 -> ../../sda3
    lrwxrwxrwx 1 root root 10 Apr 15 19:26 95a1d2c2-393a-4150-bbd2-d8e7179e7f8a -> ../../sda2
    lrwxrwxrwx 1 root root 10 Apr 15 19:26 a4b797d9-0868-4bd1-a92d-f244639039f5 -> ../../sda4
    lrwxrwxrwx 1 root root 10 Apr 15 19:26 d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 -> ../../sda8
    lrwxrwxrwx 1 root root 10 Apr 15 19:26 ed04135b-bd79-4c7c-b3b5-b0f9c2fe6826 -> ../../sda1
    lrwxrwxrwx 1 root root 10 Apr 15 19:26 f64f82a7-8f2b-4748-88b1-7b0c61e71c70 -> ../../sda5
    The root partition is supposed to be /dev/sda8, that is:
    lrwxrwxrwx 1 root root 10 Apr 15 19:26 d5bb2ad1-9e7d-4c75-b9b6-04865dd77782 -> ../../sda8
    So the correct PARTUUID followed by the one I have specified in
    arch.conf is:
    d5bb2ad1-9e7d-4c75-b9b6-04865dd77782
    d5bb2ad1-9e7d-4c75-b9b6-04865dd77782
    I'm guessing that this is really the same problem with both gummiboot and with rEFInd, but don't really know. It's clear to me that the initrd is not being correctly constructed. So I removed /etc/mkinitcpio.conf and did, as per the Arch wiki,
    pacman -Syyu mkinitcpio linux udev
    No joy.
    I don't even know which way to go at this point. If I even knew how to tell it where the real disk is in the initial ram disk shell, that would help. Better of course, would be actually solving the problem.
    Thanks!
    Last edited by n4rky (2013-04-17 21:41:36)

    I have made extremely limited progress on this issue.
    My previous attempt to specify the root partition in mkinitcpio.conf was insufficient. Furthermore, this is no place--despite the documentation--for the orthodoxy about using UUIDs rather than the straight /dev/sdx. In my case:
    root=/dev/sda8
    and run
    mkinitcpio -p linux
    It still drops me into the shell at boot. I can do
    mount /dev/sda8 /new_root/
    and exit the shell. It still won't believe it has the root device and drops me back in. I just exit.
    At this point, for a very brief moment, things look promising. It appears to be starting normally. Then, gdm.service, NetworkManager.service, and dbus.service all fail to start. There may be others but the screen goes by too quickly. At this point, it hangs trying to initialize the pacman keyring and all I can do is CTRL-ALT-DEL.
    It occurred to me that this might extend to the rEFInd configuration and so I modified it to also use /dev/sda8 rather than the UUID, but this made no difference. Trying to boot via gummiboot still yields the previously specified kernel panic.

  • Zerofree: Shrinking ARCH guest VMDK--'remount the root file-system'?

    Hi!
    [using ZEROFREE]
    Getting great results with and extra ARCH install running as a VMDK in Workstation.
    REALLY need tips on shrinking the VMDK. obviously have deleted unneeded files
    and now rather urgently need to learn what's eluding me so far.
    1) zerofree is install IN the virtual machine (VMDK)workstation  running on windows 8.
    2) Here's the instructions for zerofree:
           filesystem has to be unmounted or mounted  read-only  for  zerofree  to
           work.  It  will exit with an error message if the filesystem is mounted
           writable.
           To remount the  root  file-system  readonly,  you  can  first
           switch to single user runlevel (telinit 1) then use mount -o remount,ro
           filesystem.
    As it a VMDK and it's running would the only/best option be to: "remount the  root  file-system  readonly" ??
    OR, could i add the VMDK to another running arch system that I do have and NOT mount the VMachine thereby
    allowing zero free to run even better on that?
    Are both method JUST as efficive at shrinking? My guess would be the remount root file-system as read only
    would NOT be as efficient at shrinking.
    I could really use a brief walk-through on this as all attempts have failed so far.
    I boot the ARCH virtual machine and do what may I ask?
    Last edited by tweed (2012-06-05 07:43:41)

    How did you use/test unison? In my case, unison, of course, is used in the cpio image, where there are no cache files, because unison has not been run yet in the initcpio image, before it had a chance to be used during boot time, to generate them; and during start up is when it is used; when it creates the archives. ...a circular dependency. Yet, files changed by the user would still need to be traversed to detect changes. So, I think that even providing pre-made cache files would not guarantee that they would be valid at start up, for all configurations of installation. -- I think, though, that these cache files could be copied/saved from the initcpio image to the root (disk and RAM), after they have been created, and used next time by copying them in the initcpio image during each start up. I think $HOME would need to be set.
    Unison was not using any cache previously anyway. I was aware of that, but I wanted to prove it by deleting any cache files remaining.
    Unison, actually, was slower (4 minutes) the first time it ran in the VM, compared to the physical hardware (3:10s). I have not measured the time for its subsequent runs, but It seemed that it was faster after the first run. The VM was hosted on a newer machine than what I have used so far: the VM host has an i3-3227U at 1.9 GHz CPU with 2 cores/4 threads and 8 GB of RAM (4 GB ware dedicated to the VM); my hardware has a Pentium B940 at 2 GHz CPU with 2 cores/2 threads and 4 GB of RAM.
    I could see that, in the VM, rsync and cp were copying faster than on my hardware; they were scrolling quicker.
    Grub, initially complains that there is no image, and shows a "Press any key to continue" message; if you continue, the kernel panics.
    I'll try using "poll_device()". What arguments does it need? More than just the device; also the number of seconds to wait?
    Last edited by AGT (2014-05-20 16:49:35)

  • How to add more disk space into /   root file system

    Hi All,
    Linux  2.6.18-128
    can anyone please let us know how to add more disk space into "/" root file system.
    i have added new hard disk with space of 20GB, 
    [root@rac2 shm]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/hda1             965M  767M  149M  84% /
    /dev/hda7             1.9G  234M  1.6G  13% /var
    /dev/hda6             2.9G   69M  2.7G   3% /tmp
    /dev/hda3             7.6G  4.2G  3.0G  59% /usr
    /dev/hda2              18G   12G  4.8G  71% /u01
    LABLE=/               2.0G     0  2.0G   0% /dev/shm
    /dev/hdb2             8.9G  149M  8.3G   2% /vm
    [root@rac2 shm]#

    Dude! wrote:
    I would actually question whether or not more disks increase the risk of a disk failure. One disk can break as likely as one of two of more disks.
    Simple stats.  Buying 2 lottery tickets instead of one, gives you 2 chances to win the lottery prize. Not 1. Even though the odds of winning per ticket remains unchanged.
    2 disks buy you 2 tickets in The-Drive-Failure lottery.
    Back in the 90's, BT (British Telecom) had a 80+ node OPS cluster build with Pyramid MPP hardware. They had a dedicated store of scsi disks for replacing failed disks - as there were disk failure fairly often due to the number of disks. (a Pryamid MPP chassis looked like a Xmas tree with all the scsi drive LEDs, and BT had several)
    In my experience - one should rather expect a drive failure sooner, than later. And have some kind of contingency plan in place to recover from the failure.
    The use of symbolic links instead of striping the filesystem protects from the complete loss of the enchilada if a volume member fails, but it does not reduce the risk of loosing data.
    I would rather buy a single ticket for the drive failure lottery for a root drive, than 2 tickets in this case. And using symbolic links to "offload" non-critical files to the 2nd drive means that its lottery ticket prize is not a non-bootable server due to a toasted root drive.

  • A bad scare: root file system recovery [SOLVED]

    Hi, everybody,
    The trouble began with an odd message: KDE Daemon: new storage detected (hard disk): open in a new window, ignore. Unfortunately, the hard disk in question is statically mounted via /etc/fstab; should have been mounted all along.
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    /dev/cdrom /mnt/cdrom iso9660 ro,user,noauto,unhide,iocharset=utf8 0 0
    /dev/dvd /mnt/dvd udf ro,user,noauto,unhide,iocharset=utf8 0 0
    /dev/fd0 /mnt/fd0 vfat user,noauto 0 0
    /dev/sdb1 swap swap defaults 0 0
    /dev/sdb2 / ext3 defaults 0 1
    /dev/sdb3 /home ext3 defaults 0 1
    #/dev/sda1 /home/alexey/mnt/a ext3 defaults 0 1
    It's /dev/sda1, now commented. Real trouble began when I tried to reboot. The kernel told me there's no root file system on sdb2; it checked the disks unsuccessfully, with scary messages about bad device names and device blocks, advised me to use rootfstype=kernel option, etc. sda1 turned out "bad" too. In fallback mode the system booted, but with file systems mounted read only; not much use... Using some recovery disk I commented out the /dev/sda1 line in /etc/fstab on suspicion that sda is the real offender; tried to reboot, without much success, then rebooted again, and something clicked into place; the system is back to normal, but I fear to approach sda1 . What happened? Any suggestion/link is going to be appreciated. It was pure luck; next time it could be much worse.
    Edit:
    Looks like 'clicked into place' is just the fallback kernel; kernel-related issue? It ran smoothly after the initial upgrade for a couple of weeks.
    Edit:
    A relevant snippet from kernel.log:
    Apr 23 19:52:25 stovepipebox ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
    Apr 23 19:52:25 stovepipebox ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
    Apr 23 19:52:25 stovepipebox ata2.00: ATAPI: _NEC DVD_RW ND-4550A, 1.06, max UDMA/33
    Apr 23 19:52:25 stovepipebox ata2.00: configured for UDMA/33
    Apr 23 19:52:25 stovepipebox scsi 1:0:0:0: CD-ROM _NEC DVD_RW ND-4550A 1.06 PQ: 0 ANSI: 5
    Apr 23 19:52:25 stovepipebox sata_nv 0000:00:0e.0: version 3.5
    Apr 23 19:52:25 stovepipebox ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 23
    Apr 23 19:52:25 stovepipebox ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LSA0] -> GSI 23 (level, low) -> IRQ 16
    Apr 23 19:52:25 stovepipebox PCI: Setting latency timer of device 0000:00:0e.0 to 64
    Apr 23 19:52:25 stovepipebox scsi2 : sata_nv
    Apr 23 19:52:25 stovepipebox scsi3 : sata_nv
    Apr 23 19:52:25 stovepipebox ata3: SATA max UDMA/133 cmd 0xe800 ctl 0xe480 bmdma 0xe000 irq 16
    Apr 23 19:52:25 stovepipebox ata4: SATA max UDMA/133 cmd 0xe400 ctl 0xe080 bmdma 0xe008 irq 16
    Apr 23 19:52:25 stovepipebox ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Apr 23 19:52:25 stovepipebox ata3.00: ATA-6: ST3120827AS, 3.42, max UDMA/133
    Apr 23 19:52:25 stovepipebox ata3.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 0/32)
    Apr 23 19:52:25 stovepipebox ata3.00: model number mismatch 'ST3120827AS' != '3120827AS '
    Apr 23 19:52:25 stovepipebox ata3.00: revalidation failed (errno=-19)
    Apr 23 19:52:25 stovepipebox ata3: limiting SATA link speed to 1.5 Gbps
    Apr 23 19:52:25 stovepipebox ata3.00: limiting speed to UDMA/133:PIO3
    Apr 23 19:52:25 stovepipebox ata3: failed to recover some devices, retrying in 5 secs
    Apr 23 19:52:25 stovepipebox ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    Apr 23 19:52:25 stovepipebox ata3.00: configured for UDMA/133
    Apr 23 19:52:25 stovepipebox ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Apr 23 19:52:25 stovepipebox ata4.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
    Apr 23 19:52:25 stovepipebox ata4.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)
    Apr 23 19:52:25 stovepipebox ata4.00: configured for UDMA/133
    Apr 23 19:52:25 stovepipebox scsi 2:0:0:0: Direct-Access ATA ST3120827AS 3.42 PQ: 0 ANSI: 5
    Apr 23 19:52:25 stovepipebox scsi 3:0:0:0: Direct-Access ATA ST3320620AS 3.AA PQ: 0 ANSI: 5
    This "model number mismatch 'ST3120827AS' != '3120827AS " looks like a result of a corrupted config (at least, I suspect so ). Any questions/suggestions?
    Last edited by Llama (2008-05-02 20:20:04)

    I had this same damn thing happen. The problem is in the way the kernel gets its info from the bios. The bios has a nasty habit of switching the drives around even when sda is connected to sata1. This became a problem when libata came about and changed all drives to sdxX naming convention.
    To fix the no booting problem and the stupid rootfstype= error thing, u need to use Persistent block naming device scheme. Here on the wiki is a page dedicated to this... http://wiki.archlinux.org/index.php/Per … ice_naming
    Try it and see if it helps. I used the /dev/by-uuid.

  • Backup and restore Root File system

    Hi
    Can I take backup of Root File system using ufsdump and later restore it (Root file system) completely using ufsrestore?
    Please give me the steps or a link
    Thanks in advance
    Ashraf.

    In short yes. But the steps depends on where you are going to store the backup and if you are running Sparc or x86 and what you do with your disk in between.
    Boot in single user.
    example# ufsdump 0cfu /dev/rmt/0 /dev/rdsk/c0t3d0s0
    /dev/rmt/0 (tape) can be another partions file /backup/root_backup
    For restore it must be safeest to boot from CD.
    Mount your disk to restore to under /a
    cd /a
    ufsrestore rf /dev/rmt/0 (or your file /backup/root_backup)
    If the partition is reformatted you may have to install new bootblocks.
    Please read some from docs.sun.com
    This is just an advice, not detailed workorder.....
    /Gunnar

  • [SOLVED]Root file system changed

    I'm currently using ArchLinux
    I'm not sure what went wrong, but now when I login as root and "cd" I don't see the root file system. Instead i see
        [root@aspect ~]# ls -al
    total 36
    drwxr-x---  7 root root 4096 Apr 13 16:29 .
    drwxr-xr-x 17 root root 4096 Apr 13 08:18 ..
    -rw-------  1 root root 2849 Apr 13 16:27 .bash_history
    drwxr-xr-x  2 root root 4096 Apr 13 10:35 .config
    drwx------  3 root root 4096 Apr 13 10:34 .dbus
    -rw-------  1 root root   49 Apr 13 10:35 .directory
    drwxr-xr-x  3 root root 4096 Apr 13 10:34 .kde4
    drwxr-xr-x  3 root root 4096 Apr 13 10:35 .local
    drwx------  3 root root 4096 Apr 13 16:29 .nv
    If I cd to ".." I can see the root file system from there.
    Also When I drag files into terminal, it can't locate them. I Used a java folder I had in downlaods as an example. But it's like this everywhere.
    [aspect@aspect ~]$ file:///home/aspect/Downloads/jre bash: file:///home/aspect/Downloads/jre: No such file or directory
    Last edited by aspectratio (2015-04-13 22:05:33)

    ewaller wrote:
    aspectratio wrote:I've already done all of this. What makes you think I was running KDE as root?
    drwxr-xr-x 3 root root 4096 Apr 13 10:34 .kde4
    Sometime today a hidden directory containing kde files was created in the /root being owned by root.  That's how
    So the problem here is I came from debian. And aparently there when you cd as root, it will bring you to the atual file system.
    Fair enough.
    I was told to edit /etc/passwd and change the root dir to just / from /bin/bash
    Now I can no longer login as root. I will try to boot recue mode and chroot into the system to fix the file.
    That would be the way to fix it.  You may not need to actually chroot, just mount the root partition at /mnt and edit /mnt/etc/passwd.
    As to not running desktop environments as root -- it is a pet peeve of mine.  I am not saying this about you, you understand the issue;  but I have had arguments with people in the past about not running GUI DEs as root, and them insisting on it being their machines and they can do what they want.  They are absolutely correct.  But they can also fend for themselves.
    Edit:  If you do have another user in wheel, and if wheel can gain root privileges, just log in as that user and use sudo to fix it.
    Yeah it's a security risk.
    I've fixed the file. But I'm just not sure why I can't drag and drop paths anymore. It apears as though it's not a common thing anyways.

Maybe you are looking for

  • Problem with initialization Delta queue

    Hi Gurus, I have problem with initialization of delta queue when I try load transaction data from R3 (FM) to BI. Error message: Deviation of (64 seconds) between qRFC counter (000012365466830000080000) and actual time (08.03.2009 21:10:19). I have no

  • EKES-DABMG error  - Inbound delivery - good receipt

    I have a big problem about inbound delivery (ID)  ; There are two  ID for same purchase orders (PO1) item (POI1) and different delivery date .       deliv. date   amount ID1 ; 15.02.2007    10 pieces ID2 ; 20.02.2007    25 pieces When  Goods Receipt 

  • Planning Materials in different BOMs

    Hey Gurus, We have a situation in which a part number (6001116) is a subassembly of a higher level material (8000375).  This material (6001116) is also a material that we create a production schedule for independent of the 8000375.  We also have inde

  • Simultaneous background jobs using the same BAPI issue

    I scheduled 2 simultaneous background jobs on a custom program using the same BAPI (closing PM orders). Run 1 to CLSD orders created on year 2001 Run 2 to CLSD orders created on year 2000 What happened was while run 1 was still active, run 2 encounte

  • ClassCastException: weblogic.xml.jaxp.RegistrySAXParserFactory

    Hi all, I am struggling with including the jstl core taglib. Whenever I am including the directive in include.jsp, WL 9.2 throws the following exception during portlet access: Nested Exception is weblogic.servlet.jsp.CompilationException: Failed to c