On Mon, Jun 12, 2023 at 09:53:03PM +0200, Smits Katze wrote:
> >What would be the difference to simply saying
> >
> > sudo -i
>
> The effect should be the same (and the command is more concise).
>
> Thanks for pointing it out.
Thank you for confirmation & sorry for the nitpick :)
Cheers
--
t
>What would be the difference to simply saying
>
> sudo -i
The effect should be the same (and the command is more concise).
Thanks for pointing it out.
--
PGP: FF815935D964B268656B43DCB8037830D522909E
On Mon, Jun 12, 2023 at 06:54:40PM +0200, Smits Katze wrote:
> Debian wiki describes how to configure a read-only rootfs and how to
> run apt and unattended-upgrades in such a filesystem:
> https://wiki.debian.org/ReadonlyRoot
>
> I would like to report that I am having considerab
Debian wiki describes how to configure a read-only rootfs and how to
run apt and unattended-upgrades in such a filesystem:
https://wiki.debian.org/ReadonlyRoot
I would like to report that I am having considerable success with the
following simple command sequence:
sudo su -l
unshare -m
# in the
Rock:
Hi,
I'm trying to bring up the Debian 10 root file system on an ARM SoC
board. When the rootfs was in an SD card the board worked well. When I
put the rootfs on an NFS server and tried to boot the board through NFS
mount, it reported error through serial port:
|[FAILED] Failed to
On Tue, Aug 16, 2022 at 04:20:36PM -0400, Greg Wooledge wrote:
> On Tue, Aug 16, 2022 at 03:58:30PM -0400, Lie Rock wrote:
> > So how is the process "create system users" performed when Linux/Debian
> > starts? What can be contributing to this error?
>
> unicorn:~$ grep -ri 'create system users' /
On Tue, Aug 16, 2022 at 03:58:30PM -0400, Lie Rock wrote:
> So how is the process "create system users" performed when Linux/Debian
> starts? What can be contributing to this error?
unicorn:~$ grep -ri 'create system users' /lib/systemd
/lib/systemd/system/systemd-sysusers.service:Description=Crea
Hi,
I'm trying to bring up the Debian 10 root file system on an ARM SoC board.
When the rootfs was in an SD card the board worked well. When I put the
rootfs on an NFS server and tried to boot the board through NFS mount, it
reported error through serial port:
[FAILED] Failed to start C
other junk was written unintentionally (forgot to
> mount readonly - degraded)
>
> The task now seems to be finishing resolving which modules can bring in the
> rest of the critical infrastructure to allow access to the drives that had
> been no customized bother to bring onl
Hello everyone!
I'm currently trying to find a method to decrypt my rootfs at boot
time with a keyfile on debian stretch.
I've successfully implemented a method ([1] and [2]) which uses a
custom script to read the first 2048bit
from the usbkey memory to decrypt the disk, but I actual
Hello everyone!
I'm currently trying to find a method to decrypt my rootfs at boot time with a
keyfile on debian stretch.
I've successfully implemented a method ([1] and [2]) which uses a custom script
to read the first 2048bit
from the usbkey memory to decrypt the disk, but I actual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Err, whoops.
That wasn't supposed to be encrypted. Not sure how that happened ...
Here we go:
On 02/04/15 00:21, Richard Hector wrote:
> On 01/04/15 11:56, Martin Read wrote:
>> I have a dual-boot Win7/Debian jessie system. Because Windows
>> doesn'
-BEGIN PGP MESSAGE-
Charset: utf-8
Version: GnuPG v2.0.19 (GNU/Linux)
hQEMA07UmgrFcS2hAQf/dwmi7WfCdgUxzk0BIhdGs9qKWgbRiiVyqxLm2Min3wqF
Xw6mgqsMBh3vQ24CCVmPTF4q2eiy2ZMsGjsFwXm2SJK8WrgsSOKSFtyt77rZHpHx
SExwcy/nXHoSaynm9x3dNwfy2qcrANSmG9dWBiX3HUc1GSw08DVa50D+iqZBmyWH
csubGvcXMxbvYBAKwFZniS2Nr
It's an open bug in Debian Jessie:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767040
Until the bug is fixed you can create the file /etc/e2fsck.conf containing
> [options]
> broken_system_clock=1
Janis
Am 01.04.2015 um 00:56 schrieb Martin Read:
> I have a dual-boot Win7/Debian jessie sy
I have a dual-boot Win7/Debian jessie system. Because Windows doesn't
deal gracefully with handling the hardware time-of-day clock the proper
way (hwclock set to GMT, all TZ handling in software), this means that
the hwclock changes for daylight savings time.
The Debian installation itself cop
Thanks for your help and the replies. So this issue is now resolved.
Summary of Issue:
Mounting root as read-only as documented in
(https://wiki.debian.org/ReadonlyRoot) because rootfs is busy.
Summary of Solution:
1. 'lsof +L1' showed cupsd getting stuck on /etc/passwd (deleted).
On Thu 06 Mar 2014 at 23:05:20 +, Amit wrote:
> 0) After reboot and running 'lsof +L1':
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NLINK NODE NAME
> cupsd935 root8r REG8,1 1392 0 132095
> /etc/passwd (deleted)
I upgraded my wheezy install to jess
On Thu, Mar 06, 2014 at 11:05:20PM +, Amit wrote:
> 0) After reboot and running 'lsof +L1':
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NLINK NODE NAME
> cupsd935 root8r REG8,1 1392 0 132095
> /etc/passwd (deleted)
So it's reproducible.
> 1) Shut
Reco gmail.com> writes:
>
> Can you do the following, please:
>
> 1) Shutdown cups by systemd's way (systemctl blahblah …).
>
> 2) Start it by /etc/init.d/cups start.
>
> 3) Confirm with lsof whenever /etc/passwd is kept open.
>
> 4) While you're at it, invoke 'fuser /etc/passwd' to ensure t
On Thu, 6 Mar 2014 18:35:06 + (UTC)
Amit wrote:
> Reco gmail.com> writes:
>
> >
> > https://wiki.debian.org/ReadonlyRoot#cups says:
> >
> > CUPS stores any kind of state files under /etc (classes.conf,
> > cupsd.conf, printers.conf subscriptions.conf) and upstream is against
> > any modif
Brian cityscape.co.uk> writes:
>
> On Thu 06 Mar 2014 at 01:21:03 +, Amit wrote:
>
> > I need cups, so is there a way around this?
>
> This doesn't answer your question but I have a spare Wheezy with
> separate /, /home, and /var. I installed systemd, m
Robin gmail.com> writes:
>
> Just a suggestion have you tried a re-install of cups since fresh
> install of systemd
>
Thanks for the reply.
Yes, the first thing I did was install systemd and then all the other
packages but anyways I tried reinstalling again but no luck.
--
To UNSUBSCRIBE,
Reco gmail.com> writes:
>
> https://wiki.debian.org/ReadonlyRoot#cups says:
>
> CUPS stores any kind of state files under /etc (classes.conf,
> cupsd.conf, printers.conf subscriptions.conf) and upstream is against
> any modification.
>
> Personally I worked around similar problem by moving /et
Hi.
On Thu, 6 Mar 2014 14:49:30 +
Brian wrote:
> On Thu 06 Mar 2014 at 01:21:03 +, Amit wrote:
>
> > I need cups, so is there a way around this?
>
> This doesn't answer your question but I have a spare Wheezy with
> separate /, /home, and /var. I installe
On 6 March 2014 01:21, Amit wrote:
> Amit gmail.com> writes:
>
> [snip]
>
>>
>> However, setting up a fresh install of systemd, the readonly does not
>> have any effect. The rootfs is still mounted as rw. All I did was
>> changed /etc/fstab. Based o
On Thu 06 Mar 2014 at 01:21:03 +, Amit wrote:
> I need cups, so is there a way around this?
This doesn't answer your question but I have a spare Wheezy with
separate /, /home, and /var. I installed systemd, made the rootfs
ro in fstab and booted with init=/lib/systemd/systemd. The ro
Amit gmail.com> writes:
[snip]
>
> However, setting up a fresh install of systemd, the readonly does not
> have any effect. The rootfs is still mounted as rw. All I did was
> changed /etc/fstab. Based on the systemd man pages, this should be
> enough.
>
> How do I g
Hello,
I always run my debian systems with a separate /, /home, and /var. I
added read-only 'ro' mount to fstab for the root / partition. So far it
has been working great.
However, setting up a fresh install of systemd, the readonly does not
have any effect. The rootfs is still mou
Am Samstag, 20. April 2013 schrieb Kevin Chadwick:
> > > Don't believe opinion as fact just because it's on a server hosted
> > > by freedesktop.org. Rusty Russel and the FHS is a more
> > > authoritative (and correct) source, I suggest you read it.
> >
> > I never split up / and /usr for the last
topic. When you said in the previous mail that you are working on
moving /usr to the rootfs i thought oh oh an other valueable feature goes down
the drain. But your argumentation has actually convinced me.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
> > - With a package manager, if any of the rootfs, /usr or /var are
> > damaged, you need to either restore the entire set from a backup
> > or reinstall. This comes back to the fact that all locations
> > under the control of the package manager are a unifie
ocated on the root
> > > filesystem without any problems. It's actually the default
> > > partitioning method.
> > >
> >
> > > Do you have any concrete reasons to have /usr separate from / ?
> >
> > You need to look at the rootfs section, havi
esystem
> > without any problems. It's actually the default partitioning method.
> >
>
> > Do you have any concrete reasons to have /usr separate from / ?
>
> You need to look at the rootfs section, having them separate makes what
> should be the most critical
hod.
>
> Do you have any concrete reasons to have /usr separate from / ?
You need to look at the rootfs section, having them separate makes what
should be the most critical filesystem (rootfs) 100s! of times larger
and that quite rightly contradicts the spec (good reasons are mentioned
bu
On Sat, Apr 20, 2013 at 10:50:05AM +0200, Raffaele Morelli wrote:
> 2013/4/20 Jude DaShiell
>
> > Sorry, wrong list for reply.
>
>
> ...though interesting :-)
Although, not quite correct:
http://www.lowellsmilecenter.com/blog/2008/02/04/calcium-and-stronger-teeth/
--
"If you're not careful,
On Fri, Apr 19, 2013 at 08:09:24PM +0100, Kevin Chadwick wrote:
> > > /dev/mapper/debian-usr 4,6G 1,2G3,2G 28% /usr
> >
> > There's no real need to have /usr separate from /
> > You could potentially merge the two.
>
> Unless you follow the installer, best practice and the Filesystem
>
2013/4/20 Jude DaShiell
> Sorry, wrong list for reply.
...though interesting :-)
Sorry, wrong list for reply.
On Fri, 19 Apr 2013, Raffaele Morelli wrote:
> 2013/4/19 Darac Marjal
>
> >
> > That seems correct. Device nodes don't tend to take up any space. Now
> > try it again on the filesystem (like I showed you).
> >
> >
> Ok, here follows the "relevant" ouput.
> Apart from
It's probable that the dental work that was done has misaligned several
teeth which would account for the pain spreading to places it had not
been before, everything either is connected or connects in the mouth by
way of contacts when we eat which is why I suggested a follow up visit
to find wh
> > Don't believe opinion as fact just because it's on a server hosted
> > by freedesktop.org. Rusty Russel and the FHS is a more
> > authoritative (and correct) source, I suggest you read it.
>
> I never split up / and /usr for the last century or so and they are
> all working fine.
Wow, your
Am Freitag, 19. April 2013 schrieb Kevin Chadwick:
> > > Hi,
> > >
> > > I have a debian wheezy server up, I would like to free some space
> > > on rootfs but can't guess how...
> > > Here follows the filesystem, any hints?
> > >
&g
Am Freitag, 19. April 2013 schrieb Karl E. Jorgensen:
> Hi
>
> On Fri, Apr 19, 2013 at 12:32:45PM +0100, Raffaele Morelli wrote:
> > Hi,
> >
> > I have a debian wheezy server up, I would like to free some space on
> > rootfs but can't guess how...
>
> > Hi,
> >
> > I have a debian wheezy server up, I would like to free some space
> > on rootfs but can't guess how...
> > Here follows the filesystem, any hints?
> >
> > regrds
> > /r
> >
> > debian:~# df -h
> >
Raffaele Morelli wrote:
> Eduardo M KALINOWSKI wrote:
> > You seem to be using lvm. Can't you shrink another partition to grow root?
>
> Yes I could... but I have never managed lvm and this is a production
> server..
You are using LVM. You have plenty of space. You just need to move
it around a
On Fri, Apr 19, 2013 at 01:32:45PM +0200, Raffaele Morelli wrote:
> Hi,
>
> I have a debian wheezy server up, I would like to free some space on rootfs
> but can't guess how...
> Here follows the filesystem, any hints?
>
> regrds
> /r
>
> debian:~# df -h
&
On Fri, Apr 19, 2013 at 10:53:33AM -0600, Bob Proulx wrote:
> Karl E. Jorgensen wrote:
> > Raffaele Morelli wrote:
> > > rootfs 322M 213M 93M 70% /
> > > /dev/mapper/debian-root 322M 213M 93M 70% /
> > > tmpfs 368
Karl E. Jorgensen wrote:
> Raffaele Morelli wrote:
> > rootfs 322M 213M 93M 70% /
> > /dev/mapper/debian-root 322M 213M 93M 70% /
> > tmpfs 368M 11M339M 3% /tmp
> > /dev/mapper/debian-tmp 368M 11M339M 3
basti wrote:
> You can also use "ncdu".
> Man Page says:
>
> ncdu (NCurses Disk Usage) is a curses-based version of the well-known
> 'du', and provides a fast way to see what directories are using your
> disk space.
Cool! I hadn't seen that before. Checking it out now.
I have been recommending
> I haven't actually looked at your layout but copy something like /opt
> to /usr (where it should be anyway in my opinion) and bind mount it.
Sorry move it!
--
___
'Write programs that do one thing and do it well. Write progra
> >> Ok, here follows the "relevant" ouput.
> >> Apart from spf13 vim environment, that I can remove for root user, I guess
> >> my only choice would be a pruned custom kernel... am I wrong?
> >>
> >
> > You seem to be using lvm. Can't you shrink another partition to grow root?
>
>
> Yes I co
2013/4/19 Karl E. Jorgensen
> Hi
>
> On Fri, Apr 19, 2013 at 12:32:45PM +0100, Raffaele Morelli wrote:
> > Hi,
> >
> > I have a debian wheezy server up, I would like to free some space on
> rootfs but
> > can't guess how...
> > Here follows t
Hi
On Fri, Apr 19, 2013 at 12:32:45PM +0100, Raffaele Morelli wrote:
> Hi,
>
> I have a debian wheezy server up, I would like to free some space on rootfs
> but
> can't guess how...
> Here follows the filesystem, any hints?
>
> regrds
> /r
>
> debian:
2013/4/19 Eduardo M KALINOWSKI
> On Sex, 19 Abr 2013, Raffaele Morelli wrote:
>
>> Ok, here follows the "relevant" ouput.
>> Apart from spf13 vim environment, that I can remove for root user, I guess
>> my only choice would be a pruned custom kernel... am I wrong?
>>
>
> You seem to be using lvm.
Hello,
Raffaele Morelli a écrit :
>
> I have a debian wheezy server up, I would like to free some space on rootfs
> but can't guess how...
> Here follows the filesystem, any hints?
>
> debian:~# df -h
> File system Dim. Usati Dispon. Uso% Montato su
>
On Sex, 19 Abr 2013, Raffaele Morelli wrote:
Ok, here follows the "relevant" ouput.
Apart from spf13 vim environment, that I can remove for root user, I guess
my only choice would be a pruned custom kernel... am I wrong?
You seem to be using lvm. Can't you shrink another partition to grow root?
2013/4/19 Darac Marjal
>
> That seems correct. Device nodes don't tend to take up any space. Now
> try it again on the filesystem (like I showed you).
>
>
Ok, here follows the "relevant" ouput.
Apart from spf13 vim environment, that I can remove for root user, I guess
my only choice would be a pr
On 04/19/2013 01:32 PM, Raffaele Morelli wrote:
> Hi,
>
> I have a debian wheezy server up, I would like to free some space on
> rootfs but can't guess how...
> Here follows the filesystem, any hints?
>
> regrds
> /r
>
> debian:~# df -h
> File system
>> On Fri, Apr 19, 2013 at 01:32:45PM +0200, Raffaele Morelli wrote:
>>>Hi,
>>>I have a debian wheezy server up, I would like to free some space on
>>>rootfs but can't guess how...
>>>Here follows the filesystem, any hints?
>> You ha
uld like to free some space
> on
> > � �rootfs but can't guess how...
> > � �Here follows the filesystem, any hints?
>
> You have 213Mb in your root file system, that seems fairly small to me
> (especially as you have 477Gb kicking around
2013/4/19 Darac Marjal
> On Fri, Apr 19, 2013 at 01:32:45PM +0200, Raffaele Morelli wrote:
> >Hi,
> >I have a debian wheezy server up, I would like to free some space on
> >rootfs but can't guess how...
> >Here follows the filesystem, any hints?
On Fri, Apr 19, 2013 at 01:32:45PM +0200, Raffaele Morelli wrote:
>Hi,
>I have a debian wheezy server up, I would like to free some space on
> rootfs but can't guess how...
>Here follows the filesystem, any hints?
You have 213Mb in your root file system, that seem
Hi,
I have a debian wheezy server up, I would like to free some space on rootfs
but can't guess how...
Here follows the filesystem, any hints?
regrds
/r
debian:~# df -h
File system Dim. Usati Dispon. Uso% Montato su
rootfs 322M 213M 93M 70% /
Sven Joachim wrote:
On 2012-06-09 16:07 +0200, Roman V.Leon. wrote:
Please give me a tip - is it normal that i see in 'df -h' output that
my rootfs is mounted twice ?:
Yes, that's normal. You did not see it in the past when /etc/mtab was a
regular file, but now /etc/mtab
On 09.06.2012 17:07, Roman V.Leon. wrote:
> Hello gents.
> Please give me a tip - is it normal that i see in 'df -h' output that my
> rootfs is mounted twice ?:
>
> $ df -h
>
> rootfs 97G 34G 59G 37% /
>
> /dev/disk/by-uuid/a863f3c2-ddaf-4c2
On 09.06.2012 18:49, Sven Joachim wrote:
On 2012-06-09 16:07 +0200, Roman V.Leon. wrote:
Please give me a tip - is it normal that i see in 'df -h' output that
my rootfs is mounted twice ?:
Yes, that's normal. You did not see it in the past when /etc/mtab was a
regular fil
On 2012-06-09 16:07 +0200, Roman V.Leon. wrote:
> Please give me a tip - is it normal that i see in 'df -h' output that
> my rootfs is mounted twice ?:
Yes, that's normal. You did not see it in the past when /etc/mtab was a
regular file, but now /etc/mtab is a symlink to /p
Hello gents.
Please give me a tip - is it normal that i see in 'df -h' output that my
rootfs is mounted twice ?:
$ df -h
....
rootfs 97G 34G 59G 37% /
/dev/disk/by-uuid/a863f3c2-ddaf-4c23-9d56-51245edbe394 97G 34G 59G
37% /
Thanks.
--
Cheers,
Roman V.Leo
> noatime,discard,data=ordered,errors=remount-ro 0 1
>
> rd@blackbox:~$ mount
> rootfs on / type rootfs (rw)
^^
This doesn't make sense. Could you try removing the quotes from the
UUID="" entry in fstab?
> The result of the t
Rainer Dorsch wrote the following on 11.05.2011 12:05
> Am Montag, 9. Mai 2011 schrieb Thilo Six:
>> Andrei Popescu wrote the following on 09.05.2011 09:18
>>
>>>> rd@blackbox:~$ mount|grep rootfs
>>>> rootfs on / type rootfs (rw)
>>>> rd@b
Am Montag, 9. Mai 2011 schrieb Thilo Six:
> Andrei Popescu wrote the following on 09.05.2011 09:18
>
> >> rd@blackbox:~$ mount|grep rootfs
> >> rootfs on / type rootfs (rw)
> >> rd@blackbox:~$
> >
> > I don't have any 'rootfs' in the
hich I think was not there before):
> >
> > findfs: Unable to resolve ...
> >
> > http://bokomoko.de/~rd/ext4-rootfs-uuid/IMG_6119.JPG
> >
> > for my root partition. The system boot without a problem though, and when
> > booted findfs works out ok:
>
Andrei Popescu wrote the following on 09.05.2011 09:18
>> rd@blackbox:~$ mount|grep rootfs
>> rootfs on / type rootfs (rw)
>> rd@blackbox:~$
>
> I don't have any 'rootfs' in the output of mount, instead I have this:
>
> /dev/sda6 on / type ext3 (
On Du, 08 mai 11, 23:23:52, Rainer Dorsch wrote:
>
> rd@blackbox:~$ mount|grep rootfs
> rootfs on / type rootfs (rw)
> rd@blackbox:~$
I don't have any 'rootfs' in the output of mount, instead I have this:
/dev/sda6 on / type ext3 (rw,noatime,errors=remount-ro,
(rw,noatime,discard,data=ordered)
> >
> > but not for root
> >
> > rootfs on / type rootfs (rw)
> >
> > Were the noatime, discard, and data options lost somewhere on the
> > way? Can I verify that they work?
>
> Quoting Ted Ts'o from
&
resolve ...
>
> http://bokomoko.de/~rd/ext4-rootfs-uuid/IMG_6119.JPG
>
> for my root partition. The system boot without a problem though, and when
> booted findfs works out ok:
>
> blackbox:~# findfs UUID="4a4eb948-2d2b-4188-96ae-76a3776ae69c"
> /dev/sdb1
> blackbox:~#
Hello Rainer,
On Sun, May 08, 2011 at 04:14:53PM +0200, Rainer Dorsch wrote:
> [...]
> When I now run the mount command, I get all options listed for /home
>
> /dev/sdc2 on /home type ext4 (rw,noatime,discard,data=ordered)
>
> but not for root
>
> rootfs on / type r
-55fe-49e5-97b7-0f6e7f63661a" /homeext4
noatime,discard,data=ordered 0 2
When I now run the mount command, I get all options listed for /home
/dev/sdc2 on /home type ext4 (rw,noatime,discard,data=ordered)
but not for root
rootfs on / ty
Hello,
I moved my root partition to a new SSD and used ext4 as filesystem. Everything
works well, except that I get an error message during boot (which I think was
not there before):
findfs: Unable to resolve ...
http://bokomoko.de/~rd/ext4-rootfs-uuid/IMG_6119.JPG
for my root partition. The
hi,
we want to use the security advantages from NFSv4 for our diskless
clients. I Build the initrams under Squeeze but the client won't boot,
if I tell Solaris10 to accept NFSv4 only :-/
I saw the bug #409271
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409271) for Lenny, but
why doesn't sup
I don't know: it just works. As long as you have the lvm2 package
installed
and the initrd package was created after the lvm2 package was installed,
it
should just work.
Hi Stefan,
After I changed root device to /dev/mapper/volume-root, Linux boots
successfully. And I didn't make anything
On Wed, May 09, 2007 at 09:23:52AM -0400, Stefan Monnier wrote:
> >> Try use /dev/mapper/volume-root instead.
> >> I'm not sure why, but I recently had a similar problem where using
> >> /dev/Debian/root didn't work but /dev/mapper/Debian-root did (even though
> >> once the boot is over, /dev/Debia
>> Try use /dev/mapper/volume-root instead.
>> I'm not sure why, but I recently had a similar problem where using
>> /dev/Debian/root didn't work but /dev/mapper/Debian-root did (even though
>> once the boot is over, /dev/Debian/root can be used just fine, it looks
>> like the alternate name is con
> I setup /boot as a seperate disk parition. The rest is for LVM.
> /dev/volume/root is OK when I use a rescue CDRom. And I re-build the
> initrd, adding all dm-* modules to the initrd. Any suggestion?
Try use /dev/mapper/volume-root instead.
I'm not sure why, but I recently had a similar pro
Try use /dev/mapper/volume-root instead.
I'm not sure why, but I recently had a similar problem where using
/dev/Debian/root didn't work but /dev/mapper/Debian-root did (even though
once the boot is over, /dev/Debian/root can be used just fine, it looks
like the alternate name is constructed lat
> I setup my rootfs as an LVM, the menu.lst of grub looks like this;
> title Debian GNU/Linux, kernel 2.6.18-4-386
> root(hd0,0)
> kernel /vmlinuz-2.6.18-4-686 root=/dev/volume/root ro
> initrd /my_init
> savedefault
> Error happens
Dear all,
I setup my rootfs as an LVM, the menu.lst of grub looks like this;
title Debian GNU/Linux, kernel 2.6.18-4-386
root(hd0,0)
kernel /vmlinuz-2.6.18-4-686 root=/dev/volume/root ro
initrd /my_init
savedefault
Error happens when the kernel tried to
> Lukas Ruf <[EMAIL PROTECTED]> [2004-01-02 12:16]:
>
> Dear all,
>
> when returning back to work after the Xmas-break, my root-file
> system was mounted read-only. However, I have no idea why this
> happened -- and problems fixing it. Any help would be greatly
> appreciated!
>
Thanks for all th
On Fri, 02 Jan 2004 12:26:36 +0100, Jan Minar wrote:
> On Fri, Jan 02, 2004 at 12:16:35PM +0100, Lukas Ruf wrote:
>> Dec 30 07:35:52 [kernel] EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc:
>> unable to read inode block - inode=972554, block=1966176
>> Dec 30 07:35:52 [kernel] Remounting fi
2 [kernel] EXT3-fs error (device
> ide0(3,2)): ext3_get_inode_loc: unable to read inode block -
> inode=972554, block=1966176 Dec 30 07:35:52 [kernel] Remounting
> filesystem read-only Dec 30 07:35:52 [kernel] EXT3-fs error (device
> ide0(3,2)) in start_transaction: Journal has aborted
&g
On Fri, Jan 02, 2004 at 12:16:35PM +0100, Lukas Ruf wrote:
> Dec 30 07:35:52 [kernel] EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc:
> unable to read inode block - inode=972554, block=1966176
> Dec 30 07:35:52 [kernel] Remounting filesystem read-only
This is probably what it should do: rem
start_transaction:
Journal has aborted
Trying to remount the rootfs rw yields
# mount -o remount,rw /
mount: block device /dev/hda2 is write-protected, mounting read-only
# uname -a
Linux komsys-pc-ruf 2.4.23 #1 Tue Dec 2 17:34:37 CET 2003 i686 GNU/Linux
# uptime
12:10:54 up 30 days, 17:58, 8 users, load
Heinrich Rebehn said:
> Hi,
>
> I have a problem with rpc.statd. We run our linux machines as diskless
> clients, they mount their root fs via nfs from a server. For security
> reasons i would like to export the root fs readonly. However, rpc.statd
> will not run. It exits without an error message
Hi,
I have a problem with rpc.statd. We run our linux machines as diskless clients,
they mount their root fs via nfs from a server. For security reasons i would
like to export the root fs readonly. However, rpc.statd will not run. It exits
without an error message, but reports
Sep 26 15:33:48 rp
Hi,
I have a problem with rpc.statd. We run our linux machines as diskless clients,
they mount their root fs via nfs from a server. For security reasons i would
like to export the root fs readonly. However, rpc.statd will not run. It exits
without an error message, but reports
Sep 26 15:33:48 rp
Hi,
I have a problem with rpc.statd. We run our linux machines as diskless clients,
they mount their root fs via nfs from a server. For security reasons i would
like to export the root fs readonly. However, rpc.statd will not run. It exits
without an error message, but reports
Sep 26 15:33:48 rp
Hi,
I am building a minimal rootfs that will loads as a large ramdisk when
booting some nodes on a clustered system. I'm basically pulling pieces by
hand from a working PowerPC potato system as each node is PowerPC-based.
I only have the need to allow serial login and networking (rshd et
cause rootfs is on /dev/sdf (in real life my room is a big black hole,
collection everything). When i switch off one or two hd's, and rootfs
become /dev/sdd1, all is working fine.
workaround: i have a old, working system on /dev/sda1. if i boot this, and
write lilo from there on /dev/sdf ,
97 matches
Mail list logo
