On 4/26/22 15:04, Charles Curley wrote:
On Mon, 25 Apr 2022 14:56:50 -0700 David Christensen wrote:
On 4/25/22 07:18, Charles Curley wrote:
On Sun, 24 Apr 2022 22:52:15 -0700 David Christensen wrote:
Rather than a Live Linux distribution for troubleshooting, I install
Debian onto a
Update. I had a friend with a power supply checker check the power
supply. The +12 volt line is running at 11.5v, barely within spec.
Fishy, but livable for the nonce.
I had been running Finnix as Debian wouldn't boot. I pulled all the
external USB lines except for a 3.5" external floppy disk
On 4/25/22 07:18, Charles Curley wrote:
On Sun, 24 Apr 2022 22:52:15 -0700
David Christensen wrote:
So, RAID 5 HDD's are sda, sdc, and sdd, and optical is sdb?
Optical is sr0.
Interesting. (Must be the SATA controller expansion card?)
sda is an SSD with all the system, /home, etc.
On Sun, 24 Apr 2022 22:47:50 -0700
David Christensen wrote:
> I will assume all three HDD's are the same make and model, per
> smartctl(8) report below.
Nope. Two WD Reds, as the report indicates, but not bought at the same
time so likely to be different in detail. One Seagate Ironwolf.
> >>
On Sun, 24 Apr 2022 22:52:15 -0700
David Christensen wrote:
> So, RAID 5 HDD's are sda, sdc, and sdd, and optical is sdb?
Optical is sr0. sda is an SSD with all the system, /home, etc. md0 is
mounted at /crc.
>
>
> You do have a backup of your Debian system configuration files and
> your
On 4/24/22 17:10, Charles Curley wrote:
On Sun, 24 Apr 2022 13:08:03 -0600
Charles Curley wrote:
I have three hard drives in a RAID 5 array.
RAID has not yet failed the errant drive. Just now, via ssh into finnix:
root@0:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [linear]
On 4/24/22 15:37, Charles Curley wrote:
On Sun, 24 Apr 2022 14:07:14 -0700
David Christensen wrote:
On 4/24/22 12:08, Charles Curley wrote:
I have three hard drives in a RAID 5 array.
What is the make and model of your motherboard?
ASUS H97M-E
I'd call that a multimedia desktop
On Sun, 24 Apr 2022 13:08:03 -0600
Charles Curley wrote:
> I have three hard drives in a RAID 5 array.
RAID has not yet failed the errant drive. Just now, via ssh into finnix:
root@0:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1]
[raid10]
On Sun, 24 Apr 2022 14:07:14 -0700
David Christensen wrote:
> On 4/24/22 12:08, Charles Curley wrote:
> > I have three hard drives in a RAID 5 array.
>
>
> What is the make and model of your motherboard? RAID HDD's?
ASUS H97M-E
>
>
> How is the motherboard connected to the HDD's?
SATA.
On 4/24/22 12:08, Charles Curley wrote:
I have three hard drives in a RAID 5 array. This morning my motherboard
went wonky and crashed. USB devices on the motherboard are acting up. I
cannot reboot to Debian. I can, however, boot to finnix 120. Using
that, I have fscked all partitions, including
Hello Charles
On Sun, Apr 24, 2022 at 01:08:03PM -0600, Charles Curley wrote:
> I have three hard drives in a RAID 5 array. This morning my motherboard
> went wonky and crashed. USB devices on the motherboard are acting up. I
> cannot reboot to Debian. I can, however, boot to finnix 120. Using
>
I have three hard drives in a RAID 5 array. This morning my motherboard
went wonky and crashed. USB devices on the motherboard are acting up. I
cannot reboot to Debian. I can, however, boot to finnix 120. Using
that, I have fscked all partitions, including the RAID array. I am
running checksums,
Thomas Schmitt wrote:
> But, as said previously, old PC-BIOS does not care for partitions.
> GRUB does. Normally it can handle partition tables if the necessary GRUB
> modules are loaded. For GPT: insmod part_gpt
Thank you Thomas, I now understand this use case.
Hi,
deloptes wrote:
> I am not sure if grub can boot off GPT without UEFI.
That's the use case of the GRUB BIOS boot partition with Type GUID
21686148-6449-6e6f-744e656564454649.
See "GPT" section in
https://www.gnu.org/software/grub/manual/grub/html_node/BIOS-installation.html
It is
David Wright wrote:
> The OP has described a problem with a ~2006 laptop which, as far as
> I can understand it, involves GPT devices (as well as MBR ones),
> and *BIOS* booting.
>
I am not sure if grub can boot off GPT without UEFI. I honestly never
thought of this. For me both go hand in
On Fri 03 Jul 2020 at 21:04:44 (+0200), deloptes wrote:
> Matthew Campbell wrote:
>
> > Nothing seems good enough. Do you want a picture? I'm not typing all of
> > that in on my tablet.
Some people post pictures to appropriate sites when it's not possible
to copy the text (eg, in the BIOS,
Matthew Campbell wrote:
> Nothing seems good enough. Do you want a picture? I'm not typing all of
> that in on my tablet. Let's just let it go. I'm working on understanding
> grub. I'm going to boot from a USB flash drive.
When I want to boot from the USB drive with GPT configured I first make
drive.
>> >> >> […]
>> >> >> The hard drive, /dev/sdb, always responds faster than the USB flash
>> >> >> drives so it is always /dev/sdb.
>> >> >>
>> >> >> Now Debian Linux is running on my new hard drive using
t; >> The hard drive, /dev/sdb, always responds faster than the USB flash
> >> >> drives so it is always /dev/sdb.
> >> >>
> >> >> Now Debian Linux is running on my new hard drive using /dev/sdb1 as the
> >> >> root partition.
> > […]
> &
gt; /dev/sdb is the new 4 TB Toshiba External USB 3.0 hard drive.
> >> […]
> >> The hard drive, /dev/sdb, always responds faster than the USB flash drives
> >> so it is always /dev/sdb.
> >>
> >> Now Debian Linux is running on my new hard drive using
On 2020-07-02 01:12, Matthew Campbell wrote:
The 4 TB hard drive uses a GPT type partition table, not an MBR type table,
which is why the computer can't see it. It can't make sense of GPT tables. It
is a Toshiba Satellite laptop. Satellite P105-S6187, model number
PSPAAU-01L00S. I just
debian-user:
This message was only sent to the OP by mistake.
David
On 2020-06-14 18:16, Matthew Campbell wrote:
I'm kind of stuck using the ProtonMail app on my tablet.
The message you replied to was properly indented. Other than
top-posting and the "name=Mathew..." field, your
Hi,
Matthew Campbell wrote:
> The 4 TB hard drive uses a GPT type partition table, not an MBR type table,
> which is why the computer can't see it. It can't make sense of GPT tables.
Not knowing what's actually causing your problem, i have to doubt this
theory.
If the machine's firmware has no
ly partition. Both use a DOS MBR partition table
> that sets the first partition as active/bootable.
>
> The hard drive, /dev/sdb, always responds faster than the USB flash drives so
> it is always /dev/sdb.
>
> Now Debian Linux is running on my new hard drive using /dev/sd
Matthew Campbell wrote:
> My computer cannot see a GPT partition table. I've had to use a dos MBR
> partition table on my USB flash drives. I mount my file systems as
> read-only first so I can check them after booting before remounting them
> read-write.
I am sorry to say it, but you are not
Matthew Campbell wrote:
> Now Debian Linux is running on my new hard drive using /dev/sdb1 as the
> root partition. I need to set up a separate USB flash drive to do all of
> this by default so I don't have to do all of this work every time the
> computer boots up. I also need to i
On Lu, 15 iun 20, 01:16:16, Matthew Campbell wrote:
> I'm kind of stuck using the ProtonMail app on my tablet.
The ProtonMail web app has the option to send plain text only.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description: PGP signature
Matthew Campbell wrote:
> I'm kind of stuck using the ProtonMail app on my tablet.
>
> I would like to be able to disconnect the internal hard drive in the
> laptop. I'll need to turn off the laptop before moving it so I can look
> for that model number. I hope to get to that soon. I can't do
Man, that text really got screwed up.
name=Matthew%20Campbell=trenix25%40pm.me
Original Message
On Jun 14, 2020, 6:20 PM, Matthew Campbell wrote:
> The internal hard drive was visible to Grub, as was the other external USB
> hard drive, a Western Digital drive. Having an
The internal hard drive was visible to Grub, as was the other external USB hard
drive, a Western Digital drive. Having an external hard drive connected with
USB is not the problem. Grub was on /dev/sda and used to boot the Western
Digital drive just fine, until Grub was reconfigured to boot the
The Wanderer wrote:
> That's *probably* not a problem relative to the fact that this is a USB3
> external hard drive, but it certainly can't be helping.
I am not sure, but I think there were 686 BIOSes that could not see 4TB
disks
On 2020-06-13 at 18:44, David Christensen wrote:
[that on 2020-06-13 at 15:38, Matthew Campbell wrote:]
>> /dev/sda: Toshiba MK1234GS, 111.8 GiB (Internal)
>> /dev/sr0: MATSHITADVD-RAM UJ-850S , DVD R/W (Internal IDE)
>> /dev/sdb: Toshiba External USB 3.0 3.7 TiB
>> /dev/sdc: PNY 32 USB 2.0 FD
Matthew Campell -- Whatever client software you are using for e-mail, it
is not indenting previous message content when you reply. This makes it
very hard to follow the conversation, especially when there are replies
to replies, to replies, to replies, etc.. Rather than trying to fix the
of your USB flash drive?
Answered above.
Are you using a USB 2.0 port or a USB 3.0 port?
All USB ports are USB 2.0.
> Grub has /dev/sdb1 listed as an option, but says the disk does not exist and
> to load the kernel first, which of course is on the new hard drive partition
> /dev/sdb1
in too. The flash drive is
> _really_ slow.
>
> Grub has /dev/sdb1 listed as an option, but says the disk does not
> exist and to load the kernel first, which of course is on the new hard
> drive partition /dev/sdb1 which I can access just fine after starting
> the kernel. The catch is t
gt; exist and to load the kernel first, which of course is on the new hard
> drive partition /dev/sdb1 which I can access just fine after starting
> the kernel. The catch is that I have to boot the flash drive /dev/sdc1
> to do so thus making it the root filesystem.
>
> 1) How can I he
w.
>
> Grub has /dev/sdb1 listed as an option, but says the disk does not exist and
> to load the kernel first, which of course is on the new hard drive partition
> /dev/sdb1 which I can access just fine after starting the kernel. The catch
> is that I have to boot the flash dri
and model of your USB flash drive?
Are you using a USB 2.0 port or a USB 3.0 port?
Grub has /dev/sdb1 listed as an option, but says the disk does not exist and to
load the kernel first, which of course is on the new hard drive partition
/dev/sdb1 which I can access just fine after starting
Matthew Campbell wrote:
> I booted the Debian netinst disc and installed Linux on /dev/sdb1 as the
> root partition. My computer is old. The system BIOS does not see this hard
> drive, nor does Grub, but the Linux kernel does. I'm running the
> 4.19.0-9-686-pae kernel, #1 SMP Debian 4.19.118-2
to install Linux on a 32 GB USB flash drive just to get my
computer to boot. Now I can boot Windows again too. The flash drive is
_really_ slow.
Grub has /dev/sdb1 listed as an option, but says the disk does not
exist and to load the kernel first, which of course is on the new hard
drive
Matthew Campbell wrote:
> I hope I don't create a fight with this.
It's really much more rare than your recent experience would
suggest.
> I booted the Debian netinst disc and installed Linux on /dev/sdb1 as the root
> partition. My computer is old. The system BIOS does not see this hard
On Mi, 12 feb 20, 09:08:26, Greg Wooledge wrote:
> On Wed, Feb 12, 2020 at 03:01:52PM +0100, Klaus Singvogel wrote:
> > kaye n wrote:
> > > *For the future, you could paste the (relevant part from) the output of
> > > 'parted -l'.*
> > > Just curious, never encountered that command before.
> > >
Le mercredi 12 février 2020 15:10:04 UTC+1, Felix Miata a écrit :
[...]
> If you present to it what it wants, it makes no partitioning changes. If you
> don't, it will divide up what you do give it, as long as what you do give it
> can meet its minimum requirement.
[...]
I am sure now that you
On Wed, Feb 12, 2020 at 03:01:52PM +0100, Klaus Singvogel wrote:
> kaye n wrote:
> > *For the future, you could paste the (relevant part from) the output of
> > 'parted -l'.*
> > Just curious, never encountered that command before.
> > kaye@laptop:~$ parted -l
> > bash: parted: command not found
>
didier.gau...@gmail.com composed on 2020-02-12 01:57 (UTC-0800):
>> Windows will automatically create a partition out of the 50GB partition
>> that I made for it?
> I may be wrong, but I do not think the Microsoft Windows installer will do
> so: it will probably try to create other partitions
kaye n wrote:
> *The (U)EFI partition seems far to small, I think mine was about 200 MB
> originaly and I extended it to 700 MB, so I was able to make UEFI updates.
>
> *Are UEFI updates necessary? What's the smallest allowable size I can
> make for UEFI partition? Or is that not a wise thing to
Please use a correct quoting method: it is difficult to differenciate your
discourse from others when when replying to you :-)
Le mercredi 12 février 2020 09:00:05 UTC+1, kaye n a écrit :
> Are UEFI updates necessary? What's the smallest allowable size I can make
> for UEFI partition? Or is
On Mi, 12 feb 20, 15:53:37, kaye n wrote:
>
> *For the future, you could paste the (relevant part from) the output of
> 'parted -l'.*
> Just curious, never encountered that command before.
> kaye@laptop:~$ parted -l
> bash: parted: command not found
It's in package 'parted' and must be run as
*The (U)EFI partition seems far to small, I think mine was about 200 MB
originaly and I extended it to 700 MB, so I was able to make UEFI updates.*Are
UEFI updates necessary? What's the smallest allowable size I can make for
UEFI partition? Or is that not a wise thing to do?
*PXE Boot is booting
On Ma, 11 feb 20, 21:07:05, kaye n wrote:
> Thank you guys for telling me the email got lost. I'll just describe it.
>
> The partition table is GPT.
>
> Imagine you're looking at the graphical presentation of my hdd in GParted.
>
> Starting from the left:
For the future, you could paste the
kaye n composed on 2020-02-11 21:07 (UTC+0800):
> The partition table is GPT.
Created how? Did you do it yourself prior to beginning installation of Debian?
> Imagine you're looking at the graphical presentation of my hdd in GParted.
> Starting from the left:
> 858GB NTFS partition (intended
Thanks.
Two thoughts about your failures:
The (U)EFI partition seems far to small, I think mine was about 200 MB
originaly and I extended it to 700 MB, so I was able to make UEFI updates.
PXE Boot is booting over network (TFTP) and not want you want. You can
configure your boot device in the
Thank you guys for telling me the email got lost. I'll just describe it.
The partition table is GPT.
Imagine you're looking at the graphical presentation of my hdd in GParted.
Starting from the left:
858GB NTFS partition (intended for storing all kinds of data)
then
20GB ext4 partition,
Felix Miata wrote:
> kaye n composed on 2020-02-11 17:23 (UTC+0800):
>
> > No one?
>
> Your OP seems to have gotten lost in the ether. I don't see it on
> https://lists.debian.org/debian-user/2020/02/threads.html and don't remember
> seeing it arrive among any other debian-user email. I do see
kaye n composed on 2020-02-11 17:23 (UTC+0800):
> No one?
Your OP seems to have gotten lost in the ether. I don't see it on
https://lists.debian.org/debian-user/2020/02/threads.html and don't remember
seeing it arrive among any other debian-user email. I do see there another
original post from
No one?
On Thu, Feb 6, 2020 at 6:35 PM kaye n wrote:
> Hello Friends!
>
> Are my attached files too big? If so, let me know, I'll make them smaller
> next time.
>
> debian_01.jpg shows how I formatted the brand new hard drive. My goal is
> to install Debian first, then
On Sat 16 Mar 2019 at 10:49:19 (+0100), Pascal Hambourg wrote:
> Le 11/03/2019 à 19:46, David Wright a écrit :
> > On Sat 09 Mar 2019 at 20:31:36 (+0100), Pascal Hambourg wrote:
> > >
> > > I did not mean using UDF on opticals discs but on regular drives, just
> > > as any other general purpose
Le 11/03/2019 à 19:46, David Wright a écrit :
On Sat 09 Mar 2019 at 20:31:36 (+0100), Pascal Hambourg wrote:
I did not mean using UDF on opticals discs but on regular drives, just
as any other general purpose filesystem. I once considered using it
for file sharing between Windows and Linux
On Sat 09 Mar 2019 at 20:31:36 (+0100), Pascal Hambourg wrote:
> Le 08/03/2019 à 04:15, David Wright a écrit :
> > On Thu 07 Mar 2019 at 23:12:29 (+0100), Pascal Hambourg wrote:
> > > Le 07/03/2019 à 20:23, David Wright a écrit :
> > > >
> > > > A filesystem
> > > > that has a label, has that
Le 08/03/2019 à 04:15, David Wright a écrit :
On Thu 07 Mar 2019 at 23:12:29 (+0100), Pascal Hambourg wrote:
Le 07/03/2019 à 20:23, David Wright a écrit :
A filesystem
that has a label, has that label regardless of any OS.
Have you ever used UDF ?
Yes. As far as my experience goes,
Please don't oversnip. This subthread was about labels (aka LABELs).
On Fri 08 Mar 2019 at 08:20:40 (-0500), Greg Wooledge wrote:
> On Thu, Mar 07, 2019 at 09:15:51PM -0600, David Wright wrote:
> > On Thu 07 Mar 2019 at 23:12:29 (+0100), Pascal Hambourg wrote:
> > > Le 07/03/2019 à 20:23, David
On Thu, Mar 07, 2019 at 09:15:51PM -0600, David Wright wrote:
> Yes. As far as my experience goes, there's not a lot of difference.
> I've had no occasion to *write* DVDs on a computer system, so I can
> only speak of reading them.
For writing, fstab and mount are not involved in any way
David Wright wrote:
> I would not expect to find the characters
> /dev/disk/by-label/ anywhere in the partition.
>
> That string belongs to the linux system, not to the card.
>
> That's what I meant by "actually belongs to the filesystems".
OK, that's clear and I understand.
>> I'm not
On Thu 07 Mar 2019 at 23:12:29 (+0100), Pascal Hambourg wrote:
> Le 07/03/2019 à 20:23, David Wright a écrit :
> >
> > A filesystem
> > that has a label, has that label regardless of any OS.
>
> Have you ever used UDF ?
Yes. As far as my experience goes, there's not a lot of difference.
I've
On Thu 07 Mar 2019 at 13:49:42 (-0700), Cousin Stanley wrote:
> David Wright wrote:
>
> > I prefer to populate fstab with canonical information
> > that actually belongs to the filesystems that are to be mounted.
>
> I don't understand what you're saying here.
>
> Does a disk label not
Michael Stone wrote:
> On Thu, Mar 07, 2019 at 01:49:42PM -0700, Cousin Stanley wrote:
>>David Wright wrote:
>>> All that stuff in /dev/disk/ is just an ephemeral
>>> bunch of convenient symbolic links, presumably conjured
>>> up by udev or somesuch, if not the linux kernel
>>
>> But are they
Le 07/03/2019 à 20:23, David Wright a écrit :
A filesystem
that has a label, has that label regardless of any OS.
Have you ever used UDF ? It has a set of identifiers, and I observed
that Windows and blkid did not use the same identifier as the label.
On Thu, Mar 07, 2019 at 01:49:42PM -0700, Cousin Stanley wrote:
David Wright wrote:
All that stuff in /dev/disk/ is just an ephemeral
bunch of convenient symbolic links, presumably conjured
up by udev or somesuch, if not the linux kernel
But are they not accurate after boot
for particular
David Wright wrote:
> I prefer to populate fstab with canonical information
> that actually belongs to the filesystems that are to be mounted.
I don't understand what you're saying here.
Does a disk label not belong to a filesystem
that is to be mounted ?
> A filesystem that has a
On Thu 07 Mar 2019 at 09:59:43 (-0700), Cousin Stanley wrote:
> Michael Stone wrote:
> > On Thu, Mar 07, 2019 at 07:11:36AM -0700, Cousin Stanley wrote:
> >>Stephen P. Molnar wrote:
> >>>
> >>> and my fstab is:
> >>>
> >>> # /etc/fstab: static file system information.
> >>>
> >>
> >>
On Thu, Mar 07, 2019 at 09:59:43AM -0700, Cousin Stanley wrote:
Michael Stone wrote:
On Thu, Mar 07, 2019 at 07:11:36AM -0700, Cousin Stanley wrote:
Stephen P. Molnar wrote:
and my fstab is:
# /etc/fstab: static file system information.
I've found that labeling my disk
Michael Stone wrote:
> On Thu, Mar 07, 2019 at 07:11:36AM -0700, Cousin Stanley wrote:
>>Stephen P. Molnar wrote:
>>
>>>
>>> and my fstab is:
>>>
>>> # /etc/fstab: static file system information.
>>>
>>
>> I've found that labeling my disk partitions
>> and using
Cousin Stanley composed on 2019-03-07 07:11 (UTC-0700):
> To label the disk partitions check the man pages
> for the following labeling options
>
>$ ls -1 /sbin | grep label
>dosfslabel
>e2label
>exfatlabel
>fatlabel
>ntfslabel
>swaplabel
> The e2label
On Thu, Mar 07, 2019 at 07:11:36AM -0700, Cousin Stanley wrote:
Stephen P. Molnar wrote:
and my fstab is:
# /etc/fstab: static file system information.
I've found that labeling my disk partitions
and using /dev/disk/by-label/xyzzy lines
in the /etc/fstab file seems to be
Stephen P. Molnar wrote:
>
> and my fstab is:
>
> # /etc/fstab: static file system information.
>
I've found that labeling my disk partitions
and using /dev/disk/by-label/xyzzy lines
in the /etc/fstab file seems to be much easier
for my own small brain to comprehend.
I would beg the group's indulgence again, as I want to be sure I get
this correctly.
I think this is what I want as the fstab:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust
Le 05/03/2019 à 15:17, Stephen P. Molnar a écrit :
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 457.9G 0 part /
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 7.9G 0 part [SWAP]
sdb 8:16 0 1.8T 0 disk
├─sdb1 8:17 0 1.8T
On 03/01/2019 01:56 PM, David Wright wrote:
On Fri 01 Mar 2019 at 08:46:30 (-0500), Stephen P. Molnar wrote:
I am sure that you will castigate men for two things:
1. Top posting
2. Not replying to debian-users
However, I wanted to keep my reply private
in the hope of not starting a flame
Hi.
On Fri, Mar 01, 2019 at 12:49:11PM -0500, Stefan Monnier wrote:
> >>nofail is intended for removable drives that could be missing on boot,
> >>such as Thinkpad ultrabay drives/CF or SD cards.
> > It is also, as he said, useful if you don't want a failure of
> > a non-essential disk to
>>nofail is intended for removable drives that could be missing on boot,
>>such as Thinkpad ultrabay drives/CF or SD cards.
> It is also, as he said, useful if you don't want a failure of
> a non-essential disk to make the system drop to single user on boot.
Yup. `nofail` corresponds to the
On Fri 01 Mar 2019 at 12:00:06 (-0500), Greg Wooledge wrote:
> On Fri, Mar 01, 2019 at 10:52:00AM -0600, David Wright wrote:
> > On Fri 01 Mar 2019 at 01:30:47 (-0500), Cindy-Sue Causey wrote:
> > > That's what I'd been thinking, too. Because of your question, I just
> > > tried a search for...
>
On Fri 01 Mar 2019 at 07:30:15 (+), Dekks Herton wrote:
> David Wright writes:
> > On Thu 28 Feb 2019 at 15:45:47 (-0500), Stephen P. Molnar wrote:
> >> # /etc/fstab: static file system information.
> >> #
> >> # Use 'blkid' to print the universally unique identifier for a
> >> # device;
On Fri, Mar 01, 2019 at 10:52:00AM -0600, David Wright wrote:
> On Fri 01 Mar 2019 at 01:30:47 (-0500), Cindy-Sue Causey wrote:
> > That's what I'd been thinking, too. Because of your question, I just
> > tried a search for...
> >
> > "defaults,rw" /etc/fstab
>
> You've really limited what can
On Fri 01 Mar 2019 at 02:51:33 (-0500), Felix Miata wrote:
> Cindy-Sue Causey composed on 2019-03-01 01:30 (UTC-0500):
> > Felix Miata wrote:
> >> David Wright composed on 2019-02-28 20:26 (UTC-0600):
> >>> I always add an explicit rw or ro under options, along with defaults.
>
> >> English can
On Fri 01 Mar 2019 at 01:30:47 (-0500), Cindy-Sue Causey wrote:
> On 2/28/19, Felix Miata wrote:
> > David Wright composed on 2019-02-28 20:26 (UTC-0600):
> >
> >> I always add an explicit rw or ro under options, along with defaults.
> >
> > English can be tricky. Please clarify. AIUI, the string
On Fri, Mar 01, 2019 at 07:30:15AM +, Dekks Herton wrote:
David Wright writes:
I always add an explicit rw or ro under options, along with defaults.
With systemd, I add nofail to any filesystems that aren't vital for
the system to run, which means the system will still boot fully
without
Cindy-Sue Causey composed on 2019-03-01 01:30 (UTC-0500):
> Felix Miata wrote:
>> David Wright composed on 2019-02-28 20:26 (UTC-0600):
>>> I always add an explicit rw or ro under options, along with defaults.
>> English can be tricky. Please clarify. AIUI, the string "defaults" is a
>>
David Wright writes:
> On Thu 28 Feb 2019 at 15:45:47 (-0500), Stephen P. Molnar wrote:
>> I am running Stretch and after much trial and tribulation, and at
>> times abject horror, I have succeeded in installing a new SSD.
>>
>> My drive structure is:
>>
>> comp@AbNormal:~$ lsblk
>> NAME
On 2/28/19, Felix Miata wrote:
> David Wright composed on 2019-02-28 20:26 (UTC-0600):
>
>> I always add an explicit rw or ro under options, along with defaults.
>
> English can be tricky. Please clarify. AIUI, the string "defaults" is a
> placeholder, unnecessary if
> any other option is
David Wright composed on 2019-02-28 20:26 (UTC-0600):
> I always add an explicit rw or ro under options, along with defaults.
English can be tricky. Please clarify. AIUI, the string "defaults" is a
placeholder, unnecessary if
any other option is specified. Man mount doesn't make it clear to me.
On Thu 28 Feb 2019 at 15:45:47 (-0500), Stephen P. Molnar wrote:
> I am running Stretch and after much trial and tribulation, and at
> times abject horror, I have succeeded in installing a new SSD.
>
> My drive structure is:
>
> comp@AbNormal:~$ lsblk
> NAME MAJ:MIN RM SIZE RO TYPE
"Stephen P. Molnar" writes:
> I am running Stretch and after much trial and tribulation, and at times
> abject horror, I have succeeded in installing a new SSD.
>
> My drive structure is:
>
> comp@AbNormal:~$ lsblk
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:00 465.8G 0 disk
I am running Stretch and after much trial and tribulation, and at times
abject horror, I have succeeded in installing a new SSD.
My drive structure is:
comp@AbNormal:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 465.8G 0 disk
├─sda1 8:10 457.9G 0 part /
├─sda2
I have made a copy of the / file system from the boot
drive on a Debian Squeeze system to a new flash drive as the
original drive is about 13 years old, works fine, but I don't
want to push my luck too far. I used fdisk to format the new
drive, made Partition 1 bootable and then used rsync
I have made a copy of the / file system from the boot
drive on a Debian Squeeze system to a new flash drive as the
original drive is about 13 years old, works fine, but I don't
want to push my luck too far. I used fdisk to format the new
drive, made Partition 1 bootable and then used rsync
Very sorry for the duplicate posting. It looked like the first
attempt bounced so I re-sent it and both worked.
Martin
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
On 26/04/12 10:02 AM, Martin McCormick wrote:
I have made a copy of the / file system from the boot
drive on a Debian Squeeze system to a new flash drive as the
original drive is about 13 years old, works fine, but I don't
want to push my luck too far. I used fdisk to format the new
Gary Dale writes:
Personally, I'd just dd the entire old disk to the new one. Then use
gparted (from a live distro) to resize your partitions.
Actually, that is probably the best solution. I did that on a
previous disk several months ago and it worked fine
However, since you have already done
Le 15036ième jour après Epoch,
Kjetil brinchmann Halvorsen écrivait:
I have a new usb hard drive of the specs in the subject line. On
plugging it in it shows on the desktop,
but on clicking it nothing happens. Anybody have experience getting
this to work on debian
(squeeze)?
I've exactly
I should add that the package says it has usb 3.0
On Thu, Mar 3, 2011 at 17:27, Kjetil brinchmann Halvorsen
kjetil1...@gmail.com wrote:
I have a new usb hard drive of the specs in the subject line. On
plugging it in it shows on the desktop,
but on clicking it nothing happens. Anybody have
1 - 100 of 170 matches
Mail list logo
