Ubuntu :: Loop Device Error When Shutdown Since Upgrade To 9.10
Apr 6, 2010
When I shutdown, I have a black screen with a message of I/O error, loop device... And the computer doesn't complete to shut down. This problem appear since I upgrade to ubuntu 9.10.
I've recently started using Linux Mint (version 10) on a Dell Mini 1012 netbook. I'm using a loop device to mount a file on a NAS but whenever this loop device is mounted and has been accessed, my machine fails to shutdown.
Firstly I mount a share on the NAS using cifs (the NAS is aimed at Windows machines so doesn't support NFS). I have a sparse file on the share (which I created using Cygwin in Windows, using the dd command).
I used losetup to create a loop device and formatted it as reiserfs.This works and I can successfully use the mount point. I'm using it with Backintime.If I try to shutdown my machine without unmounting the loop device, shutdown hangs.
These messages just keep repeating and the system never shuts down.So I assume the problem is something to do with unmounting the CIFS/loop device.If I unmount the loop device all is fine. I don't need to unmount the cifs share.Any ideas on how to resolve? Should I add a script to run during shutdown (i.e linked from /etc/rc0.d and /etc/rc6.d) to sync and unmount the loop device? Or is there a better solution?
1. Physical HDD1, mounted in /media/MYDATA 2. Physical HDD2, mounted in /media/MYDATA/MYMOVIES
This works, and has all my information. Unfortunately I can not use CIFS to get my data, because of a bug with wireless connection and umounting at shutdown. Until yesterday, I have no problem at all, mounting my NFS unit automatically in /media/MYDATA perfectly. But, when I go to /media/MYDATA/MYMOVIES in my laptops, filesystem is empty. I've included /media/MYMOVIES in the exports file (server) and in the fstab (client) and...it worked!!
But...system does not shutdown at all. If I manually try to umount /media/MYDATA the message received is "resource busy". :/ so...I guess this is the problem. If I manually umount /media/MYDATA/MYMOVIES first, laptop shutdown perfectly.
yesterday i upgraded Ubuntu 10.04 to 10.10. During installation i also upgraded grub to version 2. It said that there were two options that i could choose to boot and i choose both. Installation finished with out a hitch. When i attempted restart my laptop i got this message:
error: no such device: 12631218-8ac6-4505-b4cb-a66a1de1814f grub rescue>
I tried the command help and received a message saying that the help command was not recognized. So i then gave Google a bit of a work out and have tried reinstalling grub and manually coping the grub files all to no avail. The problem i believe stems from how i have Ubuntu installed. I have Ubuntu installed like an application on windows 7 on a separate partition on my hard drive. Looking back on it i'm not to sure why i choose that route, but that is how it is installed.
# mount -o loop /root/image.iso /media/cdrom in SLES10 (and SLES9), "mount" displays the name of the iso file: # mount ... /root/image.iso on /media/cdrom type iso9660 (rw,loop=/dev/loop0)
However, in SLES11, "mount" now displays the loop device rather than the filename:
# mount ... /dev/loop0 on /media/cdrom type iso9660 (rw)
This is somewhat less than useful. Is there any way to display the filename rather than the loop device?
I just upgraded to 10.04 Netbook Remix.When I boot, it gets past the splash screen and to the desktop. Before it can load anything, it acts as if it is looping. The wallpaper loads, the screen blinks white and then it loads the wallpaper again... then a white screen, then the wallpaper.I've tried to bring up the terminal and can't do that. I've also rebooted in recovery mode which didn't help.I'm at a loss. I'm on a windoze machine now since I can't get on my netbook.
I just finished the upgrade of 10.10 to 11.04, restarted and now i can't login anymore, i'm stuck in an endless login loop.
1) Boot 2) Xorg starts 3) I see my user, login 4) Screen goes black like it's loading 5) Loop back to login
It's not a password issue, i can login in command line It's not a profile issue cause i tried creating a new user from the command line and it still loops. I looks briefly at the /var/log/... but i couldn't find anything relevant,respond ASAP this is my work PC.
I thought it would be simple since it's a very simple a relatively new machine (2months ago)
The umount command sync and release the USB device (pen drive or external HD) from the filesystem, but does not shutdown it, like Nautilus does with the safe remove. How can i properly shutdown it from the command line?
I need to flash my BIOS to get rid of an error: "Intel uCode loading error". On [URL] I have found a tutorial, that looks to be fine. I can even see in the comments, that somebody have done this with success from Ubuntu 9.04, the very same system, that I use. Nevertheless I cannot make this bootCD with my Ubuntu 9.04, as it doesn't know the loop option to mount the image.
In the tutorial it says: "Requirements for this step is that you have support for the vfat and loop file systems in the kernel. Or you can have those features compiled as modules. In the latter case you can load the modules before the next step, like this:
modprobe vfat modprobe loop"
loop doesn't seem to be present in my system, and the command modprobe loop returns an error that the module is not available. I tried to follow the tutorial anyway, but with no success. How can I get the module lopp? I also want to use it to make iso images bootsble from the harddisk.
I have a requirement to check the following conditions..If my folders are not A and B then list files in the directory else no listing the filesso my if loop is some thing like this.
Code: if [ $dirName = "C" && $dirName != "A" && != "B" ] then ls -la
I've got a 'nested' for loop which has a grep in it, if the grep fails there's no output - however the error code is still $0 and the second for loop is still entered, there's also a grep in the second for loop.I guess ultimately what i need to know is whether there's a way of making grep generate an error code. when no results are found?
Since May 12,2009. Our system lifekeeper has the error log "lifekeeper error: DEVICE FAILURE on SCSI device '/dev/add'", but it ran normally. Until last week, it failover to the standby server. The disk still running, the error still come out.
I'd like to mount an iso file ,however, it failed as following: ljk@ljk-laptop:~/Test$ modinfo loop ERROR: modinfo: could not find module loop what I can do?
I'm running Ubuntu 10.04, and ever since last upgrade a couple of days ago (I think), everytime I hit shutdown on the gnome-panel (admittedly, I haven't tried the command line shutdown) the computer restarts itself. This computer is dual-booted with Win 7, and the shutdown command there properly halts the system.
recently my HP Pavilion's Western Digital (WD2500JS) HDD has begun failing (bluescreens, slow, etc...). I was able to attach it to another computer using a IDE to USB adapter and save my personal files (pics, music, etc...), so the drive has not yet completely died. So I bought a SATA Seagate Barracuda 500GB HDD and wanted to use my restore discs that HP made me purchase off of them to reinstall my Windows Vista Home Premium Edition, which OF COURSE didn't work. So after researching a bit I found the best idea would be to make and Image copy of the original HDD and put it on the new one. So I tried using Clonezilla which ran in an endless loop giving error after error for hours while trying to image the disk. Fortunately my work has a ImageMASSter 4004i which is a piece of hardware that does a direct, drive to drive image from the Master drive to the destination drive.
But unfortunately this didn't work either. It was telling me that their was an error within the destination drive, something like "0x84 URMWT Sequencer failed to complete". Does the drive need to be completely empty?Should I reformat it before I try this (if so which FS?)? I plugged it into my laptop with USB to SATA adapter and was unable to mount it (this was after I had it in the Imaging Hardware Device, not sure if that could have screwed something up). The strange thing is that the last couple of days the new drive did work, I was using it for temporary storage of some files.
my laptop is shutting down after i type in the password to start the upgrade.
logs:
syslog
WARNING: Could not launch application 'gnome-user-share.desktop': Unable to start application: Failed to execute child process "/usr/lib/gnome-user-share/gnome-user-share" (No such file or directory)
auth.log
administrator : no tty present and no askpass program specified ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/shutdown -h now
I am getting an error when i generat a report with squid's report generator ( sarg )is there a tool or way that i can find where in the log file the error is, the log file is 61442 lines, and it's gonna take me forever to find the error,
I have written the following script in my linux server to add users for LDAP database.But i can't able to run this.
The script is as following
#!/bin/bash echo "Mention the username which you want to convert LDIF format" read username if ["$username" -e "/ldiffile/passwd"]; then echo "Username already exists" else cat /etc/passwd | grep -i "$username" >> /ldiffile/passwd fi The output which i got : . ldapadd.sh Mention the username which you want to convert LDIF format yal2361 -bash: [yal2361: command not found
I was upgrading from 10 to 11 and the laptop battery died during the installation (it was accidentally unplugged). Can I recover or do I need to do a complete install?
I keep getting the following msg as I try to upgrade from 10.04 -> 10.10 ... "Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. This can be caused by:
* Upgrading to a pre-release version of Ubuntu * Running the current pre-release version of Ubuntu * Unofficial software packages not provided by Ubuntu
If none of this applies, then please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bug report." I don't think any of the issues above apply - can anyone offer advice on how to get around or "force " the upgrade
I just compiled my first own kernel (I'm using Arch Linux), following the tutorial on the german site. Now I tried to boot it, I ended up failing with this message: Code: Waiting 10 seconds for device /dev/sda1 ... Root device '/dev/sda1' doesn't exist, Attempting to create it. ERROR: Unable to determine major/minor number of root device '/dev/sda1' Here is the important part of my menu.lst:
[Code]....
I simply copy&pasted the Arch-entry, i.e. I also had the disk by uuid there. The failure message was the same, just the root device name was the different name Also, at first I did not have the initrd line in my menu.lst (as written in my tutorial that I may not need it). In this case I had this error message:
I upgraded to 13.1 and found the restart, shutdown buttons do not work. I have to resort to the terminal commands init 6, or poweroff. I then tried to install flash plugin. I modified the slackbuild script as per normal. Then issued the following command which seemed to succeed. But when I try to play utube movie it says flash is not installed. Do I need to rebuild the system?
Code: root@redeemer:/tmp# installpkg flash-player-plugin-10.0_r45-x86_64-1_SBo.tgz Verifying package flash-player-plugin-10.0_r45-x86_64-1_SBo.tgz. Installing package flash-player-plugin-10.0_r45-x86_64-1_SBo.tgz: Package Description: # flash-player-plugin (flash plugin for web browsers) # Provides Adobe Flash plugin for browsers that recognize # /usr/lib(64)/mozilla/plugins as a valid plugin directory # Plugin is subject to Adobe terms of use: # [URL] # Plugin is subject to Adobe Flash EULA: # [URL] # Package flash-player-plugin-10.0_r45-x86_64-1_SBo.tgz installed.
I am using Ubuntu 10.04 on a dual-boot system with Windows 7. Yesterday I upgraded from 2.6.32-23 to 2.6.32-24. After that, pressing the shutdown button and selecting shutdown or restart (whether on the login page or after I've logged in) will only bring me back to the login page. I can shutdown or restart if I do sudo shutdown now, but I'd prefer to use the GUI. Also, there is no sound now (not a big deal, but still not good). And I can't access my storage partition (not the windows7 partition, but a third ntfs partition with data on it). I get the error message that I am unauthorized to mount. I have the only account on this computer, so I should be authorized. This one is a HUGE problem for me, because I need to be able to access my data for work. None of these were problems before the upgrade.
Oh yeah, and quickstart is not enabled. Also, if I go to Power Management, and try to alter what to do when Power Button is pressed, my only option is Ask Me. I know these have been problems/solutions to the shutdown/restart problem in the past.
as a normal user when I click logout from a KDE session nothing happens and I can't re-launch logout again, shutdown is doing the same.I have just upgraded to fc14 from fc13 yesterday tried to delete .kde folder and it has not been succesful tried to create another user and log to kde session and the new user also failed to logout or shutdown Root user is able to logout and shutdown I have no probs on GNOME for root or users.
I am getting the same errors everytime I boot the server up:
Error: no such device {SOME-UUID} Error: no suck disk
After that the system boots normally, but Im afraid ignoring this error can make my system crash in the future. I figured it was a grub error and I tried the update-grub2 command, it does detect all installed kernels no problem, but after I reboot I get the same error message.
So I've tried some hours ago to install the new kernel 2.6.38 and when I did the reboot, it prompted this error: "Error 11: Unrecognize device strong
Press any key to continue..." I know this is such a general question but how to install the new kernel with Fedora 14? I think I did compiled and configured it ok and did something that wasn't recognized by grub or perhaps when I ran the command to make the new initrd.