Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-22 Thread Robbi Nespu
On 3/20/21 6:10 PM, Alexander V. Makartsev wrote: If you look through information OP gathered for us, you should notice "/dev/sda" has only one partition with NTFS filesystem. Yes both disk only have one partition -- Email : Robbi Nespu PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 F

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-20 Thread Alexander V. Makartsev
On 20.03.2021 22:05, Andy Smith wrote: Anyway in OP's position, they have lost data which they need to restore and while they could wait and see if the errors are increasing in number they probably just want to get it replaced ASAP. Thanks for your input, Andy. Now OP should be able to make a ri

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-20 Thread Andy Smith
Hello, On Fri, Mar 19, 2021 at 10:36:37PM +0500, Alexander V. Makartsev wrote: > Personally, I don't think it is wise to throw away any HDD as soon as it > gets a few pending bad blocks for whatever reason. It really depends upon your risk stance. At home, on my home fileserver, it has RAID, it

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-20 Thread Alexander V. Makartsev
On 20.03.2021 13:50, David wrote: On Fri, 19 Mar 2021 at 19:53, Alexander V. Makartsev wrote: To perform surface scans you can use SMART short and long scans, and also a program called "badblocks" from the package "e2fsprogs". Be sure to unmount "/dev/sda1" before performing the scans. Hi, I

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-20 Thread David
On Fri, 19 Mar 2021 at 19:53, Alexander V. Makartsev wrote: > To perform surface scans you can use SMART short and long scans, and also a > program called "badblocks" from the package "e2fsprogs". > Be sure to unmount "/dev/sda1" before performing the scans. Hi, I wonder why you give this advic

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-19 Thread Jochen Spieker
Alexander V. Makartsev: > On 19.03.2021 21:23, Jochen Spieker wrote: >>> Note : Linux installed on sdb (ext4) and sda is a NTFS file system and >>> >>> I don't want my SSD or HDD died suddenly >> But I am afraid that is exactly what is happening. > > You can't be so sure, not until OP reports bac

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-19 Thread Jochen Spieker
Robbi Nespu: > > I worried I might missing some package for hdd and sdd maintainance (coz I > doing minimal install previously) There is no maintenance that needs to be done for hard disks or solid state disks to increase longevity. It often makes sense to setup smartmontools which can monitor th

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-19 Thread Alexander V. Makartsev
On 19.03.2021 21:23, Jochen Spieker wrote: Note : Linux installed on sdb (ext4) and sda is a NTFS file system and I don't want my SSD or HDD died suddenly But I am afraid that is exactly what is happening. You can't be so sure, not until OP reports back with testing results. I would not worr

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-19 Thread Alexander V. Makartsev
On 19.03.2021 07:07, Robbi Nespu wrote: On Thu, 18 Mar 2021 23:06:31 +0500 "Alexander V. Makartsev" wrote: Partitions mounted with 'errors=remount-ro' option will be remounted as read-only automatically, if a kernel detects an error. I suggest you to dig a little deeper, because there is a poss

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread Robbi Nespu
On Thu, 18 Mar 2021 23:06:31 +0500 "Alexander V. Makartsev" wrote: Partitions mounted with 'errors=remount-ro' option will be remounted as read-only automatically, if a kernel detects an error. I suggest you to dig a little deeper, because there is a possibility a hardware problem is the sourc

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread Robbi Nespu
On Thu, 18 Mar 2021 10:23:57 -0500 David Wright wrote: Well, that's the nature of the beast, and what backups are for. Was your fsck successful? Can you now read the files on the disk? the fsck are successful, not sure every files inside are readable or corrupt but the most files I accessed l

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread Robbi Nespu
On Thu, 18 Mar 2021 17:45:55 +0300 L Ka wrote: Old disk management tools did such alignment because they believed that any drive uses 512 byte sectors. But modern software (starting from Win7 I believe) uses 4KB alignment because it is compatible with advanced format and SSD. Do you mean linux

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread Alexander V. Makartsev
. "ls /tmp" also work but writing anything not working, then I realize my system file become read only! I reboot the computer and saw the reboot process said "ignoring read-only"..when the computer boot-up, all I see is a black terminal said " fsck error on boot: /dev/

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread David Wright
On Thu 18 Mar 2021 at 18:49:57 (+0300), IL Ka wrote: > > > > Steady on. There's likely to be a load of personal data on this drive. > > > > Yes, backup should be done first! > > > That partition table looks perfectly normal for disks of a certain vintage; > > > I agree, but from "fdisk" output I

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread Felix Miata
IL Ka composed on 2021-03-18 18:40 (UTC+0300): >> This old alignment usually only reduces performance on a 4k sector HDD. > Here is output from topic starter's fdisk: ... > Sector size (logical/physical): 512 bytes / 4096 bytes > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > Device B

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread IL Ka
> > > Steady on. There's likely to be a load of personal data on this drive. > Yes, backup should be done first! > That partition table looks perfectly normal for disks of a certain vintage; > I agree, but from "fdisk" output I see 4K (advanced format). Is your drive advanced-formatted? Of cou

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread IL Ka
> > > This old alignment usually only reduces performance on a 4k sector HDD. Here is output from topic starter's fdisk: === Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (m

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread Felix Miata
IL Ka composed on 2021-03-18 17:45 (UTC+0300): > Robbi Nespu wrote: > Device Boot StartEndSectors Size Id Type >> /dev/sda1 63 1953520456 1953520394 931.5G 7 HPFS/NTFS/exFAT > This one is wrong. > https://wiki.debian.org/DiskBlockAlignment > Old disk management tools

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread David Wright
On Thu 18 Mar 2021 at 17:45:55 (+0300), IL Ka wrote: > On Thu, Mar 18, 2021 at 5:28 PM Robbi Nespu wrote: > > > May I know why you want to check sdb instead of sda? > > > Oops, I made a typo:) Oh, I thought you said that because (from the OP): "that so weird. I execute df -h and my drive are

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread IL Ka
On Thu, Mar 18, 2021 at 5:28 PM Robbi Nespu wrote: > May I know why you want to check sdb instead of sda? > Oops, I made a typo:) > > /dev/sdb1 * 2048 234440703 234438656 111.8G 83 Linux > Your sdb is aligned successfully Device Boot StartEndSectors Size Id Type > /dev/

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread Robbi Nespu
May I know why you want to check sdb instead of sda? btw, this is output for both: - Disk /dev/sdb: 111.79 GiB, 120034123776 bytes, 234441648 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512

