Ubuntu :: Intermittent Boot Failure - Error "cannot Mount Sdb1"
Jan 4, 2011
I have 10.10 installed and working OK. The Home directory is located on a second 1TB disk (sdb1). Recently, I've started to experience random boot failures where the start-up routine gets as far as showing the '10.10' logo with the progress dots underneath, but then throws up an error message saying that it cannot mount sdb1. I then have an option to Quit or drop into the shell to do a manual restart.
If I then do a Ctrl/Alt/Del, the system reboots, but usually fails again. Powering off and on, sometimes more than once, is the only way to eventually get a clean boot. The drive causing the problem is fairly new and all the diagnostic checks seem to indicate that it's healthy, so I'm not sure what causes the problem.
I used the ntfs-config utility to mount my windows drives automatically at startup. While doing so, I had my USB-HDD still attached, and after making changes and rebooting, it did something unknown I didn't expect and I cannot mount my USB-HDD again, and it gives me the following error message:
Error mounting: mount exited with exit code 1: helper failed with: mount: only root can mount /dev/sdb1 on /media/MyUSBDrive
I did manage to open it somehow, but then all the data was erased apart from ~3 GiB [edit: it's got some kind of extra drive built-in which is mounted as a CD-ROM drive, and when I open that one first all the files are missing in the actual drive, otherwise I get the message above]. I don't know what information I should include here, but my fstab looks like this:
fuse: failed to access mountpoint /media/sdb1: No such file or directory
What should I do to recover my files and fix the mount error? [edit: at the very least, how do I backup my files onto my internal HDD so I can format it and recover it in this manner]
For backup purposes, I built a RAID6 array on USB. When during the night the backup filesystem is being mounted, every so many days, a random disk fails:
Code: sd 9:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 9:0:0:0: [sdb] Sense Key : Illegal Request [current] sd 9:0:0:0: [sdb] Add. Sense: Invalid field in cdb[code].....
In other words, my RAID set fails every so many mounts, but I know how to fix it.What I want to find out is:
- Why is a random drive failed every now and then?
- How can I prevent that drive from being failed?
BTW: I have a second RAID set that has been functioning for years without error, so the setup I use must be correct. The only difference between both RAID arrays is the different vendor of the disks.
I'm having intermittent network failure on my laptop but I can't figure out why. I have a cable modem and a 10Mb/s (bits) connection (at least that's what I'm paying for). The modem is connected to a wireless router, to which my laptop connects wirelessly. Quite often my speed drops considerably-- sometimes as low as a few hundred bytes per second. Other times it fails completely. This will happen with just about any server you can imagine, including the Debian FTP mirrors in the US.
- When I do file transfers over the local network from my laptop to my desktop, they go pretty fast, around 2 MB/s. I believe my wireless card (Intel 3495) maxes out at 3 MB/s (bytes), so that seems reasonable. - When I download a file from the outside network, it usually goes pretty fast too, around 1 MB/s, which is close to my limit.
So why is it that the connection between the laptop and the external network is so slow? I've tried power cycling, but it doesn't really help. I can't think of anything else to try.
I'm trying to solve an intermittant serial port problem on an embedded medical monitor. We have determined that the port is receiving characters from the external device but the serial thread is not transferring the chars from the buffer. this problem happens at start up about 1 in 50 boots. We're using kernal 2.6.29.6.
I have a system that has an intermittent issue with copying files. Below is the error that occurs. Error while copying "<filename>" There was an error coping the file into network:/// Operation not support by backend
The user has Ubuntu 8.04. They are using the Nautilus window to copy files (drag and drop) from a CD/DVD or USB device. The directory they are copying onto is a RAID0 device with approximately 2T of space, and more than enough space to take the files. The permissions for the drive and folders are set to the user.
This occurs randomly and is very frustrating. We cannot duplicate it and when it does occur, it will happen once, then work fine. I've been checking forums and help files all over, but find nothing similar. The only stuff I find is if it's a new install and the permissions haven't been set correctly. Even a confirmation that someone else has seen this before.
I just installed pysdm so I could configure what drives mount on boot, and now when I go to access my external harddrive, this is what I get:
Unable to mount Hard Drive
Error mounting: mount exited with exit code 1: helper failed with:
[mntent]: line 11 in /etc/fstab is bad [mntent]: line 12 in /etc/fstab is bad [mntent]: line 13 in /etc/fstab is bad [mntent]: line 14 in /etc/fstab is bad mount: can't find /dev/sdb1 in /etc/fstab or /etc/mtab
I'm trying to get some data off of an external harddrive. I get a few errors:Unable to mountError mounting: mount: /dev/sdb1: can't read superblock.I then tried to run a read disk benchmark on disk utility and that seemed okay.I then tried
Ubuntu 10.04 has just failed to load from my hard drive, so I've resorted to booting from CD just to get the machine going.I'm wondering if my main boot drive has gone caput??When trying to mount it using DISK UTILITY...get the message: Error mounting volume
Error mounting: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,missing codepage or helper program, or other error.In some cases useful info is found in syslog - try dmesg | tail or so
I installed from a live disc months ago. It worked fine for a while, don't remember what caused the change.
Now when I boot, I get this message:
Quote:
I have several hdds in this desktop box, one other has a OS on it, has the Hardy version. But i disconnected that (it all used to work with both drives connected and I was able to use that boot menu to change from one OS to the other). I can boot by getting to "boot menu" by pushing the "esc" key when the bios starts (just after the beep). It gives the option to start from, with a list of possible devices to choose from. I don't know where this menu is from, bios or other. I select hard drive, then select the correct hard drive and it starts right up. That is nonsense though. I really no longer need version 8.04 but keep it as a backup in case my preferred OS/hdd fails.
I have an external usb disk connected to a Debian desktop. A couple of days ago these messages started appearing in dmesg
Code: [154343.010908] EXT3-fs error (device sdb1): ext3_get_inode_loc: unable to read inode block - inode=14352940, block=57409572 [154343.014425] EXT3-fs error (device sdb1): ext3_find_entry: reading directory #13272620 offset 0 [154343.014913] EXT3-fs error (device sdb1): ext3_find_entry: reading directory #3440641 offset 0 [154343.022172] Buffer I/O error on device sdb1, logical block 53138974 [154343.022209] lost page write due to I/O error on sdb1 [154343.022218] Buffer I/O error on device sdb1, logical block 53138976 [154343.022252] lost page write due to I/O error on sdb1 [154343.022256] Buffer I/O error on device sdb1, logical block 53138977
When this appears the disk becomes unavailable and I have to remove and plug it in and mount again. After that it works couple of hour and then the problem appears again. Is this a hardware problem?
I had occasion to add a few lines to rc.sysinit. Turns out the lines syntax was wrong. Instead of the booting ignoring those lines and proceeding on, then giving me an error warning or perhaps dumping into the interactive mode it just hung up! After several tries at moving on I discovered ESC dropped me into some sort of unannounced shell I got the installation disk out and with the repair system option using VI I got the lines deleted and all went back to normal. Now my suggestion is that if something does not make sense in terms of syntax while booting then cover it by doing the above and ignoring it with a warning later.
have set up a server with OS on a 250GB disk (sdd) and 3x 1.5TB drives for a RAID5 storage setup (sda, sdb and sdc).Using webmin I can delete and create a primary partition in each one. But while I can also format sda and sdc, it refuses to do sdb for some reason:Executing command mkfs -t ext4 /dev/sdb1 ; partprobe ..mke2fs 1.41.11 (14-Mar-2010) /dev/sdb1 is apparently in use by the system; will not make a filesystem here!
But I'm not using it simon@ubuntu:~$ lsof | grep /dev/sdb simon@ubuntu:~$ lsof | grep /dev/sdb1
I just bought a brand new hardrive (40gb western digital) IDE, 10 pin.I have gone through the installation and partioned the hardrive, when it gets to 100% it asks me to reboot.So i take the disk out, and then it says DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER:So i press enter and i get the same message> How can i get Ubuntu to boot up?The computer is a 2003 Medion pc with 512mb of RAM And an AMD Athlon processor. The computer has a sticker on that says: Designed for windows xp.
Last night when I turned on my lap top (5 year old Acer TravelMate 4650), it was not able to boot up (10.04 LTS). No system files could be read and a lot of error messages was displayed. In fact, it has done a few checks for disk error lately during boot up, but no further warnings given. I gave up recovering, and simply re-installed Ubntu 10.04. I was wondering if this could be related to a virus attack?
Hard Drive: Western Digital Caviar Black 500Gb 6Gbs Sata Asus Sata DVD/CD Burner Core i3 3.3GHz Sandy Bridge chipset MSI P67A-GD55 Motherboard Zotac GTS 450
I have a problem where the live cd gives this error message:
I have installed a new Linux distro (just to test it) on my usb memory stick, and I'm trying to run it. I don't know if what I did is correct so far, anyways here's what I have:
Grub on sda (internal hard disk) sdb with no boot loader (memory stick)
In grub I've been doing: root (hd1,0) kernel /kernel-genkernel-x86_64-2.6.37-sabayon root=/dev/sdb1 vga=normal initrd /initramfs-genkernel-x86_64-2.6.37-sabayon boot
This seems to work (as opposed to when I forgot the root= parameter, which almost destroyed my linux on sda1 ), but during startup the system complains about no root bein found on /dev/sdb1. I also tried (hd1,0), but it didn't change much.
I'm sure I can boot an OS from usb on my computer, so doesn anyone know what I'm doing wrong?
I have a netbook with a 150GB hard drive in it. A while ago I dropped my netbook and it wouldn't boot. Had a "failed command: READ FPDMA QUEUED" error at startup. So naturally I went and reinstalled. Reinstalling worked fine and I had my computer back. What I didn't account for was the fact that anytime it lost power and didn't shut down properly, I'd get the same error. I can't seem to recover my data either. Can't get any live disks to mount the hard drive after this error but for some reason I can still reinstall Crunchbang (essentially debian). Now I know there are bad sectors or something because when I try to use the disk that came with the netbook with an image of Windows XP that writes to the entire hard drive it throws an error but linux will avoid this I suppose when installing.
Now all of this is to say, being a laptop, several times I have left it on overnight when I fall asleep working or have to run into to town and it'll die and then I lose all my data, rather irritating. What's causing this error? What can I do to prevent it besides getting a new hard drive? If I can't prevent it from happening in the future is there a way to recover the data off the hard drive? Here's the section of the boot log that contains the error: [url]
I'm using POP yahoo and it usually works, but often I will get a popup saying unable to connect to POP server... Error sending username: +OK maildrop ready, ... If I cancel & try again later it usually works. The error is getting more frequent.
The external hard drive which contains all my photos and where I backed-up all my important documents is no longer recognized. It is a three month old 500GB Iomage Prestige Desktop Hard Drive.When I plug it in, it is recognised as a USB device, because it shows up when I type lsusb, but dmesg gives this error message.
[19712.013250] usb 2-2: new high speed USB device using ehci_hcd and address 21 [19712.145347] usb 2-2: configuration #1 chosen from 1 choice [19712.147214] scsi25 : SCSI emulation for USB Mass Storage devices
[code]....
I popped the disk out of the casing put it on a SATA connect internally and then tried the file recovery programs testdisk/photorec and SpinRite, but both failed because they couldn't recognize the external hard disk.
I have Fedora 13 installed on a new PC and have two types of intermittent boot hangups. What logs exist within Fedora 13 that may help me identify the cause or causes of these hangups? Todate, a reboot gets over the problems but I wish to get this sorted whilst the PC is still under warranty.
I just upgraded from 9.10 to 10.04.Now, when I boot up, I encounter an error in the boot cycle "An error occurred while mounting /media/cdrom0" "Press S to skip mounting or M for manual recovery"Pressing S does work to get me through the cycle and does not affect CD-ROM use once the OS loads. How would I find out what is causing the error or is there a safe way to stop it from trying to mount a drive with no media in it?Quote:GNU nano 2.2.2 File: /etc/fstab
I did upgrade my Ubuntu on 10.10 and had always a Dual-Boot with Win7. After the install of Ubuntu, my grub wouldn't work anymore. I could only boot into Ubuntu, but GRUB didn't even appear. I already tried but this brought only the installs for Ubuntu and GRUB didn't start. Afterwards I tried to recover my MBR with the help of my Win7 DVD, but this didn't work out too. Now I can't boot neither Ubuntu nor Win7 and have to run from the Live-CD. I also tried to fix it with but setup(hd0) only returned, Error 17: Cannot mount etc. What can I do? I need my Windows for work and I don't want to reinstall neither Ubuntu nor Win7. Output of fdisk -l gives:
I was running 11.0 and it stalled in the middle of a number of updates. On reboot I now get (if I remember correctly) Error 15: File not found.I managed to get my hands on a 11.0 live cd and started trying to fix grub. However, when I try mounting the harddrive using "mount /dev/sda1" I got
Code: can`t find sda1 in /etc/fstab or /etc/mtab "mount /dev/sda1 /mnt" gives
