I'm very new to linux and running debian 4.0. On boot got an error:
I did a ghost image of drive before I do any more damage and when performing the ghost, ghost stated I need to run fsck. I created the image and noticed that a lot of folders were missing (bin, boot and others).
1. How do I run check disk from an boot disk?
2. Is there something else I should consider?
I installed Debian on my PC with a Acer Stock motherboard (xc600) with amd64 and after the installation finished it told me to remove my installation media and reboot. After reboot I was returned this message ' ERROR: No boot disk has been detected or the disk has failed.'. I have verified with gparted using mint live OS that I have Debian installed on my system.
I got believes that this may have be caused by a broken grub or I need to configure something I don't know how in BIOS.
I will update the topic later..
My installation media was a USB 2.0 flashdrive with a Debian 8.2 Jessie Installer and 9 different Linux distros. I have installed Debian multiple times before on my laptop and never had this problem so I know how to go through the installation process and set the partitions.
I have updated from Karmic to Lucid not long ago, and everything went smooth and my system is been working like a charm for about a month. And it still does, with the only issue being that every time I restart my system, one of my partitions is checked.
My disk is split into 4 partitions: sda1, NTFS for windows sda2, ext4 for "/" sda3, ext2 for /home sda4, swap
Now what seems to happen is that sda3 is being marked as "not clean" on every shutdown, which makes me assume that is not being umounted at all.
I've been reading logs, commenting network drives out on fstab.. nothing does the trick.
I've booted into single mode and run e2fsck (which doesn't find anything wrong, and marks the FS as "clean") and then rebooted. The result is: if the FS wasn't mounted when I restart, then I get a clean boot once, but it is checked on the following one; if it was mounted then it is again checked at start-up.
Again, all points to the problem being that the FS is not cleanly umounted on shut-down.
I could not find any log with info of the processes killed and FS umounted at shut-down, so if anybody knows where to look, it could be a good start.
Every time I boot up I have to go through a disk check and then restart, how do I stop it from happening? When the disk checks happening I press escape and it usually says its deleted inode something because it has zero Dtime or some thing similar and also a paragraph of repeated lines saying something like all system files need alsa base.cnfg it will be ignored in a future release then the disk check completes and it restarts and is fine then, also sometimes it says dev/sda5 (my ubuntu partition) was not cleanly unmounted check forces. Is their a way to stop this happening as it ends up taking ages just to login.
I applying changes through update manager in ubuntu 10.04 then my computer froze. So I had to restart it manually. Now I can't boot ubuntu normal or recovery mode.I get an error message saying 'the disk drive / is not ready yet or blah blah'.I don't have a livecd to fix it this with... but here is my 'cat /etc/fstab' relevant output
I have a custom modified Ubuntu LiveCD. Sometimes when I boot from the CD, after it detects the HDDs it starts automatically scanning and repairing them even if the partitions are windows partitions. What do I need to modify to make it not scan/repair any partitions/drives at boot?
as far as i know Debian "Squeeze" has a disk check utility, but you can't run this on a mounted filesystem. Is there a way to trigger this during boot (before filesystem is mounted) ? I can run this once a month to keep filesystem healthy....
Is there any way to allow normal fsck boot-time checks when running on battery power? After looking around, the only solution I've seen is to manually alter the /etc/init.d/checkfs.sh and /etc/init.d/checkroot.sh files and remove the AC power check. There must be a better way than that surely?
I was using Terminal and browsing a directory in my home folder. My "home" directory is located on "/dev/sdb1". When in Terminal I typed "ls" in one of my directories and the output was garbage. The output didn't show the files in the directory. I think it said something like, "input/output error". Unfortunately, I didn't write the exact error down. Instead I rebooted.The hard disk with the problem is:
Code: $ sudo hdparm -I /dev/sdb [sudo] password for brian:
my Fedora 11 system is not starting anylonger. It stops with the message:
VFS: Can't find ext4 filesystem on dev dm-0
The system told me since a while, that a lot of the sectors of one disk of the (software) RAID compound are failed already. So tried to disconnect each of the disks and start them separately. Unfortunaltly this is not working (for one its is not working at all, the other wents the same far as with both), when I tried to recover the system with the Fedora DVD, it said no distribution found. I am quite new and do not know so much about linux system, so i do not know what further information you could need. Maybe it can be important, that both disks are encryped (the system wents so far, that I can type in the password).
There is a disk 500 gb, it is broken on /boot and on /root and on /dev/sda1 and /dev/sda2. Whether prompt it is possible to redistribute a disk without loss of data namely it is necessary to make/boot and two equivalent on disk volume.
WinXp sp3 is on disk sdb, then installed Ubuntu 10.04 on sda, can go into diff OS without any problem. I am going to move sda to another machine, when I unplug sda, WinXp can't start to boot on sdb. How to fix it?below is my case output$ sudo fdisk -l
Disk /dev/sda: 160.0 GB ... Device Boot Start End Blocks Id System
I received the following error when I got home from work today. If this was a windows environment, my first inclination would be to boot off my dvd and then run a chkdsk on the drive to flag any bad sectors that might exist. But there's a complication for me.
Code: Select allThis message was generated by the smartd daemon running on: host name: LinuxDesktop DNS domain: [Empty]
The following warning/error was logged by the smartd daemon: Device: /dev/sdc [SAT], 1 Currently unreadable (pending) sectors Device info: WDC WD5000AAKS-65V0A0, S/N:WD-WCAWF2422464, WWN:5-0014ee-157c5db9a, FW:05.01D05, 500 GB For details see host's SYSLOG.
You can also use the smartctl utility for further investigation.The original message about this issue was sent at Sun Feb 14 13:43:17 2016 MST.Another message will be sent in 24 hours if the problem persists.
From gnome-disks Code: Select allDisk is OK, 418 bad sectors (28° C / 82° F)
I did a bit of reading and it seems that most people suggest using badblocks to first get a list of badblocks from the drive and save it to a file. Then use e2fsck to then mark the blocks listed in the badblocks file as bad on the hard drive. My problem here is that this drive is part of a RAID5 array that hosts my OS. I wanted to confirm if this was still the correct process.I boot to my Live Debian disk, stop the raid array if it's active. Then run badblocks + e2fsck commands on the drive in question and then reboot.
I have a (slightly complicated) dual/multi boot system.
I keep getting boot errors (when choosing ubuntu from the grub2 menu)
Code: Serious errors were found while checking the disk drive for /boot
If I switch off and restart, ubuntu will then start without issue.
My setup is like this ....3 disks, one with 10.10 clean install - so Grub2, separate partitions for /, /boot and /home, one with windows 7, one with windows XP and 10.04 wubi (this is my old disk which I will trash once I'm happy with my upgrade to 10.10 & 7 on separate disks.
I installed 7 and 10.10 with ONLY their disks installed. After both were working, I added all disks and rejigged the grub2 menu (using update-grub and StartUp-Manager).
This problem only seems to occur if my previous boot was not 10.10 ( I will investigate this further). It's as if something (grub2 ?, the bios ?) is remembering part of the previous boot and not using the grub2 menu completely.
I installed an OS on the second hard-disk/partition3 (/dev/sdb3; OS was FreeBSD). Added the entry and when i boot: nothing. I choose the OS from grub's menu, the list of choices vanishes, the background image stays, and there it hangs. It hangs until i hit: ctrl+alt+backspace. I have thought: to hell with it, and installed Debian/Lenny. Same problem (OH!).
I also installed the boot-loader to the second disk (/dev/sdb), hit F11 after the BIOS-screen and chosen the second hard-disk to boot from: a similar problem. It hangs, and the keyboard is "dead". I am clueless what to check for (i checked the general culprits, but with UUID its all a bit of a mess. I would say it looks good, but wouldn't bet on it) Anyone ever heard of something like that? Without error message its not easy to use the amazing Google. I do a bit of grub-troubleshooting, usually it works, but usually i get error-messages.
I made two threads about it, in case they contain useful info, here they are: http://www.linuxquestions.org/questions ... sd-827059/ http://forums.freebsd.org/showthread.php?t=17021
I have a sata 320 gb with mandriva linux 2009.1 on it.And it is what curently atached to my cpu. It is shown as 'sda' in the partition table.I also have another 40gb hard disk with windows xp installed on it.It is shown as 'hda' in the partition table . Now what i want to do is attach this 40gb hard disk to my pc and configure grub on my 320gb hard disk('sda') so as to boot windows xp(which is residing on the second hard disk,'hda')Can anyone tell me if what im doing is feasible or not? If it is feasible,can anyone suggest me how to get it working. I know i just need to add 2-3 lines to my grub.conf, but dont know what exactly i need to write.
I suspect one of my hard disks is faulty and I need to run a check on them. I have seen the documentation about 'e2fsck' but this states that this is unsafe if the filesystem is mounted. Unfortunately the device in question mounted on the root filesystem, so unmounting it is likely to create problems.
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 newly installed debian squeeze with software raid. The way I did was, as also given in this thread.
- I have 2 HDD with 500 GB each. For each of them, I created 3 partitions (/boot, / and swap) - I selected the hard drive and created a new partition table - I created a new partition that was 1GB. I then specified to use the partition as a Physical Volume for RAID. and used for /boot and enabled bootable. - Created another partition, which is of 480 GB, and then specified to use the partition as a Physical Volume for RAID. and used for /. - Created another partion and used for swap
Then RAID configuration: Through Configure RAID menu -> create MD device -> (2 for the number of drives, 0 for spare devices) Next select the partitions you want to be members of /dev/MD0. I selected /dev/sda1 and /dev/sdb1 (for /boot) Next select the partitions you want to be members of /dev/MD1. I selected /dev/sda6 and /dev/sdb6 (for /) And no RAID for swap partitions
'Finish Partitioning and write changes to disk' --> Finish the rest of the install like normal. Everything is ok now, except I am not sure how to test my raid config. When I pull the power of the HDD, it only boots from one disk. I read in some forum that I may have to install GRUB manually on the other. In Debian Squeeze, there is no grub command. Not sure how to make my software raid bootable from both disk. I configured /boot partitions of both disks to be boot=yes. Not sure whether that is ok.
I scored a Dell poweredge 6300 from a local pawn shop. It has the capability to boot from cd-rom, but apparently not with isolinux, which is what the debian installer cd uses. I was able to boot to UBCD411 (Ultimate Boot CD, which uses syslinux), but didn't see any option to boot to a CD (maybe I'm missing something here?). I tried using the boot floppy from this site. I didn't expect it to work (it's from the Woody era), and it did not. I got a message that says SYSLINUX ver.XXXX CBIOS boot failed. I went to [URL].. and looked for a boot floppy image for Lenny, but apparently it doesn't exist. I did however find the boot floppy image for Etch.
To be honest, even if I did find the Lenny floppy boot image, I'm not sure how to use it to point the system to the installer CD. So, I have two questions:
1) Does anyone know of a boot floppy image for Lenny, or if I could use the Etch boot floppy image?
2) How would one boot from floppy, then point the system to the installer CD?
System info: (4) Xeon Pentium 2 processors 500 Mhz (6) UltraSCSI hard drives (1) SCSI cd-rom drive (1) SCSI dvd-rom drive (1) Floppy drive (1) 10/100 NIC
I'm open to any other suggestions as to how I could install Debian Lenny on this machine.
It frozen up occasionally, when that happens, usually the harddisk light lights up continuously. So I suspect some process is writing to the disk, which prevent other process to go on. how do I find out who's using a lot of IO?
want to know enable 32-bit IO-support on my hard driveusing hdparm . But before I enable 32-bit support , I want to knowwhether my hard drive supports 32-bit IO or not. I tried the -I option with hdparm , but it is not telling clearlywhether it supports 32-bit or not. The following is the output from the hard drive of my system (hdparm -I ) .
I am dual booting XP and ubuntu, and everytime i want to go to XP through GRUB, and every time a Windows Disk Check apears. How can i stop this? I've set my hard drive partions to 50/50 (20GB on each side)so could that be the problem?
I'm trying to setup a PXE server with Jessie. I've got the basic setup working by following the steps at [URL] .... That part was really easy. I would like to make the process as automated as possible and then add Win7/10 to the system as well.
The first hurdle I've come across is the fact that netboot downloads everything off the repositories. This has the potential to use up a lot of bandwidth and I would like to avoid this if possible. The first idea I came across was to create a local mirror, this way not only will I be installing everything off the LAN but I'll also be getting all the updates for my systems off the LAN too. I wasn't too keen on this. The other option that I read about was to use the debian ISOs instead.
What I have tried is to copy the Debian ISO to /var/www/html/debian
Then, when my boot via the pxe, i set the option to manually select a repository and then i type in the IP address for my webserver for the address and type in /debian for the mirror directory.
However it breaks at this point. I get a message saying "Downloading a file failed"
I would prefer the as much of the install to come from the ISO as possible to keep bandwidth usage to a minimum.
For Win10, I read that I have to use an AIK to build the Winpe and then boot that. Then I can load the Windows10 ISO via nfs through Winpe.
pxelinux.cfg/default Code: Select allroot@DHCP:/srv/tftp# cat pxelinux.cfg/default UI menu.c32 TITLE PXE Test Boot LABEL Debian 8 kernel linux append vga=normal preseed/url=http://192.168.0.254/debian/preseed.txt initrd=initrd.gz --
LABEL Windows 10 kernel ?? append ??
LABEL HardDrive Boot
This is a preseed I have setup so far
Code: Select all#### Contents of the preconfiguration file (for jessie) ### Localization # Preseeding only locale sets language, country and locale. d-i debian-installer/locale string en_US
I am not sure if this is the correct section but it has to do with a faulty HD. So, the datacenter confirmed that the HD needs to be changed. They put it back and asked me when they should replace it. I told them to wait a bit.
Since then, one of the VPS hosted in this server is booting on "initramfs"