I have Squeeze (amd64).During sudo aptitude update && sudo aptitude -y full-upgrade && sudo aptitude autoclean the command stalled and did not react on ^C so I forced-quit the terminal window. When rebooting ... the system tells me it is read-only.To solve the problem I booted from Debian Live CD and did sudo mount -n -o -t ext3 remount,rw /dev/sda1 /.I also did sudo fsck /dev/sda1 and it was clean./etc/mtab gives /dev/sda1 / ext3 rw,errors=remount-ro 0 0
But still ... when I boot from disk ... it is read-only.
I down loaded Debian 5.0.4 and burned it to CD (several times I might add till it was right) and now the computer I'm putting it on wont acknowledge it as a boot disk and load. It does not have a problem with my windows cd, which has a crack and the start of all my problems, But not the Debian CD-1 disk. what now? The computer is an IBM thinkpad a22p. Everything works as far as I can tell. But I was going to reinstall Windows and failed in that because of a small crack on the edge of the disk that stopped the install and any hope of accessing the file on the laptop. Microsoft does not support windows xp any longer, you must buy windows 7, but the ibm will not run it due to processor speed and ram limitations. But it will run linux and I'm willing to try it just to get out of microsoft control.
Idon't know what else to do. This is the link to where I downloaded the software ( [URL] ). The others five that i downloaded were on the same page that I got this one. Are there bad files here? Is there a missing file in the disc?
I am trying to build a test VM with VirtualBox 3.2.8, hosted on Ubuntu 10.04 amd64. I am trying to install Debian Squeeze from the daily build (specifically, from the following URL):
[URL]
(I've also tried the netinst ISO in the same directory.) The sha1sums are correct for each image.
When I start the VM, it refuses to boot, giving me the message "FATAL: No bootable medium found! System halted."
I would like to note that I've used VirtualBox for several years now, and GNU/Linux since 1995. So I have some experience in the field. (Of course experience is not much guard against brown-bag mistakes.) I've tried this same VM with an Ubuntu ISO (simply switching the attached ISO in the config), and it boots and installs OK.
Is there a known problem with the daily builds vs. VirtualBox?
I'm getting BSOD when I'm booting my main system (debian 8 fully updated). I get a BSOD with a _ sign. URL...because I can't access to failed boots files. Besides having the files
Code: Select allfelipe@debian ~ % ls /var/log/journal 362d07f9e18b45f8aec4575c347f181d 92e8a448f7a348719da129184a7e6821
Code: Select allfelipe@debian ~ % journalctl --list-boots 0 0c51ae5b67f144059c5470dbe345d621 vie 2016-03-25 09:05:29 ART—vie 2016-03-25 09:11:58 ART
i already wasted 2 dvds triying to burn the windows vista iso.First time i burned in BRASERO, and nothing, i finished burning the disc and i cant boot from there.Now i burned with K3B and same, i burned the image [the iso image works] and i wait, and nothing.The problem is, i cant read the DVD , in cairo dock when i try to execute it says"failed to mount cddvd drive" same happens to both burned dvds.
In Ubuntu 910 on my Asus EEE-PC1005HA, I notice that during boot, when the screen is dark between the plain Ubuntu logo and the animated purple screen, there is a brief message:udev[488] cannot read file (rest of message goes by too fast for me)This doesn't seem to hurt anything. My system has been working just fine for a long time. I don't know how long the message has been there. Perhaps it merely lengthens boot time? Should I care? If I should care, where might the message be logged (so that I don't have to photograph the screen)?
I have a linux server running ubuntu 10.04, kernel Linux server 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux. A few months ago I installed ubuntu to a USB flash drive (Patriot 16GB) and was able to successfully boot off it, and everything was running fine. Then all of a sudden I noticed that the root filesystem was read-only, and I saw errors in the kernel log:
I tried reading the drive to see if there was a problem with the drive itself:
root@server:~# dd if=/dev/sdc of=/dev/null dd: reading `/dev/sdc': Input/output error 1966184+0 records in 1966184+0 records out 1006686208 bytes (1.0 GB) copied, 2.12427 s, 474 MB/s
But the strange thing is that if I put that usb stick in a different linux server, I'm able to read the whole drive. If I run fsck, it fixes a bunch of errors, but when I put the drive back in the original PC it will work for a while and then fail with the same type of I/O error (not at the same offset though). I had this same problem occur on a different USB stick in the same server, I had thought it was bad media so I replaced it, but now the same problem is happening on a different usb drive. I have backups of the data, but I would really like to figure out what is causing this before I throw in the towel and buy a new PC.
So I upgraded my hard drive and went with a clean Lucid install. But now I want to get files off my old drive. When I re-hooked it back up (now 2 drives in the system), ubuntu refuses to boot. It kind of boots then just hangs. Never gets to the desktop, and the HD lite on my case is constantly flickering (what could it be doing??)
I have it set up correctly in my BIOS so that the new drive is the boot drive, not the old one. The only difference is that the new drive is sata and the old drive is old school pata (ide). I even tried pulling out the old pata drive and hooking it up to a USB adapter I have. Looking at it in the Disk Manager, it shows it as unformatted, and old faithful GParted doesn't even see it!
Now get this: I pulled out my new sata and put back in the old ide drive and guess what, now it wont boot! Grub (probably MBR) is screwed up also! Any ideas how I can read the data from that old drive? Ether by getting my new lucid install to boot with the old drive as a slave in the system, or by hooking it up externally using USB?
I've been reading various tutorials of the boot process but still am not clear. I don't care about grub stage 1 and 1.5 at the starting point of when the root filesystem is loaded into VFS(Virtualfilesystem), who is loading it, and from that point on. 1) Does grub load the root filesystem(read only) into VFS?2) Does the kernel load the root filesystem(read only) into VFS?3) Does INIT load the root filesystem(read only) into VFS?after this is concluded....Does INIT or the Kernel create the real root filesystem(rw)...right before the pivot.root
I downloaded the 7 Cds .iso and I proceed to make a copy in a cds. I change the boot in my PC and restart the PC to read the cds. But the program instalation not running. What I need to do?
I tend to get constant crashes when using internet browsers ( Google Chrome and Firefox ) basically the application hangs not moving in any way, then eventually completely freezes up, the system then locks up and finally crashes.
Upon system re-start I get "Read Error" at boot ( No further information, it literally just says "Read Error" ).
It is sometimes fixed by going into the BIOS and select "Hold on No Error".
I tried installing OpenBios to see if using different BIOS firmware would resolve the issue, but the OpenBios install failed ....so no dice there either.
I am trying to work out if it is a hard drive problem or if it is purely a problem with Fedora.
It was working fine for a couple of months and when it does boot up ... the system works fine, ( Until another crash ).
It seems like the internet browsers crash the system and then the system crashes and can then no longer remember how to boot up.
what this could be that could be software based....if not it looks like I will need a new hard-drive.
I have a bad entry in /etc/fstab I have tried to tried to change in boot but it says read only. It will not take su. I have a livecd but I can't seem to get to my filesystem from a terminal where I can specify su
I have a sandisk cruzer 4gb and everytime i try to boot with it in the usb slot it doesn't get read. after bootup i have to pull it out and put it back in and then it recognizes and reads it. have usb device selected as first boot order and have even hit esc during bootup and selected usb as boot device. trying to install the unbuntu 10.10 on the netbook.
I tried to compile a 2.6.33 kernel following Alien's guide.
I pretty much used the default values for every (NEW) option avaiable. I used "make localmodconfig" on my current config (zcat /proc/config.gz) and then tried to use "make menuconfig" to check if I could change anything. I didn't understand most of the options, so I skipped it. Then I used "make bzImage modules" and "make modules_install", copied the files mentioned on the wiki and run lilo.
But when I try to boot using my custom kernel, it gives an error like "Cannot remount read-only filesystem as read-write! This can cause serious problems."
If I try to continue the boot, it hangs when trying to launch the syslog script...
The new kernel entry on lilo.conf is:
Code: image = /boot/vmlinuz-custom-2.6.33 root = /dev/sda4 label = newkernel read-only just like the default kernel entry.
By the way, one thing I changed is the kernel compression format, which I set LZMA. But it didn't seem to be the problem, since it at least started...
My F12 installation, which was installed on an HP tx2500z laptop and has been operating relatively well since January, now fails to boot after a frozen screen precipitated a forced shutdown. On reboot, I was dropped into a shell with the error message "Error reading block 1546 (Attempt to read block from file system resulted in a short read) while getting next inode from scan." recommending to run fsck manually. During the fsck run, after a substantial number of Pass 1 inode count corrections, the "Error reading block" message reappeared, with the question "Ignore error<y>" to which I answered "y".
fsck responded with "Force rewrite<y>". Since I did not know what would be written here, I said "no". I then forced shutdown, rebooted into Windows, and searched for further guidance. One suggestion was to run fsck -y on the affected partition. My laptop drive has four partitions, the first two being allocated to Windows and an HP supplied repair partition. sda3 is a tiny boot partition (100 MB), and sda4/5 is the LVM remainder.
fsck -y /dev/sda3 told me the boot partition was fine. fsck -y /dev/sda4 stopped immediately and asked "Could this be a zero-length file partition?". Given the ext3 structure, I suppose the correct answer is yes. fsck -y /dev/sda5 told me fsck.LVM2_Member: not found.
Following this, I then attempted again to reboot, and ran fsck without options. Once again, during Pass 1, Block 1546 exhibited the short read error, again asking about a rewrite - which I once again answered no. Pass 1 completed with another substantial number of inode count corrections, and Pass 2 started - immediately generating the message:
'passwd' in /etc/pam.d (65556) has deleted/unused node 7831. Clear<y>
After some hesitancy, I said "yes", and of course a second similar message appeared. I was brave enough to answer "yes" six more times, with the first two referring to /etc/pam.d inodes, and the next four referring to /etc/security/console.apps inodes. The eighth message, also similar, referred to inodes elsewhere - but by now I did not dare to continue and forced shutdown. Is this repairable, and if so, how?
I have multi-version Kernels on a Dual Boot WinXP / openSUSE 11,3 box. It's been a LONG time since I needed to boot to Win XP and now that I find that I can't get to it, I can not say for sure what I did to break it. Looking back, I suspect that the method I used for the recent removal of one of the Kernel versions may have been innappropiate. Rather than unchecking in versions/package groups I may have just removed the unwanted kernel in the package list. Not sure. I've tried dinking around with menu.lst and Yast Boot Loader to no success. I get errors depending on what I messed with. Didn't try to reinstall grub until I checked here for help with a fix.
Somehow, the wife got her laptop into this situation yesterday. The Windows partition booted normally when selected from GRUB but os 11.3 would boot to a command line login and pretty much everything besides CTRL-D was useless as the root partition was ro.
I booted a live CD and found two a couple of strange things. First, the system clock was reset to the default date/time (2007-xx-xx). I reset that. Second, after correcting the time I ran fsck on the root and home partitions. Both went through with no errors reported but the 20GB root partition took a long,long time to complete while the 80GB home partition went pretty quickly. After doing the above, the system booted normally but both partitions reported running the transaction log as well as forcing fsck where I had just done that. My question is for future reference: how does the system react to a grossly incorrect date/time, especially where all the drive data reports being much later than the reported system time? Would this be the reason for what I saw? I have no idea how the wife managed to reset the system clock, even if the
I am editing this post to save people time and effort. This is one of those "Pilot Error" issues or faulty readout issue, not sure which. It turns out that when I saved a document in PDF format to my NTFS Drive (the one I want to share between Windows XP and Ubuntu 10) the .PDF file extension was missing.
1. Ubuntu identified the files as a PDF document (even though the file extension was not there)
2. When trying to access it by double clicking it, the message was "Unable to open document, Permission Denied"
The problem was not permissions, and it was not a PDF file according to the default Document Viewer, but it WAS a PDF file according to the directory listing. The permissions message really had nothing to do with the problem, and identifying the file as a PDF document when it didn't have an extension, was another problem. What SHOULD have happened is a file without an extension should not be identified as a PDF file or If Ubuntu says it's a PDF file, and I double click it, why is the message "Permission Denied" ?? How about "No File Extension" or something like that?
Read the following if you want to see what my problem WAS before I just appended ,PDF to the filename, and now it works fine. On the positive side, installing XP first, then setting aside a large chunk of space for a shared NTFS drive, and THEN installing Ubuntu in the free space works fine. I installed a new 320 GB drive on laptop. Installed Win XP in 32 GB Set aside 250 GB for another Windows partition using MANAGE and formatted D: as an NTFS drive Then successfully Installed ubuntu 10 into remaining unused space. Problem: Ubuntu cannot access files from D: (NTFS Windows) partition. but it can WRITE files without problems, and create directories, just not read them. Have set properties of the Windows drive to shared, still nada. Any trick I'm missing? If I plug in an external USB drive, Ubuntu can read/write to it easily, it just can't read from the 250 GB partition formatted in Windows XP that I wanted to share between operating systems.
I restore tape backup on my Linux server. At the time of booting the server it cannot able to read the filesystems.
I am getting the following message, Code: Your system appears to have shutdown uncleanly Forcing file system integrity check due to default setting Checking root filesystem fsch.ext3: file system has unsupported features (S) (/) e2fsck: Get a never version of e2fsck! (FAILED) *** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. Give root password for maintenance (or type Control-D to continue):
My brand new DVD+RW disc can't be read by debian (6.0) after trying to erase and burn a new iso into it. I used brasero for this but it failed to burn it and left it in this bad state. It could be detected before the failed brasero session though.
However, whenever I introduce the dvd into the drive after the brasero session, the dvd drive makes the same noises all the time as if it can't read something on it and is going back to the beginning and doing this all the time over and over again. The data on the dvd is not important but what I want to know is if it is possible to stop the OS from trying to read what's in it so I can use some erasing software to make the dvd useful again.
I am using Gentoo Linux and for a while now, the root file system is mounted read-only on booting. For obvious reasons, this is quite annoying as most services do not start up correctly (I do not use a separate file system for /var). After the system is up, I have to log in, remount the root file system read-write, fix /etc/mtab, mount all other file systems in from /etc/fstab and then start up all the missing daemons. I know that there are ways to make a system run properly with a read-only file system, but I would rather restore the old behaviour of a writable root file system.
The strange thing is that after running mount / -o remount,rw, the file system is mounted in writable mode without any errors. I suspected some problem with fsck, but now I have disabled automatic file system checks on the partition (tune2fs -c0 -i0).When I run dmesg, only these lines mention the partition at all, although I am not sure if not something gets lost because /var/log is not writable:
EXT3-fs (sda5): mounted filesystem with writeback data mode</code> EXT3-fs (sda5): using internal journal The line in /etc/fstab looks like this:
WinXP Partition loading as a read only and can't fix it with PYSDM (storage device manager) Let me provide some history as to how everything was installed: From my old WIN XP hard drive I used clonezilla to clone the drive to a partition on my new hard drive for Linux. Windows is on SDA4 which is the last partition of the drive, it is mounted at sda4/windows using ntfs. I then loaded Mint 8 gnome on the 2nd partition sda2 using ext3 mounted at /, sda1 is my Linux swap, and sda3 is mounted at /home using ext3. While installing I selected to mount Linux ext3 at /
When I choose to load winXP from the grub boot loader I get dev/sda4 no such device 10CDR36778638F73. Also when I try to unmount from disk utility I get the following error: Error unmounting: umount exited with exit code 1: helper failed with: umount: only root can unmount UUID=10CDF36778638F73 from /windows Seemslike I need to rename the drive but it won't let me in disk utility.
My Problem is that within PYSDM (storage device manager) I uncheck Mount file system (sda4/windows) as a read only but it will not stay unchecked. I have unchecked it hit unmount and mount and it still is checked to mount as a read only. This is the code in options for sda4 in PYSDM (storage device manager) nls=utf8,umask=007,gid=46
I have an interesting issue Ubuntu Server 8.04, The server has been running for quite a while (not designed or put together by me) but recently it has started segfualting and now will not boot apart from in read-only mode. I see the following errors in dmesg.
All of my USB -- media, flash drives, media players, SD cards -- mount as read-only on my system. Following is a bunch of output from questions I expect to be asked / debug info.
Groups I'm in gmweezel@computer:~$ groups gmweezel dialout cdrom floppy audio video plugdev netdev powerdev DMESG output gmweezel@computer:~$ dmesg | tail [17532.047289] sd 13:0:0:0: [sdg] Write Protect is off [17532.047292] sd 13:0:0:0: [sdg] Mode Sense: 45 00 00 00
tonight my laptop with debian installed is no longer reading my wireless card. It has been working for quite some time and I really have no clue as to why it stopped. I did install some updates today, but they seemed pretty minimal. I got the card to work following the same thing I did to get it to work in ubuntu which can be found URL...So what can I do to figure out why it stopped recognizing it or to fix it?
