Hi,
thanks for all your help. It's working now as expected.
Fun fact: Had a small issue with the UUIDs, where I added a quote on left
side to a system config file, but none was allowed there. Therefore
(auto-)mounting failed (/dev/disk/by-uuid/\x22...) and it took some time
till the system came u
On Thu, 18 Nov 2021 18:17:43 +0100
Hans wrote:
> as far as I know, you also have to edit /etc/crypttab.
Correct. Sorry, I forget that. "man crypttab".
Do this before you run update-grub.
>
> If one has forgotten to encrypt a partition, the easiest way is, to
> boot from a livefile system. Th
Hi all,
as far as I know, you also have to edit /etc/crypttab.
If one has forgotten to encrypt a partition, the easiest way is, to boot from
a livefile system. Then backup the whole content of this partition to an
external partition. Note, this should be a ext3 or ext4 partition, so you
preser
On Thu, 18 Nov 2021 14:40:14 +0100
Klaus Singvogel wrote:
> I installed Debian 11 (bullseye) on a fresh PC.
> I created 3 partitions: /, swap, /home.
>
> ...and forgot during installation dialog to encrypt the /home
> partition.
>
> - how can I encrypt the /home partiti
Hi,
I installed Debian 11 (bullseye) on a fresh PC.
I created 3 partitions: /, swap, /home.
...and forgot during installation dialog to encrypt the /home partition.
- how can I encrypt the /home partition now?
- In such a way that the password is asked for manual input during every boot
> which gave me some space :)
> now to figure out why that was happening
> using stumpwm and long sbcl error set
>
>
> On Fri, Mar 12, 2021 at 11:17 AM Andrei POPESCU
> wrote:
>
> > On Vi, 12 mar 21, 10:45:22, Mitchell Laks wrote:
> > > Hi,
> > >
On Vi, 12 mar 21, 17:42:48, Tixy wrote:
> On Fri, 2021-03-12 at 18:13 +0200, Andrei POPESCU wrote:
> >
> > My personal favorite:
> >
> > du -hx --max-depth=1 | sort -h
> >
>
> You can use the short option -d instead of --max-depth, and make it's
> parameter '1' come straight after [1], so
> du -hd1 | sort -h
> then 'cd' into a likely candidate directory and repeat.
Hmmm here's what I do instead:
du | sort -n | tail -n 100
-- Stefan
On Fri, 2021-03-12 at 18:13 +0200, Andrei POPESCU wrote:
> On Vi, 12 mar 21, 09:02:23, Charles Curley wrote:
> > On Fri, 12 Mar 2021 10:45:22 -0500
> > Mitchell Laks wrote:
> >
> > > I recently upgraded a system that uses sid and the /home
> > > partition
&
On Fri, 12 Mar 2021 18:13:51 +0200
Andrei POPESCU wrote:
> On Vi, 12 mar 21, 09:02:23, Charles Curley wrote:
> > On Fri, 12 Mar 2021 10:45:22 -0500
> > Mitchell Laks wrote:
> >
> > > I recently upgraded a system that uses sid and the /home partition
> > >
On Vi, 12 mar 21, 10:45:22, Mitchell Laks wrote:
> Hi,
>
> I recently upgraded a system that uses sid and the /home partition filled.
>
> I then adjusted tune2fs -m 3 /dev/md1 to give myself 20 G of space.
> Did nothing and next day already filled /home 100% again.
Please sho
On Vi, 12 mar 21, 09:02:23, Charles Curley wrote:
> On Fri, 12 Mar 2021 10:45:22 -0500
> Mitchell Laks wrote:
>
> > I recently upgraded a system that uses sid and the /home partition
> > filled.
>
> I find "du | sort -n" useful in such situations. Start a
On Fri, 12 Mar 2021 10:45:22 -0500
Mitchell Laks wrote:
> I recently upgraded a system that uses sid and the /home partition
> filled.
I find "du | sort -n" useful in such situations. Start at /home and
work your way down.
--
Does anybody read signatures any more?
https://c
Mitchell Laks wrote:
> Hi,
>
> I recently upgraded a system that uses sid and the /home partition filled.
>
> I then adjusted tune2fs -m 3 /dev/md1 to give myself 20 G of space.
> Did nothing and next day already filled /home 100% again.
> Same thing happened when i did -m
>
> tried du -sh on /home/username /* etc.
>
and what was the output?
I use
$ du -d1 | sort -n
Also, try "ncdu".
Hi,
I recently upgraded a system that uses sid and the /home partition filled.
I then adjusted tune2fs -m 3 /dev/md1 to give myself 20 G of space.
Did nothing and next day already filled /home 100% again.
Same thing happened when i did -m2.
Ok how to find the culprit ?
A long long time ago
On Tue 28 May 2019 at 14:13:42 (+0300), Sergey Belyashov wrote:
> As expected nothing is changed. I did not forget to run update-initramfs
> after change of fstab.
> Attached 3 photos: normal boot, recovery boot before pasword enter,
> recovery boot after password and Ctrl-D in recovery shell.
[I
I have found related bug in the Debian bug system:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868164
пн, 27 мая 2019 г. в 13:09, Sergey Belyashov :
> I have system with soft raid and /home is encrypted (luks with password).
> When I boot it using default boot kernel options (ro quiet) syst
I have examine initramfs image and found that it is not tries to mount
encrypted partitions other than root. Moreover, it is confirmed by dmesg
output: systemd starts before mounting of /var and /home So it is not
initrd problem. Problem somethere in system.
Best regards,
Sergey Belyashov
вт, 28
Sergey Belyashov wrote:
> As expected nothing is changed. I did not forget to run update-initramfs
> after change of fstab.
> Attached 3 photos: normal boot, recovery boot before pasword enter,
> recovery boot after password and Ctrl-D in recovery shell.
I am not a systemd expert. The images does
As expected nothing is changed. I did not forget to run update-initramfs
after change of fstab.
Attached 3 photos: normal boot, recovery boot before pasword enter,
recovery boot after password and Ctrl-D in recovery shell.
Best regards,
Sergey Belyashov
вт, 28 мая 2019 г., 9:38 deloptes :
> Serg
I'll try your suggestion. But I think problem is not here. Password ask is
after mounting all other filesystems, swapon and flush of journald:
[9.986320] intel_rapl: Found RAPL domain uncore
[ 10.203636] EXT4-fs (md0p2): mounted filesystem with ordered data mode.
Opts: (null)
[ 10.203981]
Sergey Belyashov wrote:
> Root partition is on mdraid but is not encrypted. Home is encrypted only.
> Modules are set to most already.
>
I have this setup on my server, but I removed all crypted entries from fstab
because obviously I can not sit infront of the server to type the password
when bo
Root partition is on mdraid but is not encrypted. Home is encrypted only.
Modules are set to most already.
вт, 28 мая 2019 г., 9:06 deloptes :
> Sergey Belyashov wrote:
>
> > My problem is about than year old or more. With default options (without
> > plymouth) only information about root partiti
Ross Boylan wrote:
> I've discovered that if I type my pass-phrase (waiting long enough
> that I think things have settled down), the system boots.
>
Have you tried setting up the display parameters properly in grub? Sometimes
on notebooks the default settings are different and do not match pred
Sergey Belyashov wrote:
> My problem is about than year old or more. With default options (without
> plymouth) only information about root partition mount or fsck. Later it
> replaced by partition waiting "progress" (moving red asterisks). I have
> try to wait about a minute and try to enter luks
My problem is about than year old or more. With default options (without
plymouth) only information about root partition mount or fsck. Later it
replaced by partition waiting "progress" (moving red asterisks). I have try
to wait about a minute and try to enter luks password, but no any changes.
I t
For at least the last couple of weeks I've had the screen go
completely blank during bootup, after displaying initial messages (I
changed from "quiet" to "debug" for kernel startup). This is with a
luks encrypted root. I saw it under jessie and buster. I blamed
failing hardware (I can't get into
I have system with soft raid and /home is encrypted (one of raid1
partitions is encrypted using luks with password). When I boot it using
default boot kernel options (ro quiet) systemd stops on waiting for
partition, but no any password prompt. I try to boot with plymouth (ro
quiet splash), but it
I have system with soft raid and /home is encrypted (luks with password).
When I boot it using default boot kernel options (ro quiet) systemd stops
on waiting for partition, but no any password prompt. I try to boot with
plymouth (ro quiet splash), but it does not help me. I may boot only using
"re
On 1/12/18 6:23 AM, Roberto C. Sánchez wrote:
> On Fri, Nov 30, 2018 at 12:14:40PM -0500, Default User wrote:
>>I often see people recommend a separate home partition.
>>But why would (or not) that be better than just a home directory within
>>the root director
On Sat 01 Dec 2018 at 12:22:09 -0500, Gene Heskett wrote:
> On Saturday 01 December 2018 10:02:29 rhkra...@gmail.com wrote:
>
> > On Friday, November 30, 2018 07:26:33 PM Gene Heskett wrote:
> > > On Friday 30 November 2018 13:58:52 Michael Stone wrote:
> > > > On Fri, Nov 30, 2018 at 05:23:09PM
On Fri, Nov 30, 2018 at 08:39:55PM -0600, David Wright wrote:
> On Fri 30 Nov 2018 at 11:23:57 (-1000), Joel Roth wrote:
> > On Fri, Nov 30, 2018 Cindy-Sue Causey wrote:
> > > Cliff's Notes Version Part I: Flaky USB connections are an important
> > > factor! An accidentally disconnected USB connect
On Saturday 01 December 2018 10:02:29 rhkra...@gmail.com wrote:
> On Friday, November 30, 2018 07:26:33 PM Gene Heskett wrote:
> > On Friday 30 November 2018 13:58:52 Michael Stone wrote:
> > > On Fri, Nov 30, 2018 at 05:23:09PM +, Michael Thompson wrote:
> > > >Because if your root partition
On Sat 01 Dec 2018 at 10:02:29 (-0500), rhkra...@gmail.com wrote:
> On Friday, November 30, 2018 07:26:33 PM Gene Heskett wrote:
> > On Friday 30 November 2018 13:58:52 Michael Stone wrote:
> > > On Fri, Nov 30, 2018 at 05:23:09PM +, Michael Thompson wrote:
> > > >Because if your root partition
On Saturday, December 01, 2018 02:54:22 AM Pascal Hambourg wrote:
> Le 01/12/2018 à 03:21, Ric Moore a écrit :
> > On 11/30/18 8:45 PM, rhkra...@gmail.com wrote:
> >> Why bother with /opt -- iirc, /opt is for optional software, not user
> >> data.
>
> Right.
>
> > True true, but you may select th
On Friday, November 30, 2018 07:26:33 PM Gene Heskett wrote:
> On Friday 30 November 2018 13:58:52 Michael Stone wrote:
> > On Fri, Nov 30, 2018 at 05:23:09PM +, Michael Thompson wrote:
> > >Because if your root partition fails, you can reinstall and all your
> > >
> > > files are safe on their
On 2018-12-01, Jimmy Johnson wrote:
>>>
>>> Opinions, please.
>
> I dislike top posting.
That isn't an opinion. This is an opinion.
--
He used sentences differently from any other prose writer. He always sounded
like a slightly drunk man who is very melancholy, who has no illusions about
life,
On 11/30/2018 09:22 AM, Hans wrote:
Am Freitag, 30. November 2018, 18:14:40 CET schrieb Default User:
When you are using a seperate home-partition you can easily install the whole
system new - and all user specific content will be saved and will not have to
configured by the user(s) again
Le 01/12/2018 à 03:21, Ric Moore a écrit :
On 11/30/18 8:45 PM, rhkra...@gmail.com wrote:
Why bother with /opt -- iirc, /opt is for optional software, not user
data.
Right.
True true, but you may select the /opt partition from the install menu
and not re-format it.
You can select arbitra
On Fri 30 Nov 2018 at 21:21:50 (-0500), Ric Moore wrote:
> On 11/30/18 8:45 PM, rhkra...@gmail.com wrote:
> > On Friday, November 30, 2018 08:32:23 PM Ric Moore wrote:
> > > Cindy, I advocate using /opt for that very reason. I leave /home/user
> > > alone. I create /opt/user directory and fill it w
On Fri 30 Nov 2018 at 11:23:57 (-1000), Joel Roth wrote:
> On Fri, Nov 30, 2018 Cindy-Sue Causey wrote:
> > Cliff's Notes Version Part I: Flaky USB connections are an important
> > factor! An accidentally disconnected USB connection can cause data to
> > become *unknowingly* redirected back to the
Hi,
On Fri, Nov 30, 2018 at 07:26:33PM -0500, Gene Heskett wrote:
> If you are going to put you /home on a separate partition, put it
> on a different disk.
>
> Unfortunately that has NOT been acceptable to the installer for most of a
> decade now.
Strange, I've been putting /home on a differen
On 11/30/18 8:45 PM, rhkra...@gmail.com wrote:
On Friday, November 30, 2018 08:32:23 PM Ric Moore wrote:
On 11/30/18 3:47 PM, Cindy-Sue Causey wrote:
Having lately been successfully "mount -B" ing my
/var/cache/apt/archives hoard, I can now easily see having those
(~/Documents, ~/Downloads, et
On Fri 30 Nov 2018 at 12:23:11 (-0500), Roberto C. Sánchez wrote:
> On Fri, Nov 30, 2018 at 12:14:40PM -0500, Default User wrote:
> >I often see people recommend a separate home partition.
> >But why would (or not) that be better than just a home directory within
> >
On Friday, November 30, 2018 08:32:23 PM Ric Moore wrote:
> On 11/30/18 3:47 PM, Cindy-Sue Causey wrote:
> > Having lately been successfully "mount -B" ing my
> > /var/cache/apt/archives hoard, I can now easily see having those
> > (~/Documents, ~/Downloads, et al) each remaining as their own separ
On 11/30/18 3:47 PM, Cindy-Sue Causey wrote:
Having lately been successfully "mount -B" ing my
/var/cache/apt/archives hoard, I can now easily see having those
(~/Documents, ~/Downloads, et al) each remaining as their own separate
directories on a secondary partition. Fstab would then be asked t
On Friday 30 November 2018 13:58:52 Michael Stone wrote:
> On Fri, Nov 30, 2018 at 05:23:09PM +, Michael Thompson wrote:
> >Because if your root partition fails, you can reinstall and all your
> > files are safe on their own partition...
>
> ...leaving open the question of how likely that scen
On Fri, Nov 30, 2018 Cindy-Sue Causey wrote:
> Cliff's Notes Version Part I: Flaky USB connections are an important
> factor! An accidentally disconnected USB connection can cause data to
> become *unknowingly* redirected back to the original directory on the
> primary partition. That situation can
On Fri, Nov 30, 2018 at 02:14:09PM -0500, Felix Miata wrote:
Michael Stone composed on 2018-11-30 13:58 (UTC-0500):
On Fri, Nov 30, 2018 at 05:23:09PM +, Michael Thompson wrote:
Because if your root partition fails, you can reinstall and all your files are
safe on their own partition...
On 11/30/18, Roberto C. Sánchez wrote:
> On Fri, Nov 30, 2018 at 12:14:40PM -0500, Default User wrote:
>>I often see people recommend a separate home partition.
>>But why would (or not) that be better than just a home directory
>> within
>>the root directo
Michael Stone composed on 2018-11-30 13:58 (UTC-0500):
> On Fri, Nov 30, 2018 at 05:23:09PM +, Michael Thompson wrote:
>>Because if your root partition fails, you can reinstall and all your files
>>are safe on their own partition...
> ...leaving open the question of how likely that scenario
On Fri, Nov 30, 2018 at 05:23:09PM +, Michael Thompson wrote:
Because if your root partition fails, you can reinstall and all your files are
safe on their own partition...
...leaving open the question of how likely that scenario is.
Because if your root partition fails, you can reinstall and all your files are
safe on their own partition...
> On 30 Nov 2018, at 17:14, Default User wrote:
>
>
> I often see people recommend a separate home partition.
>
> But why would (or not) that be better than jus
On Fri, Nov 30, 2018 at 12:14:40PM -0500, Default User wrote:
>I often see people recommend a separate home partition.
>But why would (or not) that be better than just a home directory within
>the root directory?
>Wouldn't one less partition be simpler, and the
Am Freitag, 30. November 2018, 18:14:40 CET schrieb Default User:
When you are using a seperate home-partition you can easily install the whole
system new - and all user specific content will be saved and will not have to
configured by the user(s) again.
In case, you have no backup from the
I often see people recommend a separate home partition.
But why would (or not) that be better than just a home directory within the
root directory?
Wouldn't one less partition be simpler, and therefore (all other things
being equal) better?
Opinions, please.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Nov 04, 2017 at 12:33:48AM +0100, Michael Lange wrote:
> Hi,
>
> On Fri, 3 Nov 2017 22:34:02 +0100
> wrote:
>
> >
> > - copy the contents of /home to its future location:
> (...)
> > or cp -a /home/* /mnt
>
> to be nitpicking, should
Hi,
On Fri, 3 Nov 2017 22:34:02 +0100
wrote:
>
> - copy the contents of /home to its future location:
(...)
> or cp -a /home/* /mnt
to be nitpicking, shouldn't this rather be
cp -a /home/. /mnt
just to cover the (admittedly unlikely) case there is some hidden
file or folder in
Thank Pol Hallen and to...@tuxteam.de!
tomas's instruction is detailed and professional, many thanks!
On Friday, November 3, 2017 5:34 PM, "to...@tuxteam.de"
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Nov 03, 2017 at 09:06:28PM +, Long Wind wrote:
> i have
i have installed wheezy at /dev/sda3, no swap
disk space isn't enough now
i want to add /dev/sda4 as /home partition
but how to do it? Thanks!
mkfs.ext4 -v /dev/sda4
login from shell (no xorg) with root and mount sda4 to /home2, copy
/home to /home2, rm home and rename home2 to home
Pol
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Nov 03, 2017 at 09:06:28PM +, Long Wind wrote:
> i have installed wheezy at /dev/sda3, no swapdisk space isn't enough nowi
> want to add /dev/sda4 as /home partitionbut how to do it? Thanks!
First, take a backup. Things tend to go wrong i
. Those
instructions unfortunately did not tell me that the crypt has to be
resized as well as the file system and the logical volume. The result
was that the all the data in the /home partition were obliterated.
Fortunately I had backed up all of them.
The new encrypted /home partition that I
On Thu, 11 Jun 2015 00:02:02 -0400
Ken Heard wrote:
> On 2015-06-10 13:17, Don Armstrong wrote:
> > On Tue, 09 Jun 2015, Ken Heard wrote:
> >> After some research I found file /etc/crypttab which contains a
> >> list of the UUIDs for encrypted partitions, /home in my case. I
> >> thought it would
On 2015-06-10 13:17, Don Armstrong wrote:
On Tue, 09 Jun 2015, Ken Heard wrote:
After some research I found file /etc/crypttab which contains a list
of the UUIDs for encrypted partitions, /home in my case. I thought it
would be a simple matter of changing the relevant UUID to the current
one. It
On Tue, 09 Jun 2015, Ken Heard wrote:
> After some research I found file /etc/crypttab which contains a list
> of the UUIDs for encrypted partitions, /home in my case. I thought it
> would be a simple matter of changing the relevant UUID to the current
> one. It is apparently not.
Did you rebuild
On Tue, 2015-06-09 at 13:37 -0400, Ken Heard wrote:
> On 2015-06-09 11:18, Ken Heard wrote:
> > For reasons which I won't go into now my encrypted home partition was
> > obliterated. (Yes, all the data thereon had been backed up.) I created
> > a new one, but of course
On 2015-06-09 11:18, Ken Heard wrote:
For reasons which I won't go into now my encrypted home partition was
obliterated. (Yes, all the data thereon had been backed up.) I created
a new one, but of course it does not have the same UUID as the previous
one.
Jessie's systemd howev
For reasons which I won't go into now my encrypted home partition was
obliterated. (Yes, all the data thereon had been backed up.) I created
a new one, but of course it does not have the same UUID as the previous
one.
Jessie's systemd however on boot continues to look for the ol
On Saturday 04 April 2015 02:33:00 Ric Moore wrote:
> On 04/03/2015 10:35 AM, Gene Heskett wrote:
> > Is booting with the single option on the kernels command line
> > insufficient for this scenario?
>
> Gene, when you first boot, boot into rescue mode and login as root.
> now /home is nicely idl
On 04/03/2015 10:35 AM, Gene Heskett wrote:
Is booting with the single option on the kernels command line
insufficient for this scenario?
Gene, when you first boot, boot into rescue mode and login as root. now
/home is nicely idle, after you have installed the 3rd new drive and
have partitione
On Fri, Apr 26, 2013 at 6:22 AM, Bob Proulx wrote:
> Dan wrote:
>> - Backup home and the files from /etc passwd, group, shadow and gshadow
>> ...
>> - merge the old passwd, group, shadow and gshadow with the new files
>> found in /etc
>
> You so far have three votes against doing this but I will v
Dan wrote:
> - Backup home and the files from /etc passwd, group, shadow and gshadow
> ...
> - merge the old passwd, group, shadow and gshadow with the new files
> found in /etc
You so far have three votes against doing this but I will vote *for*
doing it. I think this is okay. It all depends up
Le Jeu 25 avril 2013 12:54, Dan a écrit :
> Hi,
>
>
> As I explained in a previous email I had an issue with the ATI driver
> and squeeze and I decided to wipe squeeze and install wheezy. Luckily the
> home partition is separated from the rest.
>
> Which would be the best
installation process.
I did it during my laptop re-install'. To avoid to copy data from
backup and to save time.
I do not have any ref to the doc' and currently no time to search for
but take a look at the doc', it can be helpful if you want to keep your
/home and the data on it as i
ncluded to the /
directory, instead of an additional partition. After installation you
can remove /home and mount the home partition instead, by /etc/fstab.
I prefer to keep everything within / and don't use a separated /home, so
I have to copy an old /home, resp. I only copy emails and
Hi,
As I explained in a previous email I had an issue with the ATI driver
and squeeze and I decided to wipe squeeze and install wheezy. Luckily
the home partition is separated from the rest.
Which would be the best way to proceed?
I was going to do the following:
- Backup home and the files
On Sat, September 8, 2012 5:28 am, Lisi wrote:
> On Saturday 08 September 2012 12:05:32 Weaver wrote:
>> That's with reinstalling with the stable disc of the time, then
>> upgrading
>> all the way back up to unstable.
>> No back up.
>> Nothing!
>
> Ouch!! You obviously enjoy playing Russian roule
ions. Thus, I have finally decided
> to move on to Debian 6 (squeeze) and then possibly even to Debian sid,
> which I have already used for some time as the aptosid
> distribution. I would like however to preserve my /home partition. Is
> that **advisable** or should I delete this partition a
have finally decided to move on to Debian 6 (squeeze) and then
> possibly even to Debian sid, which I have already used for some time as
> the aptosid distribution. I would like however to preserve my /home
> partition. Is that **advisable** or should I delete this partition as
> well
On Saturday 08 September 2012 12:05:32 Weaver wrote:
> That's with reinstalling with the stable disc of the time, then upgrading
> all the way back up to unstable.
> No back up.
> Nothing!
Ouch!! You obviously enjoy playing Russian roulette!
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ..
e aptosid
>>> distribution. I would like however to preserve my /home partition. Is
>>> that **advisable** or should I delete this partition as well?
>>
>> No, you can do that.
>> The facility to have the /home partition specified, in a new install, is
>>
"Weaver" writes:
> On Fri, September 7, 2012 5:33 pm, Mauricio Calvao wrote:
>> to move on to Debian 6 (squeeze) and then possibly even to Debian sid,
>> which I have already used for some time as the aptosid
>> distribution. I would like however to preserve
distribution. I would like however to preserve my /home partition. Is
> that **advisable** or should I delete this partition as well?
You can keep your home partition as is. It is advisable to put
everything on at least a RAID-1 as it improves your chances to survive
disk failures. In any case,
ions. Thus, I have finally decided
> to move on to Debian 6 (squeeze) and then possibly even to Debian sid,
> which I have already used for some time as the aptosid
> distribution. I would like however to preserve my /home partition. Is
> that **advisable** or should I delete this partition
On Fri, 07 Sep 2012 21:33:15 -0300, Mauricio Calvao wrote:
> I would like however to preserve my /home partition. Is that
> **advisable** or should I delete this partition as well?
Depending on how much version dependant stuff you put there.
I personally never put any version dependant
to Debian sid,
which I have already used for some time as the aptosid
distribution. I would like however to preserve my /home partition. Is
that **advisable** or should I delete this partition as well?
Thanks in advance!
--
###
Prof. Mauricio Ortiz Calvao
Jon Dowland wrote:
On Wed, Jan 13, 2010 at 08:10:29AM -0700, Paul Scott wrote:
/dev/hda10 4366 4870 4056381 83 Linux
To me the problem is clearly about the file system not the partition.
This seems like an interesting problem. I'm still mostly
convinced it is actually a partitio
Jon Dowland wrote:
On Wed, Jan 13, 2010 at 08:10:29AM -0700, Paul Scott wrote:
/dev/hda10 4366 4870 4056381 83 Linux
To me the problem is clearly about the file system not the partition.
This seems like an interesting problem. I'm still mostly
convinced it is actually a partitio
On Wed, Jan 13, 2010 at 08:10:29AM -0700, Paul Scott wrote:
> /dev/hda10 4366 4870 4056381 83 Linux
>
> To me the problem is clearly about the file system not the partition.
This seems like an interesting problem. I'm still mostly
convinced it is actually a partition problem. 10 is quite a
green wrote:
Paul Scott wrote at 2010-01-12 21:55 -0600:
green wrote:
I don't recall seeing the output of 'fdisk -l' on the sid system;
perhaps it would list disk sda instead of hda.
Send the output of 'fdisk -l'.
I'm only sending the relevant line since I have to type it.
Paul Scott wrote at 2010-01-12 21:55 -0600:
> green wrote:
> >I don't recall seeing the output of 'fdisk -l' on the sid system;
> >perhaps it would list disk sda instead of hda.
Send the output of 'fdisk -l'.
signature.asc
Description: Digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Scott wrote:
> green wrote:
>> ... ... ...
>> I don't recall seeing the output of 'fdisk -l' on the sid system;
>> perhaps it would list disk sda instead of hda.
>>
>> Try 'mount /dev/sda10 /home' on the sid system. If that works, change
>> hda10
green wrote:
Paul Scott wrote at 2010-01-12 12:50 -0600:
green wrote:
What filesystem is it?
ext2 (maybe ext3 but I don't think so)
What is the output of 'mount /dev/hda10' on the sid system?
mount: special device /dev/hda10 does not exist
This means the de
Paul Scott wrote at 2010-01-12 12:50 -0600:
> green wrote:
> >What filesystem is it?
> ext2 (maybe ext3 but I don't think so)
> >What is the output of 'mount /dev/hda10' on the sid system?
> mount: special device /dev/hda10 does not exist
This means the device node in /dev for that partition does
green wrote:
Paul Scott wrote at 2010-01-11 11:12 -0600:
Late on Dec. 25 I rebooted my sid system and my home directory is no
longer visible to my system even to Grub. It contains my home
directory. An Ubuntu 8.10 live CD sees it just fine. I normally keep
everything updated unless apt-lis
Paul Scott wrote at 2010-01-11 11:12 -0600:
> Late on Dec. 25 I rebooted my sid system and my home directory is no
> longer visible to my system even to Grub. It contains my home
> directory. An Ubuntu 8.10 live CD sees it just fine. I normally keep
> everything updated unless apt-listbugs shows
Mark wrote:
On Mon, Jan 11, 2010 at 10:12:19AM -0700, Paul Scott wrote:
> Sorry for reposting but my home system is effectively unusable.
>
> Late on Dec. 25 I rebooted my sid system and my home directory is no
> longer visible to my system even to Grub. It contains my home
> directory. An Ubun
Waterhorse wrote:
-Original Message-
From: lego_12...@rambler.ru
To: debian-user@lists.debian.org
Date: 01/11/10 19:24
Subject: Re: Ubuntu 8.10 sees my home partition, sid of Dec. 25 doesn't
On Mon, Jan 11, 2010 at 10:12:19AM -0700, Paul Scott wrote:
Sorry for repo
> -Original Message-
> From: lego_12...@rambler.ru
> To: debian-user@lists.debian.org
> Date: 01/11/10 19:24
> Subject: Re: Ubuntu 8.10 sees my home partition, sid of Dec. 25 doesn't
>
> On Mon, Jan 11, 2010 at 10:12:19AM -0700, Paul Scott wrote:
> >
1 - 100 of 131 matches
Mail list logo