Re: fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread IL Ka
> > I don't want my SSD or HDD died suddenly > You need to check smart. https://en.wikipedia.org/wiki/S.M.A.R.T. Package is called "smartmontools" https://packages.debian.org/sid/smartmontools > fdisk output also said "Partition 1 does not start on physical sector > boundary." on my sda1 > > r

fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY and Partition 1 does not start on physical sector boundary

2021-03-18 Thread Robbi Nespu
writing anything not working, then I realize my system file become read only! I reboot the computer and saw the reboot process said "ignoring read-only"..when the computer boot-up, all I see is a black terminal said " fsck error on boot: /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck M

Unexpected inconsistency error message after rebooting a newly installed debian wheezy with preseed (lvm partitioning) - Any idea how to auto run fsck after installation, slipstreamed to preseed.cfg

2015-01-08 Thread Eran M.
Hi all, Below is my preseed.cfg file. What's wrong with it? Why am I getting "unexpected inconsistency" and forced to run fsck after a fresh installation? d-i debian-installer/locale string en_US d-i keyboard-configuration/xkb-keymap select us d-i console-ke

Re: /dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.

2000-06-20 Thread Colin Watson
[EMAIL PROTECTED] (Colin Watson) wrote: >Jay Kelly <[EMAIL PROTECTED]> wrote: >>And how do I run fsck? > >'man fsck'. Hmm, sorry, I suppose you might not be able to get to the man pages (though you should be able to find them somewhere on the web). Try 'fsck /dev/hda1'. -- Colin Watson

Re: /dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.

2000-06-20 Thread Colin Watson
"Joseph de los Santos" <[EMAIL PROTECTED]> wrote: >man fsck? lol just kidding.. try to use e2fsck if you have it. e2fsck is >much better (in my opinion) in fixing file system problems. e2fsck and fsck are identical on an ext2 filesystem, and on anything else e2fsck won't work. # In actualit

Re: /dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.

2000-06-20 Thread Colin Watson
then I did a reboot and when it comes to checking /dev/hda1 I >get another error: >/dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. Just as a sanity check: you did reboot by way of a clean shutdown, didn't you? If not, do; if so, then you may have hardware problems, so make

Re: /dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.

2000-06-20 Thread Joseph de los Santos
gt; To: Sent: Tuesday, June 20, 2000 5:16 PM Subject: /dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. > Hello Group, > I am having a problem getting my Potato box to boot. I just installed a Half > Life Game server and it has been working great all day. I tried to read my > mai

/dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.

2000-06-20 Thread Jay Kelly
cking /dev/hda1 I get another error: /dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. so how do I fix this? Was this coaused by Hale Life I installed? And how do I run fsck? Thanks guys

Re: HELP! [homega@vlc.servicom.es: unexpected inconsistency!]

1999-03-15 Thread Richard Lyon
> Now, after two days > it has happened yet again ... this time while editing various files on > three different consoles: all of a sudden I got a message (don't remember > which one), and couldn't do anything else, not even ^C. I had to reset the > machine (^AltDel wouldn't work either) and the

HELP! [homega@vlc.servicom.es: unexpected inconsistency!]

1999-03-15 Thread homega
- > X-Envelope-Sender: [EMAIL PROTECTED] > Date: Sat, 13 Mar 1999 00:58:34 +0100 > From: [EMAIL PROTECTED] > To: Debian List > Subject: unexpected inconsistency! > Mail-Followup-To: Debian List > X-Mailer: Mutt 0.93i > I was using netscape (communicator4.5) and all of

unexpected inconsistency!

1999-03-13 Thread homega
I was using netscape (communicator4.5) and all of a sudden... the x-window hanged! Not even Ctrl-Alt-Backspace would work, so I had to resort to the reset button. Now, on reboot, the problem came when checking hdc6 (/home): /dev/hdc6: Unattached inode 70865 /dev/hdc6: UNEXPECTED INCONSISTENCY